Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
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/bug
@Ben
Thanks!
Patching and compiling the kernel is out of my league. I prefer the
user-friendly and "foolproof" way through the Kernel Update Utility for
Ubuntu (UKUU), mentioned above. Afaik, I can't edit the patch_realtek.c
file when doing so with UKUU.
Do you know if it's already planned to me
According to my tests GDM works as expected - checking groups the user
belongs to on different terminal emulators (e.g. xterm) proves that the
/etc/security/group.conf groups are correctly applied.
The problem in this case affects gnome-terminal alone (and the problem
is present also if using e.g.
** Also affects: language-pack-zh (Ubuntu)
Importance: Undecided
Status: New
** Package changed: language-pack-zh (Ubuntu) => language-pack-zh-hans
(Ubuntu)
** Also affects: ubuntu-translations
Importance: Undecided
Status: New
--
You received this bug notification because y
** Merge proposal linked:
https://code.launchpad.net/~osomon/network-manager/+git/network-manager/+merge/361051
--
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/175
** Changed in: systemd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1762391
Title:
pam_group.so is not evaluated by gnome-terminal
Status
** Changed in: linux (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 upower in Ubuntu.
https://bugs.launchpad.net/bugs/1745032
Title:
AC adapter status not detected on Asu
that's not an issue in recent versions
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu.
https://bugs.launchpad.ne
Last time I had the problem was dec 10 20:08 and I was using Ubuntu 19.04 with
kernel 4.20rc5 and network-manager version 1.12.4.
Since then I have not had the problem but I used kernel 4.20rc6 and 4.20rc7
also network-manager has changed to 1.12.6-0ubuntu2 and firefox has been
updated too.
If
** Branch linked: lp:~silhusk/software-properties/lp1656100-remove-
signing-keys
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1656100
Title:
Unable to remove
** Attachment removed: "printer.png"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721223/+attachment/5223123/+files/printer.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.lau
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/i
** Changed in: mesa
Status: Confirmed => Unknown
--
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/1753776
Title:
Graphics corruption just before login animation to Xorg
** Tags removed: rls-bb-incoming
** Tags added: rls-bb-notifixing
** Tags removed: rls-bb-notifixing
** Tags added: rls-bb-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.l
Public bug reported:
The screen appears to freeze, with possible SSH access from another machine
during the first minutes. After that, the system totally freezes, with not even
ethernet connection anymore.
Only hard reboot helps to solve the issue, with normal functionality afterwards.
It occurs
** Changed in: apt (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1806076
Title:
unattended-upgrade --help raises
The log file /var/log/apport.log might be helpful in sorting out why an
incomplete core was written. Could you please add it as an attachment?
** Changed in: apport (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Trace
** Attachment added: "trace at forced coredump"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1797882/+attachment/5223254/+files/wayland_stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in U
Without solving this problem, wayland cannot be used after logon, when
using dual monitor. The sesssion stops very easy and often. Work is
lost; you have to logon again. E.g. the simple switching between 2
overlapping windows causes the end of the session.
I changed src/mesa/drivers/dri/i915/intel
The issue looks like it could be what is fixed by
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/34ca1680
(the change is included in 1.10.8 which is currently not yet in bionic
but being SRUed)
--
You received this bug notification because you are a member of Ubuntu
Touch see
The issue looks like it could be what is fixed by
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/34ca1680
(the change is included in 1.10.8 which is currently not yet in bionic
but being SRUed)
--
You received this bug notification because you are a member of Ubuntu
Touch see
I still get this error in Cosmic on a Dell M6500.
The M6500 does not have a keyboard RFKILL shortcut - in only has a
physical switch. That switch correctly enables/disables WiFi.
Is this the same bug?
Dec 18 09:04:28 localhost kernel: [ 2706.037523] dell_wmi: Unknown key with
type 0x0011 and co
I'm experiencing same bug on elementary OS 5.0. It really driving me nuts.
Added initial bounty on this.
https://www.bountysource.com/issues/63898369-slow-keyboard-layouts-switch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thank you for your bug report. What desktop environment are you using?
Is it still an issue in newer Ubuntu series?
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notificat
Thank you for your bug report. There has been no activity nor new report
in a few years, could you try if that's still an issue using newer
ubuntu versions?
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
** Changed in: network-manager (Ubuntu)
Status: Confirmed =>
Those keys are handled since 1.10.10 and Ubuntu 18.10
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/9b46af1a
That update is being SRUed to bionic
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1795921
Title:
Out-of-Bounds write in systemd-netwo
Public bug reported:
Mientrasactualizaba el sistema recien instalado
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Hello Hui, or anyone else affected,
Accepted alsa-lib into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.1.6-1ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https:/
Hello errors.ubuntu.com, or anyone else affected,
Accepted software-properties into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.96.24.32.7 in a few hours, and then in the
-proposed repository.
Please help us by testin
Hello errors.ubuntu.com, or anyone else affected,
Accepted software-properties into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.96.20.8 in a few hours, and then in the -proposed
repository.
Please help us by testing t
Hello errors.ubuntu.com, or anyone else affected,
Accepted software-properties into cosmic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.96.27.1 in a few hours, and then in the -proposed
repository.
Please help us by testing t
Public bug reported:
It appears that currently using either the file command or through the
File::LibMagic interface that 1:5.34-2 on Cosmic (18.10) makes a MPEG-2
file be detected as Targa at a higher priority, thus taking precedence
over being what it actually is. See the below lines as examples
Hello Jeremy, or anyone else affected,
Accepted pango1.0 into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pango1.0/1.42.4-3ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
I wasn't aware of gmpy2. Installing it has solved this issue for me.
On Sun, Nov 25, 2018 at 9:20 AM Hans Joachim Desserud <
1804...@bugs.launchpad.net> wrote:
> Thanks for reporting.
>
> I'm a bit confused to the issue. Though I am not familiar with gmpy, it
> looks like there are two versions
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: Confirmed
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bio
Why is the cosmic task open here? I don't see an upload in the cosmic
queue and the description leads me to believe this may already be fixed
there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bu
The "set nocompatible" fix doesn't work on 18.04.1 LTS server. The
trigger condition appears to be a random operation and not repeatable.
Symptoms include loss of tab completion and syntax highlighting. It is
persistent through a re-edit of the same file. The fault can be cleared
by removing .v
The mis-interpretation of PC cursor keys when accessed vi ssh (as
described in the discussion link above) is very remeniscent of trying to
use vim.tiny not vim.basic (which server install defaults to). Maybe
this along with my above post will help characterise the bug.
--
You received this bug n
Public bug reported:
Currently, if an Ubuntu developer (or their code) is attempting to
interact with the precise archive (which is still supported in some form
via ESM) from a machine running bionic or later, they will run in to
issues verifying signatures, because the keys used to sign the preci
rev
09) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics
Controller [103c:179b]
InstallationDate: Installed on 2018-12-18 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181218)
MachineType: Hewlett-Packard HP
I have the same issue. Running Linux Mint with latest kernel.
Kernel: Linux 4.19.9-041909-generic #201812130432 SMP Thu Dec 13 09:34:53 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
It takes me disabling bluetooth, deleting the profile, re-enabling
bluetooth, and putting the mouse back in pairing mode
** Description changed:
Currently, if an Ubuntu developer (or their code) is attempting to
interact with the precise archive (which is still supported in some form
via ESM) from a machine running bionic or later, they will run in to
issues verifying signatures, because the keys used to sig
The easiest thing to do would be to just ship a keyring that had the
obsolete public signing keys. Then the consumer could hard code
that 'precise' was signed with keys A, B, C. and work stuff out like
that.
Alternatively possibly we might want to deliver some distro-info like
data.
ubuntu-rele
** Changed in: systemd (Ubuntu Disco)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: systemd (Ubuntu Cosmic)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: system
Brian, I have now added a note to the bug description to explain that
the cosmic fix is being handled as part of the gtk 3.24.2 SRU. I did
upload this fix for cosmic but I got Steve to reject it for me since we
are doing to do the 3.24.2 SRU instead. I still haven't uploaded 3.24.2
to cosmic since
** Description changed:
Impact
==
Some emoji in the emoji chooser show as black & white.
This is because these emoji default to "text presentation" instead of
"emoji presentation".
More information and a screenshot can be found in the pango issue linked
below.
Test Cas
This bug was fixed in the package e2fsprogs - 1.44.4-2ubuntu0.1
---
e2fsprogs (1.44.4-2ubuntu0.1) cosmic; urgency=medium
* debian/patches/0001-libext2fs-fix-regression-so-we-are-correctly-
transla.patch: cherry-pick upstream fix so we are correctly translating
acls in mkfs.e
The verification of the Stable Release Update for e2fsprogs 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
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include check
The attachment "dirty_patch.txt" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray
ed on 2018-12-18 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181218)
MachineType: Hewlett-Packard HP EliteBook 8470p
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/bo
You have been subscribed to a public bug:
Several applications randomly crash with same error. See attached files.
** Affects: gtk+2.0 (Ubuntu)
Importance: Undecided
Status: New
--
!xcb_xlib_threads_sequence_lost error
https://bugs.launchpad.net/bugs/1808710
You received this bug
Great to hear :)
I'm closing this report then.
** Changed in: python3-defaults (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.
** Attachment added: "_usr_bin_gpicview.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1808710/+attachment/522/+files/_usr_bin_gpicview.1000.crash
** Package changed: freecad (Ubuntu) => gtk+2.0 (Ubuntu)
--
You received this bug notification because you are a member o
** Description changed:
- Several applications randomly crash with same error. See attached files.
+ Some gkt2 applications randomly crash with same error. See attached
+ files.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Successful installation of libdvd-pkg and dpkg-reconfigure, afterwards,
to complete compilation.
Inserted known-good DVD and clicked on "Open in Videos" which launched
the Totem player.
Error msg: "Unable to play the file, DVD source is required, but is not
installed."
DVD
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1809014
Title:
mpeg-2 detected as tga (Targa image)
Status in file package in Ubuntu:
New
Bug descrip
Further investigation with a recompiled version more recent than that
shipped with 18.04 yields that syntax highlighting failure is caused by
redrawtime being exceeded - often triggered after using G to move to
the end of the file. It is not possible to set "syntax on" manually at
that point as it
Hello Daniel, or anyone else affected,
Accepted gnome-shell into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.30.1-2ubuntu1.18.10.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
Just by way of more info I was editing a gitolite conf file of 4096 lines with
the following stats to render the syntax with the cursor at the end of the file
The total time taken was 5 seconds. By default redrawtime is set to 2 seconds
so the 5 srconds taken represents a considetable drop off in
I have this problem with Ubuntu 18.04, 18.10 and Linux Mint 19, on 2 computers :
HP Pavilion dv6700 and Acer Extensa 5620Z, both with a Realtek ALC268 chipset.
Audio is working but not internal microphone (and on HP Pavilion, external
microphone doesn't work too).
--
You received this bug notifi
As explained in https://elubuntero.wordpress.com/tag/realtek-alc268/ , I
tried to add linux-backports-modules-*** but this package isn't anymore
in Ubuntu and Mint repositories.
I tried all options as explained in https://doc.ubuntu-
fr.org/audio_intel_hda , no result. Please heelp.
** Change
Public bug reported:
doesn't seem to be a major issue.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: openssh-server 1:7.6p1-4ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic i686
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: i386
Date
Setting regexpengine=1 drops this back down to 1.4 seconds. So either
this is the root cause of this particular slowdown (i.e. when syntax
highlighting gitolite format files) or at least compensates for whatever
is the root cause. According to
https://stackoverflow.com/posts/38521226 the default r
Thanks, I'll mark it "invalid" to take it off our radar again.
** Changed in: ca-certificates (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bu
This is sure surprising:
(frontend:26097): Pango-[1;33mWARNING[0m **: [34m01:57:45.798[0m: font_face
status is: out of memory
...
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon:
assertion failed (error == NULL): Failed to load
/usr/share/icons/Humanity/status/48/imag
Gert,
Please report the problem to the Mesa developers who will best be able
to help:
https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa
and then let us know the new bug ID.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
htt
If you can't log in remotely any more then that sounds like a kernel
issue. But regardless, please:
1. Reproduce the freeze again.
2. Reboot
3. Run this command to collect the system log from the previous
(frozen) boot:
journalctl -b-1 > prevboot.txt
4. Attach the file 'prevboot.txt' t
David,
Please log your own new bug from an affected machine by running:
ubuntu-bug pulseaudio
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-d
Unfortunately I don't. I let it run, came back a couple hours later and
it wasn't accepting my password. I just let it continue. Was able to
login in the morning and it finished installing while I was at work.
When I got home it worked except for the installation errors posted
here.
--
You receiv
It's already commited, check here :
http://mailman.alsa-project.org/pipermail/alsa-devel/2018-December/143282.html
--
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/1784485
The build failure for cosmic and bionic (after applying the debdiff of
#2 and #3) is because I forgot to add one more patch to add this ucm to
configure.ac.
here I fixed it, and generate an incremental debdiff for cosmic (since
the debdiff of #2 is already merged to cosmic-proposed branch). If nee
This is the debdiff for bionic, it is not an incremental debdiff (since
the debdiff of #3 is not merged to bionic-proposed branch yet), this
debdiff will replace the one in the #3. It fixed the problem of
forgetting to add dir in the configure.ac.
** Patch added: "alsa-lib_1.1.3-5ubuntu0.2.debdi
A possible work-around: Update the jack's description to PulseAudio, as
shown:
Create the file `/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-
output.conf` and populate it with:
```
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
#
** Changed in: opus (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to opus in Ubuntu.
https://bugs.launchpad.net/bugs/1799693
Title:
Stable libopus-1.3 released
Status in opus pack
77 matches
Mail list logo