** No longer affects: wireguard (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685522
Title:
out of date snapshot
To manage notifications about this bug go to:
Hey apw and adconrad -- a long time ago (2.5 years) we decided to keep
WireGuard from migrating into Ubuntu. There's been tons of progress
since then. It's now in the progress of migrating down into Debian
testing and stable. I think it's time we let it migrate into Ubuntu too.
Is there anything
It's possible this same issue is responsible for this crash in
WireGuard:
https://lists.zx2c4.com/pipermail/wireguard/2019-September/004495.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
@Vamshee,
This issue is fixed. Please try to upgrade your system and try again.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828604
Title:
Lenovo T490S and X390 GM do not have
I came across this in a Debian bug (https://bugs.debian.org/823195) and
I found a workaround similar to comment #2. This works on Debian Sid,
but not on Jessie, so this might not work on a system more than a year
or two old.
Use normal (non-natural) scrolling in Xfce settings and run a command
@ Ryan we do not test Xenial or Disco
On Thu, Aug 22, 2019 at 7:41 PM Ryan Harper <1784...@bugs.launchpad.net>
wrote:
> Finally, I did verify xenial proposed with our original test. I had
> over 100 installs with no issue.
>
> @Jason
>
> Have you had any runs on Xeni
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784665
Title:
bcache: bch_allocator_thread(): hung task timeout
To manage
** Attachment added: "spinda.maas-curtin_config.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5284072/+files/spinda.maas-curtin_config.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We're still seeing a bcache timeout failure during curtin install
2019-08-22T10:16:40+00:00 spinda
cloud-init[1604]: finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta/clear-holders: FAIL:
removing previous storage devices
2019-08-22T10:16:40+00:00 spinda cloud-init[1604]:
Just a note (mostly to other distro maintainers that may come across
this) that an alternative to completely disabling the Wacom driver's
touchscreen handling is to just add `Option "Gesture" "Off"` to the
touchscreen section of 70-wacom.conf instead.
The driver currently defaults to consuming
I am experiencing this same problem in Linux Mint 19.1. After creating a
print job, there is no response from the printer (it doesn't wake up or
anything), there is no printing, but the only message in the error log
is "CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
I also started having this same issue on my HP Spectre x360.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807406
Title:
hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from
I'm having an issue with using adcli to add a service name on Ubuntu
18.04 as well. It works on RHEL8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831448
Title:
adcli: not adding an additional
This is difficult for us to test in our lab because we are using MAAS, and
we hit this during MAAS deployments of nodes, so we would need MAAS images
built with these kernels. Additionally, this doesn't reproduce every time,
it is maybe 1/4 test runs. It may be best to find a way to reproduce this
Removed the radeon video card and tried using onboard intel graphics.
Works fine for pixio monitor but not for asus. I suspect it probably
doesn't work for the asus because of bad edid? So it would seem to me
that the problem is somewhere in amdgpu? Is there anything else I can
do to help
I've attached the edid-decode from the asus monitor. parse-edid
couldn't properly read the edid from this monitor.
** Attachment added: "asus-rog-edid-decoded.txt"
I've tried with a different monitor that also supports 144 Hz and seem
to be limited at 120 Hz on this monitor as well. I've attached the xorg
log from a boot with that monitor attached instead.
** Attachment added: "Xorg.0.log"
Attached edid output. Notice "Mode 1" is apparently the modeline that
specifies 144 Hz native resolution, but I don't see this mode in xorg
log.
** Attachment added: "Attached edid output"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834761/+attachment/5274195/+files/edid.txt
--
Sorry, I realize I left out some detail. I can get 144 Hz if I change
the resolution to 1920x1080 but that's not the native resolution for the
monitor. I'm trying to get 144 Hz / 165 Hz using the monitor's native
resolution, 2560x1440.
--
You received this bug notification because you are a
Public bug reported:
using this monitor: https://www.pixiogaming.com/px329
and this video card:
https://www.gigabyte.com/us/Graphics-Card/GV-RX580GAMING-4GD-rev-10-11
I am unable to set any refresh rates higher than 120 Hz. The video card
and the monitor both support 144 Hz and 165 Hz yet
I too am experiencing this issue when using:
Ubuntu 18.04.2 LTS
Gnome 3.28.2
Mouse moves but unable to click anything for a minute or two.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181666
** Also affects: linux
Importance: Undecided
Status: New
** No longer affects: linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802652
Title:
keyboard backlight not working on Asus
Public bug reported:
It seems a prior bug has resurfaced, with a slightly different behavior
now. (This is *not* a duplicate of gtk#1447)
**Version:** 3.32.1-2
**OS:** Ubuntu MATE 19.04
In the email composer window, if you select text in the body, and
*click* anywhere else in the composition
Public bug reported:
This error message appears whenever you try to open a VTK file inside of
Paraview. The OpenFOAM developers also ran into the same issue and found
a solution by setting some flags when building Paraview. See the thread
here for more information:
Public bug reported:
fontconfig version: 2.12.6-0ubuntu2
Related:
https://askubuntu.com/questions/1076412/firefox-freezing-with-100-cpu-
usage-for-30-seconds-when-launching-chromium
https://bugzilla.mozilla.org/show_bug.cgi?id=1495900
https://bugzilla.mozilla.org/show_bug.cgi?id=1411338
Just adding a comment to confirm that the patch is required on Ubuntu
18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732485
Title:
Crash with mime type application/xml on recent distros
To
Public bug reported:
The nfs-ganesha package installs the systemd unit file
/lib/systemd/system/nfs-ganesha-config.service
which specifies
ExecStart=/usr/lib/ganesha/nfs-ganesha-config.sh
but no such file is provided by the package so the service fails to
start.
The package does install a
Public bug reported:
Went to install Ubuntu from the try Ubuntu now desktop, and it told me
the cd, after the third time of downloading it was corrupted.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Public bug reported:
When I try to run-geiser in Emacs 26.1 on Ubuntu 19.04 Disco Dingo, I
get the following error message:
apply: Invalid function: (lambda () geiser-guile-minimum-version)
This is the same as this issue from geiser's old github:
https://github.com/jaor/geiser/issues/207
Note
Thank you for the update and the explanation. I will post some feedback
on gitlab.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827751
Title:
Shield screen is displayed after blanking even when
** No longer affects: cdoqa-system-tests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777512
Title:
key retrieval timeouts cause failures
To manage notifications about this bug go to:
Correction: I have to push the Enter key to dismiss the screen, not any
other key.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827751
Title:
Lock screen displayed after screen blanking even when
Sorry, but I am not sure I could tell the difference so I will try and
describe it as best I can.
There is no place to enter a password, but I also have my system set to
automatically log in, so I'm not sure if it would ask me for a password
if it was displayed. I do have to press a key to get
Here is the screen capture with the background settings.
** Attachment added: "Screen Capture.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827751/+attachment/5264674/+files/Screen%20Capture.png
--
You received this bug notification because you are a member of Ubuntu
** Tags added: cdo-qa foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
To manage notifications about this
-14 11:29:52.373] Couldn't read "/home/jason/.config/user-dirs.dirs":
Permission denied
[2019-05-14 11:29:53.628] Couldn't create
"/home/jason/.config/transmission-daemon": Permission denied (file-posix.c:189)
[2019-05-14 11:29:53.628] Couldn't create
"/home/jason
I think my report is not accurate. Replacing the symlink with an
absolute one didn't help. Transmission seems to want to read my user
dirs no matter what.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My mistake, it is still present. I just wasn't waiting long enough
after the screen blank before waking the screen up. Waited a bit and it
is back, even with the extension running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also tried editing /etc/default/acpi-support and commenting out the line
LOCK_SCREEN=true. That did not work.
Just found a workaround that seems to take care of the problem. Install
the Gnome Extension: Disable Screen Shield and activate it. The lock
screen no longer appears after screen
** Tags added: cpe-onsite
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777512
Title:
key retrieval timeouts cause failures
To manage notifications about this bug go to:
Sub'd ~field-high.
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- rt #112309: keyserver.ubuntu.com increased failure rates over past few days
+ key retrieval timeouts cause failures
** Description changed:
- keyserver failures
This occurrs on a target machine during maas install. Apport is not
collected in this case.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Ubuntu 19.04 Gnome
Screen lock is set to off in Settings->Privacy. Blank Screen is set to
10 minutes in Settings->Power. On returning from Screen Blank, Lock
Screen is present. Does not occur after manual suspend (ie closing
laptop lid) and resuming.
In dconf I have set
Reported - https://bugs.freedesktop.org/show_bug.cgi?id=110604
Thanks for your help.
** Bug watch added: freedesktop.org Bugzilla #110604
https://bugs.freedesktop.org/show_bug.cgi?id=110604
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I did a little more testing and this looks to be specific to /home.
Even mounting over /home (no linking) with autofs results in the same
issue.
All autofs files as well as the list of packages installed have been
attached.
As a side note, having /home as a link is an artifact of some very old
Sorry - those last two comments were meant for bug #1827286.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577575
Title:
NFS share does not mount on boot using fstab
To manage notifications about
I did a little more testing and this looks to be specific to /home.
Even mounting over /home (no linking) with autofs results in the same
issue.
All autofs files as well as the list of packages installed have been
attached.
As a side note, having /home as a link is an artifact of some very old
** Attachment added: "chi.packages"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261280/+files/chi.packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
** Attachment added: "chi.packages"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+attachment/5261278/+files/chi.packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577575
** Attachment added: "auto.master"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261274/+files/auto.master
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
** Attachment added: "auto.direct1"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261267/+files/auto.direct1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
** Attachment added: "auto.net"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261269/+files/auto.net
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
** Attachment added: "auto.misc"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261271/+files/auto.misc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
** Attachment added: "auto.smb"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261268/+files/auto.smb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
** Attachment added: "autofs.conf"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261266/+files/autofs.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
** Attachment added: "master.d_direct1.autofs"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261265/+files/master.d_direct1.autofs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like the issue is symlinking to a director prior to autofs
mounting it.
Everything fine...
root@numbersix:/# ssh chi uname -a
Linux chi 4.4.0-146-generic #172-Ubuntu SMP Wed Apr 3 09:00:08 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
root@chi:~# ls -la /home
ls: cannot access '/home': No such
** Tags added: autofs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
autofs - "Too many levels of symbolic links" after apt upgrade
To manage notifications about this bug go to:
Public bug reported:
Description:Ubuntu 16.04.6 LTS
Release:16.04
I moved to autofs this week as a workaround for Bug #1577575 failing to
mount NFS entries at boot. This worked file until I ran 'apt upgrade'
today.
Now trying to access /vol/home mount results in the following error:
Quick update - switched to autofs as a workaround for this 16.04 issue.
That was fine until I ran 'apt upgrade' today. Now I get the following
error:
root@chi:~# ls -la /vol/home/
ls: cannot access '/vol/home/': Too many levels of symbolic links
root@chi:~#
I'll be opening a new bug for
closing for inactivity, is this is still occurring in the lastest
openstack manila builds please feel free to re-open or create a new
defect Thanks!
** Changed in: manila
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
unsure of the issue
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture:
@You-Sheng
Sorry, our messages must have crossed paths.
Appears to be the third device from the strace of the fwupd process in
the hung state.
$ grep -i drm strace.log | tail -n 2
2897 20:01:01.099170 lseek(19, 1200, SEEK_SET) = 1200
2897 20:01:01.099193 read(19, ) = ?
So as you suspected,
You're probably right about the driver. I've seen other complaints from
the drm layer around amdgpu. I'll try to watch dmesg more often to catch
more of these.
Just added the files from apport.
As for the rest:
> 1) Can you please follow the things that the bot said to add your logs
to the bug.
apport information
** Tags added: apport-collected
** Description changed:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
$ lsb_release -rd
Description:Ubuntu 19.04
Release:19.04
Being a firmware updater, the machine is probably
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1826691/+attachment/5260181/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "modified.conffile..etc.fwupd.daemon.conf.txt"
https://bugs.launchpad.net/bugs/1826691/+attachment/5260183/+files/modified.conffile..etc.fwupd.daemon.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1826691/+attachment/5260182/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826691
I should note this is impacting an image built from 16.04.4. Another
image built from 16.04.1 is working fine.
Both have been pulled forward via apt dist-upgrade and their behaviors
differ - concerning in it's own right.
--
You received this bug notification because you are a member of Ubuntu
Same issue here. NFS fails to mount at boot, but logging in and issuing
a manual "mount -a" resolves until the next reboot.
It should also be noted that there's a significant delay on boot with
nfs entries in fstab - need to time it, but ~1 minute.
Why issues with something as old/stable/boring
** Summary changed:
- Right Click Menu Stuck And Causes Failure of Dock to Respond
+ Right Click Menu Stuck
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826878
Title:
Right Click Menu Stuck
To
I have another data point to add. As I was preparing to logout and log
back in, I noticed that the menu became responsive again when I closed
Nautilus, i.e. the two windows for "Files" that appear in the menu in
the screenshot.
I don't have any crash dump information, obviously, but I can supply
Public bug reported:
This is one of those things that happens apparently randomly from my
(the user's) point of view. Occasionally, when I right click on a dock
icon to bring up the menu, the menu doesn't really respond to clicking
on the commands, and then stays on my screen even after the dock
Thank you very much. I think I can live with the first option. I'll look
more into the implications, but it seems to be better than not having
the process running at all.
Not sure if I need to do anything to close this.
> 1. Blacklist synapticsmst plugin in fwupd in /etc/fwupd/daemon.conf
This
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
$ lsb_release -rd
Description:Ubuntu 19.04
Release:19.04
Being a firmware updater, the machine is probably relevant - Dell 7730.
2) The version of the package you are
MAAS is installing bind9 and configuring it for its own purposes - it
provides other config for bind, and it's perfectly reasonable to expect
maas to configure it to only listen on interfaces MAAS wants to provide
DNS services on.
** Changed in: maas
Status: Invalid => New
** Tags added:
Public bug reported:
A simple "make rpm" of master on a CentOS system throws a long error
spew, but the relevant error message appears at the end:
File not found: /tmp/rpmbuildAO7h7e/rpmbuild/BUILDROOT/cloud-
init-18.5+66.gc8c32515-1.el7.x86_64/etc/bash_completion.d/cloud-init
Reverting
With the package 1.30.1-0ubuntu1.1 from rocky-proposed in place, I ran
through the test case for this and did not hit any failures. I can
verify this fixes the issue for rocky.
** Tags removed: verification-rocky-needed
** Tags added: verification-rocky-done
--
You received this bug
** Description changed:
nova conductor running on a rhel8 host inside f28 based containers hits the
following error:
2019-01-17 13:59:37.049 46 DEBUG oslo_concurrency.lockutils
[req-284f3071-8eee-4dcb-903c-838f2e024b48 40ca1490773f49f791d3a834af3702c8
8671bdf05abf48f58a9bdcdb0ef4b740 -
** Tags added: cdo-qa cdo-release-blocker foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812935
Title:
oslo cache mempool issues with python3
To manage notifications about this
I've recently found that while pairing with this pen does not work,
"merely" connecting to the pen does work. That is:
# This command fails
$ echo -e "scan on\npair \nscan off" | bluetoothctl
# But this command works
$ echo -e "scan on\nconnect \nscan off" | bluetoothctl
Looking through the
I've just built and installed the master branch of gnome-bluetooth
(commit b4edf6a8) and didn't see any behavioral change. Since it isn't
even possible to pair through bluetoothctl, I wasn't particularly
hopeful that an update to gnome-bluetooth would fix things.
--
You received this bug
Upstream ticket: http://tracker.ceph.com/issues/39031
** Bug watch added: tracker.ceph.com/issues #39031
http://tracker.ceph.com/issues/39031
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820976
Hey Chuck is this bug still occurring? Could you also let me know what
version of OpenStack you are using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664279
Title:
Traceback when configuring
Public bug reported:
https://launchpadlibrarian.net/416079314/buildlog_ubuntu-trusty-
amd64.wayland_1.12.0-1~ubuntu16.04.3~ubuntu14.04.1~ppa2_BUILDING.txt.gz
make[1]: Leaving directory `/<>'
dh_installdocs -a -O--builddirectory=build/
dh_installchangelogs -a -O--builddirectory=build/
@Christian
- release: bionic
- seabios: 1.10.2-1ubuntu1
- qemu: 1:2.11+dfsg-1ubuntu7.10
- libvirt: 4.0.0-1ubuntu8.8
- ovmf - this is a uefi thing right? we're not using it.
- kernel 2019-03-18T12:17:11+00:00 elastic-2 kernel: [0.00]
Linux version 4.15.0-46-generic
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1804804/+attachment/5248039/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804804
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1804804/+attachment/5248046/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804804
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1804804/+attachment/5248036/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804804
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1804804/+attachment/5248049/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804804
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1804804/+attachment/5248040/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804804
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1804804/+attachment/5248045/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804804
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1804804/+attachment/5248047/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804804
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1804804/+attachment/5248043/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804804
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1804804/+attachment/5248038/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ashley 1774 F pulseaudio
/dev/snd/controlC0: ashley 1774 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
Lsusb:
Currently experiencing this problem in disco on an Acer One 10 S1003. screen is
by default in portrait, which makes using the keyboard attachment a little
painful.
For default landscape mode, I manually set:
xinput set-prop 13 "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
and try to
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1804804/+attachment/5248044/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1804804/+attachment/5248048/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804804
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1804804/+attachment/5248041/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804804
301 - 400 of 7697 matches
Mail list logo
