This was an issue for me initially in 12.04 but it seems to be fixed
now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/888134
Title:
automatic detection of plugged in /
I just hit this with the dbus message:
[] bhearsum@voot:$ indicator-datetime-preferences
(indicator-datetime-preferences:5764): Unique-DBus-WARNING **: Error
while sending message: Did not receive a reply. Possible causes include:
the remote application did not send a reply, the message bus
Apologies for the delay in replying. Here's a more exact description of the
problem:
1) Try to use external monitor by plugging it in
2) Monitor gets enabled, but monitor layout is wrong
3) Open gnome-control center to the Displays section
4) Re-arrange monitors, hit Apply
5) Screens blink and
I just started hitting this in Ubuntu 12.04, running 'awesome'. When I try to
launch gnome-setting-daemon I get:
➜ ~ gnome-settings-daemon
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-AASi0t/pkcs11: No
such file or directory
** (process:1884): WARNING **:
This is still an issue in Ubuntu 12.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/888134
Title:
automatic detection of plugged in / removed monitor is too aggressive
The instructions in this forum post effectively worked around the issue
for me: http://ubuntuforums.org/showpost.php?p=10301640postcount=8
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
This bug is still affecting me, and makes it impossible to use external
displays that don't get autodetected correctly (eg, wrong rotation,
location - whatever). What can I do to help track down the cause of the
problem and/or fix?
--
You received this bug notification because you are a member
I also found that when I went back to awesome after making display
changes in Unity, that autodetect now defaults to what I want it too.
So, that's a workaround for certain use cases (but really sucks if you
change your configuration often).
--
You received this bug notification because you are
I just thought to try to reproduce in Unity, and couldn't do so with it.
So, there seems to be some weird interaction between either awesome and
whatever is doing this detection, or maybe I'm supposed to have a daemon
running that I don't, or I dunno what else.
--
You received this bug
Here's the log as you requested Chris. Here's an exact description of what I
did:
* touch ~/gsd-debug-randr
* Exit Awesome, GDM restarts
* Login again
* Plug in VGA cable, nothing happens
* Open Display settings, new monitor is automatically enabled but in the wrong
position
* I move it to the
One thing that I've noticed recently is that I can't unplug and then
plug back into my monitors without a reboot. This also means that I
can't suspend and resume without losing the external monitors. I'm not
sure if this issue belongs in here or elsewhere.
--
You received this bug notification
I've got that in progress. In the meantime, I realized there was a newer
kernel+driver from yours and the xorg-edgers PPAs, so I did that upgrade, and
now unity-control-center only sees one external monitor, with the second being
treated as a mirror of the first. This is using:
3.17 functions almost 100% correct. I'm able to use both external
displays again, and Ubuntu can see them after unplugging/plugging in,
and after suspend/wake. The only issue is that I sometimes have to
disable and re-enable the monitors to get a picture back after plugging
back in or waking back
Darius - looks like I was, for some reason. I didn't expect that to be
the case while still having your PPA active, I guess I misunderstand how
that works though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel
I'm on 14.10 with:
* Lenovo T440s (00:02.0 VGA compatible controller: Intel Corporation
Haswell-ULT Integrated Graphics Controller (rev 0b))
* 2 Dell U2413 displays with DP 1.2 enabled.
* Kernel: 3.16.0-25-generic #33hf73386v20141106b1-Ubuntu SMP
* Driver: ii xserver-xorg-video-intel
I was speaking to folks in #intel-gfx, and one of them suggested that I
file a bug on freedesktop.org about my crash. That's
https://bugs.freedesktop.org/show_bug.cgi?id=86475.
** Bug watch added: freedesktop.org Bugzilla #86475
https://bugs.freedesktop.org/show_bug.cgi?id=86475
--
You
The Freedesktop bug that I filed got closed, saying my crash is most
likely a bug in the Ubuntu backport.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Title:
Here's some additional debug logs that David Airline helped me get.
** Attachment added: debug level 6 logs
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1104230/+attachment/4264338/+files/debug6.log
--
You received this bug notification because you are a member of
I happened to notice a new xserver-xorg-video-intel package was
published yesterday (2:2.99.916+git20141119.a90cc3b3-0ubuntu0sarvatt). I
tried it and still have the same crash.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Any update here?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Title:
DisplayPort 1.2 MST support is missing in the Intel driver
Status in X.org
Same thing, unfortunately:
[ 37.881345] [ cut here ]
[ 37.881363] WARNING: CPU: 0 PID: 1850 at
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_ddi.c:850
intel_ddi_pll_select+0x7f/0x3c0 [i915]()
[ 37.881364] Invalid DDI encoder type 11
[ 37.881365] Modules
And here's X logs from around the same time:
[ 520.969] (II) intel(0): resizing framebuffer to 3120x2751
[ 521.017] (II) intel(0): switch to mode 1920x1200@60.0 on DP1-1 using pipe
0, position (1920, 0), rotation left, reflection none
[ 521.420] (II) intel(0): switch to mode 1920x1080@60.0
Sorry about that. 3.16.0-26.34hf73386v20141126b1 is much improved. I'm
able to set modes on my external monitors now, but whether or not they
work is somewhat inconsistent. For example, right now my configuration
is like this: http://people.mozilla.org/~bhearsum/sattap/ae5e1315.png,
but the yellow
** Attachment added: dmesg output when trying to set display settings as
desired
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1104230/+attachment/4269008/+files/latest.log
--
You received this bug notification because you are a member of Desktop
Packages, which is
One final thing: the display that is on is consistent. When I logged out
of my normal window manager (awesome) and switched to Unity, the yellow
monitor turned on and the green one turned off. Even after logging back
into awesome, this state persisted.
--
You received this bug notification
Apologies for the spam, but I just fixed it. Turns out my video adapter
was only set to 256MB. Changing it to 512MB in the BIOS has all three
monitors working consistently \o/.
Thanks so much Dariusz, it's great to have this set-up going finally!
--
You received this bug notification because
I'm hitting this on Ubuntu 14.10 as well. Out of the box, the left
button generates button 4 events, the right button generates button 5
events, and the middle button generates nothing at all.
The situation improves a little bit by setting UpDownScrolling=0
(synclient UpDownScrolling=0), after
Sorry for the long delay response. I just tested the 3.16.0-28 kernel
and unfortunately it doesn't even detect all of my displays correctly --
it only shows 1 external monitor in the display settings rather than
both. I get picture on both of them, but I can't set them up correctly
any more.
--
Looks like I'm probably running the cached version, d'oh:
apt-cache policy linux-image-3.16.0-28
linux-image-3.16.0-28-generic:
Nakaluklok: 3.16.0-28.38
Kandidato: 3.16.0-28.38
Talaang Bersyon:
*** 3.16.0-28.38 0
500 http://ca.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64
Unfortunately, I have the same behaviour with your kernel:
➜ ~ uname -a
Linux dib 3.16.0-28-generic #37hf73386v20141212b2-Ubuntu SMP Fri Dec 12
08:30:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
http://people.mozilla.org/~bhearsum/sattap/080347a3.png
--
You received this bug notification
For what it's worth, this kernel seems to be working 100% fine for my set-up:
Linux dib 3.17.1-031701-generic #201410150735 SMP Wed Oct 15 11:36:31 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
When my laptop woke this morning, both external displays came back.
--
You received this bug notification
31 matches
Mail list logo
