Confirmed on Ubuntu 18.04 (clear installation).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1712866
Title:
icons from qt applications disappear after scre
JFTR, in case anyone is looking at this:
The fix for xenial and trusty has been merged into the fix for 1737441,
and was fixed there, as the regression that manifested in this bug due
to the fix for 1737441 never manifested in those releases, as there was
no upload with just that fix.
--
You rec
--- Comment From abhir...@in.ibm.com 2018-09-12 05:05 EDT---
Vorlon,
On investigation, comparing steps , behaviour with Ubuntu and Other
distros, adding below data.
Other distros, nmcli behaviour
Deactivation of bond steps via our script/code:
+
Seems like the point release would be a reasonable SRU.
Mark
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w option
Status
Fine-grained network security for snaps is going to be fantastic, but
it's also a rich area, and when networking policy stuff is done
simplistically it becomes awkward more than useful.
I'd suggest that we start now working up detailed design on the topic,
so that when we are ready to start implem
You have been subscribed to a public bug:
I never experienced problems with corporate servers on 14.04 and 16.04,
but with 18.04 I have to restart systemd-resolved a few times per day.
What I see: Internet addresses are resolved, but corporate ones aren't.
What I do to fix: sudo service systemd-r
@philippe-vaucher
I'm not quite concerned about what other distros do. Imho, it is buggy to not
have `sbin` in the default built-in bash path - so i'd call fedora's bash
built-in path still buggy ;-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
I never experienced problems with corporate servers on 14.04 and 16.04,
but with 18.04 I have to restart systemd-resolved a few times per day.
What I see: Internet addresses are resolved, but corporate ones aren't.
What I do to fix: sudo service systemd-resolved restart. Afte
** Summary changed:
- remove /boot/initrd.img-*.old-dkms files left behind
+ [SRU] remove orphaned initrd old-dkms files in /boot
** Description changed:
[Impact]
If a dkms package is installed which has REMAKE_INITRD or the same setting
has been manually configured by a user then when a ke
Domain-less external/network lookups are not supported.
Domain must be set on DNS Servers: 192.168.200.1
Either change your router settings to set a domain of your choice,
or make one up in /etc/systemd/resolved.conf by changing Domains= setting
If you set a domain, do things start to resolve?
Well, there is not much to say here... and there are no relevant logs.
Maybe look at the journal from last boot?
I.e. $ journalctl -b -1 -e
to see if there is anything intersting Maybe a keyboard key to
shutdown was pressed, or `shutdown now` was typed in the terminal, or
some such.
** Chang
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/796588
Title:
Fine-grained network mediation
Status in AppArmor:
In Progress
Status in apparmo
** Also affects: landscape-client (Ubuntu Cosmic)
Importance: High
Assignee: Dave Jones (waveform)
Status: Fix Committed
** Also affects: systemd (Ubuntu Cosmic)
Importance: High
Assignee: Dimitri John Ledkov (xnox)
Status: Confirmed
--
You received this bug notific
Hello bugproxy, or anyone else affected,
Accepted binutils into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/binutils/2.26.1-1ubuntu1~16.04.7 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
I'm seeing this in Ubuntu 18.04 as well. I have 2 printers configured an
HP LaserJet p4015 and a Canon ImageRunner C5030.
kernel: [35100.990629] audit: type=1400 audit(1536755161.327:158):
apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd"
pid=15321 comm="cupsd" capability=12 capname
attaching xenial sru patch
** Description changed:
[Impact]
If a dkms package is installed which has REMAKE_INITRD or the same setting
has been manually configured by a user then when a kernel is removed its
possible for an ".old-dkms" file to be left in /boot with no associated kernel.
attaching bionic sru patch
** Patch added: "initramfs-tools_0.130ubuntu3.3_debdiff_0.130ubuntu3.4.patch"
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187983/+files/initramfs-tools_0.130ubuntu3.3_debdiff_0.130ubuntu3.4.patch
** Tags added: bionic
--
You received t
attaching cosmic patch
** Patch added: "initramfs-tools_0.131ubuntu10_debdiff_0.131ubuntu11.patch"
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187984/+files/initramfs-tools_0.131ubuntu10_debdiff_0.131ubuntu11.patch
--
You received this bug notification because yo
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1781242
Title:
as segfault with invalid -march=
** No longer affects: gxneur (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1771041
Title:
Remove gconf from Ubuntu
Status in autopilot-legacy package in Ubuntu:
** Description changed:
I'd like to update the toolchain packages in bionic, to state which we
have in cosmic on May 07:
- LP: #1771635: binutils updates from the branch
- gcc-8, update to the final 8.1.0 release
- gcc-7, updates to the gcc-7-branch up to the time of the
8.1.0
Successfully verified on xenial:
ubuntu@hwe0001:~$ apt-cache policy binutils
binutils:
Installed: 2.26.1-1ubuntu1~16.04.7
Candidate: 2.26.1-1ubuntu1~16.04.7
Version table:
*** 2.26.1-1ubuntu1~16.04.7 500
500 http://us.ports.ubuntu.com/ubuntu-ports xenial-proposed/main s390x
Package
Yes. As Bionic is an LTS release, it would be wise to include the
OpenSSL LTS release in it, which is version 1.1.1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1780807
T
Public bug reported:
Description:Ubuntu 18.04.1 LTS
Release:18.04
python2.7:
Installed: 2.7.15~rc1-1
Candidate: 2.7.15~rc1-1
-Python 2.7.15rc1 has the problem below ---
$ python
Python 2.7.15rc1 (default, Apr 15 2018, 21:51:34)
[GCC 7.3.0] on linu
Reinstalled from bionic-updates and confirmed working.
Thanks again to all involved in resolving this!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busyb
Public bug reported:
I haven't verified this, but I believe that ifupdown works through udevadm
hooks.
So udevadm hotplug event -> ifup eth0.
Any subprocesses of a udevadm hook will be restricted by the
systemd-udevd.service
restrictions, which currently are
RestrictAddressFamilies=AF_UNIX AF
** Also affects: binutils (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1763098
Title:
Multiple memory corrup
1.6.2 in 18.04 would be a life saver as I have hit this issue and the
only resolution is to compile iptables myself. I can verify that 1.6.2
resolves this issue and I havn't had any other problems on 18.04 as far
as other tools calling 1.6.2
--
You received this bug notification because you are
This is invalid.
It actually all still works because:
udev hook /lib/udev/rules.d/80-ifupdown.rules calls /lib/udev/ifupdown-hotplug
which calls
systemctl --no-block start $(systemd-escape --template ifup@.service
$INTERFACE)
Then the ifup@.service is what actually brings up the device.
Tha
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/712351
Title:
init: exit not detected with 'ex
Bash regression appears to have been introduced in:
https://git.launchpad.net/ubuntu/+source/bash/diff/debian/patches/deb-bash-config.diff?id=c2fee82da8f6caa77764ac65bb7fc237314915f8
i.e. 4.3~rc1-1 upload to debian/experimental
https://git.launchpad.net/ubuntu/+source/bash/commit/?id=c2fee82da8f6c
The problem resides in virtual machines with some kind of broken
consoles (or not correctly handled ones).
I narrowed down the problem to the the following command that is run on
setupcon:
setfont -C /dev/tty1 /etc/console-setup/Lat15-VGA16.psf.gz -m /etc
/console-setup/cached_ISO-8859-1.acm.gz
Sam, trusty bug from 2017, still an issue?
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: iproute2 (Ubuntu)
Status: New => Incomplete
--
You received
I also agree, given OpenSSL Version 1.1.0 will be supported until one
year after the release of 1.1.1 (i.e 2019/09/11), migrating to 1.1.1 LTS
would be the best course of action for 18.04 LTS (EOL 2023/04):
https://www.openssl.org/policies/releasestrat.html
Quoting from yesterday's 1.1.1 release
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188099/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchp
apport information
** Tags added: apport-collected
** Description changed:
TP-Link Archer T2UH, AC600, version 1
After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows
10 I was immediately able to connect).
So searching on the web I found some kind of "solution", whi
apport information
** Attachment added: "IpAddr.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188102/+files/IpAddr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188101/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
htt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188100/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
htt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188103/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bug
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188104/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "NetDevice.lo.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188107/+files/NetDevice.lo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
htt
apport information
** Attachment added: "NetDevice.ra0.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188108/+files/NetDevice.ra0.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
h
apport information
** Attachment added: "NetDevice.wlp4s0.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188109/+files/NetDevice.wlp4s0.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubu
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188113/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188115/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188114/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188112/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
apport information
** Attachment added: "NetDevice.enp3s0.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188106/+files/NetDevice.enp3s0.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubu
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188116/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://b
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188117/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.lau
This recently happened to me with linux-image-4.15.0-34-generic
see bug #1792213
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1766974
Title:
/dev/dri/card0
Status in xorg
You have been subscribed to a public bug:
Since Ubuntu switched to Gnome, display scaling does not work correctly.
This is because my external monitor is detected as 7" although it is
32". All applications which use Qt auto scaling have huge controls!
It seems like many users have the same proble
apport information
** Attachment added: "nmcli-con.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188120/+files/nmcli-con.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188119/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https:/
apport information
** Attachment added: "PciNetwork.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188111/+files/PciNetwork.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https:/
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188118/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188105/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "NetworkManager.conf.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188110/+files/NetworkManager.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager
Broken auto-scaling is a bug in Qt. If your monitor is incorrectly
detected as 7", there's probably also a kernel or X.org bug somewhere.
** Package changed: vlc (Ubuntu) => qtbase-opensource-src (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
Public bug reported:
affects ubuntu/openssh
Hi,
This bug is present in openssh in ubuntu trusty, I haven't tested other
releases. When X11 forwarding is enabled (via ssh_config, or via -X),
but no DISPLAY is available, ssh client produces this warning:
DISPLAY "(null)" invalid; disabling X11 f
** Also affects: kernel
Importance: Undecided
Status: New
** Also affects: xorg-server
Importance: Undecided
Status: New
** Summary changed:
- Display size detected wrongly
+ Display size detected incorrectly
--
You received this bug notification because you are a member of
@xnox
sudo apt install dracut-core did not work for me.
In my case:
raid md1 was unmounted but raid md0 was not.
raid md0 was mounted to /
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad
And it actually got added as a systemd job.. so this is not actually
fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1503773
Title:
Drop ondemand init script
Statu
Never had this problem until recently, but seems to align with updates
being installed. Using 18.04.1 and yes, "sudo kbd_mode -s" seems to fix
it. Using Dell XPS 9350.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-se
This is still broken, at least on my 18.04. apt-get autoremove does not
touch old kernels. What is the process for re-reporting this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bug
Thanks for the bug report.
1. Can you please run this command on the machine and send us the
output?
xrandr --verbose
2. Please also run this command to send more system information:
apport-collect 1792167
** Project changed: kernel => mutter
** Project changed: mutter => mir
** No longe
Dell AW17R3, Skylake i7-6700HQ, nVidia GTX 970M, Thunderbolt USB-C,
Ubuntu 16.04.5 LTS, Kernel 4.13-0-36-generic. Error appears with
`journalctl --follow` whilst monitoring for unrelated error message
tonight.
Complete log below:
$ journalctl --follow
-- Logs begin at Sat 2018-08-04 14:57:01 MDT.
Sorry to necro this bug but can someone clarify that as of now, a fresh
16.04 install with the defaults+LVM will *not* fill the /boot partition?
It was still happening for me as recently as a month or two ago I think.
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
I am currently using Cosmic (which is not released yet) and version
0.131ubuntu10 of "initramfs-tools" always generates unbootable initrd.
After I select the kernel to boot during GRUB it says: "Loading initial
ramdisk... Error: Out of memory". And then it halts forever.
This
This bug was fixed in the package bash - 4.4.18-2ubuntu3
---
bash (4.4.18-2ubuntu3) cosmic; urgency=medium
* Resurrect "Set the default path to comply with Debian policy" in
deb-bash-config.diff which went missing since 4.2+dfsg-1 or so.
LP: #1792004 LP: #1614080 Closes: #78
This bug was fixed in the package bash - 4.4.18-2ubuntu3
---
bash (4.4.18-2ubuntu3) cosmic; urgency=medium
* Resurrect "Set the default path to comply with Debian policy" in
deb-bash-config.diff which went missing since 4.2+dfsg-1 or so.
LP: #1792004 LP: #1614080 Closes: #78
After the update to the latest available version of the package ..
initramfs-tools/bionic-updates,bionic-updates,now 0.130ubuntu3.3 all
[installed]
the problem still exists!
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename: bionic
--
You received t
73 matches
Mail list logo