This bug was fixed in the package autopilot -
1.4+14.04.20140123.1-0ubuntu1
---
autopilot (1.4+14.04.20140123.1-0ubuntu1) trusty; urgency=low
[ Barry Warsaw ]
* Make Autopilot tracepoint extension module compatible with python 3.
(LP: #1266574)
[ Christopher Lee ]
* Handl
** Changed in: autopilot
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: autopilot
Status: Fix Committed => Fix Released
** Changed in: autopilot (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member o
** Changed in: autopilot (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258170
Title:
autopilot crashed with SIGSEGV in XLastKnownRequestProcesse
Nice, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258170
Title:
autopilot crashed with SIGSEGV in XLastKnownRequestProcessed()
To manage notifications about this bug go to:
https://bugs.
Fix committed into lp:autopilot at revision None, scheduled for release
in autopilot, milestone 1.4
** Changed in: autopilot
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Changed in: autopilot
Status: Triaged => In Progress
** Changed in: autopilot (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258170
Title:
a
** Branch linked: lp:~pitti/autopilot/fix-gdk-display
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258170
Title:
autopilot crashed with SIGSEGV in XLastKnownRequestProcessed()
To manage notificat
That's how the geometry property is being used:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/unity/tests/test_panel.py", line 1172,
in test_panel_title_updates_moving_window
drag_window_to_screen(calc_win, monitor)
File "/usr/lib/python2.7/dist-packages/unity/
Turns out that the GdkX11.X11Display has no public constructor, so it's
invalid to create a GdkDisplay like that. The official API is to use
Gdk.Display.get_default(), which makes this whole thing work. The
question is now, how did that ever work? The same python command crashes
in saucy and raring
More complete example with a valid XID (but doesn't make a difference):
xvfb-run python -c 'from gi.repository import Gdk, GdkX11; display =
GdkX11.X11Display(); print("display:", display); rw =
Gdk.get_default_root_window(); print("rootwin:", rw); xid =
rw.get_xid(); print("xid:", xid); fd =
GdkX
Simple reproducer:
python -c 'from gi.repository import GdkX11; display =
GdkX11.X11Display(); print("display:", display); fd =
GdkX11.X11Window.foreign_new_for_display(display, 1); print("foreign:",
fd); origin = fd.get_origin(); print("origin:", origin)'
--
You received this bug notification
Hi Martin,
Just to confirm your results, it only occurs on my system with both the
internal monitor and an external monitor. Sorry for my misinformation
about being internal monitor only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I can reproduce the crash if I use my internal and the external monitor
side by side. Mouse behaviour in Unity in that mode is awfully buggy
(you can't move between the two monitors, and the mouse area seems to
randomly switch between the two), but it reproduces the crash.
** Changed in: autopilot
Hi Martin,
This is affecting the qa-intel-4000 Jenkins CI machine. Here is the
console log from that machine: http://q-jenkins.ubuntu-ci:8080/job
/autopilot-trusty-daily_release/823/label=qa-intel-4000/console
This is how I discovered the issue and was able to reproduce on my
system (Dell XPS 13
I ran this test 15 times on my system (ThinkPad X230, external DVI,
Intel graphics, current trusty) without any crash/failure. Do you have a
pointer to a failed log? Does this test require a particular display
configuration, such as multiple monitors?
** Changed in: autopilot (Ubuntu)
Statu
** Changed in: autopilot (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258170
Title:
autopilot crashed with SIGSEGV in XLastKnownRequestP
This looks like a crash deep inside Gtk to me. I'll see if I can find
someone to take a look.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258170
Title:
autopilot crashed with SIGSEGV in XLastKnow
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258170
Title:
autopilot crashed with SIGSEGV in XLastKnownRequestProcessed()
To manage notification
18 matches
Mail list logo
