I'm actually running Arch on my desktops now, so I don't have a free
system to try this out with. if upstream says it's fixed, then it's
probably fine to close this for now and re-open it if the problem re-
appears for someone else.
--
You received this bug notification because you are a member
just tried to use netplan on a public facing server, discovered there's
no `ucarp` integration, and discovered this bug.
is there any ETA on these outstanding items? network HA is a nightmare
without CARP, this feels like essential server functionality.
--
You received this bug notification
ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2: tessa 3387 F pulseaudio
/dev/snd/controlC0: tessa 3387 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop
Interestingly, if I run my monitor off my NVidia card, and the audio off
the Intel HDMI, then the Intel audio works correctly. it's only when my
display is connected to the Intel DisplayPort alongside my receiver on
the Intel HDMI that it totally messes up.
--
You received this bug notification
note that if I set the output to 7.1 mode, it sounds identically garbled
to 5.1 mode. but if I set it to Digital Stereo, no sound comes out at
all.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
note that this sounds like this bug upstream, but using that module option
doesn't fix the issue:
https://bugzilla.kernel.org/show_bug.cgi?id=74861
** Bug watch added: Linux Kernel Bug Tracker #74861
https://bugzilla.kernel.org/show_bug.cgi?id=74861
--
You received this bug notification
Public bug reported:
I've been having ongoing issues with pulse and my nvidia video card
doing hdmi audio, so I thought I'd try using my builtin intel HDMI port
for audio instead. However, when I switch the HDMI cable to that port,
and select it in pulse, all the audio sounds crackly and garbled,
Public bug reported:
in the past, I've used DisplayCalGUI to calibrate my displays. however,
that software hasn't been updated to use Python3 properly, so it doesn't
run on recent Ubuntu releases. I thought I'd try the builtin gnome
calibration, but it seems completely broken on 20.10. I've tried
*** This bug is a duplicate of bug 1872461 ***
https://bugs.launchpad.net/bugs/1872461
and this is all after uninstalling the sound-output-device-chooser
extension, so I feel like that's a bit of a red herring for my actual
issue.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1872461 ***
https://bugs.launchpad.net/bugs/1872461
awesome, glad to hear it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1906137
Title:
*** This bug is a duplicate of bug 1872461 ***
https://bugs.launchpad.net/bugs/1872461
had another crash immediately after. seems like the primary trigger is
playing games in steam, especially games using the proton runtime layer
for running windows games. so it seems like something's perhaps
*** This bug is a duplicate of bug 1872461 ***
https://bugs.launchpad.net/bugs/1872461
just had another crash, with all the extensions disabled. I tried
running ubuntu-bug on the crash file, but it didn't give me a bug to
link in here, not sure why. the error it reported is:
"gnome-shell
it's also worth noting that my laptop, which is also seeing a bunch of
these crashes on gnome-shell, doesn't have any extra extensions
installed that don't come from Ubuntu. this may be coincidence, but it
does feel off that after upgrading to 20.10 both my systems that run
Ubuntu on the desktop
hey Daniel,
if I'm reading the first part of your reply right, it sounds like gnome-
shell extensions can hard crash gnome-shell? which means it's not safe
to ever use any extensions? i feel like i must be misunderstanding that,
since ubuntu distributes a set of extensions by default in the
Public bug reported:
this is probably a dupe of a bunch of other gnome-shell crashing bugs.
just noting that since upgrading to 20.10, both my systems (which use
the nvidia binary X drivers) have gnome-shell crashing multiple times a
day. it restarts fine, but while it's crashing it locks up the
and per your suggestion, here's the upstream bug I just filed:
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1678
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1678
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1678
--
You received this bug notification because you are
filed an upstream bug for this one as well:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1901286
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1901286
Unfortunately, nothing shows up in journalctl. Is that where nautilus
normally logs things? The images have all kinds of names, since they all
fail, but consistently I see failures on very basic names like
"icon.png" or "2020-01-01_365243.jpeg" or similar.
--
You received this bug notification
Interestingly, I just noticed in the man page that nautilus has a self-
check function. when I run `nautlius -c` and then look at journalctl, I
see the following. not sure what it means, but nautilus thinks there's a
problem:
Nov 23 02:18:45 boxxy org.gnome.Nautilus[1125330]: running
as an update, this is still broken on 20.10. as well, I've noticed an
interesting detail, which is that thumbnailing *is* working on my
connected Google Drive. so it really does just seem to be samba shares.
As well, I've discovered that if I remove the
`/home/tessa/.cache/thumbnails/fail/gnome
icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2
Mapped file virtio-win-0.1.185.iso as /dev/loop0.
and then the ISO shows as mounted in nautilus. so I guess it's not a
problem with the ISO itself, but with whatever nautilus+gnome is doing
to try and mount it.
--
You received this bug notification because you are a member of Desktop
Packages,
]: Mounted /dev/loop1p1 at
/media/tessa/Ubuntu 20.04.1 LTS amd64 on behalf of uid 1000
Oct 29 18:02:06 boxxy udisksd[2567]: Set up loop device /dev/loop1 (backed by
/home/tessa/Downloads/ISOs/ubuntu-20.04.1-desktop-amd64.iso)
Oct 29 18:02:07 boxxy fwupd[6497]: 01:02:07:0315 FuEngine
hmmm. it doesn't seem to be every disk image, but it does seem to be a
great number of them. my 20.04.1 install ISO works fine, but the virtio-
win-0.1.185.iso that I was using fine in 20.04 causes this problem
consistently for me. I watched the output of `journalctl -b 0`, and
nothing was printed
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2: tessa 3387 F pulseaudio
/dev
oDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2: tessa 3387 F pulseaudio
/dev/snd/controlC0: tessa 3387 F pulseaudio
CasperMD5Chec
Public bug reported:
After upgrading to 20.10, my mouse either takes an extraordinarily long
time to reconnect (2+m), or it never reconnects until I unplug and
replug my usb bluetooth dongle. It was slow to reconnect on 20.04
(10-30s), but it seems pretty much broken on 20.10.
ProblemType: Bug
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2: tessa 3387 F pulseaudio
Public bug reported:
after upgrading to 20.10, mounting ISOs fails after a bit over 20s, with a GTK
dialogue that reads:
```
Error attaching disk image:
GDBus.Error:org.freedesktop.UDisks2.Error.Fails: Error waiting for loop object
after creating '/dev/loop5': Timed out waiting for object
Ok, the problem is recurring again, so I've gathered a backtrace with
that dbgsym package installed, hopefully it provides more insight as to
where things are getting blocked up.
** Attachment added: "gdb-nautilus-2020-10-19.txt"
yep, there we go, works fine now. I wonder what component malfunctioned
when setting that, could have been wine or vlc or any number of things
that prevent sleep while playing media, I suppose. It's too bad that
there's no indicator or overrider to let a user know what's going on in
this scenario.
why am I not surprised that sending a cryptic dbus command is the
"correct" way to lock the screen from the cli these days.
in any case, I can run that command as often as you like, and it always
returns success to the shell, but it never locks the screen:
tessa@boxxy:~/Downloads$
Public bug reported:
I've got nautilus configured to display thumbnails on network shares
(prefs -> search -> thumbnails -> all files), but in 20.04 it
never shows thumbnails on my samba network shares. Not sure what broke
since previous ubuntu releases, but it's definitely not working now.
local
Public bug reported:
the zsys automatic zfs snapshots use up an incredible amount of disk
space by snapshotting things they shouldn't on every package install
(like user's home directories). as well, there seems to be no cleanup
done whatsoever. a month or so after installing my new desktop, my
eneric x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F..
ame: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/sn
-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2: tessa 3387 F pulseaudio
/dev/snd/controlC0: tessa 3387 F
icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2: tessa
.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa
40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7
inux 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/sn
-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F
ok well, this is exceptionally weird. I was seeing some issues with my
wine install where the internal state was all messed up and it was just
hanging starting apps and so I blew it away and rebuilt it, and now
I can't reproduce this nautilus issue.
Is there any connection between nautilus
there doesn't seem to be a nautilus-dbg package or similar which
includes the debug symbols, unfortunately. here's a stacktrace from
while it's waiting.
** Attachment added: "gdb-nautilus-2020-08-15.txt"
gdb output from nautilus after startup has completed.
** Attachment added: "gdb-nautilus-2020-08-14.txt"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1891712/+attachment/5401585/+files/gdb-nautilus-2020-08-14.txt
--
You received this bug notification because you are a member of
Alright, just tested this. ran date before starting nautilus, got "Fri
14 Aug 2020 05:02:02 PM PDT", ran it once the window appeared, got "Fri
14 Aug 2020 05:03:02 PM PDT", so pretty much a full minute to the
second. and here's what I see from journalctl during that period:
Aug 14 17:02:36 boxxy
Public bug reported:
I'm filing this bug separately because it appears to be distinct from
#1063282, but the root cause may be similar.
when I start nautilus and it's not already running, it can take an
extremely long time to start, up to even 2m before a file browser
appears. as well, opening
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2: tessa 3387 F pulseaudio
/dev/snd/controlC0: tessa 3387 F pulseaudio
x 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7
chitecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2: tessa 3387 F pulseaudio
/dev/snd/controlC0: tessa 3387 F
dia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2: tessa 3387 F pulseaudio
/dev/
dules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...
1-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2: tessa 3387 F pulseaudio
/dev/snd/controlC0: tessa 3387 F...
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2: tessa 3387 F pulseaudio
/dev/snd/controlC0: tessa 3387 F pulseaudio
CasperMD5CheckResult: skip
nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio
/dev/snd/controlC2: tessa 3387 F
40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F pulseaudio
/dev/snd/pcmC1D7p: tessa
: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 3387 F
Public bug reported:
after upgrading to ubuntu 19.10, vulkan support when using the intel
card in my laptop is broken. running any of my example vulkan apps shows
the following error:
$ vkcube
vkcube:
/build/vulkan-tools-IZAxVX/vulkan-tools-1.1.114.0+dfsg1/cube/cube.c:3175:
demo_init_vk:
here forever ]
```
it appears to be setting at least some of the environment vars incorrectly,
with the agent pid pointing to nothing:
```
$ export | grep SSH
declare -x SSH_AGENT_PID="3300"
declare -x SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"
$ ps auxf | grep 3
]
```
it appears to be setting at least some of the environment vars incorrectly,
with the agent pid pointing to nothing:
```
$ export | grep SSH
declare -x SSH_AGENT_PID="3300"
declare -x SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"
$ ps auxf | grep 3300
tessa 5950 0.0
t;
declare -x SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"
$ ps auxf | grep 3300
tessa 5950 0.0 0.0 8856 760 pts/0S+ 11:50 0:00 |
| \_ grep --color=auto 3300
$ ps axf | grep keyring
2642 pts/0S+ 0:00 | | \_ grep --color=auto keyr
timidity packages installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0c
.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio
timidity packages installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0c
ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio
/dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio
CurrentDesktop: pop:GNOME
DistroRelease: Pop!_OS 18.10
vicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio
/dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio
CurrentDesktop: pop:GNOME
Dis
installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0c: tessa
have any timidity packages installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev
packages installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0c: tessa
timidity packages installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0c
ortVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio
/dev/snd/pcmC0D0p: tessa
installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0c: tessa 11703 F
as I don't
have any timidity packages installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaud
```
tessa@viper:~$ fuser -v /dev/snd/pcmC*
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio
/dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio
tessa@viper:~$ pacmd list
Daemon not responding.
```
--
You received this bug notification
have any timidity packages installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/sn
y packages installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0
y packages installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0c: tessa
y packages installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0
y packages installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tessa 11703 F pulseaudio
/dev/snd/controlC0: tessa 11703 F pulseaudio
/dev/snd/pcmC0D0
: tessa 11703 F pulseaudio
+ /dev/snd/controlC0: tessa 11703 F pulseaudio
+ /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio
+ /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio
+ CurrentDesktop: pop:GNOME
+ DistroRelease: Pop!_OS 18.10
+ InstallationDate: Installed on 2018-03
Digging into the pulse config on 18.10, it looks like instead of using
the daemon mode it's trying to setup up some sort of IPC socket, but
this isn't getting run correctly:
tessa@viper:~$ systemctl start pulseaudio.socket
tessa@viper:~$ systemctl status pulseaudio.socket
● pulseaudio.socket
Public bug reported:
I've got guake set to use my system monospaced font (which is Ubuntu
Mono). however, on every fresh login, it resets to some other font until
I go into the guake prefs and unckeck then recheck the "Use the system
fixed width font" box. It seems to remember it's checked, but
hmmm. I tried that, but no dice for me. pulse starts in a terminal, but
nothing in my session sees a sound device still. for the one started in
a terminal, it doesn't respond to kill signals, and needs to be kill
-9d.
I suspect the "/usr/bin/pulseaudio --daemonize=no" process is just
grabbing the
Public bug reported:
After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
works, it no longer shows any of the audio output devices, not even the
builtin HDMI which usually always shows.
Not sure what happened, but this is a major regression and needs to be
fixed. Note that this
other report in the wild: https://askubuntu.com/questions/1085176/sound-
device-lost-after-update-to-18-10
note that their debugging steps don't even work for me, running pacmd
just gets a complaint that the pulse daemon isn't running, even though
it looks like systemd intentionally started it in
note: I'm seeing this issue even though I don't have any timidity packages
installed. so I've opened another report to track that base issue:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714
--
You received this bug notification because you are a member of Desktop
Packages,
did some more digging, found a blacklist for nouveau on my system, which
is necessary to load the switcharoo stuff. removed that, rebooted, now
nouveau loads at boot and nvidia-prime claims it runs correctly, but
it's still working incorrectly. I've narrowed it down though.
when nvidia-prime cats
Public bug reported:
in 18.04, nvidia-prime's "intel" mode doesn't work. it's attempting to
disable the card at boot using the following command:
/bin/sh -c echo OFF > /sys/kernel/debug/vgaswitcheroo/switch
however, that command doesn't work on 18.04, the whole vgaswitcheroo
subdirector is
Just ran into this upgrading from 17.10 to 18.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1769954
Title:
package desktop-file-utils 0.23-1ubuntu3 failed to
Public bug reported:
Looking at the gnome-keyring packages in 17.10, I see the following
files, which should be auto-starting the gnome-keyring ssh agent
service:
/usr/lib/systemd/user/gnome-keyring-ssh.service
/usr/lib/systemd/user/graphical-session-pre.target.wants/gnome-keyring-ssh.service
Public bug reported:
After upgrading to Ubuntu 17.10 and switching to GDM3 for my display
manager, gnome-keyring-daemon doesn't seem to be correctly creating its
auth agent socket.
I get an environment variable correctly set:
⟫ export | grep SSH
declare -x
I'm on 17.10 now, and while it doesn't completely break like it did in
17.04, I'm getting the screen going to sleep within a few minutes of
logging in, after booting with the laptop lid closed. I'm also finding
if I leave the monitor sleeping overnight after doing a screen lock, it
refuses to wake
Public bug reported:
After upgrading to Ubuntu 17.10, the keyboard shortcut to lock the
screen (by default, Win-L) doesn't lock the screen anymore. If I go into
the keyboard shortcuts settings panel and change it, whatever I change
it to does nothing, either. However, the icon in the gnome login
@seb128: yeah, this is my point. I don't think the ticket I was trying
to report with different issues specific to gnome-shell on wayland is
the same as this ticket. It certainly doesn't seem to be solvable by
manually setting anything in gnome-tweak-tool. What should I do when I
already opened a
Note that while gnome-tweak-tool seems to produce expected results for
me under gnome-shell/xorg, it doesn't on gnome-shell/wayland. Under
wayland, no configuration in gnome-tweak-tool seems to stop the machine
from sleeping if the lid is/started closed.
I was trying to report that Wayland
Public bug reported:
Just testing out gnome-shell on Wayland, Ubuntu 17.04. When I close my
laptop lid to just use my external display, the machine sleeps, even
though sleeping on battery power is disabled in power settings. When
running on Xorg, it correctly disables the builtin display and
That definitely seems to help here, thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1351772
Title:
"disable touchpad while typing" doesn't work
Status in OEM
same question but for 17.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1351772
Title:
"disable touchpad while typing" doesn't work
Status in OEM Priority Project:
Still a problem in 17.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1351772
Title:
"disable touchpad while typing" doesn't work
Status in unity-settings-daemon
Public bug reported:
Since upgrading from 16.04 to 16.10, I've noticed the following
regression: screen scaling settings in the unity-control-center screen
panel aren't correctly restored after a reboot or a re-login. I've got
multiple monitors at different scaling factors, so this is quite a
1 - 100 of 105 matches
Mail list logo
