I linked the wrong bug; sorry.
https://bugs.launchpad.net/bugs/1767703 is the one to view the carnage
in the aftermath of this change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668148
Title:
B
I spent days trying unsuccessfully to do a clean install of 18.04 onto a
system with an existing version of Linux. Each time the installer would
appear to be working properly, only to bomb out with an error after half
an hour.
Eventually I gave up, REFORMATTED MY HARD DRIVE and was able to get the
Wonderful news! I'm glad we finally have a proper bug we can track.
Thanks for the update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767703
Title:
Calling 'apt-install grub-efi-amd64-signed' f
For the record, this bug is in the top 30 out of ALL of Ubuntu by bug
heat: https://bugs.launchpad.net/ubuntu/+bugs?orderby=-heat&start=0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767703
Title:
> I did get the warning.
I'm sure you did. With 293 people affected by this bug I'm sure there
are some that got a warning and ignored it.
I agree with Till; there is definitely something wrong with the
detection in some component somewhere.
--
You received this bug notification because you are
> A warning message prompted you that this could be a problem
Why do you keep saying this?
I ran the installer maybe five or six times and NEVER saw ANY warning
message. Stop claiming that I did.
This bug is NOT invalid.
** Changed in: grub-installer (Ubuntu)
Status: Invalid => Incomple
This bug also affects me; clean install of Bionic onto real hardware.
Let me know if I can supply any data that would be helpful in debugging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768230
Tit
Thanks for weighing in.
I don't mean to imply that there's a bug in Ubiquity. But there's
clearly a failure somewhere in the installation process.
And I'm going to complain every time this bug is closed as "invalid"
until there's a more appropriate bug to reference.
--
You received this bug not
There are some edge cases when the user's disk is partitioned to boot in
bios mode, but the EFI mode installer doesn't detect it.
There is supposed to be a warning message about this combination but it
does not always show up -- as evidenced by this thread.
For these users, there is NO indication
** Changed in: grub-installer (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767703
Title:
Calling 'apt-install grub-efi-amd64-signed' failed
To manage
I've been running Linux as my sole OS since 2001 and have been dual-
booting Windows and Linux since the summer of 2015.
In particular, Windows 7 with Ubuntu 15.04.
Upgraded in-place to 15.10 in December 2015. Then to 16.04 in May 2016.
Upgraded the Windows side to Windows 10 without issue in Jul
Public bug reported:
Trying to clean install Ubuntu 18.04 from a flash drive. It failed to
install and suggested that I file this bug report.
I have nothing else to add, sorry.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-gener
It seems the indicator is not displayed at all in Ubuntu 17.04 Zesty
Zapus under Unity for *all* Electron-based applications. For me it's
Discord that doesn't work.
Editing the .desktop shortcut with "env XDG_CURRENT_DESKTOP=Unity foo"
works for me as well.
I agree that changing the variable back
I'm seeing the same behavior after a reboot. Two fwupd processes
consuming 100% CPU each.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637024
Title:
fwupd consuming very high cpu after startup/log
Updated to the latest version of thermald and rebooted.
$ dmesg | grep "locked by BIOS"
(no output)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656528
Title:
thermald spamming syslog with 'sysf
The VERY first time I ran the stress test there was a single message:
Feb 1 18:04:11 graham-desktop stress-ng: invoked with 'stress-ng --cpu 0 -t
300s' by user 1000
Feb 1 18:04:11 graham-desktop stress-ng: system: 'graham-desktop' Linux
4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2
Well, it took a week but the messages started back up again. I did a
10-minute strace, so hopefully the log has the info you're looking for.
** Attachment added: "strace-2.log"
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1656528/+attachment/4807602/+files/strace-2.log
--
You rec
I'll reopen the bug if they return at some point and try to get you that
strace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656528
Title:
thermald spamming syslog with 'sysfs write failed
cons
Thanks for all your attention to my little issue. Sorry for rebooting in
the middle of a diagnostic session; I guess that's bad form.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656528
Title:
the
For the record, Crashplan is backing up a LOT of files for me: 3,324,286
files, so "watch file system in real-time" really could have been a LOT
of inotify watches.
25 minutes of uptime and still no thermald messages to the syslog.
--
You received this bug notification because you are a member o
I've got good and bad news. I configured Crashplan to no longer "Watch
file system in real-time" and rebooted (to get rid of any stale open
inotify watches).
And so far there hasn't been a single 'sysfs write failed
constraint_0_power_limit_uw' message written to the syslog since
rebooting (19 min
I attached the strace log.
Is there a chance it's related to this?
http://unix.stackexchange.com/questions/285529/internet-stops-working-
failed-to-add-run-systemd-ask-password-to-directory-wa
https://bugzilla.redhat.com/show_bug.cgi?id=894483
After I updated /etc/ssh/sshd_config I got an inter
** Attachment added: "strace.log"
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1656528/+attachment/4805141/+files/strace.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656528
Title:
Yikes. Well, it looks like I need to disable SSH password authentication
but here it is.
** Attachment added: "thermald-2.log"
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1656528/+attachment/4805137/+files/thermald-2.log
--
You received this bug notification because you are a me
Attached. I'll save you some suspense, though; it's literally the same
line over and over 38,000 times.
$ cut -b 16- thermald.log | sort | uniq -c
38147 graham-desktop thermald[1086]: sysfs write failed
constraint_0_power_limit_uw
** Attachment added: "thermald.log"
https://bugs.launchpa
$ grep "model name" /proc/cpuinfo
model name : Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (repeated 8 times)
And there's really nothing in the kernel log, I swear. I've attached it
just so you can see for yourself.
** Attachment added: "/var/log/kern.log"
https://bugs.launchpad.net/ubuntu
Public bug reported:
This seems somewhat related to
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1543046
For some reason thermald is writing the message "sysfs write failed
constraint_0_power_limit_uw" to the syslog every few seconds. However,
there's nothing in the kernel log.
$ cat
Public bug reported:
Just trying to update using Software Updater
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-34-generic 4.8.0-34.36
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
Still having this problem.
$ uname -a
Linux foo 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64
x86_64 x86_64 GNU/Linux
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"
--
You received this bug n
I also have this problem. Nothing shows up in dmesg or lsusb when I plug
a hard drive into the USB 3.0 ports on the back of my PC. The same drive
works normally if I use a USB 2 port instead.
Let me know if I can post any diagnostic information that would help
tracking this down.
--
You received
*** This bug is a duplicate of bug 842572 ***
https://bugs.launchpad.net/bugs/842572
Also happens on a clean install of 12.04. Crash was repeatable when
USHARE_ENABLE_DLNA=yes
...was in /etc/ushare.conf. Removing it (changing back to)
USHARE_ENABLE_DLNA=
...fixed the problem and ushare se
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913580
Title:
Not sure. Trying 12.04 alpha 1 installer. It "crashed" and directed me
here.
To manage notifications about this bug go to:
https://bugs.
Public bug reported:
?
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.9.5
ProcVersionSignature: Ubuntu 3.2.0-2.5-generic 3.2.0-rc3
Uname: Linux 3.2.0-2-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CasperVersion: 1.292
Date: Sun Jan 8 17:37:01 2012
LiveMediaBu
Same issue for me; attempting a dist-upgrade from 8.10 LTS.
Upgrade threw an error but then seemed to finish. However, upon
rebooting, the system was in an unusable state. Thanks to seeing this
page before rebooting, I knew to try
# apt-get remove linux-image-2.6.24-19-generic
...and then the
34 matches
Mail list logo
