Public bug reported:
The current GameMode package version is from an outdated git revision.
Stable version 1.5 was released last month.
Notably, the new version includes changes to avoid causing performance
regressions on Intel integrated GPUs:
Take care, current kernel 4.15.0-1036.38 still not bootable with EFI.
** Changed in: linux-raspi2 (Ubuntu)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
** Tags added: efi raspberry raspi2 uefi
** Tags added: raspberrypi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827750
Title:
Not boot with EFI
To manage notifications about this bug go to:
** Changed in: linux-raspi2 (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827750
Title:
Not boot with EFI
To manage notifications about this
System started, but I can't parse temperature. CPU freq info work fine.
cat: /sys/class/thermal/thermal_zone0/temp: No such file or directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827750
Dependency error of linux-headers-4.15.0-1035-raspi2 package. This is
required itself.
dpkg: package dependencies do not allow configuring the
linux-headers-4.15.0-1035-raspi2 package:
linux-headers-4.15.0-1035-raspi2 depends on linux-raspi2-headers-4.15.0-1035,
however:
The
Public bug reported:
Hello. I can't boot with linux-raspi2 kernel, but linux-generic work fine.
Please add support kernel option CONFIG_U(EFI)_STUB=y as default.
Thanks.
os: ubuntu 18.04 lts arm64
hw: raspberry pi 3b (+ tiano core uefi)
** Affects: linux-raspi2 (Ubuntu)
Importance:
I've confirmed that the nvidia-384 package in zesty-proposed is working
as expected (both GL and Vulkan apps work correctly).
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726809
Title:
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726809
Title:
Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json
To manage notifications about this
Looks like that's working here, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726809
Title:
Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json
To manage notifications
Public bug reported:
The Vulkan nvidia_icd.json included with the nvidia-384 package has the
wrong "library_path" set, meaning that no Vulkan apps can run. For
example, running "vulkaninfo" gives the following:
ERROR: [loader] Code 0 : loader_scanned_icd_add: Attempt to retrieve either
I am still having this issue. Ubuntu 14.04LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/934001
Title:
java assert failure: java: ../../src/xcb_io.c:178:
dequeue_pending_request: Assertion
The issue is that CONFIG_ANDROID_LOW_MEMORY_KILLER is enabled. I'm not
sure why this is on in the Ubuntu default kernel configuration as it
implements Android-specific behaviour. I installed the latest upstream
kernel package and the kernel config still has the low memory killer
enabled, so the
Public bug reported:
When I'm doing something memory intensive such as compiling a large
project I find that I start getting processes killed (mainly Chrome),
despite there still being a large amount of swap free. At first I
thought this was being done by the normal Linux oom-killer, but it's
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1206891/+attachment/3756049/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206891
Title:
apport information
** Attachment added: HookError_cloud_archive.txt
https://bugs.launchpad.net/bugs/1206891/+attachment/3756040/+files/HookError_cloud_archive.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected raring
** Description changed:
When I'm doing something memory intensive such as compiling a large
project I find that I start getting processes killed (mainly Chrome),
despite there still being a large amount of swap free. At first I
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1206891/+attachment/3756046/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1206891/+attachment/3756044/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206891
Title:
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1206891/+attachment/3756048/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206891
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1206891/+attachment/3756050/+files/UdevLog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: HookError_source_linux.txt
https://bugs.launchpad.net/bugs/1206891/+attachment/3756041/+files/HookError_source_linux.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1206891/+attachment/3756045/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206891
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1206891/+attachment/3756043/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206891
Title:
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1206891/+attachment/3756047/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206891
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1206891/+attachment/3756042/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206891
Title:
automount[2274]: lookup_init:136: lookup(yp): map auto.master: Local
domain name not set
type sudo hostname computername to fix.
found answer here
http://askubuntu.com/questions/40977/setting-up-nfs-client-shows-local-domain-name-not-set-error
this just happened to me, scary thing was it was
automount[2274]: lookup_init:136: lookup(yp): map auto.master: Local
domain name not set
type sudo hostname computername to fix.
found answer here
http://askubuntu.com/questions/40977/setting-up-nfs-client-shows-local-domain-name-not-set-error
this just happened to me, scary thing was it was
I saw that fix when I was googling around, but that fix went into .18,
and it's fixed on most distros with .18 or newer, so I was mystified as
to why it was happening on Gutsy.
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
https://bugs.launchpad.net/bugs/110585
You
As a workaround, you can add this to the kernel command line when
booting:
sym53c8xx.blacklist=true
That worked for me on my Compaq Proliant DL360 (G1), after some poking
around in busybox I found that d-i can have modules blacklisted by
adding module.blacklist=true to the command line.
--
Public bug reported:
Binary package hint: update-manager-core
I installed Edgy in a Xen VM using xen-tools on a feisty host. Xen-tools
didn't install psmisc in the VM, so when I tried to upgrade the VM to
feisty using do-release-upgrade, it died because it couldn't find
killall. Installing
See what I said, it's purposely disabled for a reason. If a process is
using logd for it's stdout, and logd gets stopped, that process will die
with SIGPIPE
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Binary package hint: system-config-printer
The system-config-printer tool (installable from Add/Remove Programs)
installs a menu item in System - Administration with the same title as
the menu item provided by gnome-cups-manager. This is confusing, since
you can't see which
Logd doesn't get started by default or used by default because there is
a bug in it, not just because it isn't started:
25-02-2007 13:43:25 AlexExtreme btw, what is the problem with logd?
25-02-2007 13:44:30 Keybuk kill it, any job with it as stdout ends up dying
mysteriously and silently
--
Heh, oops. I didn't mean to call the patch initctl.5, the actual patch
doesn't touch that file ;)
--
Documentation about vanished /etc/inittab should be added
https://launchpad.net/bugs/72058
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Here's a patch to add an initctl man page saying that it is deprecated
and has been replaced with the event.d directory. It points the reader
to the getting started document on the Upstart website.
Suggested changelog entry:
* util/man/inittab.5: new inittab man page mentioning that inittab has
Oops, forgot to add the patch
** Attachment added: initctl.5 man page
http://librarian.launchpad.net/5107967/upstart-add-initctl-man-page.diff
--
Documentation about vanished /etc/inittab should be added
https://launchpad.net/bugs/72058
--
ubuntu-bugs mailing list
Ok, it seems that console owner puts the output to tty12, the tty gdm
was running on.
--
Strange console output on shutdown
https://launchpad.net/bugs/69950
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hmm, when I do that I don't seem to get any output.
--
Strange console output on shutdown
https://launchpad.net/bugs/69950
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
I downloaded the desktop i386 ISO, and verified it with md5sums several
times. It also boots fine in qemu. But I have tried burning it to CD-RW
- I've tried it in 3 different machines, with 5 different CDs - and each
time the CD gets burnt incorrectly, i.e. the same sectors
40 matches
Mail list logo
