Public bug reported:
please, when you can, do look into this troublesome little issue.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pulseaudio 1:16.1+dfsg1-2ubuntu10
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules:
Public bug reported:
Client no longer connects. previous version had no problem
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager-openvpn 1.8.18-1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
I just upgraded to 21.10, and it affects the Firefox from Snap if FF
isn't using the automatic system theme extension.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579268
Title:
Mouse cursor is
*** This bug is a duplicate of bug 1900334 ***
https://bugs.launchpad.net/bugs/1900334
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Had the same issue but installed and removed "teamviewer" a view days
before upgrading to 21.04. Could user "irc" being left from this former
program installation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The CONFIG_FANOTIFY_ACCESS_PERMISSIONS option is required for certain
security products, like Microsoft Defender for Endpoints, to operate
correctly. As far as I can tell, it causes no overhead (when not
actively using it), in terms of code size or startup time.
It is
Same as above...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908921
Title:
No system tray detected by hp-systray
To manage notifications about this bug go to:
Public bug reported:
Es konnte nicht ermittelt werden, welche Systemaktualisierungen
verfügbar sind
Ein unlösbares Problem trat während der Berechnung der
Systemaktualisierung auf.
Die wurde wahrscheinlich verursacht durch:
* Inoffizielle Software-Pakete, die nicht von Ubuntu
Public bug reported:
on ubuntu 20.10 paprefs does not find modules, as it uses a hardcoded path.
workaround:
cd /usr/lib
sudo ln -s pulse-13.99.2 pulse-13.99
see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531251
strace paprefs 2>&1 |grep /lib/pulse
Public bug reported:
I can't reliably reproduce this crash, and I don't know, even
approximately, what's causing it, or what I might be doing to possibly
cause it. It just randomly crashes, and dumps me back to the login
screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg
the UI btw would be "certutil"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862331
Title:
[upstream] mozilla cert8.db and key3.db are denied by apparmor
To manage notifications about this bug go
well, obviously the firefox profile is used because NSS wants to find
its certificates for digital signing.
I would also argue that it shouldn't request "w" permissions, but "r" is
expected.
I also suggested using ~/.pki/nssdb but...
16:41 < _rene_> is there any plan to be able to use
Public bug reported:
same issue on groovy on my Lenovo T14 AMD.
https://bugs.archlinux.org/task/68313
already fixed upstream
https://github.com/alsa-project/alsa-ucm-conf/issues/55
** Affects: alsa-ucm-conf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
FYI:
It seems that the issue is still present in the currently available
focal/universe packages:
virt-manager 1:2.2.1-3ubuntu2
If you run into this issue, like I did, the upstream version like Christian
Ehrhardt mentioned above is needed.
See also:
Public bug reported:
to reproduce:
install gtk-3-examples on a system with software rendering, like virtualbox.
run gtk3-demo --run=glarea
observe black boxes.
I fixed it upstream with this commit:
https://gitlab.gnome.org/GNOME/gtk/-/commit/69334021a22a79f5fddb30f0872fcf3fc6bc1cf0
** Affects:
It is hard to feel any enthusiasm from Ubuntu to backport the fix.
Considering how many issues I have run into trying to use Ubuntu WSL image, I
am not sure Ubuntu has any real interest in WSL. Just like Apple is not really
into that boot camp thingy.
--
You received this bug notification
I tried the mainline kernel and the error is gone. What next?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874464
Title:
NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
To manage
here comes the error:
[ 60.259403] [ cut here ]
[ 60.259405] NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
[ 60.259416] WARNING: CPU: 6 PID: 0 at net/sched/sch_generic.c:447
dev_watchdog+0x258/0x260
[ 60.259417] Modules linked in: vboxnetadp(OE)
I can confirm this error on my system after upgrade from bionic to
focal. System works "normaly" but error appears in the logs.
Adding "pcie_aspm=off" does not help in my case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What is the expected latency for it to reach Bionic? 1.5 months has passed
since...
I think there is no real benefit if it gets released in 2023 :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I am creating snapshots of my /-subvolume and use send | receive for
incremental transferring. Sometimes I get errors like "ERROR: cannot
open /media/Backup/OS/snapshots/snap_2020-05-13_11:39/o13170-19818-0: No
such file or directory" When I look deeper with the -v option, it
Public bug reported:
My laptop has a 4K display.
Default Resolution = 3840x2160, scale = 200%.
If I set resolution to 1920x1080, everything on the desktop is scaled to double
size.
So, if I reduce the Scale setting from 200% to 100%, I would expect everything
to look normal again, but it does
Re #42; pardon; machine-confusion. The problem with 4.15.0-72 indeed but
on a Xeon E5606, AMD HD 5770 graphics
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776616
Title:
Ubuntu 18.04 getting
Re #41, "Can anyone else confirm?"
For me and for a few other reports out there, the problem *started* with
4.15.0-72. Core 2 Duo with old G45 onboard graphics.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm also facing the same problem and I found a solution which worked for
me on amd64. My system is using UEFI without secure boot from a gpt
partitioned drive.
Please try to install the package shim-signed.
This fixed the problem for me. Chainloading Windows even works after
uninstalling the
Public bug reported:
The startscript /usr/games/glhack is not passing the command line
arguments to the executable.
The script currently reads:
#!/bin/sh
exec /usr/lib/games/glhack/glhack
but it should be:
#!/bin/sh
exec /usr/lib/games/glhack/glhack "$@"
Then all those command line
The game, by default (without command line options), starts fullscreen
in 800x600. This turns off my left and right monitor and makes my
central monitor complain about the rather outdated resolution.
The ability to pass the "--windowed" command line option this program
didn't work very well on my
I have the same issue and the upstream patch fixes it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822048
Title:
cluster report not displayed
To manage notifications about this bug go to:
Is this still considered an issue?
I booted ami-0bc11fa490cf2ead7 (ubuntu/images/hvm-ssd/ubuntu-
xenial-16.04-amd64-server-20190204.3) on an m5.large in eu-west-1 and it
was fine.
** Attachment added: "kern.log"
Public bug reported:
I'm pretty sure this might be related to bug #1769397.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
.tmp.unity_support_test.0:
ApportVersion:
he order, so that LXQt prefers the plain gtk3
> VCL > plugin over the gtk3_kde5 one.
>
> Any other opinions on this?
I disagree. It's Lx*Qt*, so one should prefer the qt5 plugin. But does
it have a file picker?
Regards,
Rene
--
You received this bug notification because you are a memb
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1814069/+attachment/5234593/+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/1814069
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1814069/+attachment/5234588/+files/CurrentDmesg.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/1814069/+attachment/5234594/+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/1814069
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1814069/+attachment/5234595/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1814069/+attachment/5234592/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected uec-images
** Description changed:
Ubuntu stuck on booting on HyperV Server 2008R2.
I saw kernel messages, seems to load ram image the boot is stuck.
Seems to be a problem with hyperv drivers propably harddrive.
Reverted back to the
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1814069/+attachment/5234589/+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/1814069
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1814069/+attachment/5234591/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1814069/+attachment/5234590/+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/1814069
Kernel Version linux-image-4.15.0-44
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814069
Title:
kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
To manage notifications about
Public bug reported:
Ubuntu stuck on booting on HyperV Server 2008R2.
I saw kernel messages, seems to load ram image the boot is stuck.
Seems to be a problem with hyperv drivers propably harddrive.
Reverted back to the previous kernel.
Description:Ubuntu 18.04.1 LTS
Release:
Public bug reported:
System info:
Description:Ubuntu 18.10
Release:18.10
bro:
Installed: 2.5.4-1build1
Candidate: 2.5.4-1build1
Version table:
*** 2.5.4-1build1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64
Packages
So glad I took the time to report this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789097
Title:
winbind does not work after reboot on Mint 19 / Ubuntu 18.04
To manage notifications about this
Hi Brian,
thank you for providing this fix. It works fine on a minimal 18.10 server. I
installed systemd 239-7ubuntu10.5 on a updated system.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of
I just checked 18.10 with systemd 239-7ubuntu10.4 and it fails with the
same error message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804603
Title:
systemd-tmpfiles-setup.service fails on
** Attachment added: "apt log with 'Bad file descriptor' error"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+attachment/5218416/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I did some tests. This issue is clearly related to btrfs, because I can not
reproduce this with ext4. If you have a different filesystem, you have a
different issue, maybe the one in https://launchpad.net/bugs/1804847.
How to reproduce this:
1) clean install from
Yes but only because they have reverted the changes from CVE-2018-6954. This
will come back very soon. Have a look at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.10 and
https://launchpad.net/bugs/1804847 .
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6954
Could someone please have a look at https://launchpad.net/bugs/1804603
because the changes made to fix CVE-2018-6954 break systemd-tmpfiles
also in a different way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In our network setup systemd-networkd fails to configure everything
correctly. Our systems have two NIC which are configured via DHCP. One
NIC is in a service network without a default route. With this setup we
get systemd-networkd-wait-online.service failing after timeout
Public bug reported:
After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service
fails with:
Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and
Directories...
Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory
or subvolume "/var":
My vintage MacBook4,1 is obviously also affected by this:
[0.00] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR* [CRTC:41:pipe B] flip_done timed out
[0.00] [ cut here ]
[0.00] vblank wait timed out on crtc 1
[0.00]
(In reply to Ville Syrjala from comment #78)
> Fixes posted:
> https://patchwork.freedesktop.org/series/52378/
Awesome, big thanks! Works for me, tested on MacBook4,1
https://www.youtube.com/watch?v=GqH21-KcFzU
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I also tested last kernel from mainline (following #25 & #26 ,just for
confirmation...)
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19
modinfo rtl8723be says:
filename:
/lib/modules/4.19.0-041900-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723be/rtl8723be.ko
firmware:
I tested last proposed kernel 4.15.0-39, but the issue is still there, no
signal with either no ant_sel, ant_sel=0, ant_sel=1 or ant_sel=2.
In my environment the last working kernel is 4.15.0-32 with ant_sel=2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Upstream seems silent; bug remains in NEW state and no follow-up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789097
Title:
winbind does not work after reboot on Mint 19 / Ubuntu 18.04
To
Actually, no, that doesn't work for me. Was expecting it would given the
comments on the samba bug, but, well, no. It *does* work to send HUP
once booted:
rene@t5500:~$ ping WD-NETCENTER
ping: WD-NETCENTER: Name or service not known
rene@t5500:~$ sudo kill -HUP $(systemctl show winbind -p MainPID
As to the reply you got on
https://bugzilla.samba.org/show_bug.cgi?id=13607, I can deny a "net
cache flush" doing anything to get WINS name resolving going for me when
booted with the original service file:
rene@t5500:~$ ping WD-NETCENTER
ping: WD-NETCENTER: Name or service not known
** Attachment added: "winbind.service-working"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185183/+files/winbind.service-working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
oned "wins
server" configuration will be the difference. I never expected my
/etc/samba/smb.conf to be relevant since mine is fully vanilla, as
provided by the "samba-common" package. It is also attached, but:
rene@t5500:~$ debsums samba-common | grep /usr/share/samba/smb.c
** Attachment added: "log.winbindd-working"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185181/+files/log.winbindd-working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "winbind.service-nonworking"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185184/+files/winbind.service-nonworking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "log.winbindd-nonworking"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185182/+files/log.winbindd-nonworking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oh, and the mentioned vanilla smb.conf...
** Attachment added: "smb.conf"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185185/+files/smb.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
I have difficulties trying your test kernel.
maybe because I use signed kernel with secure boot ?
In the instruction you talk about
linux-image and linux-image-extra .deb packages
linux-image-extra is not in folder.
image is unsigned, and do not install.
So I installed headers, modules,
Just to add: the issue's the same and fully constant on an Intel Xeon
E5606 @2,13GHz with 8GiB running Mint 19 Cinnamon 64-bit, and an Intel
Core 2 Duo E8400 @ 3GHz withj 4GiB running Mint 19 Xfce 64-bit.
That is... it's not a subtle race and I assume anyone will see this if
installing only
Yes, the network itself comes up fine. "Does not work" simply means that
NetBIOS name resolution is unavailable even after it does; that e.g.
"ping NAS" for "NAS" the NetBIOS name of my, well, NAS, tells me the
name cannot be resolved.
There would not appear to be relevant logs nor configuration
I have hp-15-ac167nf with wireless chip rtl8723be and ubuntu xenial
16.04 LTS and HWE.
I got same issue: module rtl8723be option ant_sel=2 is not working
anymore from kernel 4.15.0-33.
As a workaround I boot previous kernel 4.15.0-32 (from grub menu).
On same PC, I tried ubuntu bionic 18.04, and
Public bug reported:
[copied from the Linux Mint forum]
Just installed Mint 19 and noticed a WINS name resolution buglet. I
assume this applies to Ubuntu 18.04 as well.
Windows, i.e., NetBIOS, name resolution is on Linux provided for by the
"winbindd" daemon, part of the Samba suite. One does
Public bug reported:
# lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
# apt-cache policy environment-modules
environment-modules:
Installiert: 4.1.1-1
Installationskandidat: 4.1.1-1
Versionstabelle:
*** 4.1.1-1 500
500
I've run into the same problem.
Yes, a "plugin"-type system would solve the problem.
To get in on par with other Xorg config stuff, it should be able to read
system wide configurations provided by the admin, but possibly also
enable user specific layouts from their home directory (so i don't
Public bug reported:
i don't know if this is allowed, but it's by far the most efficient way
to report my bug to multiple development teams..
my entire computer crashed into a pulp yesterday, when i changed 1 simple
setting in compiz while running cairo-dock as a window-manager/desktop
Public bug reported:
Locally modified keyboard layouts are overwritten on package upgrades
(in my case from 16.04 to 18.04) without asking if the user wants to
keep the local version or install the maintainers version.
This leads to problems and extra work for the system administrator.
The
Yes, i had to fiddle around quite a lot with the package manager to get
everything going again and it all works now (the apport information
above is from after the upgrade).
That doesn't change the fact that a do-release-upgrade shouldn't just
fail in the middle and give up. In my opinion, it
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176442/+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/1787411
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176445/+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/1787411
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176441/+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/1787411/+attachment/5176444/+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/1787411
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176443/+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/1787411
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176440/+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/1787411
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176439/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176436/+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/1787411
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176438/+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/1787411
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176437/+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/1787411
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176434/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176435/+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/1787411
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176433/+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/1787411
Title:
apport information
** Tags added: apport-collected bionic
** Description changed:
On one of my computers, do-release-upgrade from 16.04 LTS to 18.04 LTS
broke mid-update.
Logfile seems to indicate that the "doc-base" package is to blame:
2018-08-16 14:02:43,476 INFO cache.commit()
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1787411/+attachment/5176432/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+attachment/5176333/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787411
Title:
** Attachment added: "screenlog.0"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+attachment/5176335/+files/screenlog.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787411
Title:
** Attachment added: "xorg_fixup.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+attachment/5176336/+files/xorg_fixup.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787411
** Attachment added: "apt.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+attachment/5176331/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787411
Title:
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+attachment/5176334/+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/1787411
Title:
** Attachment added: "apt-term.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787411/+attachment/5176332/+files/apt-term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787411
Public bug reported:
On one of my computers, do-release-upgrade from 16.04 LTS to 18.04 LTS
broke mid-update.
Logfile seems to indicate that the "doc-base" package is to blame:
2018-08-16 14:02:43,476 INFO cache.commit()
2018-08-16 14:02:43,476 DEBUG failed to SystemUnLock() (E:Not locked)
Public bug reported:
I upgraded one of my desktops from Xubuntu 16.04 LTS to 18.04 LTS. This
broke alsa/pulseaudio, because the upgrade failed to install the linux-
modules-extra-* package.
Before the upgrade, sound worked fine, after the upgrade pulseaudio only
showed the infamous "Dummy
Patch for evdev.xml
** Patch added: "evdev.xml.patch"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1787354/+attachment/5176179/+files/evdev.xml.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I'm a software developer writing quite a lot of code.
The way the german keybooard is layed out, some essential keys like
brackets and backslash are very awkward to type (right hand holding Alt-
GR in bottom row and pressing the key right of the 0-key in top row to
get a
1 - 100 of 552 matches
Mail list logo
