Affected on 16.04 as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1746012
Title:
please disable xconsole configuration in 50-default.conf to fix
"rsyslogd-2007:
** Changed in: ubuntu-z-systems
Status: Incomplete => Fix Committed
--
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.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not
Public bug reported:
A few months back I had the same problem, then I installed lightdm and
ran it and since then bug was gone. But 2 days back I got the same bug,
I tried running lightdm again, so to stop it I ran sudo stop lightdm but
it gives out the message "unable to connect to upstart" and
See if you have any *cups* packages installed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1671974
Title:
CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
Hello Brandon,
I wasn't able to use an untrusted user account to induce this behaviour.
So, I'm making this bug public so that more people can be made aware of
the misconfiguration that is being encouraged.
It's unfortunate that the providers of this advice never actually tested
it themselves.
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1813833
Title:
User without read permission on cron.allow
https://github.com/lxc/lxd/issues/5439#issuecomment-461257784
> The fix in LXD is only partial because there's currently no safe way
for us to fix that for privileged containers due to an apparmor parser
bug that the AppArmor team is still working on.
So we've made the change only to the
This is a LXD commit, not a LXC one. LXC cannot be fixed in the same way
as it has a single apparmor policy covering both privileged and
unprivileged containers, until such time as the apparmor security issue
is resolved, there's nothing we can do to fix this issue without causing
a giant security
Hello Imre, thanks for the report. I can't reproduce this issue myself,
nor could I find anything in the source code that would suggest dash
would try to quit. In fact I'm not even sure that dash knows that it's
happened.
Here's the tail end of strace output (run on the same terminal as dash,
to
Public bug reported:
branches cosmic & disco
the impact of current lxc aa rules in conjunction with systemd v240 is
outlined here
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813622/comments/10
Whilst LXC committed the patch to its master
If anyone knows a way to pinpoint some process which sends some specific
packets, I'd be glad to investigate further.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1671974
** Description changed:
Sorry for the pre-mature post. First time using this interface.
-
I noticed this today; an automated AMI build process failed.
The AMI in question is ami-0326c210edce0ffa5 AKA (ubuntu-
eks/k8s_1.10/images/hvm-ssd/ubuntu-
I experience the same symptoms on Ubuntu 19.04 disco, but there is no
cups* packages installed:
# apt-cache policy cups*| grep Installed | grep -v none
#
The issue is definitely unrelated to CUPS.
Some other process sends many strange IPv6/UDP packets to all IPv6 local nodes
with 2 different
Public bug reported:
Sorry for the pre-mature post. First time using this interface.
I noticed this today; an automated AMI build process failed.
The AMI in question is ami-0326c210edce0ffa5 AKA (ubuntu-
eks/k8s_1.10/images/hvm-ssd/ubuntu-
bionic-18.04-amd64-server-20190204.2).
The automated
** Package changed: ubuntu => dash (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1814905
Title:
dash exits when receiving wall message
Status in dash package in
You have been subscribed to a public bug:
When using "/bin/sh" (dash) as a shell for ssh, or just starting /bin/sh
in a terminal, when the shell receives a wall message (from another user
or root), it just quits.
How to reproduce:
- start a terminal (xterm, gnome-terminal, etc), usually starts
The easiest way to get that is to unpack a tarball, zip, package, etc.,
using sudo. Chances are really good *other* files and directories also
have incorrect owner or permissions.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Laptop with multiple user accounts.
Logging in as any user has working audio, but if that session is locked
and a second user logs in, the second user gets no sound.
Workaround is for both users to log out and 2nd user to log in a fresh
session. Obviously a problem if you
** Information type changed from Private Security to Public Security
--
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/1814895
Title:
display blinking and showing content of
Any workaround? Tried editing /etc/apparmor.d/lightdm-guest-session with
the suggested change but doesn't work
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1273524
Title:
Public bug reported:
Hi,
I'm not sure this issue is really a bug.
Since August 2018, I try to upgrade 16.04.5 to 18.04 LTS with no success.
Each upgrades are aborted with a loop detected when installing python's
packages.
Since PPAs was purged, and I left only one line uncommented in
The new stable version indicate the fix mentioned by seb128 is there but
no indication has been made in the debian/changelog to automatically
change the status, which breaks the SRU machinery for this particular
bug.
--- network-manager-1.10.6/src/nm-manager.c 2018-03-12 08:59:48.0
** Description changed:
+ [Impact]
+ Ubuntu crash reports and package installation failures may not include
DpkgTerminalLog.txt if there is a UnicodeDecodeError trying to read the dpkg
log file.
+
+ [Test Case]
+ Because the fix is simple and its complicated to have a dpkg log file with
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1799913
Title:
Unhandled lockdown error (-2) - iphone
Thanks for the update, closing!
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1799913
Title:
Unhandled lockdown error (-2) - iphone
Finally I have ran `sudo chmod g-w /` to be completely sure and rebooted again.
As the result I can connect to this machine from my LAN.
Just curious - why did I have 1004:1004 rights on /?
** Changed in: openssh (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
** Changed in: apport (Ubuntu Bionic)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: apport (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I have checked about 1004 and got:
ls -ld /
drwxrwxr-x 32 1004 1004 4096 Dec 9 23:22 /
- it is really strange.
So I ran
sudo chown root: /
ls -ld /
drwxrwxr-x 32 root root 4096 Dec 9 23:22 /
And reinstalled SSHD again:
sudo apt-get install --reinstall
More detailed information on this issue is below:
The customer has Ubuntu OEM through Dell. The laptop goes into deep sleep over
night and they can no longer use their BT devices. You click on bt via GUI and
try to toggle on and it looks like it is doing something and goes right back to
off.
This bug is solved in 18.04 LTS.
--
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.launchpad.net/bugs/1636282
Title:
network-manager after suspend showing arrow icon instead of wifi
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1814941
Title:
package libxml2:amd64 2.9.3+dfsg1-1ubuntu0.6 failed to
Public bug reported:
i don't know i was just updating the os and i had this issue and i am
not familiar with linux so i just reported it .
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libxml2:amd64 2.9.3+dfsg1-1ubuntu0.6
ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic
Seen on 18.04.1. WorkARound?
* soft memlock 262144
* hard memlock 262144
# End of file
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1662244
Title:
lightdm causes all
No, it would have been impossible for any desktop image (even pending)
to contain the new systemd on the 31st of January.
The first image that contains the new systemd is from 20190204 or later.
** Changed in: systemd (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
You received
** Changed in: systemd (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1804487
Title:
systemd-resolved has
Public bug reported:
Nautilus 3.30 has new path-bar. And hence it doesn't look good with
current design.
I had several ideas to solve the problem. Hence opened a discussion
thread in community hub to get opinions from developers and users.
See:
I will open a merge once this gets finalized.
**
Thanks for filing this bug in Ubuntu.
There are some interesting warnings in the logs you provided:
WARN: uid is 0 but '/' is owned by 1004
WARN: / is group writable!
and
Setting up openssh-server (1:7.2p2-4ubuntu2.6) ...
Unsafe symlinks encountered in /var/run/sshd, refusing.
More details
** Changed in: nut (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1176548
Title:
nut-server fails if modemmanager is scanning
** Description changed:
Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso
- Bluetotth mouse tested with HP X4b BT Last mouse stops responding
+ Bluetooth mouse tested with HP X4b BT Last mouse stops responding
after long extended deep sleep (24-48 hours).
Bluetooth settings
*** This bug is a duplicate of bug 1814925 ***
https://bugs.launchpad.net/bugs/1814925
running ubuntu-bug bluez; I received a new bug id 1814925. These bugs
are all related.
** This bug has been marked a duplicate of bug 1814925
Bluetooth mouse stops responding after extended deep sleep
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
*** This bug is a duplicate of bug 1814925 ***
https://bugs.launchpad.net/bugs/1814925
running ubuntu-bug bluez; I received a new bug id 1814925. These bugs
are all related.
** This bug has been marked a duplicate of bug 1814925
Bluetooth mouse stops responding after extended deep sleep
Public bug reported:
Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso
Bluetooth mouse tested with HP X4b BT Last mouse stops responding
after long extended deep sleep (24-48 hours).
Bluetooth settings window which initially reported Bluetooth as
connected now shows disconnected. Pushing
Daniel, my name is Jill and I have the customer's capture so I have to
run the apport-collect from the customer's system. Juan is our back
line engineer that opened the case with you so we could have Canonical
and Dell collaborate. If this is not correct. How can I get you the
data?
--
You
1813208 is a duplicate of this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1812446
Title:
Bluetooth mouse stops responding after 24-48 hours of connectivity
Status
I am asking our colleague Juan to respond but yes these are 2 bugs that
are duplicate of each other. Let Juan know what you need from us to
take this further?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
@cadirol
most likely your system is broken, insecure and vulnerable to the
relevant CVE. Please provide output from journal logs, and permissions
of the root directory
$ ls -latr /
$ journalctl -b
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Installing mesa 18.2.8 from the updates ppa fixes the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1814808
Title:
18.04 update to libglapi-mesa/libglx-mesa0
--- Comment From indira.pr...@in.ibm.com 2019-02-06 09:45 EDT---
Triggered crash with patch using crashkernel=8192M and did not see OOM traces
and dump copied properly as below
root@woo:/var/crash/201902060928# pwd
/var/crash/201902060928
root@woo:/var/crash/201902060928# ls -l
total
--- Comment From indira.pr...@in.ibm.com 2019-02-06 09:27 EDT---
(In reply to comment #82)
> The system has too many devices, so too many drivers are using too much
> memory. So, the system goes out-of-memory before makedumpfile is complete.
> Please, reserve more memory on crashkernel,
Good day
Same issue here! After upgrade systemd from 229-4ubuntu21.10 to
229-4ubuntu21.15 and a reboot, ssh did not start anymore.
As ugly workaround i ran #mkdir -p -m0755 /var/run/sshd && systemctl restart
ssh.service
$ uname -a
Linux aws01.nts.ch 4.4.0-142-generic #168-Ubuntu SMP Wed Jan
it's also discussed on
https://gitlab.gnome.org/GNOME/nautilus/issues/713
** Changed in: glib2.0 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
That's discussed upstream on
https://gitlab.gnome.org/GNOME/glib/issues/1414 and basically their
opinion is that firefox shouldn't claim to be a x-scheme-handler/ftp
handler
** Summary changed:
- Double-click doesn't open default application
+ firefox is used to open ftp share files
** Package
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1814885
Title:
packagekitd crashed with SIGABRT in std::terminate()
You have been subscribed to a public bug:
Ubuntu 18.04
Nautilus 1:3.26.0-0ubuntu1
Bluefish 2.2.10
When I open a .php file from a FTP server browsed with Nautilus, Chrome
is opened instead of the default application Bluefish.
Steps to reproduce:
1. Connect to an FTP server via Nautilus
2a.
Is that still an issue in current Ubuntu versions?
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Invalid
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided => Low
** Changed in: glib2.0 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
try the updates ppa, which has mesa 18.2.8:
https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in
Bai Lee,
Is this still an issue? Unless you provide us with more information
about the hardware and Ubuntu version you are using we are unable to
help.
** Changed in: upower (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
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.launchpad.net/bugs/1814827
Title:
wireless hard blocked in ubuntu 18.04
There is a new version including that fix now
** Changed in: totem-pl-parser (Ubuntu)
Importance: Undecided => Low
** Changed in: totem-pl-parser (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
The system has too many devices, so too many drivers are using too much
memory. So, the system goes out-of-memory before makedumpfile is
complete. Please, reserve more memory on crashkernel, reboot the system
and repeat the crash test.
To reserve more memory on crashkernel, edit file
62 matches
Mail list logo
