Seeing that this is a new point-release with just one affecting feature,
I think it should be fine to still include it in cosmic. Please proceed.
** Changed in: nginx (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Sanjana Gaur (3sanjanagaur)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407913
Title:
In 3840x2160 high resolution mode, display
This bug happens to me also. I had this problem in my laptop during a
few months. But it disappeared after a while. Now it suddenly appeared
on my desktop. 16.04 LTS. I dont have other users in my computers as
others mentioned. It happened after a few weeks of a fresh Ubuntu
installation. Annoying
** Description changed:
+ [Impact]
+ We should remind user about the possibility to enable Livepatch because at
the moment we only suggest to do so in gnome-initial-setup.
+
+ [Test Case]
+ Please note that the reminder will not be shown the first 3 times you start
update-manager.
+
+ 1. Make
69.0.3497.81-0ubuntu1 is now in cosmic.
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790962
Title:
Public bug reported:
Go to About menu item and in popup window, click "License". Nothing
happens.
On stdout, i get:
about:INFO License screen has been opened
ui_util:INFO Initializing UI for Dialog
exceptions:ERROR Unhandled Exception
Traceback (most recent call last):
File
** Changed in: kdegraphics
Status: New => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/204358
Title:
ksnapshot: Problem with offscreen pieces of windows
To manage notifications
Hello! Sorry to be the bearer of bad news, but this project has been
unmaintained for many years and I will be closing this bug. Spectacle is
the replacement for ksnapshot now. Please test again and file a new bug
for Spectacle if you still have issues. Thank you!
--
You received this bug
systemd pull request: https://github.com/systemd/systemd/pull/10033
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787495
Title:
no explanation for the events in the networkd-dispatcher manpage
To
Ok, tank you I look at this. Best regards...
Éric Cosnard (+33 678 881 758).
Le 06/09/2018 à 17:57, Joseph Salisbury a écrit :
> You may need to run the following from a terminal:
>
> sudo apt-get install -f
> sudo apt-get clean
> sudo apt-get update
>
> Then re-install the package or updates.
Public bug reported:
running conjure-up from snap with snapped lxd on amd64 bionic with a
previously lxd init'd lxd allows to deploy spells to localhost with lxd.
On arm64 it appears the localhost/lxd provider doesn't detect lxd
whether package or snap derived despite it being there and useable
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks. Sorry, I forgot to mention you need to run it under 'sudo' to
avoid all those "Permission denied" errors.
Try this:
sudo lsof -c gdm3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597150
Note to myself:
Combine mainline kernel: git://kernel.ubuntu.com/ubuntu/linux.git
Ubuntu kernel: git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
in one repo.
Get git://kernel.ubuntu.com/ubuntu/kteam-tools.git
Setup needed chroots (amd64 + arch you need)
sudo ./make_chroot bionic amd64
>From the upstream bug:
Can someone who has seen this and make this happen obtain tools logs with the
HGFS server logging enabled?
How to set up the logging is as follows:
Create the following file:
/etc/vmware-tools/tools.conf
Edit it with the following details (modified to your file location
Sorry I had copied the wrong locale settings.
As can be seen in the attached procenviron.txt the settings were US English
when I submitted the bug report.
Strangely the xinetd seems to remember the previous German settings for time
and date even if I uninstall and reinstall it.
The phenomenon
Hi, here is the detail of what happend:
- remove all files from /var/crash
- restart computer, the Ubuntu screen with the dots is shown
- when time of greeting appears in /var/crash _usr_bin_Xwayland.124.crash and
.lock files
- some seconds after appears _usr_bin_gnome-shell.124.crash in this
** Tags added: xenial2bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791229
Title:
upgrade crashed
To manage notifications about this bug go to:
Yeah this isn't released yet in Debian.
The actual change is
https://gitlab.com/psmisc/psmisc/commit/38829585c4f5b67c8c2a8cbdf86761a72ace43f6
But it is not that this would be a fix, as you already said "-n 0" can help.
This just switches defaults.
And I doubt we would go ahead so late in the
Trying to split the above case #1
#1a (just binutils)
The following packages will be upgraded:
binutils binutils-common binutils-powerpc64le-linux-gnu libbinutils
=> ok
#1b (almost all but gcc-8)
The following packages will be upgraded:
binutils binutils-common binutils-powerpc64le-linux-gnu
Actually I realized the two LANG lists in your bug report are the same.
Which exactly did change?
I see the proc environ of the bug atatchments shows many LANG settings.
They are ALL English - so is the problem that is has all "EN" while you'd
expect some to be "de"?
Check for LC and LANG in
Same problem here on my Xenial system with intel-microcode
3.20180807a.0ubuntu0.16.04.1 and linux-image-4.4.0-134-generic 4.4.0-134.160,
with an Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz.
L1TF: System has more than MAX_PA/2 memory. L1TF mitigation not effective.
--
You received this bug
And lots of spamming of the kernel log with:
[ 456.583067] mpt2sas_cm0: _ctl_host_trace_buffer_show: host_trace_buffer is
not registered
[ 456.583078] mpt2sas_cm0: _ctl_host_trace_buffer_show: host_trace_buffer is
not registered
[ 456.583100] mpt2sas_cm0: _ctl_host_trace_buffer_show:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: avahi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791168
Title:
Hangs when accessing:
/sys/devices/pci:00/:00:05.0/:05:00.0/host4/scsi_host/host4/version_product
/sys/devices/pci:00/:00:05.0/:05:00.0/host4/scsi_host/host4/prot_guard_type
/sys/devices/pci:00/:00:05.0/:05:00.0/host4/scsi_host/host4/ioc_reset_count
I was wondering if it would just "iniherit" the bad lang from the parent
until that is respawned with the fresh settings, but that would be init
which doesn't have a lang env set usually - so that should be odd to
check (as you say that would be a reboot).
I wonder about your "but xinetd still
Same problem on a fresh install from Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha
amd64 (20180822)
with snapd released (no longer in proposed)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791087
Public bug reported:
ubuntu@pepe:~$ uname -a
Linux pepe 4.15.0-34-lowlatency #37~16.04.1-Ubuntu SMP PREEMPT Tue Aug 28
11:33:58 UTC 2018 i686 i686 i686 GNU/Linux
The sysfs test in ubuntu_stress_smoke_test will hang on this node.
Sep 7 06:50:01 pepe stress-ng: invoked with './stress-n' by user
A workaround is to set manually a different MAC address in bond0.netdev:
[NetDev]
Name=bond0
Kind=bond
MACAddress=16:d6:b0:24:16:3c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791245
Title:
Public bug reported:
The problem seems to incriminate systemd-networkd (v229-4ubuntu21.1), not the
network/bonding configuration.
When a full bonding configuration is made with systemd in /etc/systemd/network,
on 2 two differents physical hosts, same hardware and in same VLAN:
-
This bug was fixed in the package secureboot-db - 1.2
---
secureboot-db (1.2) cosmic; urgency=medium
* Apply the August 2016 dbx updates from Microsoft. LP: #1776996.
* chattr -i the EFI variables before trying to call sbkeysync, since the
kernel now has these files
Hi Peter
You seems to be downgrading from a manually installed package created by the
upstream TeXstudio maintainers (texstudio-qt4 2.12.10-2) to the version
available in Ubuntu (2.12.6+debian-2) which is not supported as TeXstudio in
Debian/Ubuntu is split into several packages.
First
Public bug reported:
Hello,
Hardening guides (Securing Debian, CIS, etc...) advise to mount /dev/tmp
with the noexec option. Initramfs hooks are using the /usr/bin/test
utility to check if a file is executable to manage dependencies (if [!
-x /myfile]; then) and copy new files. Therefore, if
This bug was fixed in the package efivar - 34-1ubuntu1
---
efivar (34-1ubuntu1) cosmic; urgency=medium
* debian/patches/fix-wrong-open-flags.patch: Fix wrong flags when
opening variable in append mode. Closes LP: #1791222.
-- Steve Langasek Thu, 06 Sep 2018
22:53:34 -0700
Same issue for me:
- Community Theme Snap,
- Wayland
---
Mutter version: 3.28.3-2~ubuntu18.04.1
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
GNOME Terminal 3.28.2 using VTE 0.52.2 +GNUTLS -PCRE2
** Attachment added: "Screenshot from 2018-09-07
Phillip, the goal is BOTH secure boot AND encryption. This bug report
specifically deals with the latter, not the former. Why are you so
against encryption? I don't understand!
In the EU, GDPR is law, and in the rest of the world, encryption is
pretty much already de rigueur.
If you are arguing
*** This bug is a duplicate of bug 1720651 ***
https://bugs.launchpad.net/bugs/1720651
Same issue for me:
- Community Theme Snap,
- Wayland
---
Mutter version: 3.28.3-2~ubuntu18.04.1
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename: bionic
Please paste the output of the following command:
$ apt-cache policy libqt5gui5 libqt5widgets5 virtualbox-qt smplayer
This way we will be able to know what are the package versions on your
system and where did you install them from.
Also, if possible, run:
$ apport-collect 1791166
That will
** Changed in: gnome-session (Ubuntu)
Assignee: Marco Trevisan (Treviño) (3v1n0) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790532
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746349
Title:
I don't think so.
Because this error message happens all the time it's going to happen at
the same time as other Bluetooth problems. So people will *think* it's
related to those other problems because both occur concurrently in the
log.
However because we already know this error message happens
Expected closest good/bad as git Builds:
Last 4.13 git tag Ubuntu-4.13.0-32.35 - working
First 4.14 git tag Ubuntu-4.14.0-11.13 -
$ git bisect start
$ git bisect good Ubuntu-4.13.0-32.35
$ git bisect bad Ubuntu-4.14.0-11.13
Build is slow, but it seems I can bisect from here ...
Arr shortly
While it's true that this makes efivar -a non-functional, we have other
tools in main (sbkeysync from sbsigntool) which can be used to do these
SecureBoot db updates, so while an SRU is justified I'm not planning to
do one at this time.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 961627 ***
https://bugs.launchpad.net/bugs/961627
** This bug has been marked a duplicate of bug 961627
partclone.reiserfs is missing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
i'm running vmware as guest. I also experienced the same problem with
18.04
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-software 3.20.5-0ubuntu0.16.04.11
ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
"So it would be most helpful if anyone is experiencing actual problems
to report those in a separate bug."
@Daniel
You might want to reconsider if this is related to Bluetooth failures, at least
the message is specifically linked to Bluetooth connection issues as seen in my
tests.
See
Public bug reported:
error installing semicode os
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.8.13 [modified: usr/share/ubiquity/apt-setup]
ProcVersionSignature: Ubuntu 4.4.0-105.128~14.04.1-generic 4.4.98
Uname: Linux 4.4.0-105-generic i686
ApportVersion:
Public bug reported:
Not sure -maybe server timed out
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.25
ProcVersionSignature: Ubuntu 4.4.0-134.160-powerpc64-smp 4.4.140
Uname: Linux 4.4.0-134-powerpc64-smp ppc64
ApportVersion: 2.20.1-0ubuntu2.18
Lots of errors etc in syslog, added some notes on top of the obvious
errors.
Kernel keeps spamming syslog with these
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748565):
kernel: [15621.044566] Bluetooth: hci0: last event is not cmd complete (0x0f)
Note: this kernel message disappears
Public bug reported:
[SRU Justification]
When using append mode, libefivar's efivarfs_set_variable() opens the target
file with flags O_APPEND|O_CREAT, which fails to actually define a read/write
mode and therefore the file is opened read-only. This makes it impossible to
use efivar to append
501 - 550 of 550 matches
Mail list logo