** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpa
*** This bug is a duplicate of bug 1583801 ***
https://bugs.launchpad.net/bugs/1583801
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1583801, so it is being marked as such. Please look
You have been subscribed to a public bug:
Using ubuntu wayland with dual monitors, configured above each other.
Dock is configured at both displays, not hiding.
Icons for "terminal" and "libreofffice Writer" are present at the dock.
Start terminal on primary screen by mouseclick on dock.
Start li
Randy,
It is true, but we have different definitions of "old".
By "old behaviour" we are referring to previous Gnome releases that also
used libinput. And by "old behaviour" you are referring to much older
releases of Ubuntu (Unity) that used the X synaptics touchpad driver
instead of libinput.
Randy,
It is true, but we have different definitions of "old".
By "old behaviour" we are referring to previous Gnome releases that also
used libinput. And by "old behaviour" you are referring to much older
releases of Ubuntu (Unity) that used the X synaptics touchpad driver
instead of libinput.
This is probably not assigned to the right package. It's not an issue
with e2fsprogs, but whatever component is running fsck. This might be
systemd, or upstart, or whatever the heck Ubuntu is using these days.
I lost track a while ago. :-)
I can tell, you as the Debian maintainer of e2fsprogs
Public bug reported:
Happens 100% of the time, but only in one directory.
1) cd into that directory (cd ~/gplus)
2) eog .
3) segfault
stack trace:
#0 0x76c8db8d in gtk_tree_model_get_valist () at
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#1 0x76c8de7d in gtk_tree_model_get () at
Can this be bumped up to a high importance? This is a major issue as not
checking the file system leads to a broken system.
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bu
** Project changed: launchpad => sudo (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1797944
Title:
sudoers entries with FQDN are ignored on Ubuntu 14.04
Status in
You have been subscribed to a public bug:
Here is the short example of /etc/sudoers in order to reproduce the issue that
if host is defined as FQDN then such string is skipped on Ubuntu 14.04. The
following sudo is installed on the host "1.8.9p5-1ubuntu1.4 amd64"
~
~# cat /etc/sudoe
The claim that "You can get the old behavior back with the GNOME Tweaks
app" is simply not true. You can toggle between the two menu methods
(two-finger tap and bottom-right click), but I cannot get back the old
behavior of being able to do BOTH. This is not asking people to choose
between the Mac
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1797555/+attachment/5201395/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bu
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1797555/+attachment/5201394/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubun
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1797555/+attachment/5201393/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1797555/+attachment/5201396/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.l
the apport is done. thx for the responses. hope this helps!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1797555
Title:
headphone not detected on initialization
Stat
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1797555/+attachment/5201392/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://
apport information
** Tags added: apport-collected bionic
** Description changed:
every time i initialize the computer with the headphone connected, there's no
sound in the headphones. i have to take the headphone off and plug it again,
then i'm prompted with the ubuntu window asking if it's
** Changed in: fwupd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libusb in Ubuntu.
https://bugs.launchpad.net/bugs/1631002
Title:
fwupd crashed with SIGSEGV in malloc_consoli
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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.n
** Description changed:
+
+ [Impact]
+ Any user of Ubuntu on multipath, where the default path separator has been
changed to something else. This possibly affects other scenarios where the
partition separator can be changed.
+
+ [Test case]
+ 1) Install Ubuntu on multipath system
+ 2) Change /
Correct, I hadn't noticed that part.
The issue I have with this patch still stands, nothing guarantees that
the separator is "", "p", or "-part", but at least we're covering the
most likely cases.
I'm sponsoring the patch now, we'll land this as SRU to 18.10 and 18.04.
** Changed in: util-linux
I found time to run more tests and discovered that my patches were
wrong... And the fix was actually even simpler.
root@netplan:~# cat fix-bug-1770082.diff
Index: b/netplan/cli/commands/apply.py
===
--- a/netplan/cli/commands/apply.py
This bug fix causes a regression in Xenial when installing initramfs-
tools in QEMU, since the version of QEMU in Xenial does not support
syncfs():
/bin/sync: error syncing '/boot/initrd.img-4.14.44-v7ooicgsn': Function
not implemented
--
You received this bug notification because you are a memb
ubuntu@lp1748147:~$ dpkg -l systemd | grep systemd
ii systemd229-4ubuntu21.4 amd64system and service manager
ubuntu@lp1748147:~$ ls -lad /var/log
drwxrwxr-x 7 root syslog 4096 Oct 15 16:32 /var/log
ubuntu@lp1748147:~$ sudo apt install --reinstall systemd
...
ubuntu@lp1748147:~$ ls
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1797941
Title:
package tzdata 2018e-0ubuntu0.18.04 failed to install/upgrade: package
Public bug reported:
Too many errors install failed.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: fontconfig 2.12.6-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144
Uname: Linux 4.4.0-137-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Mon
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[
Public bug reported:
package installation failed, inconsistent content
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: tzdata 2018e-0ubuntu0.18.04
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architectur
@adconrad - ack. Just a comment - This time there was less than a month
between installing this bionic instance, doing the sru test and then
reverting - so I had at least some recollection of what went on. If it
had been 3 years - I'd have no chance and would wonder what was going
on. I guess I'd
To be clear, nvidia was never removed, as far as I can tell, but it was
installed and then nouveau selected as the default. So, the upgrade
upgraded nvidia (which is fine), but then the default became nvidia
again.
Not sure what should really happen in this case, or if maybe selecting
nouveau sho
This bug was fixed in the package systemd - 239-7ubuntu10
---
systemd (239-7ubuntu10) cosmic; urgency=medium
* units: Disable journald Watchdog (LP: #1773148)
* Add conflicts with upstart and systemd-shim. (LP: #1773859)
-- Dimitri John Ledkov Thu, 04 Oct 2018 15:58:51
+0100
This bug was fixed in the package systemd - 239-7ubuntu10
---
systemd (239-7ubuntu10) cosmic; urgency=medium
* units: Disable journald Watchdog (LP: #1773148)
* Add conflicts with upstart and systemd-shim. (LP: #1773859)
-- Dimitri John Ledkov Thu, 04 Oct 2018 15:58:51
+0100
** Attachment added: "apt-term.log"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797932/+attachment/5201289/+files/apt-term.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
** Attachment added: "postupgrade.png"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797932/+attachment/5201287/+files/postupgrade.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properti
** Attachment added: "preupgrade.png"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797932/+attachment/5201286/+files/preupgrade.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797932/+attachment/5201290/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ub
Attaching logs from /var/log/dist-upgrade
** Attachment added: "apt.log"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797932/+attachment/5201288/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
** Attachment added: "main.log"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797932/+attachment/5201291/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
Public bug reported:
Upgraded Bionic to Cosmic with iso from 13/10.
Prior to upgrading was using the nouveau driver.
Had previously installed nvidia to test a recent SRU fix. Once I had
tested the fix I had gone back to additional drivers to revert to
nouveau. Attached 2 screenshots from during
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
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
Not sure which part of this fixes the problem, but I don't have any
issues after I run the following:
echo '* hard nofile 2097152' | sudo tee -a /etc/security/limits.conf
echo '* soft nofile 2097152' | sudo tee -a /etc/security/limits.conf
echo 'root hard nofile 2097152' | sudo tee -a /etc/securit
It's a shame I can't edit comments on Launchpad: Please disregard my
last comment, I seem to have misread the pbuilder issue, sorry for the
noise. That doesn't change the validity of my point about updating
debootstrap though.
--
You received this bug notification because you are a member of Ubun
This bug was fixed in the package packagekit - 1.1.10-1ubuntu7
---
packagekit (1.1.10-1ubuntu7) cosmic; urgency=medium
* Pass --no-restart-after-upgrade to dh_installsystemd to avoid PackageKit
restarting while upgrading under PackageKit (LP: #1790613)
-- Julian Andres Klode
Going over my notes on this topic I realized that I hadn't pointed out
in my previous message that the issue I've pointed out has already
triggered a workaround (that shouldn't be necessary IMHO) in the
pbuilder project:
https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/599394
In my opinion
** Changed in: friendly-recovery (Ubuntu Dd-series)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
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/1766872
Title:
'
> Precise archive is only signed with the old key. To support using the
precise archive in newer releases, such as with debootstrap, we need to
do the following ...
This comment implied to me that the use of debootstrap to create an
Ubuntu 12.04 chroot on e.g. Ubuntu 18.04 (which includes the ubun
** Changed in: friendly-recovery (Ubuntu Cosmic)
Assignee: Eric Desrochers (slashd) => Dimitri John Ledkov (xnox)
--
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/1766872
Hello Eric, or anyone else affected,
Accepted friendly-recovery into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/friendly-
recovery/0.2.38ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
This is good. After accepting please double-check if the resume
functionality really didn't regress. Thanks!
** Changed in: friendly-recovery (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-bionic
--
You received this bug notifi
** Description changed:
[Impact]
* network menu in recovery mode doesn't work correctly, blocking at
starting systemd services depends to enable networking.
[Test Case]
* Boot w/ Xenial or Bionic in recovery mode via grub
* Choose "network" in friendly-recovery menu
T
I have a similar case. Let me know if you want me to file a new bug and
where to file it.
Test Case
=
Install Ubuntu 18.10 in VirtualBox. Restart
Log in. Open Settings > Details > Users. Unlock then turn on Automatic Login.
Restart.
I get the similar corrupted display. My screen resolutio
** Description changed:
[Impact]
* network menu in recovery mode doesn't work correctly, blocking at
starting systemd services depends to enable networking.
[Test Case]
* Boot w/ Xenial or Bionic in recovery mode via grub
* Choose "network" in friendly-recovery menu
T
** Changed in: ubuntu-power-systems
Importance: High => Medium
** Changed in: util-linux (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.n
** Description changed:
[Impact]
- * network menu in recovery mode doesn't work correctly, blocking at
+ * network menu in recovery mode doesn't work correctly, blocking at
starting systemd services depends to enable networking.
[Test Case]
- * Boot w/ Xenial or Bionic in recover
Hi,
FYI I checked with the Security Team and this CVE seems considered low prio.
But the ubuntu-security-sponsor is subscribed so the will get to consider it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
FWIW, the option to pass is --no-restart-after-upgrade
--
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/1790613
Title:
Regression: packagekit crashes updating itself to a
Uploaded, both in unapproved
** Changed in: packagekit (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: packagekit (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: packagekit (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notifi
** Description changed:
+ [Impact]
+
+ * network menu in recovery mode doesn't work correctly, blocking at
+ starting systemd services depends to enable networking.
+
+ [Test Case]
+
+ * Boot w/ Xenial or Bionic in recovery mode via grub
+ * Choose "network" in friendly-recovery menu
+
+ T
** Description changed:
+ [Impact]
Bionic: 18.04
Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1
Updating with pkcon upgrade or plasma-discover crashes packagekit mid
transaction, requiring user intervention on the command line.
In plasma-discover the gui reports
primary error is no "com.ubuntu.apport.apport-gtk-root", the second
error came in sepperate pop-up for "linux-image-
extra-4.13.0.40~16.04.1". This indicates bad support for an AMD 7tr gen
processor on my DELL computer.
--
You received this bug notification because you are a member of Ubuntu
Touc
Daniel Borkmann's contact information seems to be available at
http://borkmann.ch .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1777010
Title:
ip token set, results in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bug
I don't seem to have this issue on 18.04 either, so it seems to be
limited to 14.04.
$ ps aux | grep [p]olkit
root 1453 0.0 0.0 292924 8796 ?Ssl Oct12 0:01
/usr/lib/policykit-1/polkitd --no-debug
bmaupin 16637 0.0 0.1 323808 19996 ?Sl 08:10 0:00
/usr/lib/policyk
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dpkg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs
Hi,
I think I have the same problem. I have a Latitude 7390 with the WD15
Dock.
I get a connection to the Display Port and VGA but not to the HDMI Port.
I have connect my second monitor with HDMI, but it isnt working.
$ xrandr
Screen 0: minimum 320 x 200, current 3840 x 1200, maximum 8192 x 8192
No,it's not useful.And I tried acpi_listen,still no output when i press
Fn+Down
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1797862
Title:
Cannot turn off keyboard backl
Public bug reported:
ntpd keeps printing "Soliciting pool server" in the syslog (once every 5
seconds).
$ ntpq -c pe
remote refid st t when poll reach delay offset jitter
==
0.ubuntu.pool.n .POOL
^^^
You also need to reboot after changing that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1797862
Title:
Cannot turn off keyboard backlight
Status in linux package i
Does changing your upower.service file fix the problem?
Remove: ProtectKernelTunables=true
And add: ProtectKernelTunables=false
If so then this may be related to bug 1796550 and
https://gitlab.freedesktop.org/upower/upower/issues/73
** Also affects: upower (Ubuntu)
Importance: Undecided
These would be two different bugs:
* Cannot turn off keyboard backlight.
* Unable to control screen brightness via fn keys
Please reword this bug to only describe one of them. And then move the
other issue into a new bug if you would like.
** Package changed: xorg (Ubuntu) => ubuntu
** Chang
Public bug reported:
/sys/class/leds $ ls
asus-wireless::airplane input10::capslock input10::compose input10::kana
input10::numlock input10::scrolllock input4::capslock input4::numlock
input4::scrolllock phy0-led
There isn't any asus kbd backlight folder. `xset led off` doesn't work f
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
*** This bug is a duplicate of bug 1797855 ***
https://bugs.launchpad.net/bugs/1797855
** Package changed: xorg (Ubuntu) => ubuntu
** This bug has been marked a duplicate of bug 1797855
Xorg crash
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
Public bug reported:
System freezes and crashes several times a day and reboot itself.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset
Public bug reported:
System freezes, crashes and reboot itself several times a day.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rsyslog (Ubuntu)
Status: New => Confirmed
--
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.n
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
systemd. This problem was most recently seen with package version
239-7ubuntu9, the problem page at
https://errors.ubuntu.com/problem/b04775223b30ca8d18a711d33b9fa79ea1fe52d4
contains more detai
Great, glad that we sorted it out. the "." is a bash syntax afaik and to
source shell script, it's working on script only and not to start
compiler binaries
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touc
FWIW a cleaner workaround that also works is creating a /etc/Muttrc.d/00
-fix-black-bar.rc that does
color normal default default
This way you don't have to deal with conffile changes on next upgrade.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
80 matches
Mail list logo
