[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (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/1300557
T
Hello? Any corrections for that revisions range you wanted me to
bisect?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
To manage notifications abou
This last weird effect was transient; it went away after a reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
To manage notifications about this
It just got a bit weirder.
I've got my custom xrandr-defined 2560×1440 resolution going. But for
purposes like window placement, resizing windows, and maximising
windows, the UI seems to think it's 1920×1080 or thereabouts.
So if I open a whole bunch of editor windows from the shell, they all
ap
This is getting awkward. The upper-bound version you wanted me to
bisect is also missing from the Ubuntu/upstream version mapping. So
even if I want to bisect upstream versions I still have the same
problem. Are you sure you gave me the correct versions for bisection?
Maybe you meant 3.13.0-20.4
Thanks. Could you also update that section? It says that it applies in
two situations, but it never actually lists those two situations. I
*think* (but without already knowing of course I can't be sure) that
it's meant to refer to a list of three headings, “BISECTING: A MERGE
BASE MUST BE TESTED
Jeroen T. Vermeulen, as advised in
https://wiki.ubuntu.com/Kernel/KernelBisection#Map_Ubuntu_kernel_to_mainline_kernel_for_mainline_bisection
it would be best to switch to commit bisecting the mainline kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for following up. I read most of that document, but it's
difficult in places. My understanding is that what you're asking me to
do is what's described under “Commit bisecting Ubuntu kernel versions,”
correct? That's the only part of the main page (excluding the FAQ
below) that seems to ap
Jeroen T. Vermeulen, just to advise, you asking follow up questions
doesn't make this less Incomplete, or more Confirmed. Until this is
bisected, it's most difficult for a developer to attend to this, let
alone have this Triaged and upstreamed.
Despite this, I want to confirm you have read the ent
If you don't have time to read what I wrote, or if something I wrote is
not clear, just say so and I will understand. Let's not get caught in
the endless Confirmed/Incomplete circle.
I'll summarise what I said before, to make it easier to digest:
You asked me to bisect between 3.13.0.18.38 and 3
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
To manage notifications about thi
Read back and it will become clear.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer wor
Jeroen T. Vermeulen, instructions for commit bisecting are fully defined
in the previously provided article. So, it is unclear how precisely you
can't find kernel sources.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
Once again: with the given instructions I can't bisect kernel commits
any further. Is there another way to obtain the kernel source versions
we need?
Marking as Confirmed again until then, to avoid this bug timing out.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
To manage notifications about thi
Oh, one other thing: with the older kernels I can play AssaultCube
again! I couldn't really do that with the current Vivid kernels because
the frame rate was too low. Reported frame rate would be around 60 fps,
but it looks more like 10 fps. With these old kernels it plays
smoothly.
--
You rec
Nope, the Utopic kernel branch only has 3.13.0-19.40 and 3.13.0-20.41,
nothing inbetween.
So, all I know is up to and including 3.13.0-19.40 it still works OK.
The problem must have been introduced later than that.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You rece
The Precise kernel repository finished downloading, but it doesn't have
3.13.0-20.24. It has 3.13.0-19.39 and 3.13.0-20.41, nothing inbetween.
Pinning my hopes on the Utopic branch...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
3.13.0-19.40 also works OK! So it broke sometime after that.
I'm now trying to find 3.13.0-20.24 in one of the kernel branches from
before Vivid. It's not in the Trusty branch. I can't get the Quantal,
Raring, or Saucy ones, presumably because those releases are no longer
supported. Downloadin
Using the ubuntu-vivid kernel branch, 3.13.0-18.38 works OK.
That branch has no tag Ubuntu-3.13.0.20.24 or Ubuntu-3.13.0-20.24. The
closest tags I see are Ubuntu-3.13.0-19.40 and Ubuntu-3.13.0-20.41.
I'll try 3.13.0-19.40 next.
--
You received this bug notification because you are a member of U
Jeroen T. Vermeulen, the next step is to fully commit bisect from kernel
3.13.0.18.38 to 3.13.0.20.24 in order to identify the last good kernel
commit, followed immediately by the first bad one. This will allow for a
more expedited analysis of the root cause of your issue. Could you
please do this
** Tags removed: kernel-bug-exists-upstream-4.0-rc4 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-4.1-rc8 needs-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Tried 4.1-rc8 as well for good measure. Still no improvement. Highest
resolution offered in the System Settings is 1920×1200.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen re
No Tried 4.1-rc7. No change.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
To
Jeroen T. Vermeulen, could you please test the latest mainline (kernel
4.1-rc7) and advise to the results?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Marking this bug as "Confirmed" to avoid timeout. It was marked
Incomplete pending testing against Saucy, but as of a few months ago the
results are shown above.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member o
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
To manage notificati
After another reboot this effect seems to have gone away. So I still
don't have my native resolution available by default, but at least I can
get it back by defining it with xrandr.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Correction: that last upgrade was *from* 3.19.0-14.14, not *to* it. It
was the upgrade to 3.19.0-15.15.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer work
Hurray, the problem just got a little worse!
After the upgrade to kernel 3.19.0-14.14, when I define my monitor's
native resolution using xrandr, I get the right *resolution* but still
not the right number of *pixels*. So I'm getting (as far as I can see)
one logical pixel per physical pixel on t
Well, I did some bisecting but the results are disappointing. Actually
I ended up trisecting. On Saucy, kernel...
3.11.0-12 was OK. Recognised my full native resolution and enabled it
by default. Wonderful.
3.11.0-13 to 3.11.0.24 inclusive were completely messed up. They booted
in some ultra
I could temporarily swap out the hard drive and install Saucy on the
spare. More after the weekend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
T
Jeroen T. Vermeulen, working at it from a different angle, would you be
able to boot into a Saucy environment, and then test the latest mainline
kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/13
Okay, I got a seemingly successful install of the last Saucy kernel.
But it's not working very well: I get a super-low-res login screen, and
the system doesn't respond to keyboard or mouse. (It does notice the
power button, so it's not frozen). This happens both with the default
boot on that kern
Trying 13.11.0-17. There was a problem while installing linux-headers
though... "fwts-efi-runtime-dkmis 15.03.00-0ubuntu1: fwts-efi-runtime-
dkms kernel module failed to build." Somewhere along the way it said:
run-parts: executing /etc/kernel/postinst.d/dkms 3.11.0-17-generic
/boot/vmlinuz-3.
Jeroen T. Vermeulen, could you please boot into a kernel from Saucy
following https://wiki.ubuntu.com/Kernel/KernelBisection and advise if
this issue is still reproducible?
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
The latest upstream version I found there was v4.0-rc4-vivid. It boots,
but it doesn't fix the problem.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.0-rc4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Jeroen T. Vermeulen, could you please test the latest upstream kernel
available from the very top line at the top of the page (the release
names are irrelevant for testing, and please do not test the daily
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will
allow additional ups
The version that was installed on March 31 was 3.13.0.20.24. The
version I uninstalled right after that was 3.13.0.18.38.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolut
Jeroen T. Vermeulen, which kernel version specifically was updated (i.e.
from what version to what version)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer
According to the dpkg.log for that date, quite a lot: libc-bin for
amd64. Also gcc-4.8, gcc-4.9, along with g++, cpp, libgcc1, libstdc++6
etc, for amd64 and i386; and libitm1, libgomp1, libgfortran3, libasan0,
libatomic1, libtsan0, libquadmath0, libthumbnailer0, apport, apport-gtk,
python3-proble
Jeroen T. Vermeulen, could you please advise what packages were upgraded
precisely on 2014-04-01 that correlates to this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen re
No change in 15.04. I can add the resolution with xrandr, and after
that I can use it. But after reboot, I have to do it again.
The upgrade got stuck with a black screen and no networking, but I
eventually got out of it with the "apt-get dist-upgrade" dance from the
console. I hope that hasn't
I first upgraded to 14.10; that didn't change anything. Trying 15.04
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
To manage notifications abo
Something happened to this bug's conversation: the message asking me to
upgrade the BIOS has been removed/hidden.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no lo
Jeroen T. Vermeulen, could you please test for this via
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?
** Tags removed: bios-outdated-f7
** Tags added: latest-bios-f7
** Changed in: xorg (Ubuntu)
Importance: Low => Medium
--
You received this bug notification becaus
Okay, I got out of that situation with the help of the flashrom people.
My BIOS is now updated.
It helped a bit in that I can now define and add my resolution again
using xrandr. It won't stay added though: I need to define and add it
every time I boot. Otherwise, the resolution is not in the Di
I'm trying the BIOS upgrade as per those instructions. The only
applicable option was the flashrom one, which seems to have hosed my
BIOS. It's still on now, but I won't be able to boot it again. Kindly
mark this bug New again to give me time to recover and retry!
--
You received this bug noti
Jeroen T. Vermeulen, as per http://www.gigabyte.com/products/product-
page.aspx?pid=4519#driver an update to your computer's buggy and
outdated BIOS is available (F7). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?
If it doesn't, could you ple
Jeroen T. Vermeulen, as per http://www.gigabyte.com/products/product-
page.aspx?pid=4519#driver an update to your computer's buggy and
outdated BIOS is available (F7). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?
If it doesn't, could you ple
** Description changed:
My display's native resolution is 2560×1440 pixels. Prior to, I think,
Saucy I could only reach this resolution by adding it using xrandr, and
then calling xrandr on boot/login to select that resolution. The
Display preferences did not show any higher options than
51 matches
Mail list logo
