** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1580311
Title:
Laptop boots only if external display connected
To manage
Haven't seen this for a while with 16.10 / 4.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525390
Title:
[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
pipe A
To manage
Ok, the magic workaround is to disable the "Legacy option ROM" feature
in the BIOS, which happens to be the BIOS default. Go figure why the
kernel stopped liking whatever that setting implies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Bug still present with Ubuntu 16.10 kernel 4.8.0-26-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580311
Title:
Laptop boots only if external display connected
To manage notifications
Dude, it's obviously not the BIOS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580311
Title:
Laptop boots only if external display connected
To manage notifications about this bug go to:
Testing 4.7.0-040700 I see the 'new' behaviour of the system failing to
boot even if an external display is connected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580311
Title:
Laptop boots only
** Summary changed:
- Laptop panel output only if external display connected
+ Laptop boots only if external display connected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580311
Title:
Laptop
As of 4.4.0-28-generic I can no longer boot even with an external display
attached.
I have had to revert completely to 4.2.0-35.
So, there we go a change in behaviour between the current and previous
4.4.0 packages. Surely thatś enough to find an inciminating commit?
I'm sorry, but this kernel
I'm sorry, but there's no way I can do that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580311
Title:
Laptop panel output only if external display connected
To manage notifications about this
Confirmed for that too. See you for 4.8..
On 4 Jul 2016 16:45, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> wrote:
> mjh, in the future, please ensure you check for newer kernels before
> reporting test results, as the latest mainline kernel is now 4.7-r
Confirmed present in 4.7-rc3
** 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/1580311
Title:
Laptop panel output only if external
Sure there is something more proactive that can be done than mere testing of
new kernels and BIOSes?
It should be possible to isolate the cause of the problem by comparing the
diffs between 4.2.0-040200 and 4.2.0-35-generic, as I mentioned above.
--
You received this bug notification because
Confirmed present on 16.04 with kernel 4.4.0-24 and latest BIOS (4.0.7)
** 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/1525390
# dmidecode -s bios-version && sudo dmidecode -s bios-release-date
4.0.7
04/26/2016
Attached is a screenshot of the fractional kernel stack trace that appears when
I am able to bring up the system with an HDMI display attached.
Without the external display the system definitely doesn't come up
I've tried the new BIOS. No change.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: bios-outdated-4.0.7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580311
** Tags removed: bios-outdated-4.0.7
** 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/1580311
Title:
Laptop panel output only if
her M. Penalver" <
christopher.m.penal...@gmail.com> wrote:
> mjh, as per http://www.dell.com/support/home/us/en/19/product-
> support/product/inspiron-15-3552-laptop/drivers?os=biosa an update to
> your computer's buggy, insecure, and outdated BIOS is available (4.0.7).
> I
I guess I'll just buy a Mac then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580311
Title:
Laptop panel output only if external display connected
To manage notifications about this bug go to:
** Summary changed:
- Regression: drm / modesetting failure for i915
+ Laptop panel output only if external display connected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580311
Title:
Laptop
Confirmed present on 16.04 with kernel 4.4.0-22-generic, on the same hardware
as my original report
Still occurs at about the same time as a Wifi dropout (which requires a reload
of the wifi kernel modules to clear). Not clear which is causative of the other.
--
You received this bug
Another observation: booting with 4.4.0-22-generic is successful if I
have an external HDMI display connected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580311
Title:
Regression: drm /
I've checked the mainline kernels and determined that 4.2.0-040200
exhibits the problem, while 15.10's 4.2.0-35-generic is ok. I don't know
how to proceed from here to determine the differences between the two.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I can't test further than 4.2.0 because of bug 1580311 which is stopping
any video output at all on later kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525390
Title:
If I get a chance I'll try to establish which kernel introduces the
regression.
** 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.
AFAICT I did -- I tested 4.6-rc7 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc7-wily/
I can't go any further than installing and testing ready-built kernel
deb packages, I'm afraid.
** Tags removed: ubuntu
** Tags added: ubuntukernel-bug-exists-upstream
** Tags removed:
I've now tried with combinations of the kernel options:
acpi_backlist=vendor
and
video=eDP-1:1366x768e
without apparent change in behaviour
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580311
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525390
Title:
[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
pipe A
To
ditto 4.6.0-rc7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580311
Title:
Regression: drm / modesetting failure for i915
To manage notifications about this bug go to:
Just tried 4.5.3-040503-generic from the mainline ppa repo
http://kernel.ubuntu.com/~kernel-ppa/mainline
The behaviour is superficially the same as with 4.4 -- nomodeset is required to
boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Kernel hangs at boot with modesettings
+ Regression: drm / modesetting failure for i915
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Booting 4.4.0-22 with just the kernel arguments
root=/dev/mapper/ubuntu--15--vg-root ro
and filming the kernel bring-up messages, I see that it the very last thing
displayed is:
[]fb: switching to inteldrmfb from EFI VGA
before the screne blanks (no backlight) and the machine becomes non-
Public bug reported:
Hi,
Since updating to 16.04 with kernel vmlinuz-4.4.0-22-generic my laptop
no longer completes the boot sequence under a normal boot scenario - the
"loading initrd..." message is displayed, then, when the VGA modesetting
usually kicks the display into a higher resolution,
The problem is still present in 4.2.0-27-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525390
Title:
[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
pipe A
To
Sorry, I'm not going to test any kernel that I can't just apt-get install.
I currently have 4.2.0-25-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525390
Title:
I saw there were .debs there and, against my better judgement, installed the
latest (4.5.0-040500rc1)
It fails to boot, giving me a black screen after "loading ramdisk.."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Revved BIOS again to 4.0.3
Same symptoms observed.
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
4.0.3
11/17/2015
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525390
Hi,
Since making the bug report, I've updated the BIOS, without any apparent
improvement.
Matt
On 9 January 2016 at 06:36, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> mjh, thank you for reporting this and helping make Ubuntu better.
>
> As per http
** Description changed:
Dell 3552 Inspiron laptop, bouth with Ubuntu 14.04LTS upgraded, to
15.10.
Every few minutes the following appears in the syslog:
[ 6355.488381] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
failure on pipe A (start=1171 end=1172)
-
- accompanied by
Public bug reported:
Dell 3552 Inspiron laptop, bouth with Ubuntu 14.04LTS upgraded, to
15.10.
Every few minutes the following appears in the syslog:
[ 6355.488381] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure
on pipe A (start=1171 end=1172)
accompanied by a failure of the
Public bug reported:
Expected behaviour: -- echo should print one \ for every escaped backslash
(\\)
$ echo
Observed behaviour :
$ echo \\# one escaped-bs
\
$ echo # two escaped
\
$ echo \\ # three escaped
\\
$ echo # 4 escaped
\\
** Affects: dash (Ubuntu)
Never mind, I see this has has already received the ubiquitous WONTFIX.
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/259671
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1462002
Title:
dash
The magic is
gsettings set org.gnome.Terminal.Legacy.Settings confirm-close false
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454827
Title:
Can't disable the window close confirmation anymore
Public bug reported:
Objective: Disable gnome-terminal's close confirmation dialog
On Ubuntu = 14.10, I would do the following:
gconf-editor - apps - gnome-terminal - global - untick
confirm_window_close
This no longer works with 15.04.
The above process inserts that key into the
Public bug reported:
Hi,
I have an Asus X202E laptop, with i3-2365M CPU and iGPU. I find that
the display switching between integrated and external displays no longer
works.
Steps to reproduce:
* Boot laptop without extenal display attached.
* Log in.
* Connect external, powered-on display
New issue. Happens with the current 13.10 kernel, doesn't happen with the
current 13.04 kernel.
El 21/10/2013 18:41, Joseph Salisbury joseph.salisb...@canonical.com
escribió:
Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
Would it be possible for you to test the
My workaround was to disable the Left Alt shortcut key for the HUD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227920
Title:
after suspend/resume, the Unity HUD is always open when I unlock the
Public bug reported:
Hi,
I have Ubuntu 13.10 guests on an Ubuntu 13.10 host, using QEMU and KVM.
I have one shared directory, shared with the QEMU argument:
-virtfs
local,path=shared-filesystem,security_model=none,mount_tag=context \
and mounted on the guest as:
/lib/mod/mount -t 9p
Confirmed that the regression is in 3.11.0-12-generic. Reverted the
kernel of the host to 13.04's vmlinuz-3.8.0-31-generic , with no other
changes to the OS, and the problem is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
?
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: cyrus-common-2.4 2.4.12-2
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu8
AptOrdering:
python-evolution: Install
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012609
Title:
package cyrus-common-2.4 2.4.12-2 failed to install/upgrade: le sous-
processus script post-installation installé a retourné une erreur
50 matches
Mail list logo
