I believe this is still an issue, given you're running Wayland and
HiDPI, as that combo seems to tie cursor config to the scaling of the
specific window, not to the desktop as a whole. so it may be unrelated
to kwin and more just specific to scaling+wayland.
in any case, I no longer use either KDE
another person bit by this on LTS and wondering why it never got fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868517
Title:
Stray /usr/.crates2.json file
To manage notifications about this
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 o
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 beca
note that I've switched to using pipewire to replace pulse, and it
doesn't have this problem. so this is definitely a pulse specific issue.
thankfully pipewire is mature enough to use full time now, and I'd
recommend folks experiencing this problem give it a shot, since it
offers pulse, alsa, and j
as a point of side comparison, the system that was exhibiting this
behaviour was reinstalled with Arch, also running cinnamon, and it
doesn't exhibit these symptoms there. so if you can't replicate this
issue it may have been some one off config error with that specific box.
--
You received this
Public bug reported:
on ubuntu 20.10, "fish help" launches a web help page for the shell, but
it always launches in chrome, not my configured browser (firefox).
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: fish 3.1.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-43.49-lowlatency 5.8.18
Una
I think it's an important use case to support, since it's more than
likely going to be needed once Ubuntu supports ZFS on server installs.
the zfs tools and scripts should definitely be bulletproof'd to handle
any zfs fs configuration, especially around something like this where it
should be easy t
Public bug reported:
I'm finding that the libclc support for current AMD APUs is missing, at
least for Ryzen 4000 series laptop APUs. when running something like
`hashcat -b --force`, you get the following:
clBuildProgram(): CL_BUILD_PROGRAM_FAILURE
fatal error: cannot open file '/usr/lib/clc/gf
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 b
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909703
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 beca
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:
I haven't used cinnamon before, so I don't know if this is normal, but
there's tons of apps which relay on system tray functionality that don't
show up in the cinnamon tray. For example: telegram, barrier, ipfs-
desktop, discord, etc.
These apps all show up correctly in the g
it's also worth noting that a small minority of icons do show up.
syncthing, guake, and ibus all show up correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909172
Title:
cinnamon tray doesn't
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
awesome, glad to hear it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906137
Title:
gnome-shell on 20.1
*** 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 membe
*** 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 cras
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 deskto
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 ha
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 w
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 a
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901286
Title:
gnome-disk-image-mo
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
nautilus_sel
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 be
awesome, as long as 4.4.1 is up to date I'm fine to close this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905163
Title:
krita <= 4.3.0 crashes in multimonitor setups due to a qt monitor
handl
fixed in 21.04
** Changed in: krita (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to krita in Ubuntu.
https://bugs.launchpad.net/bugs/1905163
Title:
krita <= 4.3.0 crashes in multimonitor setups
note that I've also verified using the upstream PPA to install
krita-4.4.0 fixes this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905163
Title:
krita <= 4.3.0 crashes in multimonitor setup
Public bug reported:
This is an upstream bug that was fixed in June, but didn't make it in
time for the 20.10 release.
https://krita-artists.org/t/4-3-beta-crash-assert-krita-screen-
qguiapplication-screens-size-screen-0/8226/8
I'm experiencing this now on 20.10, which makes sense since the late
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/
additional behaviour I've noticed:
on first boot, when the sound device isn't in use for a while, it stops
sending bitstream data to the receiver, until there's a new audio event.
it seems to be some sort of device sleep mode.
on 20.04, after resuming from sleep, this device sleep mode wouldn't
a
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 Ubuntu
Bugs, which
]: 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
Like I mentioned, the kernel drivers seem fine. It appears to be a
userspace software regression, either in bluez or in the gnome
components that call bluez. the adaptor seems dead after resuming from
sleep, until the gnome bluetooth settings panel is opened. this must
call some sort of refresh fun
Well, that's sort of irrelevant for those of us having this problem. I
just checked, and mine is a Broadcom BCM20702A0, so not exactly a niche
vendor. I'm especially concerned since it seems like it's just not
correctly re-scanning for bluetooth devices after waking from sleep due
to some sort of s
i just had a bug for 20.10 merged into this one. note that in my case,
this just started happening since upgrading to 20.10, and it happens
with multiple different brands of bluetooth adaptor. as well, if use my
keyboard to open the bluetooth settings panel in gnome, then everything
immediately rec
** Summary changed:
- pulseaudio has is buggy with hdmi audio and sleep/wake
+ pulseaudio breaks hdmi audio on sleep/wake in ubuntu 20.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888598
Title:
this is the log after resuming, where no audio devices are available
post-resume except the internal SPDIF. so this bug has gotten
significantly worse in the move from 20.04->20.10.
** Attachment added: "2020-10-26-pulseaudio.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/18885
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
Di
Note that I made the changes you recommended in those files and had used
it for a couple weeks, and it seemed to be behaving as expected. However
after the update to 20.10, it seems to have reverted the changes and now
my sound is broken again, experiencing even *worse* problems with
puleaudio 1:13
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 (udisk
Public bug reported:
my upgrade from 20.04 to 20.10 hung on `libc` with a message that was
something like "checking init scripts". I had to kill it from the
terminal, and then of course the whole upgrade failed. after the upgrade
failed, X repeatedly crashed until I had to log out.
Running `aptit
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"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1891712
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 gather this has been an issue for a long time, but I'm just running
into it now. basically, the nvidia binary drivers, no matter the
version, don't seem to properly handle vsync if you have 2 displays. no
combination of options seems to fix this so that it works correctly,
t
Public bug reported:
I've got nautilus configured to display thumbnails on network shares
(prefs -> search&preview -> 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
Alright, I've read through some of these design docs. it's unfortunate
they're buried in blog posts and not just laid out on an ubuntu site
about zsys and zfs usage on Ubuntu, but at least now I know where they
are.
More to the point, all I've done is watch some movies and download some
games on s
as well, I'd highly recommend a command for zsysctl to purge up to X
number of old states, so that an admin can manually get disk usage under
control if necessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
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 1T
"after resume, the active output device is hdmi-stereo-0 (monitor)?" ->
as I've noted before, for some reason after resume, it switches around
the numbering which output is actually which physical connection. this
is could be the root cause of the issue I'm seeing, but given all the
other weirdness
this is the log entries only post resume. the output is incorrect after
resume, as usual.
** Attachment added: "2020-09-09-pa.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5409287/+files/2020-09-09-pa.log
--
You received this bug notification because you
it appears to, yes. i only tested it a couple times, but it consistently
stayed on the same audio output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888598
Title:
pulseaudio has is buggy with hd
the before and after outputs of catting this card are identical
according to diff, so I've just included the before output here.
** Attachment added: "before.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5407463/+files/before.txt
--
You received this bug
also, I looked for the error you described, and it's not present, but I
do see this:
2539:D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(8) failed:
Invalid argument
2542:D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(8) failed:
Invalid argument
2545:D: [pulseaudio] alsa
after pacmd --list, when the system has woken from sleep, and now is on
the wrong sound output. note that it's not going to the internal sound
card at the moment, but the other hdmi device. even though looking at
the diff, it thinks the default sync hasn't changed, it actually is now
going to the w
before pacmd --list, with the input correctly selected as 5.1 surround
on HDMI / DisplayPort 2.
** Attachment added: "before.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5406020/+files/before.txt
--
You received this bug notification because you are a m
and here's another new wrinkle... it looks like after my machine has
been put to sleep and woken up a few times, it now creates a new dummy
audio device each time, until my system is full of dummy audio devices.
seriously what is up with sleep/wake and pulse in ubuntu 20.04??
--
You received thi
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 and
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"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1891712/+attachment/5401888/+file
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 Ub
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 p
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 ce
I'm seeing another fun intermittent issue after waking from sleep on my
system. sometimes after resume, the audio is really static-y, until i
turn the volume down one notch and back up again. next time it happens
I'll attach the logs again, just to see if there's anything illuminating
there. it onl
ok, made that change. it stayed on the correct input after a reboot, and
after sleep/resume. however, sleep/resume still messes up the device
ordering so i still have to change it to the new "correct" dev after
resume. still. headway! :)
--
You received this bug notification because you are a mem
alright, here's the pa debug log where I did a fresh boot, set audio
from s/pdif to the hdmi audio output, then put the machine to sleep and
woke it, and then set the audio to the other hdmi output device after
the system switched them around.
** Attachment added: "pa.log.xz"
https://bugs.laun
alright, I see on boot, it changing the configured default when I switch
to HDMI audio from p/sdif:
4203:I: [pulseaudio] core.c: configured_default_sink: alsa_output.pci-
_01_00.1.hdmi-surround-extra1 -> alsa_output.pci-_01_00.1.hdmi-
surround
and after suspend/resume, there are no new me
ok, after setting it post-reboot, I see the following setting it as the
default in the logs:
4572:I: [pulseaudio] core.c: default_sink: alsa_output.pci-
_00_1b.0.iec958-stereo -> alsa_output.pci-_01_00.1.hdmi-surround
as well as the following active ports with `pactl list`:
Ports
yep, looks like even after sleep and when things are all messed up,
they're still listed as available:
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency
offset 0 usec, available: yes)
properties:
device
Alright, I just ran the test. When I unplug the hdmi cable connected to
the receiver, it switches to s/pdif. I left it for 30s, then plugged it
back in, and it correctly switched back.
Put it to sleep, woke it up, and the audio outputs were all messed up
again. So it's something that's happening d
I should also note, I tested this issue in KDE, and saw the same issues.
So it doesn't seem to have anything to do with gnome or the gnome-
control-center.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
Fresh install of Ubuntu 20.04, logged into a fresh KDE session.
Increased the cursor size because I'm on a high res display, and noticed
that when the mouse is over a window, the cursor size is correct, but
when it's over the desktop, it's always the default (tiny) size. This
ok, did a dist upgrade, now I'm on kernel 5.4.0-42-generic and gnome-
control-center 3.36.4-0ubuntu1. bugs still persist. notably, after
sleep/resume:
- defaulted to s/pdif audio
- switched hdmi/dp audio outputs, so i have to use hdmi/dp 2 to get audio out,
but it still sees surroundsound only on
ProcVersionSignature: 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
```
root@boxxy:~# apt remove --purge snapd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
libllvm9
Use 'apt autoremove' to remove it.
The following packages will be REMOVE
Public bug reported:
when installed with a zfs root on Ubuntu 20.04, the installer creates a
filesystem for /var/snap. however, the postrm script of the snapd tries
to remove that directory, and it can't, because it's a mounted
filesystem. the script should do the correct thing (destroy the
filesy
@brian-murray: oh! when I first tried it after upgrading, it didn't
spawn the details window or open the web browser link or anything. it
appears to be working now, so it must've just been a fluke. definitely
looks better!
** Changed in: apport (Ubuntu)
Status: Incomplete => Fix Released
-
as far as I can tell, this is still an issue on Ubuntu 20.04.
** Changed in: apport (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997333
Title:
ubuntu-bug ref
OK! Confirmed this was a hardware failure, thanks for helping me look
into it!
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849751
h. further kernel bisecting work has uncovered that I can't get the
video to work properly even with a 19.04 usb key now. so there may be a
hardware failure here at work, I'll need to investigate further. I'll
talk to tech support for my hardware vendor and update this ticket once
I know more.
hmmm ok. testing is proving difficult. I'm running zfs root, and zfs-
dkms won't build on the current 5.4-rc, it does all the config step, but
on build it just says "kernel package linux-
headers-5.4.0-050400rc5-generic is not supported". any suggestions?
--
You received this bug notification bec
Oh damn, didn't realize nomodeset disables *everything* these days.
in any case, I'm on an optimus laptop with both intel and nvidia, and I
can switch between nvidia only, or optimus (both cards active) mode in
the bios. prior to 19.10, things worked fine. but after 19.10, things
have been an utte
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: Assert
Public bug reported:
there are two OCI hooks which should be included in the systemd-
container package, or in their own packages which are recommended by
systemd-container. they allow containers based on systemd as pid1 to run
correctly in unprivileged runtimes based on OCI, such as docker.
http
well, there was ubuntu updates over the last week, and since then I
haven't seen this problem re-occur. I guess we can close and re-open if
it resurfaces, since I can't repro now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
looks like it's not just ssh. when the screen is locked, unlocking the
screen hangs too unless I pop over to another tty and kill gnome-
keyring-daemon. as well, other services which use the keyring, like aws-
vault also hang. (https://github.com/99designs/aws-vault)
does the keyring daemon output
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
Public bug reported:
I'm having a really weird issue since reinstalling Ubuntu 19.04 the
other day. This is on a system76 laptop with a bios toggle between
nvidia prime mode (intel graphics connected to the display, nvidia card
must be trunked through it) and discrete mode (intel graphics
deactiva
Public bug reported:
Trying to freshly install php-libsodium on both Ubuntu 18.04 or 18.10,
causes all php scripts to start throwing the following error:
# php -v
PHP Fatal error: sodium_init() in Unknown on line 0
PHP 7.2.15-0ubuntu0.18.04.1 (cli) (built: Feb 8 2019 14:54:22) ( NTS )
Copyright
pyrit 0.4.0 is already in the ubuntu repos, so this can probably be
closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346312
Title:
[needs-packaging] Pyrit 0.2.1 - Advances in attacking WPA-PSK
ok, I've figured some more out with the help of system76 support:
https://github.com/pop-os/pop/issues/389
the TL&DR is that the issue seems to be caused by the systemd init
scripts, and that stopping them all and running pulseaudio manually
works fine. so this isn't really even a pulse issue, bu
I've already tried reinstalling pulseaudio, and it doesn't do anything.
I can't really afford to reinstall my work laptop right now, I really
need it to just, you know, work. ;)
but I also need working sound so I'm not really sure what to do. is
there really no way to debug pulseaudio and why it's
Booting off USB, sound works fine, soundcards show up correctly. So...
it's something that got messed up in the upgrade from 18.04, I guess?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799007
Title
Ahh yes, there everything is in /dev/snd, so really starting to feel
like a pulseaudio bug.
$ ls /dev/snd
by-pathcontrolC1 hwC1D0pcmC0D0p pcmC1D3p pcmC1D8p timer
controlC0 hwC0D0 pcmC0D0c pcmC0D1p pcmC1D7p seq
I'll try the USB boot thing this aft and get back to you.
--
You
note that the sound devices seem to be correctly detected by the kernel:
[ 28.963298] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=2
(0x14/0x1b/0x0/0x0/0x0)
[ 28.963299] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0
(0x0/0x0/0x0/0x0/0x0)
[ 28.963300] snd_hda_codec_realtek hdaudioC0
yes, that's where I've been looking. nothing listed for input or output
in the sound control panel.
** Attachment added: "Screenshot from 2018-11-02 10-44-35.png"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+attachment/5208409/+files/Screenshot%20from%202018-11-02%2010-44
ahhh well like I said that crash dump was from after uninstalling the
jack packages. things are still broken without jack installed. no sound
in any app.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
1 - 100 of 254 matches
Mail list logo
