Uncommenting "WaylandEnable=false " worked.
Removing gdm3 did not work, I just got redirected to a tty3 login shell.
Thanks again
--
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/bug
I just tested this. It worked for me as well. Thanks, Nebojša.
--
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/1752053
Title:
nvidia-390 fails to boot graphical display
Statu
Please compare "/sys/kernel/debug/wakeup_sources" before/after suspend.
--
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/1799038
Title:
Ubuntu 18.10 does not suspend on lid
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. Bu
** Bug watch added: Red Hat Bugzilla #1315239
https://bugzilla.redhat.com/show_bug.cgi?id=1315239
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=1315239
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
Public bug reported:
Sorry for using Ubuntu to report an Xubuntu bug, but the problem is
exactly that bug reporting is not working for me in Xubuntu. When I
tried to create what eventually became bug 1799868 here on Xubuntu, as
soon as the web browser (Chrome) came up, it waas reporting a problem
This very likely seems like a Launchpad problem, not an apport problem.
Do you recall the exact text used?
** Changed in: apport (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to appor
Public bug reported:
I can use seq(1) to generate sequences of large numbers if I use the
default increment:
$ seq 170141183460469231731687303715884105721
170141183460469231731687303715884105725
170141183460469231731687303715884105721
170141183460469231731687303715884105722
170141183460469231731
*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546
This still happens on ubuntu 18.10.
sudo kbd_mode -s does work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https
This still happens on ubuntu 18.10.
sudo kbd_mode -s does work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt-f2 switches to virtual terminal 2
S
It's worse than I thought. Increments of 2 fail even when aa factor of
100 away from the limit:
kevin@plato-x:~$ seq 170141183460469231731687303715884105721 1
170141183460469231731687303715884105725 | head -10
170141183460469231731687303715884105721
170141183460469231731687303715884105722
170141
*** This bug is a duplicate of bug 1799844 ***
https://bugs.launchpad.net/bugs/1799844
** This bug has been marked a duplicate of bug 1799844
dose not work rite
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in U
*** This bug is a duplicate of bug 1798790 ***
https://bugs.launchpad.net/bugs/1798790
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1798790, so it is being marked as such. Please look
I think the main hint is in comment #15:
tessa@viper:~$ pacmd list
Daemon not responding.
This means pulseaudio has either hung, crashed or been killed. Please
follow these instructions to see if you can find any evidence of a
crash:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_rep
*** This bug is a duplicate of bug 210472 ***
https://bugs.launchpad.net/bugs/210472
Thanks! The problem is:
ii timidity-daemon 2.14.0-8
all runs TiMidity++ as a system-wide MIDI sequencer
which makes this a duplicate of bug 210472.
Please just uninst
If the problem still happens in the final release of 18.10:
http://releases.ubuntu.com/18.10/ubuntu-18.10-desktop-amd64.iso
then yes this bug needs to be reopened. Or another one logged. But since
you are the original reporter, I would say reopen.
** Changed in: snapd (Ubuntu)
Status: Won'
"Incomplete" makes sense to me because it appears the problem stopped
happening after 3.28, and not at all in 3.30. We will need more time to
verify that's really true:
https://errors.ubuntu.com/problem/87e4666825764619cb47f3837f871d88d65dd606
and if so then this is "Fix Released" already.
--
Y
Public bug reported:
package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
exited with return code 127
kernel installations halt while scanning mdadm arrays, eventually timing
out and failing
ProblemType: Package
DistroRe
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1799858
Title:
package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to
Public bug reported:
I have small script that invokes another shell script as root thus:
#!/bin/bash
echo "mypass" | sudo -p '' -S /usr/StorMan/StorMan.sh
when running in 16.04 LTS this didn't display a password prompt which I
understand to be correct behaviour. Since upgrading to 18.04.1 LTS t
It would be nice to have some warning the added security benefits available in
18.04 would be removed upon upgrade to 18.10...
😥
There really needs to be some sort of dialogue box warning the user.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
It would be nice to have some warning the added security benefits available
in 18.04 would be removed upon upgrade to 18.10...
😥
There really needs to be some sort of dialogue box warning the user.
On Mon, Oct 22, 2018, 6:31 PM Matthew Paul Thomas
wrote:
> I’ve reported bug 1799310 about warnin
@osomon,
Just verified both chrome AND chromium (v70) experience this bug. The
colours are ugly and dull when a colour profile is active. It's
immediately obvious in the Google logo on the search page. And the
problem goes away as soon as I remove the colour profile and restart the
browser.
** Ch
:) You're welcome.
--
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/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mesa package in Ubuntu:
Fix Released
Public bug reported:
WILL NOT UNINSTAL
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
Compi
The above "confirmed fixed" link is broken.
If you'll pardon another ignorant question: when does this fix show up
in distro?
Just tried 18.10 and persistence renders live Ubuntu completely
unusable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
OMG! Where u were all this time?! Thank you very much!
--
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/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mes
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
This is related to a problem I've encountered today with lvmcache
partitions.
>From a fresh Ubuntu 18.04 install, with lvm2 installed, I create an LVM
on HDD's with an SSD partitioned to provide cache:
lvcreate -n home_lv_root -L 1.2Tb vg0
vgextend vg0 /dev/nvme0n1p6
lvcreate -n home_lv_cache
Please try, in the /etc/gdm3/custom.conf, uncomment WaylandEnable=false
and Nvidia driver will work with gdm3.
--
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/1752053
Title:
n
** Also affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1778946
Title:
No dns resolution after c
** Also affects: ppp (Ubuntu)
Importance: Undecided
Status: New
--
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/1778946
Title:
No dns resolution after clo
** Changed in: glib2.0 (Ubuntu)
Status: In Progress => Incomplete
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Incomplete
--
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
** Branch linked: lp:~brian-murray/apport/executable-snap-bin
--
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/1760220
Title:
ubuntu-bug with program path says as a snap does
Public bug reported:
While working on the development of a Python package I created (deb-pkg-
tools) that uses python-apt and refers to its documentation I noticed
that the online documentation seems to have disappeared...
This makes it impossible for my project to cross-reference the python-
apt
For whatever it's worth: I wouldn't mind spending a bit of time trying
to set up https://python-apt.readthedocs.io/ based on the git repository
at https://git.launchpad.net/ubuntu/+source/python-apt, although I can't
tell if this plan will actually work without trying it (for example I
don't know i
Public bug reported:
$ ubuntu-bug /usr/bin/vim
Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash
file]
ubuntu-bug: error: /usr/bin/vim does not belong to a package.
[ 2:41PM 10508 ] [ bdmurray@impulse:~ ]
$ file /usr/bin/vim
/usr/bin/vim: symbolic link to /e
** Description changed:
[Impact]
The rimap authentication mechanism in saslauthd can hit a condition
where it will start spinning and using all available CPU. This condition
can be easily encountered when an authentication is happening and the
imap service is being restarted.
Fur
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/cyrus-sasl2/+git/cyrus-sasl2/+merge/357779
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bu
I would say workaround not solution
--
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/1752053
Title:
nvidia-390 fails to boot graphical display
Status in mesa package in Ubuntu
** Description changed:
[Impact]
The rimap authentication mechanism in saslauthd can hit a condition
where it will start spinning and using all available CPU. This condition
can be easily encountered when an authentication is happening and the
imap service is being restarted.
Fur
Solution found with NVidia support.
GDM3 causing Ubuntu 18.10 to "freeze" before login screen
After remove GDM3 and LightDM installation Ununtu booted as usually
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Changed in: apport (Ubuntu)
Status: New => In Progress
** Changed in: apport (Ubuntu)
Importance: Undecided => High
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Tou
Ok, trusty isn't affected because the loop there has an exit clause:
+ ret = read(s, rbuf+rc, sizeof(rbuf)-rc);
+ if ( ret<0 ) {
+ rc = ret;
+ break;
+ } else {
+ if (ret == 0) {
+ loopc += 1;
+
** Attachment added: "journal output attached"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+attachment/5205033/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
I'm unable to trigger this bug when running the test case on trusty,
even though the same code is there. I also tried adjusting the sleep.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.lau
This bug was fixed in the package systemd - 229-4ubuntu21.5
---
systemd (229-4ubuntu21.5) xenial; urgency=medium
[ Dimitri John Ledkov ]
* systemctl: correctly proceed to immediate shutdown if scheduling fails
(LP: #1670291)
* hwdb: update micmute on Dell laptops. (LP: #1738
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
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.5
---
systemd (229-4ubuntu21.5) xenial; urgency=medium
[ Dimitri John Ledkov ]
* systemctl: correctly proceed to immediate shutdown if scheduling fails
(LP: #1670291)
* hwdb: update micmute on Dell laptops. (LP: #1738
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.5
---
systemd (229-4ubuntu21.5) xenial; urgency=medium
[ Dimitri John Ledkov ]
* systemctl: correctly proceed to immediate shutdown if scheduling fails
(LP: #1670291)
* hwdb: update micmute on Dell laptops. (LP: #1738
This bug was fixed in the package systemd - 229-4ubuntu21.5
---
systemd (229-4ubuntu21.5) xenial; urgency=medium
[ Dimitri John Ledkov ]
* systemctl: correctly proceed to immediate shutdown if scheduling fails
(LP: #1670291)
* hwdb: update micmute on Dell laptops. (LP: #1738
This bug was fixed in the package systemd - 229-4ubuntu21.5
---
systemd (229-4ubuntu21.5) xenial; urgency=medium
[ Dimitri John Ledkov ]
* systemctl: correctly proceed to immediate shutdown if scheduling fails
(LP: #1670291)
* hwdb: update micmute on Dell laptops. (LP: #1738
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.5
---
systemd (229-4ubuntu21.5) xenial; urgency=medium
[ Dimitri John Ledkov ]
* systemctl: correctly proceed to immediate shutdown if scheduling fails
(LP: #1670291)
* hwdb: update micmute on Dell laptops. (LP: #1738
In journalctl I found that whenever the machine reached suspend target,
ACPI kicked in to wake the machine again.
kernel: ACPI: Low-level resume complete
Today, I put the machine to sleep (using the alt option on the shutdown menu).
The machine woke up every two seconds and went to sleep again (f
** Description changed:
[Impact]
The rimap authentication mechanism in saslauthd can hit a condition
where it will start spinning and using all available CPU. This condition
can be easily encountered when an authentication is happening and the
imap service is being restarted.
-
- Onc
Debconf executes scripts from /tmp by default but you can try continuing
securing the system by changing apt's temp file configuration:
https://serverfault.com/questions/72356/how-useful-is-mounting-tmp-noexec
Anyway this is definitely not a bug in u-u, maybe a wishlist one for
debconf.
** Chang
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ The rimap authentication mechanism in saslauthd can hit a condition
+ where it will start spinning and using all available CPU. This condition
+ can be easily encountered when an authentication is ha
Found this opened report related to the nvidia driver
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1795808
--
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.ne
Public bug reported:
python3 from python3-defaults is 3.6.5-3ubuntu1
python3-lib2to3 from python3-stdlib-extensions Depends: python3 (>=
3.6.6-1~)
Either python3-stdlib-extensions dep should be lowered, or
python3-defaults should be rebuilt.
** Affects: python3-defaults (Ubuntu)
Importance
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [Test Ca
I agree that it should be fixed in u-u. Patches are welcome.
** Changed in: unattended-upgrades (Ubuntu)
Importance: Medium => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https:/
Fixed in this commit: https://github.com/mvo5/unattended-
upgrades/commit/7c5e5476711fab6b9977116792262e16efe626ec
** Changed in: unattended-upgrades (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1799738
Title:
dose not work rite
Status in xorg package in Ubuntu
Reassigning to update-manager since it started the installation, u-u
does not seem to be at fault here.
** Package changed: unattended-upgrades (Ubuntu) => update-manager
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Also affects: openvpn-systemd-resolved (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: openvpn-systemd-resolved (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Also affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
--
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.net/bugs/1799206
Title:
SRU: update p
It is quite strange but it is not an unattended-upgrades bug. Do you
still observe it?
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-up
This is a bug in smfpd, which is not packaged in Ubuntu.
https://www.keypressure.com/blog/what-is-smfpd/
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
*** This bug is a duplicate of bug 1778946 ***
https://bugs.launchpad.net/bugs/1778946
Yeah, I think so. Thanks.
** This bug has been marked a duplicate of bug 1778946
No dns resolution after closing a vpn/pptp connection
--
You received this bug notification because you are a member o
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
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
Either this change will make the rfkill button work (good), or not
(current behaviour). Given the code paths, validating similar SKUs for
non-regression is a good enough confidence level that this change
doesn't regress other/unrelated machines. It's a low risk to accept this
change as is, because
** Package changed: unattended-upgrades (Ubuntu) => flashplugin-nonfree
(Ubuntu)
--
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/1689756
Title:
package unattend
is this a duplicate of https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1778946 ?
--
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/1797415
Title:
DNS stops wo
The broken dcservice file is not part of Ubuntu. If you still experience
the issue please track down the origin and open a bug there. @colan
Apport directed you there because it had no better idea, but it is just
a script doing pre-processing of crashes.
** Changed in: unattended-upgrades (Ubuntu
** Description changed:
IN start UBUNTU
Application can no longer access your dumetz1...@gmail.com Online
- Account. Choose online Accounts from the user menu to reinstale access
+ Account. Choose online Accounts from the user menu to reinstate access
to this account.
--
You received th
It should be linked/merged to this bug:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173
** Also affects: qtbase-opensource-src (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Thanks. I think that's sufficient justification.
--
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/1762385
Title:
dell_wmi: Unknown key codes
Status in OEM Priority Project:
Thanks. Out of band Dimitri explained to me that "unknown" isn't really
a mapping, which I think is key.
--
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/1738153
Title:
need
*** This bug is a duplicate of bug 1683383 ***
https://bugs.launchpad.net/bugs/1683383
The same on Ubuntu 18.04 LTS with Gnome.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
*** This bug is a duplicate of bug 1776173 ***
https://bugs.launchpad.net/bugs/1776173
** This bug has been marked a duplicate of bug 1776173
qt print dialog shipped with bionic ignores printer defaults
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
After my most recent Ubuntu 16.04 LTS update (that required both an
authorization password request and a post-installation reboot) the
following message appears briefly in a small window in the top right
corner of the screen after I sign into Ubuntu:
"Applications can no longer access your [@ATT.n
Please confirm the exact package version tested.
What about my question in comment 10? The Regression Potential currently
says "it just add one more mapping" but this doesn't appear to be true
because a mapping was also removed.
--
You received this bug notification because you are a member of U
Public bug reported:
I can't run Ubuntu 18.10 with nVidia drivers (340.107). They ran just
fine on 18.04, but not on 18.10. The system freezes at start up (the
furthest that it gets is 'Starting Gnome Display Manager'). X-org
Nouveau driver is working ok, but it's not ideal, I get strange
flickeri
I have upgraded to Ubuntu 18.04 (bionic) and I am experiencing the same
problem. I don't have permission to change the bug status, should I
submit another bug report?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver
*** This bug is a duplicate of bug 1789637 ***
https://bugs.launchpad.net/bugs/1789637
Locking across dpkg frontend is being fixed and the fix will be ported
back to Xenial. I'm setting this bug as a duplicate of the one tracking
the fix of unattended-upgrades. Please follow the state of that
@racb
unknown is a placeholder, which is now assigned to wlan. Without unknown, there
would be debugging error kernel messages `unknown key pressed`. So previously
we knew the physical key exists and is pressable, but dind't know what it
should do, but now we do know what it does.
--
You recei
Thank you for checking that this doesn't introduce a regression on
unaffected hardware.
Note that we don't currently have a verification for the actual reason
this is being SRU'd, which is "rfkill keyboard shortcuts not working as
intended on some Dell machines".
--
You received this bug notific
The attachment "Patch for padding" 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-murr
Public bug reported:
My rsyslog configuration listens on TCP port 514 and is bound to an
address on tun0 (created by an openvpn server daemon):
module(load="imtcp")
input(type="imtcp" port="514" address="10.8.9.1")
This machine rebooted (due to unattended upgrades) overnight and when it
came
*** This bug is a duplicate of bug 1789637 ***
https://bugs.launchpad.net/bugs/1789637
The implementation of the frontend lock in _all_ dpkg frontends can make
u-u avoid this crash. Making this bug as a duplicate of the bug tracking
the frontend lock implementation for u-u.
** This bug has be
This started happening after installing lubuntu-desktop. Even after
removing it, it is still failing to mount. After running "keyctl link @u
@s", it works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
htt
Note: I'm using 18.04
--
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/1718658
Title:
ecryptfs-mount-private fails to initialize ecryptfs keys
Status in ecryptfs-utils pack
I was offsite all day yesterday. I came in today and the lock screen
was responsive. Unplugging the monitor seemed to prevent the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchp
That sounds great!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed to userspace
Status in gnome-settings-daemon package in Ubu
I discussed with slangasek, who said:
- The workaround is to either to configure systemd to restart rsyslog when
the socket is available, or to have openvpn restart rsyslog when the VPN comes
up.
- The definitive fix would require rsyslogd to grow netlink support (or be
managed by something
I'm seeing what I believe to be the same issue with Visual Studio Code.
If I try to start it after logging in using Gnome on Wayland, I find
myself looking at a login screen. (If I login to Gnome on Xorg this does
not happen.)
There is a core file in my home directory
There is also a file in /va
1 - 100 of 197 matches
Mail list logo
