When I installed noble on other machines I found that removing the
/var/log/ntpstats directory before I started meant this bug did not
occur.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2082084
Titl
Public bug reported:
When using locally mirrored repositories of Ubuntu ESM packages in
20.04, upgrades are picked up by software updater but being reported as
needing to enable pro in settings (see screenshot). Client machines are
attached to Ubuntu Pro but no additional services are enabled.
Al
Public bug reported:
during do_release_update to 24.4.1
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: ntpsec 1.2.2+dfsg1-4build2
ProcVersionSignature: Ubuntu 5.15.0-122.132-generic 5.15.163
Uname: Linux 5.15.0-122-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvp
Public bug reported:
it simply reported "Installer crashed". The last message I saw before
it crashed was "creating user 20%".
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubiquity 24.04.5
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
Nonfre
Here is the danger of this bug on a laptop (as I've experienced):
The system, from all appearances looks powered down (with the exception
of the power indicator which remains lit on my laptop). Unfortunately,
the power indicator is not in a conspicuous place which means that in
order to *verify*
I've confirmed that by rolling back to a prior kernel
(5.11.0-46-generic), the system shuts down normally.
Temp work around I used was to
>sudo vi /etc/default/grub
GRUB_DEFAULT=0
#GRUB_TIMEOUT_STYLE=hidden <-- comment this line
GRUB_TIMEOUT=10 <-- change this line to a value between 5 and 10
GR
I believe I'm having the same issue as well. Have tried both GUI and
terminal commands.
Ubuntu 20.04.3
Uname: 5.13.0-27-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958724
Title:
System
As an earlier faculty scholar, I understand how tough dealing with
admission paperwork may be. Regardless of the essay form, you happen to
be necessary to submit, it may acquire a whole lot of your time when you
are hoping to do it all by yourself. To minimize emotional tension and
help you save so
Public bug reported:
Release of Ubuntu: Ubuntu 18.04.5 LTS
Architecture: aarch64
Package version of libzstd-dev: 1.3.3+dfsg-2ubuntu1.2
Ubuntu 18 has libzstd 1.3.3 which doesn't initialise the variable
"legacyVersion" before use. You can see in the function
ZSTD_deco
Sorry I was not clear enough.
When I said "Filled with" I meant that they were the files occupying space. I'm
sorry if that gave the idea that the corresponding vmlinuz-* files weren't
present - it was just that in terms of bytes occupied, the initrd files are the
big ones.
As you can see from
Ok, did it.
That's freed up a load of space.
Where would I file the bug about having two sets of kernels?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra pa
I've not yet found a way to make a USB boot that would allow me to start
the machine in the event of something going wrong. Without a plan to
revert the change, I'm a bit nervous. I know it *should* work fine - but
I don't want to suddenly have an unbootable laptop I can't rescue.
--
You received
Thanks for that advice.
I'm a bit in trepidation about removing the default HWE. How do I protect
myself from having an unbootable system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
And then I tried "sudo linux-purge --keep=1".
That has tidied up a bit, but there's still not much space?field.comment=And
then I tried "sudo linux-purge --keep=1".
That has tidied up a bit, but there's still not much space.
Now /boot contains:
# du -sh /boot/*
248K/boot/config-5.10.0-1038-oe
Here is the result of linux-purge --info
My /boot is like this:
# du -sh /boot/*
248K/boot/config-5.10.0-1038-oem
248K/boot/config-5.10.0-1044-oem
248K/boot/config-5.11.0-25-generic
248K/boot/config-5.11.0-27-generic
244K/boot/config-5.8.0-63-generic
48M /boot/efi
8.0M/
I managed to get some free space back on /boot.
I'm posting this in the hopes that what I did may inform any fixing process.
1) List kernels with `dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+'`
2) Delete the oldest initrd with update-initramfs -d -k 5.8.0-59-generic. There
was now 111Mb free
I have now run linux-purge. It only freed up 50Mb or so, and no kernels
got removed
** Attachment added: "Directory listing for /boot"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+attachment/5512828/+files/slash-boot-contents-post-linux-purge.txt
--
You received th
Ok, more information. Just got warned that /boot is full again.
I have attached a directory listing for /boot.
Where do I find the logs for the update process that's doing this?
** Attachment added: "Directory listing for /boot"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/16
This was a fresh install of 20.04. I enabled encryption as it's a work laptop.
I don't think I have logs - just the failure due to /boot being full on the
update UI.
I then followed the instructions at
https://help.ubuntu.com/community/RemoveOldKernels under "Safely remove old
kernels" so I coul
Just ran in to this on Ubuntu 20.04, with an encrypted root partition. The
partition layout is the one automatically generated when you install and ask
for root partition encryption - I didn't mess with it.
Drive is 512Gb NVME
Machine is a Lenovo Thinkbook 15
Kernel 5.8.0-59-generic
The /boot pa
Upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4112
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925683
Title:
Cursor Tracking with Gnome Shell Magnifier on Wayland
To manage n
Public bug reported:
Affected version
GNOME 3.36 - 3.40.
Ubuntu 20.04, 20.10, 21.04 and Fedora 34 Beta.
Wayland only.
Bug summary
When running GNOME shell with Wayland, the cursor and focus tracking
functionality of the magnifier (a11y feature) do not correctly compute the
cursor/focus location.
Hello; I am also trying to make this work. I'm get the same Java error,
and trying to run down the comments about 6.1. This is what I see:
(base) cuz@ubuntu:~$ uname -a
Linux ubuntu 5.8.0-48-generic #54~20.04.1-Ubuntu SMP Sat Mar 20 13:40:25 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
(base) cuz@ubun
Public bug reported:
During Install of Ubuntu, the installer crashed before complete.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zc
Public bug reported:
Previous installation: Xubuntu 18.04.5 LTS 32bit kernel
- Removed SDA1 /root partition using installer
- Created new /root partition at SDA1
- Created EFI partition SDA5
- /Home partition on 500G HDD
- /storage partition on 1.2T HDD
After entering configuration information i
Just experienced this bug on Xubuntu 20.04.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762248
Title:
WiFi connection suddenly drops
To manage notifications about this bug go to:
https://bugs.
Public bug reported:
The mouse tracking when using the Gnome shell magnifier doesn't work.
Text cursor and focus cursor tracking works fine.
To re-poroduce enable the magnification by pressing Super + Alt + 8.
Move the mouse around and observe the magnified view remaining in one
place. The magnif
Public bug reported:
If talkd server is configured, utalk immediately crashes. I'm using Ubuntu
20.04 with utalk 1.0.1.beta-8build3 amd64. If talkd server is not configured, I
get a normal could not connect message and it exits. When the server is
configured, I see the following output:
(~)(mas
Hi Simone
I have also suffered from the bug that you mention in the past before
suffering from this bug, bug 1870736 and bug 1873403 currently. I might
be wrong, but I think that the bug that you mention might be covered by
bug 1874559.
Kind Regards
Thomas
--
You received this bug notification
Public bug reported:
Upgraded to beta release of 20.4 and Nautilus file manager now is
exhibiting a problem reported in older versions. When clicking on
folders in the left side window the folder will be dragged to where ever
the mouse is moved. The work around is to click once move slightly the
OK, thank you for your help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871067
Title:
libreoffice doesn't start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
Fixed it!
The problem is caused by the package `mesa-opencl-icd` or one of its
dependencies.
I removed this package and its dependencies and now LibreOffie works
fine.
I'm not sure if this is a bug or expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
> So you fixed the discord issue and then were able to launch your
libreoffice (original deb version) and it displayed?
No, so far I have been able to get the version installed from the
repository (debs) to work.
I've removed the Discord snap to try and ensure it is not causing a
problem. But thi
I uninstalled LibreOffice and tried the snap version. Which works fine.
I uninstalled the snap version and re-installed via apt. But it still
fails to start.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
I've fixed the Discord issue. Turns out it constantly tries to scan for
other applications so it can show what game you are playing. I'll
reboot and give it a try though.
I have noticed that after trying to launch LibreOffice my system memory
usages goes crazy. At the desktop after a reboot my sy
OK, done.
The square the middle of the screen was when I launched from the
application menu and hasn't happened again.
I've noticed that if I try to reboot after attempting to launch
libreoffice, my system will hang.
** Attachment added: "journalctl-output.txt"
https://bugs.launchpad.net/ubu
Hi, I didn't explicitly install it. I performed a regular none-minimal
installation. I've attached the output of the command requested.
** Attachment added: "libreoffice-pkgs.txt"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1871067/+attachment/5347882/+files/libreoffice-pkgs.txt
Here is a list of installed snaps too.
** Attachment added: "instlled-snaps.txt"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1871067/+attachment/5347883/+files/instlled-snaps.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Appears to work fine in a VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871067
Title:
libreoffice doesn't start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
Public bug reported:
None of the LibreOffice applications will start. I've tried from the
application launcher and terminal.
There is no output from the terminal.
Sometimes I get a white square in the centre of the screen.
I can't find any log files in order to get any useful details. Is there
*** This bug is a duplicate of bug 1850654 ***
https://bugs.launchpad.net/bugs/1850654
** This bug has been marked a duplicate of bug 1850654
update-initramfs complains of missing amdgpu firmware files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug appears to have been fixed at some point in the development of
gnome 3.6, still present in 3.4 on Ubutnu 19.10 and 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/1831140
Title:
GNOME
Both applications are fine with standard Yaru and Adwaita.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857191
Title:
Dark themes don't work well with highlighted current line in gedit
To manage
Yes, just tested both applications with Adwaita-dark.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857191
Title:
Dark themes don't work well with highlighted current line in gedit
To manage notif
I've attached a screen shot from a program called Ghidra. It is a Java
application and so it may be that it is a different issue. But it is
using the GTK theme and the colours look the same as gedit.
** Attachment added: "Screenshot from 2020-04-02 22-42-48.png"
https://bugs.launchpad.net/ubun
The same issue happens with other applications too. It's not just gedit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857191
Title:
Dark themes don't work well with highlighted current line in ged
Public bug reported:
In some applications the contrast between the background and text colour
is very poor when using the Yaru theme in "Dark Mode".
For example, If the theme is set to Dark via the settings application
under "Appearance" and gedit (GNOME Text Editor" is launched. The
background o
Tested, looks to have done the trick. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869671
Title:
plymouth missing plugin label.so
To manage notifications about this bug go to:
https://bug
I did search for existing bugs but didn't find anything that wasn't old.
My apologies If I've missed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869671
Title:
plymouth missing plugin label.s
Public bug reported:
On a clean install of Ubuntu 20.04 the following messages are printed
while updating the initramfs.
update-initramfs: Generating /boot/initrd.img-5.4.0-18-generic
W: Possible missing firmware /lib/firmware/amdgpu/navi12_gpu_info.bin for
module amdgpu
W: Possible missing firm
Public bug reported:
When updating the initramfs the following warnings are output.
update-initramfs: Generating /boot/initrd.img-5.4.0-18-generic
W: plymouth: The plugin label.so is missing, the selected theme might not work
as expected.
W: plymouth: You might want to install the plymouth-theme
Public bug reported:
Affected version
Tested with Ubuntu 20.04 current daily build using Xorg. Mutter version
3.36.
Bug summary
When using the GNOME magnifier feature ghost copies of dialogues such as
the Alt+F2 window or the password prompt appear if the magnified view
moves away from the dial
Public bug reported:
Error occurs after pin for the PIV card is entered into the GNOME login GUI.
Error in /var/log/messages:
gdm-session-wor[23783]: segfault at 0 ip 7f3e851589ab sp 7ffd2e747300
error 6 in libcrypto.so.1.1[7f3e84f6a000+29b000]
Remove "crl_online" from cert_policy in /et
Public bug reported:
N/A
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-release-upgrader-core 1:19.04.16.9
ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
Uname: Linux 5.0.0-38-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.3
Architecture: amd64
CrashDB: ubuntu
Date: Thu Fe
Public bug reported:
After prompting me to restart for updates, Firefox no longer starts. If
started from terminal, I am told it has segfaulted.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 70.0.1+build1-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
U
Public bug reported:
occurred during 10.10 upgrade from 19.04
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: nvidia-340 340.107-0ubuntu6
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvp
Posted alsa-info.sh to http://alsa-
project.org/db/?f=aea8019642712707b206b1ebf30ceada504b58c2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807138
Title:
[ALC256 - Razer Blade 15 2018] Headphones
OK, stopped working again today. I think I undid everything I've been
testing with hdajackretask (i.e. removed boot override) yesterday while
it was still working and double-checked it today.
Here are the results from hdajacksensetest:
mclark ~ sudo hdajacksensetest -a //no headphones
Pin 0
Just an FYI, the netcat -U /var/run/acpid.socket is now seeing the
headphone jack event. Everything appears to be working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807138
Title:
[ALC256 - Raz
Private bug reported:
Microsoft office 365 setup is providing complete cloud-based productivity
package across the globe.Sign on to office.com/setup and download
office.com/setup365 personal record now.After foundation of the setup, open any
MS Office application, and enter the thing key for in
Public bug reported:
unable to acces the requested logs
system won't allow to open secondary click menu, keyboard shortcut{ctl-alt-T},
nor activities access.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux
Upstream bug is here: https://gitlab.gnome.org/GNOME/mutter/issues/625
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #625
https://gitlab.gnome.org/GNOME/mutter/issues/625
** Description changed:
When using the GNOME magnifier (Zoom) feature the magnified display
- flickers when u
I've tested the updated package in the PPA and all the settings now work
as expected. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831144
Title:
GNOME control center UI does not update
Also tested on Fedora 30, the issue exists but manifests slightly
differently.
Should I raise this upstream? If so which GNOME project should it be
raised against?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Yep, I will test as soon as I get home tonight.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831144
Title:
GNOME control center UI does not update dconf setting for magnifier
mouse tracking m od
Completely removedd all extensions include those shipped with Ubuntu
19.04. Issue still occurs. Also tested with a clean install in VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831140
Title:
G
I couldn't figure out why I didn't see the issue in my VM. But
additional testing shows the issue in the VM. It depends on which
windows are visible. If you close all windows and return to the desktop
it always occurs.
Also enabling the 'Magnifier extends outside screen' checkbox also
causes the i
I've had a stab at working out what the problem is. I have an idea which
I have posted to the upstream bug report. But I've no way to test this
out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183114
OK, opened a new bug upstream under the correct project this time.
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/555
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #555
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/555
--
You received this bug
Both of my machines are now on 19.04, I'm still seeing the issue. I've
got all extensions turned off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831140
Title:
GNOME Magnifier Flickering when usi
OK, turns out my laptop is on 18.10 not 19.04. I assumed the upgrade
would go all the way but I was wrong. :(
I'm upgrading now and will test again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18311
Turns out I already reported this on the GNOME gitlab a while back but
have had no reply. I've updated it with the new information I've
learned. Here is the link: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/865
I've looked at the commit but it's not immediately obvious to me why it
isn't wo
Here is the lspci output from my laptop.
** Attachment added: "lspci -k output (Dell XPS 3630)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831140/+attachment/5268096/+files/dell-xps-lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I've attached the requested output.
I have done additional testing today on my Dell XPS laptop running
Ubuntu 19.04, my personal desktop running 18.04 and my work PC running
18.04.
* I removed all extensions, uninstalled packages for those that had them or
deleted via the gnome extension website
Tested on physical hardware with 19.04. The issue is still present but
the viaul manifestaton is slightly different. Rather than black flickers
it's more of a shading effect that flickers on and off with mouse
movement. It can also be caused by enabling the option to extent the
magnified contents b
Tested in an 19.04 VM and the issue deos not appear to be present. I
will test on real hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831140
Title:
GNOME Magnifier Flickering when using no
Public bug reported:
If you attempt to change the mouse cursor tracking mode in the gnome
control centre UI for the gnome magnifier the radio buttons have no
effect. If yous use dconf-editor to manual change the option at:
org.gnome.desktop.a11y.magnifier.mouse-tracking the setting will have an
ef
Public bug reported:
When using the GNOME magnifier (Zoom) feature the magnified display
flickers when used in any of the following modes: Left, Right, Top or
Bottom screen part. This occures when the mouse moves towards the edge
directly opossite to the magnified view.
To reproduce:
* Open GNOME
Cool, I will try that!
As a heads up though, this sound quality is only after uninstalling and
reinstalling pulse audio and maybe something else (apologies for not
giving better details there, I didn't think to submit a bug until I ran
out of things to try). Before I did that, a voice recorded by
Ya, here's a quick wav file I just recorded with arecord.
** Attachment added: "Recorded with internal microphone"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827440/+attachment/5261539/+files/filename.wav
--
You received this bug notification because you are a member of Ubun
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261101/+files/WifiSyslog.txt
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You receive
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261096/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/182
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261100/+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/1827440
Title:
[X
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261092/+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/1827440
Title:
[X1
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261095/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261099/+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/1827440
Title:
[X
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261094/+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/1827440
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261097/+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/1827440
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261098/+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/1827440
Titl
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261093/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827440
Title:
[X1
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261091/+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/1827440
Title:
apport information
** Tags added: apport-collected
** Description changed:
Hopefully all the necessary info is in the extra stuff that
automatically got sent.
Basically, I didn't do anything fancy, but audio recorded with my
microphone (through Skype, and arecord in the Terminal) has
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261089/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827440
Title:
[X1 Ca
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1827440/+attachment/5261090/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827440
Public bug reported:
Hopefully all the necessary info is in the extra stuff that
automatically got sent.
Basically, I didn't do anything fancy, but audio recorded with my
microphone (through Skype, and arecord in the Terminal) has tons of
static and the voice is distorted or saturated.
Booting t
Since it's still not working on 19.04, guess that answers my question as
to whether to upgrade or not. I've confirmed that the acpid isn't
seeing the plug in event by running:
netcat -U /var/run/acpid.socket
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am using Xubuntu 18.10 and I find that the delete key does not function at
all, unless an image is opened in a separate window.
I have re-compiled Geeqie v1.3 with 18.10 and I find the same problem, so I
suspect the problem is originating outside Geeqie.
I have only an ancient laptop with me at
Confirmed the fix is working. I'm running Virtualbox 6.0.6 on an Ubuntu
18.04 LTS host, to build an Ubuntu 16.04 VM guest.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818049
Title:
virtualbox dkm
Verified package 3.28.3+git20190124-0ubuntu18.04.2 does fix the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767648
Title:
Top bar and shell dialogs are not displayed properly when zoom is
Adding --background to the start-stop-daemon command in the init script
seems to get around the issue.
start-stop-daemon --background --start -c tenshi --pidfile $PIDFILE
--startas $DAEMON -- -P $PIDFILE
This is documented as a "last resort" by start-stop-daemon. Maybe there
is a better solution.
1 - 100 of 1428 matches
Mail list logo
