The download from http://releases.ubuntu.com/17.10/ubuntu-17.10-server-
amd64.iso works (i.e the sha256 checksum is correct). However I continue
to get a different checksum every time I download it from
http://uk.releases.ubuntu.com/17.10/ubuntu-17.10-server-amd64.iso.
@ Brian Murray - As it's wor
@Brian Murray - Thanks for checking.
Given that no one else seems to have this problem, I can only guess that
my ISP's proxy sends me an old cached version or someone indeed does the
unbelievable.
I will investigate and report back.
--
You received this bug notification because you are a member
@bot As it currently stand I don't suspect a bug in a particular
package. All it seams to me that some or all web servers that provide
the Ubuntu 17.10 "ubuntu-17.10-server-amd64.iso", are not up to date and
therefore the sha256sums results do not match the ones provided with
http://uk.releases.ubu
Could it be that the mirror is not up to date? It shows that the ISO was
updated on 17/10/2017 whereas I do find it likely that it should be at
least 19/10/2017?
ubuntu-17.10-server-amd64.iso 2017-10-17 20:46 745M Server
install image for 64-bit PC (AMD64) computers (standard download)
Public bug reported:
Current Time is 12:10 BST
When I download the "ubuntu-17.10-server-amd64.iso" from
http://uk.releases.ubuntu.com//17.10/ubuntu-17.10-server-amd64.iso
the sha256sum published at
http://uk.releases.ubuntu.com//17.10/SHA256SUMS does not match the
sha256sum of the ISO downloade
I believe I encounter this issue with Ubuntu 17.10, which uses "gnome-
session 3.26.1-0ubuntu5".
The story, I installed Ubuntu 17.04 back in September 2017 and been
using Online Accounts for three Gmail accounts. The email client
Evolution was working fine. I then upgraded to Ubuntu 17.10 a couple
This is a re-write of my previous response, as I should have reviewed it
before submitting. I have simply been too excited! ;-)
@Kai-Heng Feng and @Anmar Queja
I have upgraded to Ubuntu 17.10 and used the suggested nouveau.modeset=0
kernel boot option.
It works perfectly. I can indeed see many i
@Kai-Heng Feng and @Anmar Queja
I have upgraded to Ubuntu 17.10 and used the suggested nouveau.modeset=0 kernel
boot option.
It works perfectly. I can indeed see many improvement. Most and foremost
Wayland is working as far as I can see!
The only hiccup I had was with the laptop suspending right
I have tested with provided kernel at
http://people.canonical.com/~khfeng/lp1697556/3/
The test setup was the same as previously.
Short answer: It does not work.
Long answer: I can see the icon circling for a while. While this happens
I cannot toggle between the boot text output and the circling
I have tested with kernel 4.10.0-lp1697556
http://people.canonical.com/~khfeng/lp1697556/2/ with the default kernel
parameters and with the same hardware setup as previously.
Short answer: It works.
Long answer: The login screen is displayed on built in monitor, while
the laptop is closed. The lo
I have tested with kernel 4.11.0-rc1-lp1697556 with the default kernel
with the same hardware setup as previously.
Short answer: It works.
Long answer: The login screen is displayed on built in monitor, while
the laptop is closed. The login works. Network issues but they are not
relevant to this
Your question:
"so what's the result on v4.12-rc1, without "nomodeset"?"
Short answer: It does not freeze.
Detailed answer:
With v4.12-rc1, by using the default kernel arguments (i.e. without
"nomodeset"), it does not freeze. It shows the login screen on the closed
laptop, which you pointed out
** Attachment added: "Kernel 4.12-rc1 log using default kernel argument"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957550/+files/kernel.log.4.12-rc1WithDefaultKernelArguments.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Attachment added: "Kernel 4.11.12 log using nomodeset argument"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957291/+files/kernel.log.4.11.12.nomodeset.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Attachment added: "Kernel 4.11.12 log when using blacklist nouveau arguments"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957292/+files/kernel.log.4.11.12.blacklist.nouveau.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
@Kai-Heng
In answer to your question "Can you confirm v4.11 freezes but v4.12-rc1
doesn't?", I can confirm that 4.11.12 freezes. Kernel log shows "NMI
watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [kworker/3:1:70]".
Below are the test details along with the corresponding kernel log
output.
K
** Attachment added: "Kernel 4.11.12 log using default kernel arguments"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957290/+files/kernel.log.4.11.12.WithDefaultKernelArguments.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
@Kai-Heng
Concerning your question:
v4.12-rc1 with NOMODESET -> Successfully logged in.
v4.12-rc2 with NOMODESET -> Successfully logged in.
v4.12-rc5 without NOMODESET-> Successfully logged in.
Can I say that -rc2 has freeze but -rc5 doesn't freeze?
I would say that neither of those two kernels f
@Kai-Heng
Here are the test results when starting the kernel with "blacklist=nouveau
modprobe.blacklist=nouveau".
The Dell XPS 9560 is connected to Dell Thunderbolt Dock TB16 with the external
monitor and the external keyboard being connected to the docking station.
Short answer:
v4.12-rc1 -> S
@Kai-Heng Feng (kaihengfeng)
Based on your suggestion I have tested with the below mainline kernels as well
as the current 17.04 kernel.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc2/
http://kernel.ubuntu.com/~kernel-ppa/mainline/
@dani_bs(sdaniele78)
I trust you commented and changed the state of the bug with good intent.
Please accept my apology for being so direct... it was a complete fail.
Both links referenced do not provide any solution. One link mentions to
alter the "acpi_osi kernel parameters" without details what
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556
Title:
Computer freezes after login - 4.10.0-22-generic
To manage notifi
I have reviewed the kernel source code that was committed between the
Ubuntu-4.10.0-21.23 and Ubuntu-4.10.0-22.24 and I believe commit
b93843fcde501b9264ac5dbe2c980eb0b479 introduced bug #1697556.
Commit b93843fcde501b9264ac5dbe2c980eb0b479 corresponds to
https://bugs.launchpad.net/ubuntu/
In line with comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/11,
the workarounds suggested with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/9
do not work with kernel 4.10.0-28 either. The computer freezes just
before the login screen appears.
I have tested the suggested workarounds that were given with comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/9
in conjunction with kernel 4.10.0-24. Those two workarounds basically
suggest not to use the nouveau driver but instead the Nvidia drivers.
Those workarounds
In answer to your question
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/6
I have tested with Kernel 4.12.0, and DID NOT ENCOUNTER this problem.
linux-headers-4.12.0-041200rc5_4.12.0-041200rc5.201706112031_all.deb
linux-headers-4.12.0-041200rc5-generic_4.12.0-041200rc5.201
In answer to your qeustion
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/3
* Yes, the problem is NOT encountered when using Kernel linux-
image-4.10.0-21-generic 4.10.0-21.23.
* The problem is encountered when using 4.10.0-22-generic
In response to your request
https://bu
** 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/1697556
Title:
Computer freezes after login - 4.10.0-22-generic
To manage notifications about this bug go to:
Public bug reported:
I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
ago. Login worked fine too.
A couple of days later I installed the suggested kernel update
"4.10.0-22-generic". With kernel 4.10.0-22-generic
Public bug reported:
isc-dhclient-4.3.3 does not acquire a new DHCP lease when the Ethernet
cable was disconnected and reconnected.
This problem is observed with Ubuntu 16.04 whereas it's working with
Ubuntu 14.04 (i.e. isc-dhclient-4.2.4).
The Problem:
When using Virtualbox 5.0.20 and Vagrant 1
*** This bug is a duplicate of bug 1533458 ***
https://bugs.launchpad.net/bugs/1533458
Public bug reported:
The error was encountered when I run the Ubuntu Software Updater now
(13/01/2016 - 09:00 GMT).
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fonts-tlwg-kinnari-ttf (not ins
I am running 16.04 and installing
"shutter_0.93.1-ppa1-ubuntu16.04.1_all.deb" resolved this problem for me
too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532364
Title:
Shutter silently fails
T
I am having the same problem too. Since so many different Evolution
versions are affected, I get the impression that this problem is induced
by Google...
Ubuntu 15.04 64-bit
Evolution 3.12.11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I think I got to the bottom of it.
Short version:
If the ".treeinfo" file is missing from the repository, the error "ERROR
global name 'fetcher' is not defined" is encountered.
Long version:
I had used wget to download the Centos 7 packages from a website mirror to keep
them on my local HTTP
34 matches
Mail list logo
