This sounds like the dock encountered an error and couldn't disable
properly upon locking the session. Can you provide the output of "sudo
journalctl /usr/bin/gnome-shell" when you see this behavior?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: unbound (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/1723900
Title:
unbound systemctl (re)start fails due to Apparmor profile issue
To
I did the same with:
$ uname -rv
4.13.7-041307-generic #201710141430 SMP Sat Oct 14 14:31:12 UTC 2017
and also this kernel works for me and touchpad works after resume. What
is also nice, Wi-Fi works after resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The kernel at #14 fails to boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723619
Title:
Ubuntu Desktop ISO fails to boot with nouveau on a displayport
To manage notifications about this bug
This was presumed fixed in the upstream bug report [1] and hasn't been a
problem for a couple of years now. Closing this report.
[1] https://bugzilla.kernel.org/show_bug.cgi?id=102161
** Bug watch added: Linux Kernel Bug Tracker #102161
https://bugzilla.kernel.org/show_bug.cgi?id=102161
**
Oh, by the way, it's often happens after locking then unlocking the
screen though! It often fixes the problem too (if it was before). But
not always ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug still affects me now, upgraded to the to-be-released 17.10
(artful). I was a die hard text only user of Linux systems for a while,
so I still configure system to "emulate" something like this, ie
ALT+F1...F8 to switch between workspaces. However, ALT-F5 does not
_always_ works. Sometimes
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of
The following packages ended up in the wrong component in the -proposed
pocket:
linux-meta-kvm 4.4.0.1009.9 - is in main instead of universe
linux-headers-kvm 4.4.0.1009.9 - is in main instead of universe
linux-image-kvm 4.4.0.1009.9 - is in main instead of universe
linux-kvm 4.4.0.1009.9 - is in
** Changed in: gnome-software (Ubuntu)
Status: New => Triaged
** Changed in: gnome-software (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723874
Sorry for the delay. I will try the new kernel, thanks!
On Wed, Oct 11, 2017 at 3:01 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
>
Hello Joseph,
thanks for your email. I'm trying to install the Kernel 4.14 from this
link: http://sourcedigit.com/22814-install-linux-kernel-4-14-rc5/ but it
doesn't work. After the two first commands all other show the message "not
found".
I'll try to answer your questions. This problem started
Public bug reported:
Hello, hello, I have a problem with my ASUS k550DP and my integrated Bluetooth
Ralink device, with Ubuntu 17.10
the rfkill list all command does not show me the Bluetooth device
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
**
Public bug reported:
BEHAVIOR
There's no place to upload a photo, but I can provide one upon request. I
turned screen lock off in the Privacy section of System Settings. Now, when the
monitor powers off, and I wiggle the mouse or press a keyboard key to awaken
Ubuntu 17.10, it shows the lock
Public bug reported:
Add and update firmware files as necessary to support a 4.12 based
kernel in the xenial linux-hwe-edge package.
** Affects: linux-firmware (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
--
You received this bug
** Changed in: apport (Ubuntu)
Status: New => Triaged
** Changed in: apport (Ubuntu)
Importance: Undecided => Low
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The attachment "monitor-managerxrandr-Use-a-single-supported-
scale.patch" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've applied the above mentioned patch, and rebuilt the rtl8723bs
module, but the same problem persists. Also tested kernel 4.14, and, as
expected, the same bug is there too.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you
** Patch added: "updated patch to apply cleanly to mutter in artful"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1724024/+attachment/4973082/+files/monitor-managerxrandr-Use-a-single-supported-scale.patch
--
You received this bug notification because you are a member of Ubuntu
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of
The following packages ended up in the wrong component in the -proposed
pocket:
linux-meta-kvm 4.4.0.1009.9 - is in main instead of universe
linux-headers-kvm 4.4.0.1009.9 - is in main instead of universe
linux-image-kvm 4.4.0.1009.9 - is in main instead of universe
linux-kvm 4.4.0.1009.9 - is in
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the 4.11.0-1014.14 upload package. This bug
will contain status and testing results related to that upload.
For an explanation of the tasks and the
Could you also give the latest upstream stable 3.13 kernel a try? It is
available here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.7/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723799
*** This bug is a duplicate of bug 1505409 ***
https://bugs.launchpad.net/bugs/1505409
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1505409, so is being marked as such.
** Attachment added: "deja-dup.gsettings"
https://bugs.launchpad.net/deja-dup/+bug/1717230/+attachment/4973077/+files/deja-dup.gsettings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717230
Disabling Thunderbolt support in the BIOS (F2 during boot) worked for
me.
Suspend works.
Don't know when/if I'll need the Thunderbolt. This works for now.
Thanks!
Can I provide any additional info to help you debug/fix this properly?
Cheers,
Walter
Before disabling Thunderbolt:
[
** Description changed:
- Showed error message at the end of install.
-
- LUbuntu 17.04
-
- ProblemType: Bug
- DistroRelease: Ubuntu 17.04
- Package: ubiquity 17.04.9
- ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
- Uname: Linux 4.10.0-19-generic x86_64
- ApportVersion:
Actually things are a little different with regards to OpenStack
packages in Ubuntu; the Debian OpenStack team has been a bit on and off
over the last few years, so Ubuntu leads with OpenStack packages rather
than the normal sync/merge flow with Debian, with git repositories on
Launchpad for the
No apt-ghetto, partman has a number of scripts that try to keep users
from making simple mistakes. This particular one is missing or
defective ( I seem to recall seeing one in there for this but apparently
it isn't working ).
** Package changed: grub-installer (Ubuntu) => partman-efi (Ubuntu)
Sorry. By bad on the login description! I was confusing "Ubuntu" and
"Unity" - damn this transition phase :-(
If I choose "Ubuntu on X.org" I cannot disable the dock, but if I choose
"GNOME on X.org" I can.
However, I still think this bug stands. Ether stop the extension from
showing in Tweak
Let me know do you need anything else. Will be possible to backport
fixes from 4.14 to final release of Ubuntu 17.10, so touchpad works
after resume on default Artful Aardvark install?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
Public bug reported:
This bug is for tracking the 4.11.0-1014.14 upload package. This bug
will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects:
I did following:
dpkg -i \
linux-headers-4.14.0-041400rc5_4.14.0-041400rc5.201710152230_all.deb \
linux-headers-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb
\
linux-image-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb
and rebooted the system to new
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. A warning message prompted you that this
could be a problem and recommended performing a bios mode install
instead, but you chose not to. You either need to perform the bios mode
install, or
Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=776147
** Bug watch added: GNOME Bug Tracker #776147
https://bugzilla.gnome.org/show_bug.cgi?id=776147
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. A warning message prompted you that this
could be a problem and recommended performing a bios mode install
instead, but you chose not to. You either need to perform the bios mode
install, or
failing autopkg tests for this:
linux-lts-xenial (and other EOL linux-lts-*)
these failures are due to bug 1723223; known bug that is not related to this
bug.
linux-exynos5 on armhf
this failed due to a testbed failure, unrelated to this bug.
linux on armhf
this failure is due to bug
I'm really confused now.
I've upgraded to 17.10. On my login screen I choose "GNOME on X.org" and
NOT "Ubuntu".
I too see the option in tweak tool to disable ubuntu dock, but toggling
the switch has no effect.
So the answer "Install gnome-session" for a vanilla gnome doesn't seem
to actually
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of
The following packages ended up in the wrong component in the -proposed
pocket:
linux-meta-kvm 4.4.0.1009.9 - is in main instead of universe
linux-headers-kvm 4.4.0.1009.9 - is in main instead of universe
linux-image-kvm 4.4.0.1009.9 - is in main instead of universe
linux-kvm 4.4.0.1009.9 - is in
Hi Hans, it works fine now!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721995
Title:
unknown-horizons DBUS_TYPE_INVALID
To manage notifications about this bug go to:
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. A warning message prompted you that this
could be a problem and recommended performing a bios mode install
instead, but you chose not to. You either need to perform the bios mode
install, or
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee
(sforshee)
** Changed in: kernel-sru-workflow/prepare-package-signed
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. A warning message prompted you that this
could be a problem and recommended performing a bios mode install
instead, but you chose not to. You either need to perform the bios mode
install, or
To add to my comment above, if service nova-compute restart doesn't
work, a node reboot does. The issue is that upon initial install there
is no qemu-kvm.service enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It looks like the bisect failed. All of the kernels I posted were
reported as good and resolved the bug. One or more of them should have
been bad and exhibited the bug.
I copied all of the test kernels back to
http://kernel.ubuntu.com/~jsalisbury/lp1723174. The test kernels for a
specific
The version of blkid in 16.04 is 2.27.0 and is from 02-Nov-2015, and it
supports this option. You are either running an older release than
16.04, or have an old locally built version.
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
Public bug reported:
installer crashed after marking / (root) for formatting
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.7
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Public bug reported:
I use my computer with both Hebrew & English.
My password is set in English.
I wanted to install an update of a software (Atom) through gdebi.
Because my keyboard was set on Hebrew, once the password pop up came on the
screen, I could only type letters in Hebrew, there was
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: linux (Ubuntu Zesty)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in:
Same problem here!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723789
Title:
Apturl does not handle apt links in Firefox
To manage notifications about this bug go to:
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Bb-series)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu
I solved this problem by:
juju ssh nova-compute/0(one of my bad nodes)
sudo systemctl enable qemu-kvm.service
sudo service qemu-kvm restart
sudo service nova-compute restart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1713717 ***
https://bugs.launchpad.net/bugs/1713717
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1713717, so is being marked as such.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724050
Title:
package kimchi 1.5.0-0ubuntu1 failed to install/upgrade: subprocess
installed post-removal
*** This bug is a duplicate of bug 1505409 ***
https://bugs.launchpad.net/bugs/1505409
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1505409, so is being marked as such.
I use default. It's not OK to require a person to wiggle a mouse or
touchpad whenever they want to touch their screen, for example scrolling,
changing windows, pausing/playing a video, etc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of
** Package changed: ubiquity (Ubuntu) => lubuntu-meta (Ubuntu)
** Also affects: lubuntu-next
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638420
Title:
*** This bug is a duplicate of bug 1638420 ***
https://bugs.launchpad.net/bugs/1638420
** This bug is no longer a duplicate of bug 1633913
lubuntu and ubuntustudio are missing pool; can not install without internet
connection
** This bug has been marked a duplicate of bug 1638420
LVM
Sorry for the noise, meant that for a different bug.
** Also affects: lubuntu-next
Importance: Undecided
Status: New
** No longer affects: lubuntu-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The following packages ended up in the wrong component in the -proposed
pocket:
linux-meta-kvm 4.4.0.1009.9 - is in main instead of universe
linux-headers-kvm 4.4.0.1009.9 - is in main instead of universe
linux-image-kvm 4.4.0.1009.9 - is in main instead of universe
linux-kvm 4.4.0.1009.9 - is in
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1724044
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
COmes up with errors everytime I accept software update. nginx
dependency errors seems to be linked
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: kimchi 1.5.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic
** Changed in: gambc (Debian)
Status: New => 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/422034
Title:
Gambit-C compiler/interpreter is an old version, needs update.
To
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721089
Title:
package grub-common 2.02~beta3-4ubuntu2.2 failed to
Public bug reported:
Since yesterdays update of xserver-xorg-core-hwe-16.04, the graphical
session crashes reproducibly, some time into using the session. Might be
related to using libreoffice at the time of the crash.
The relevant message from the system journal is:
kernel: [drm] GPU HANG:
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. A warning message prompted you that this
could be a problem and recommended performing a bios mode install
instead, but you chose not to. You either need to perform the bios mode
install, or
*** This bug is a duplicate of bug 1638420 ***
https://bugs.launchpad.net/bugs/1638420
** This bug has been marked a duplicate of bug 1633913
lubuntu and ubuntustudio are missing pool; can not install without internet
connection
--
You received this bug notification because you are a
@Steve, a new test kernel here, with lots of netfilter and iptables
goodness:
http://kernel.ubuntu.com/~kamal/lp1723527.1/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723527
Title:
lxd fails to
** Summary changed:
- Gnome shell is too big
+ Allow GNOME fractional scaling below 100%
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
on my setup with ubuntu 17.10, the default gnome screen keyboard, a
touchscreen and without enabling screen keyboard in universal access =>
the screen keyboard disappears as soon as i handle a mouse. Did you use
onboard or the default screen keyboard ?
--
You received this bug notification
I had a computer guy do my Ubuntu upgrade to 16 but as you wrote here, he
did not do it well (and I already paid him a generous price for his time).
He warned me he is not so familiar with Ubuntu as with Windows. So should
I call him back or pay again to have someone who really knows Ubuntu
As of ubuntu 16.04.3, the problem demonstrated below, still exists.
Here is the solution as to how to install it on a clean system. Note
carefully, I always use apt-get, not synaptic. Also note that the _apt
user already exists.
sudo chown _apt
Edit to previous comment:
And if I understand correctly from
https://bugzilla.gnome.org/show_bug.cgi?id=709183, this is importing
gtk+2 modules via 'import gtk' as well as gtk+3 modules via 'import gi'
**which causes module conflicts**.
--
You received this bug notification because you are a
Another edit:
And if I understand correctly from
https://bugzilla.gnome.org/show_bug.cgi?id=709183, this is importing
gtk+2 modules via 'import gtk' as well as gtk+3 modules via 'import gi'
which causes module conflicts **(according to the same bug)**.
** Bug watch added:
According to https://bugzilla.gnome.org/show_bug.cgi?id=709183, gtk+2
and gtk+3 are mutually exclusive.
I've opened https://github.com/asweigart/pyperclip/issues/106 with the
upstream pyperclip project.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
commit 7a4e330a7f82869d161462b6f4b47f7d8ff963f2 (for trusty kernel)
changed autopkgtest to only build the first 'flavour'. However, this
causes failure on armhf because the 'lpae' flavour is still expected,
e.g.:
note the commit mentioned in the description is for trusty, but there
are similar commits for x/y/z/a that make autopkgtest fail for those
releases as well in the same way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mysql-5.6 (Ubuntu)
Assignee: Aldo (aldocr07) => Sonu Rajput (sonurajput)
** Changed in: mysql-5.7 (Ubuntu)
Assignee: Aldo (aldocr07) => Sonu Rajput (sonurajput)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of
** Summary changed:
- zfs-auto-snapshot 1.2.2-1 is broken
+ zfs-auto-snapshot 1.2.2-1 does not make snapshots
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719724
Title:
zfs-auto-snapshot 1.2.2-1
I can confirm that Kernel 4.13 in ubuntu 17.10 beta 2 fixes this
problem. No work around is needed to boot into the system or live media.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683184
Title:
The following packages ended up in the wrong component in the -proposed
pocket:
linux-aws 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main
linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead
of
The following packages ended up in the wrong component in the -proposed
pocket:
linux-meta-kvm 4.4.0.1009.9 - is in main instead of universe
linux-headers-kvm 4.4.0.1009.9 - is in main instead of universe
linux-image-kvm 4.4.0.1009.9 - is in main instead of universe
linux-kvm 4.4.0.1009.9 - is in
linux-image-4.10.0-37-generic Commit
b1943b80d393d40a75c7fd0679f51d6f998d28d5 fixed the problem. Wifi not
working again though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723174
Title:
Intel
Narrowing down a bit more, this can also be reproduced with the
following python script:
#!/usr/bin/env python
import gtk
import gi
The 2 lines of code that appear to be conflicting are:
1) /usr/lib/python2.7/dist-packages/keyrings/alt/Gnome.py
import gi
2)
** Merge proposal unlinked:
https://code.launchpad.net/~nacc/usd-importer/+git/usd-importer/+merge/332160
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699887
Title:
src:git fails to import due
This bug report unfortunately does not include a dpkg terminal log
showing output of the failing shim-signed package install. Marking
incomplete. If you can find the output of the shim-signed package
failure in your logs, please attach it to the bug.
** Changed in: shim-signed (Ubuntu)
** Description changed:
the autopkgtests for the kernel include 'ubuntu-regression-suite' which
contains this test:
sver=`dpkg-parsechangelog -SVersion`
read x rver x &2
- exit 1
+ echo "ERROR: running version does not match source package" 1>&2
+ exit 1
fi
-
-
*** This bug is a duplicate of bug 545790 ***
https://bugs.launchpad.net/bugs/545790
** This bug has been marked a duplicate of bug 545790
package PACKAGE failed to install/upgrade: error writing to '': Success
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
It should be possible to scale down the whole shell to less than 100%
e.g. 90% 85% etc.
thanks
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.5
---
dkms (2.2.0.3-2ubuntu11.5) xenial; urgency=medium
* 0014-remove-initrd-backup.patch: When removing a kernel also remove
related .old-dkms file from /boot after its been created not before.
(LP: #1515513)
--
The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package dkms - 2.3-3ubuntu1.2
---
dkms (2.3-3ubuntu1.2) zesty; urgency=medium
* 0014-remove-initrd-backup.patch: When removing a kernel also remove
related .old-dkms file from /boot after its been created not before.
(LP: #1515513)
-- Brian
>I do not use wayland, not compatible with the nvidia drivers ...
Oh, sorry, I didn't realize.
Could you try again now that bug 1721907 is fixed, and post any error
message you get if it still crashes? I tried on my machine with libsdl2
2.0.6+dfsg1-3ubuntu1 and I no longer get the DBUS warning
** Changed in: openjdk-8 (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Tiago Stürmer Daitx (tdaitx)
** Changed in: ubuntu-power-systems
Assignee: Canonical Foundations Team (canonical-foundations) =>
(unassigned)
--
You received this bug
** Changed in: openjdk-8 (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Tiago Stürmer Daitx (tdaitx)
** Changed in: ubuntu-power-systems
Assignee: Canonical Foundations Team (canonical-foundations) =>
(unassigned)
--
You received this bug
201 - 300 of 740 matches
Mail list logo
