I've now added a check for whether CONFIG_KALLSYMS is enabled in the
running kernel and adjusted the expected test results based on that, in
qrt commit https://git.launchpad.net/qa-regression-
testing/commit/?id=cde457932459a525c75126db8a8d4b7262d4da24 . This
should address this failing test case,
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761051
Title:
laptop sound broken in latest update -- "No output or input devices
found"
To manage
Hi,
No luck. Still no touchpad :(
I was going to do a clean install of 18.04. Is this an idea?
Cheers
On 25 April 2018 at 20:17, Kai-Heng Feng
wrote:
> Please try if kernel parameter "i8042.noloop=1" works for you.
>
> --
> You received this bug notification
Interesting.
I'm glad you resolved it on your own, but lets try to understand what happened
if we can still do that after the cleanup.
Touch erroring with "does not exist" means the path is gone.
But this dir is part of package libvirt-daemon-system and if not removed should
always be there.
I would suggest testing
commit de77ecd4ef02ca783f7762e04e92b3d0964be66b
Author: Mahesh Bandewar
Date: Mon Mar 27 11:37:33 2017 -0700
bonding: improve link-status update in mii-monitoring
and
commit d94708a553022bf012fa95af10532a134eeb5a52
Author: WANG Cong
I take it this does not apply to Wine development release 3.6, so I'll
have to build from a fresh git or use the patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/357456
Title:
Wine 1.1.20
** No longer affects: libnl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312419
Title:
nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache
To manage notifications about this bug go
** Tags added: trusty2xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767247
Title:
#1069160 Could not calculate the upgrade .
To manage notifications about this bug go to:
** Attachment added: "syslog for version 20180426"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1764008/+attachment/5128130/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Same trouble with version 20180426.
** Attachment added: "partman for version 20180426"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1764008/+attachment/5128128/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** 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/1767263
Title:
16.04 to 18.04
To manage notifications about this bug go to:
Confirmed by duplicate bug reports.
** Tags added: bionic xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532267
Title:
Atheros QCA9565 Bluetooth not recognized
To manage notifications
See also bug 1475639
** Summary changed:
- 168c:0036 [Aspire E5-573G] Bluetooth not recognized
+ Atheros QCA9565 Bluetooth not recognized
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532267
*** This bug is a duplicate of bug 1532267 ***
https://bugs.launchpad.net/bugs/1532267
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 1532267, so it is being marked as such. Please
Is this still an issue? See also bug 1532267
** Summary changed:
- No adapter found in bluetooth
+ Atheros QCA9565: No adapter found in bluetooth
** Changed in: linux-firmware (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1532267 ***
https://bugs.launchpad.net/bugs/1532267
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 1532267, so it is being marked as such. Please
Public bug reported:
Can not calculate update
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.25
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture:
Public bug reported:
i don't know what kind of bug that was but i saw some pakages installing
process and its crash auto.
than some window pop- out and says can't reboot your system.
that's all i know.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.6
Public bug reported:
x
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.10
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CasperVersion: 1.387
CurrentDesktop: ubuntu:GNOME
For Xenial, when can we expect the Ubuntu-1.157.18 release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757443
Title:
Redpine: BLE radio lost issue
To manage notifications about this bug go to:
Yes, for Bionic, Redpine will push their FW into upstream linux-
firmware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757443
Title:
Redpine: BLE radio lost issue
To manage notifications about
Which laptop light do you refer to?
I can't find any PCIe errors from the dmesg in the bug report.
Also, I guess it's time to try Bionic (18.04). The GNOME in 16.04 is
quite old.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: terminator
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767245
Title:
terminator crashes on xserver, gnome-shell
To manage notifications about this bug go to:
Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764597
Title:
watchdog: BUG: soft lockup - CPU#1 stuck
Hi,
Same issue.
I am using similar test application to get the neighboring mac addresses
on a Centos 7.2.1511 machine. Installed 3.21, 3.28, 3.4 versions and all
returned with NULL.
Is this going to be fixed? Or Is there any other API within libnl3 that
can do the trick?
Abhik
--
You
Please try toggling the switch in the header bar to ON (next to the
minimize/maximize/close buttons).
If that doesn't work then it appears the problem is that the kernel has
not detected your bluetooth hardware (see rfkill.txt above).
** Also affects: gnome-control-center (Ubuntu)
[Expired for flatpak (Ubuntu) because there has been no activity for 60
days.]
** Changed in: flatpak (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for kernel-package (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: kernel-package (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for wine (Ubuntu) because there has been no activity for 60
days.]
** Changed in: wine (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658884
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741839
quiet splash ---
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
LANGUAGE=en_CA.UTF-8
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_CA.UTF-8
LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fre
[Expired for gnome-software (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: gnome-software (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Steve,
the result is:
ubuntu@ms10-34-mcdivittB0-kernel:~$ cat /proc/self/personality
0040
ubuntu@ms10-34-mcdivittB0-kernel:~$ uname -a
Linux ms10-34-mcdivittB0-kernel 3.13.0-146-generic #195-Ubuntu SMP Tue Apr 24
14:56:21 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
--
You received this
I guess that's because I pulled a bunch of fixes from v4.16 to Bionic
kernel.
I pulled two additional commits from v4.17, please try this kernel:
https://people.canonical.com/~khfeng/lp1767088/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I can't open bluetooth in the setting panel,it's gray.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture:
-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 27 08:31:02 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
: ubuntu:GNOME
Date: Fri Apr 27 03:54:15 2018
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
LANGUAGE=en_US.UTF-8
PATH=(custo
I have checked the kernel config for 4.15 linux-kvm, it's true that:
# CONFIG_KALLSYMS is not set
Do you want me to test it with the config enabled? I can build a test
kernel for this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-initial-setup (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/1766277
I had Ubuntu Mate 17.10 installed previously.
The Ubuntu 18.04 installer crashed when trying to install Grub at very
end of the 18.04 install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
** Also affects: libnl
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/1312419
Title:
nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache
To
*** This bug is a duplicate of bug 1759920 ***
https://bugs.launchpad.net/bugs/1759920
I was able to successfully boot the latest 17.10 kernel: linux-
image-4.13.0-39-generic
This issue is resolved.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have this problem, and found a thread here:
https://askubuntu.com/questions/584207/cannot-log-in-at-locked-screensaver-must-log-in-with-switch-user?utm_medium=organic_source=google_rich_qa_campaign=google_rich_qa
The fix that worked for me was a permission problem on /etc/shadow
$ ls -l
** Tags added: fixed-in-3.28.2 fixed-in-3.29.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758528
Title:
gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() from
gbm_get_next_fb_id()
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-pip (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/1659084
Title:
** Tags added: fixed-in-3.28.2 fixed-in-3.29.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723615
Title:
gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
To manage
Public bug reported:
I am upgrading from ubuntu 14.04 to 16.04
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.10
ProcVersionSignature: Ubuntu 4.4.0-121.145~14.04.1-generic 4.4.117
Uname: Linux 4.4.0-121-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
This crash is now fixed in Ubuntu 18.04. But I'll leave the gnome-shell
task open for a while to help people and bots find the bug more easily.
** No longer affects: gdm3 (Ubuntu Artful)
** No longer affects: gdm3 (Ubuntu)
--
You received this bug notification because you are a member of
I can not reproduced this issue with image "ubuntu-18.04-desktop-amd64" just
downloaded at 10:00am UTC+8.
md5sum 129292a182136a35e1f89c586dbac2e2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767067
Public bug reported:
I don't know
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libxdamage1:i386 1:1.1.4-2
ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
Uname: Linux 4.4.0-121-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CompizPlugins: No value
Public bug reported:
Hi,
I just updated my ubuntu to 18.04 and tried to run the terminator.
Terminator starts normally and when I try to maximize or press windows
key to open dash, the terminator disappears.
I have noticed that the same behavior in ubuntu 17.10 xserver also, It
works perfectly
** No longer affects: gnome-shell (Ubuntu Artful)
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** No longer affects: gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505409
Title:
gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from
_XEventsQueued()
** Changed in: thunderbird
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/274647
Title:
Thunderbird fails to perform undo operations correctly
To manage
Next, please report the problem to the dock developers here:
https://github.com/micheleg/dash-to-dock/issues
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766710
Title:
With auto-hide enabled,
Thanks. Yes I somehow missed the part about auto-hide.
** Summary changed:
- Dock and Headerbar backgrounds not coordinated
+ With auto-hide enabled, the dock darkens independently of the panel
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => Confirmed
**
On Fri, 2018-04-27 at 02:15 +, Daniel van Vugt wrote:
> I'm guessing the reason why we don't see many reports of this crash
> is
> because it's possibly triggered by shell extensions that Ubuntu
> doesn't
> normally ship with.
>
> Yours are:
> b'org.gnome.shell' b'enabled-extensions'
:28 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed
boot=casper quiet splash ---
LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fre
I'm guessing the reason why we don't see many reports of this crash is
because it's possibly triggered by shell extensions that Ubuntu doesn't
normally ship with.
Yours are:
b'org.gnome.shell' b'enabled-extensions'
b"['freon@UshakovVasilii_Github.yahoo.com', 'netsp...@hedayaty.gmail.com',
*** This bug is a duplicate of bug 1766137 ***
https://bugs.launchpad.net/bugs/1766137
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 1766137, so it is being marked as such. Please
I've reproduced this with the 4.15 linux-kvm kernel. I'm not sure why
it's doing this, though:
ubuntu@sec-bionic-amd64:~$ sudo cat /proc/modules
kvm_intel 200704 - - Live 0x
pata_acpi 12288 - - Live 0x
ubuntu@sec-bionic-amd64:~$ cat /proc/version_signature
I can't seem to find any existing reports of this crash. All I can tell
is that it looks like Ubuntu 16.04...
Please help us to debug it further by:
1. Applying the workaround from bug 994921.
2. Look in /var/crash for .crash files and when found run:
ubuntu-bug /var/crash/YOURFILE.crash
3.
On Fri, 2018-04-27 at 01:32 +, Daniel van Vugt wrote:
> Chris,
>
> You seem to have opened two bugs for this crash. Bug 1706203 is
> almost
> the same.
>
> If it's still happening then let's continue using bug 1706203.
>
Sounds good to me, I'll just have to remember the next time it happens
jeremyayerst, this report is closed. Hence, it will help immensely if you use
the computer the problem is reproducible with, and provide necessary debugging
logs by filing a new report with Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Changed in: linux
Yes it's possible one of your icons uses 16-bit colour, and explains why
we don't see other/many reports of this crash.
In theory we should hit this problem more often, given that we have:
/usr/share/icons/hicolor/
and "high color" means 16-bit (or 15-bit). But apparently most icons in there
Please also run this command to automatically attach more system
information:
apport-collect 1767065
P.S. Ubuntu 18.04 was released a few hours ago :)
https://www.ubuntu.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@experimancer, I am sorry that you thought my response was arrogant.
The nature of the release process is that it's not possible to provide
an exact hour and minute for release. The release was announced months
ago that it would happen on April 26. In an extraordinary event, it's
possible for a
Yes, i should be able to test with the v4.16 kernel. I'll try to do
that tonight.
I'm sorry I didn't see your note earlier!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761051
Title:
laptop
I also agree that https://imgur.com/qS0ODeq would be best.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762465
Title:
Nautilus sidebar theming is confusing
To manage notifications about this bug
Issue still occurring in 4.17-rc2.
Which mailing list should I email with the bug report? I have no idea
what the actual cause of this issue is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764597
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694225
Title:
[Thinkpad T450s] Click lock effect on trackpoint left button when
touchpad is disabled
To manage notifications
Public bug reported:
Ubuntu 16.04.04 LTS
Wireless LAN fails to operate stating "device not ready" on some initial
start ups. Can force the issue correct by opening Terminal and entering
"sudo modprobe wl".
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source
Public bug reported:
grub-efi-amd64-signed failed to install during new install
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.34.9+13-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
Chris,
You seem to have opened two bugs for this crash. Bug 1706203 is almost
the same.
If it's still happening then let's continue using bug 1706203.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux
Status: Confirmed => 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/1052933
Title:
Kernel oops -- IP: [] ttm_bo_mem_put+0x20/0x30 [ttm]
(radeon) 3.2.0-30
I found a work around. The thumb drive auto booted to the UEFI version
of the installer. I have a non UEFI install of Windows 10 installed. I
think that is why it crashed. I was able to successfully install Ubuntu
Mate with the traditional BIOS version of the installer. Someone should
still
: 1.394
Date: Thu Apr 26 20:33:33 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present
Public bug reported:
Ubuntu 18.04
gnome-shell 3.28.1
After login, the screen stays blank (not black but the default ubuntu
purpleish color) with only the mouse cursor on. After force restarting,
can sometimes log on the restart. When the login is completed, a message
about a gnome-shell crash
Compatibility issue with GDM on Ubuntu 18.04 was fixed in zram-config
version 0.7
Updated code and packages can be found at:
https://git.launchpad.net/~eugenesan/+git/zram-config
https://code.launchpad.net/~eugenesan/+recipe/zram-config-ppa
--
You received this bug notification because you are
Bug reports requires the "Package" information. So, here it goes. But
the bug is not limited to "rhythmbox," it is a general bug to Ubuntu
18.04 LTS.
** Package changed: ubuntu => rhythmbox (Ubuntu)
** Summary changed:
- Random vertical stripes
+ Random stripes and dots
** Description changed:
Public bug reported:
After I upgrade Kubuntu from 17.10 to 18.04, and restarted it, all I'm
seeing is my mouse cursor, which responds to my movements, and that's
pretty much it. I tried to see if I can start up sddm, but that failed.
I got to login by installing slick-greeter and use that
Compatibility issue with GDM on Ubuntu 18.04 was fixed in zram-config
version 0.7
Updated code and packages can be found at:
https://git.launchpad.net/~eugenesan/+git/zram-config
https://code.launchpad.net/~eugenesan/+recipe/zram-config-ppa
** Changed in: zram-config (Ubuntu)
Status: Fix
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
The attachment "ejabberd-pam-apparmor.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 by a Launchpad user owned by
--- Comment From chngu...@us.ibm.com 2018-04-26 20:38 EDT---
- We have decided to replace the qlogic by Emulex.
- Apply the new kernel patch in 208.
- add the slub_debug=FZPU
System is up with latest kernel and ready now.
root@boslcp3:~# uname -a
Linux boslcp3 4.15.0-20-generic
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shim-signed (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/1683663
Title:
Public bug reported:
The multilib setup is not working in the bionic version of gcc-arm-none-
eabi (gcc v6.3.1). For example, if I build a project with
"-mcpu=cortex-m4" or "-march=armv7e-m" and link with:
arm-none-eabi-gcc -o someoutput.elf object1.o object2.o -mthumb -Wl
,--gc-sections
---
LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: grub-installer (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bioni
Hi, I just tested the issue with Ubuntu 18.04 LTS which using Linux
kernel v4.15.0-20, and unfortunately the issue still exists.
I wonder if you can compare the ubuntu kernel code with kernel from
fedora or arch linux since they have no issue.
--
You received this bug notification because you
Hi Po-Hsu,
I'm not sure why this test is failing on linux-kvm. I've modified the
test in question to dump the contents of /proc/modules when the test
fails in qrt commit https://git.launchpad.net/qa-regression-
testing/commit/?id=b47b677b9f99af9539558044ccdb9b4769f1732e ; if we can
get a re-run
iso build 20180426 fixed the issue
** Changed in: ubiquity (Ubuntu)
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/1767170
Title:
Black screen with cursor o
I believe I am affected by this issue as well. I have a Google WiFi
device as a router, and everything works well for the first few days,
with the link-local address used on the Google WiFi's RA used as the
IPv6 default route.
After a couple of days however, the Google WiFi device changes its
Confirmed that applying this patch makes my perf command not crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767204
Title:
perf record crash due to swapped xyarray function signatures
To
Public bug reported:
When I put the audio out on the TV through HDMI there is a delay for the
sound to start appearing after leaving a video or music paused for a few
minutes.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu
@21:
https://lists.ubuntu.com/archives/ubuntu-announce/2018-April/000231.html
while you were demanding to be informed about every step developers and
volunteers do at the release, they did their job and made the release happen.
If you are really that interessted in the release process, i bet the
I used method 1 with the addition of disabling HDA Nvidia in
pavucontrol, configuration. I had been using HDMI output but wanted to
switch back to generic analogue stereo duplex. This was not working
until I disabled HDMI.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: wine
Status: Unknown => 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/357456
Title:
Wine 1.1.20 crashes while installing Photoshop CS4
To manage notifications
Oh, except for a less dramatic deviation from the current design the
sidebar should have orange text and an undivided dark background, I
think, rather than an orange line, as in the most recent imgur. Probably
the lighter shade of gray should be used.
--
You received this bug notification
I think the latter solution - keep the dark background but remove the
line - makes the most sense. Can this be SRU'd to 18.04 when done? I
think this is a significant enough design bug that an SRU should be
done? Regression potential would be, perhaps, that updates (the change
from the buggy UI to
1 - 100 of 764 matches
Mail list logo