Processed: severity of 722354 is normal
Processing commands for cont...@bugs.debian.org: > severity 722354 normal Bug #722354 [libdrm-dev] intel-vaapi-driver: FTBFS on kfreebsd-*: error: unknown type name 'uint64_t' Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 722354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.138090869319135.transcr...@bugs.debian.org
Processed: reassign 722354 to libdrm-dev
Processing commands for cont...@bugs.debian.org: > reassign 722354 libdrm-dev Bug #722354 [src:intel-vaapi-driver] intel-vaapi-driver: FTBFS on kfreebsd-*: error: unknown type name 'uint64_t' Bug reassigned from package 'src:intel-vaapi-driver' to 'libdrm-dev'. No longer marked as found in versions intel-vaapi-driver/1.0.20-2. Ignoring request to alter fixed versions of bug #722354 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 722354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.138090409423637.transcr...@bugs.debian.org
Bug#690826: marked as done (libx11-6: XIM support routine creates bogs timestamp (confuses gdk, rendering thunderbird and firefox unusable.))
Your message dated Fri, 4 Oct 2013 13:20:30 +0200 with message-id <20131004112030.ga26...@betterave.cristau.org> and subject line Re: Bug#690826: libx11-6: XIM support routine creates bogs timestamp (confuses gdk, rendering thunderbird and firefox unusable.) has caused the Debian Bug report #690826, regarding libx11-6: XIM support routine creates bogs timestamp (confuses gdk, rendering thunderbird and firefox unusable.) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 690826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libx11-6 Version: 2:1.5.0-1 Severity: normal Tags: l10n Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Using XIM engine to input Japanese and Chinese caused events with bogus (uninitialized) timestamps in X events. [This seems to have been ignored by many applications and libraries in the past. However, starting gdk 2 and 3, I think, in the last 18 months or so, the timestamp check is severe and gdk library stores this bogus timestamp for further processing. If the bogus timestamp is well into the future, we have a problem. A typical symptom is that the pulldown menus are no longer usable in mozilla firefox and thunderbird. Please see the mozilla bugzilla entry: Using XIM with Firefox will cause firefox menu cannot popup correctly. https://bugzilla.mozilla.org/show_bug.cgi?id=787943 Also, an earlier report of the problem of seeing bogus time stamp here. The returning event of XNextEvent() has incorrect timestamp https://bugs.freedesktop.org/show_bug.cgi?id=39367 Some other programs definitely are affected: Should reject future timestamp. https://bugzilla.gnome.org/show_bug.cgi?id=654831 Although it is not clear from the exchanges in the above URL, I think the root cause of the problem is the problem reported here. * What exactly did you do (or not do) that was effective (or ineffective)? Typing Japanese character strings into thunderbird, and then switches to another gnome-termnal console and type some Japanese string there. Then switch back to the thunderbird compose window (for new message) and then series of XEvents with bogus timestamps are generated. Depending on the particular value (picked up from stack without initialization), GDK's event handling subsequently will be screwed up :-( * What was the outcome of this action? Timing related processing may be badly affected in some applications which depend on the (bogus) timestamp recorded in GDK library data structure. For example, pull down menu no longer can be displayed in thunderbird and firefox. * What outcome did you expect instead? Correct XEvent processing. Patch below to libx11 source of debian. Of course, you would want to remove fprintf lines, but if you want, that is where you can dump the incorrect time stamp values (before setting the proper values, that is). The path in imTrans.c has not been executed in my environment so far (testing for a few days now), but I include the patch for completeness's sake. diff --git a/modules/im/ximcp/imDefLkup.c b/modules/im/ximcp/imDefLkup.c index cf75919..d82c990 100644 --- a/modules/im/ximcp/imDefLkup.c +++ b/modules/im/ximcp/imDefLkup.c @@ -713,6 +728,12 @@ _XimCommitRecv( ev.keycode = 0; ev.state = 0; +ev.time = 0L; +ev.serial = LastKnownRequestProcessed(im->core.display); +/* FIXME */ +fprintf(stderr,"%s,%d: putback k press FIXED ev.time=0 ev.serial=%lu\n", __FILE__, __LINE__, ev.serial); + + XPutBackEvent(im->core.display, (XEvent *)&ev); return True; diff --git a/modules/im/ximcp/imTrans.c b/modules/im/ximcp/imTrans.c index 0ac08aa..45fab87 100644 --- a/modules/im/ximcp/imTrans.c +++ b/modules/im/ximcp/imTrans.c @@ -228,6 +228,12 @@ _XimTransInternalConnection( kev->display = im->core.display; kev->window = spec->window; kev->keycode = 0; +/* FIXME */ +kev->time = 0L; +kev->serial = LastKnownRequestProcessed(im->core.display); +fprintf(stderr,"%s,%d: putback FIXED kev->time=0 kev->serial=%lu\n", __FILE__, __LINE__, kev->serial); + + XPutBackEvent(im->core.display, &ev); XFlush(im->core.display); spec->is_putback = True; *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (SMP w/1 CPU core) Locale: LANG=ja_JP.UTF-8, LC_
xserver-xorg-video-intel: Changes to 'ubuntu-raring'
debian/changelog |7 +
debian/patches/series |1
debian/patches/sna-fixup-possible-clones.diff | 130 ++
3 files changed, 138 insertions(+)
New commits:
commit fe699c4bc47146fb94e147df21edd988b4b252e9
Author: Timo Aaltonen
Date: Fri Oct 4 11:51:27 2013 +0300
release to raring
diff --git a/debian/changelog b/debian/changelog
index e0f0d35..d4da552 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,4 @@
-xserver-xorg-video-intel (2:2.21.6-0ubuntu4.3) UNRELEASED; urgency=low
+xserver-xorg-video-intel (2:2.21.6-0ubuntu4.3) raring-proposed; urgency=low
* sna-fixup-possible-clones.diff: Backport from 2.21.9 to fix
clone mode on haswell laptops. (LP: #1202524)
commit 35eb0d3209bb554ecd65be0d9a7faa08ac1bb342
Author: Timo Aaltonen
Date: Fri Oct 4 11:41:17 2013 +0300
sna-fixup-possible-clones.diff: Backport from 2.21.9 to fix clone mode on
haswell laptops. (LP: #1202524)
diff --git a/debian/changelog b/debian/changelog
index ef6fb6a..e0f0d35 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+xserver-xorg-video-intel (2:2.21.6-0ubuntu4.3) UNRELEASED; urgency=low
+
+ * sna-fixup-possible-clones.diff: Backport from 2.21.9 to fix
+clone mode on haswell laptops. (LP: #1202524)
+
+ -- Timo Aaltonen Fri, 04 Oct 2013 11:39:07 +0300
+
xserver-xorg-video-intel (2:2.21.6-0ubuntu4.2) raring-proposed; urgency=low
* Add hsw-green-xv.patch, backport from 2.21.10 to fix green screens when
using XV
diff --git a/debian/patches/series b/debian/patches/series
index e61d6cc..504e83f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -6,3 +6,4 @@ add-more-reserved-hsw-ids.diff
add-known-hsw-names.diff
add-more-correct-hsw-names.diff
hsw-green-xv.patch
+sna-fixup-possible-clones.diff
diff --git a/debian/patches/sna-fixup-possible-clones.diff
b/debian/patches/sna-fixup-possible-clones.diff
new file mode 100644
index 000..8af11c9
--- /dev/null
+++ b/debian/patches/sna-fixup-possible-clones.diff
@@ -0,0 +1,130 @@
+commit fc1e0702b25e647cb423851fb7228989fec28bd6
+Author: Daniel Vetter
+Date: Wed May 29 11:25:28 2013 +0100
+
+sna: fixup up possible_clones kms->X impedance mismatch
+
+We need to be a notch more careful with remapping the possible clones
+mask from the kernel:
+- SDVO and Haswell DDI have multiple connectors mapping to the same
encoder.
+- The connector list can be reordered compared to the encoder list.
+ This is used to move eDP/LVDS to the front.
+
+Also add even more debug output.
+
+Signed-off-by: Daniel Vetter
+
+--- a/src/sna/sna_display.c
b/src/sna/sna_display.c
+@@ -84,6 +84,7 @@ struct sna_property {
+ struct sna_output {
+ int id;
+ drmModeConnectorPtr mode_output;
++ int encoder_idx;
+ int num_props;
+ struct sna_property *props;
+
+@@ -98,6 +99,16 @@ struct sna_output {
+ struct list link;
+ };
+
++static inline struct sna_output *to_sna_output(xf86OutputPtr output)
++{
++ return output->driver_private;
++}
++
++static inline int to_connector_id(xf86OutputPtr output)
++{
++ return to_sna_output(output)->mode_output->connector_id;
++}
++
+ static inline struct sna_crtc *to_sna_crtc(xf86CrtcPtr crtc)
+ {
+ return crtc->driver_private;
+@@ -735,14 +746,11 @@ sna_crtc_apply(xf86CrtcPtr crtc)
+
+ for (i = 0; i < xf86_config->num_output; i++) {
+ xf86OutputPtr output = xf86_config->output[i];
+- struct sna_output *sna_output;
+
+ if (output->crtc != crtc)
+ continue;
+
+- sna_output = output->driver_private;
+- output_ids[output_count] =
+- sna_output->mode_output->connector_id;
++ output_ids[output_count] = to_connector_id(output);
+ output_count++;
+ }
+
+@@ -2326,6 +2334,7 @@ sna_output_init(ScrnInfoPtr scrn, struct
+ struct sna_output *sna_output;
+ const char *output_name;
+ char name[32];
++ int i;
+
+ koutput = drmModeGetConnector(sna->kgem.fd,
+ mode->kmode->connectors[num]);
+@@ -2380,6 +2389,13 @@ sna_output_init(ScrnInfoPtr scrn, struct
+ output->subpixel_order = subpixel_conv_table[koutput->subpixel];
+ output->driver_private = sna_output;
+
++ for (i = 0; i < mode->kmode->count_encoders; i++) {
++ if (enc.encoder_id == mode->kmode->encoders[i]) {
++ sna_output->encoder_idx = i;
++ break;
++ }
++ }
++
+ if (is_panel(koutput->connector_type))
+ sna_output_backlight_init(output);
+
+@@ -2395,33 +2411,34 @@ cleanup_connector:
+ drmModeFreeConnector(koutput);
+ }
+
+-/* The kernel reports possible encoder clones, whereas X uses a list of
+- * possible connector clones. This is works when we
Bug#720329: xserver-xorg-video-radeon: Screen keeping black at start but for the cursor
On Fre, 2013-10-04 at 00:27 +0200, Samuel Hym wrote: > > So here we go, with the dmesg, the /proc/fb and the Xorg.0.log for the > version I reported with and the latest in the archive. Same behaviour > for me, black screen with broken cursors. The radeon kernel module doesn't get loaded for some reason. Make sure it's not blacklisted somewhere in /etc/, for example. Does it help if you manually run 'sudo modprobe radeon' before starting X? -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1380877341.7499.39.camel@thor.local
intel-gpu-tools: Changes to 'debian-unstable'
.gitignore |7 ChangeLog|10261 +++ Makefile.am | 13 NEWS | 59 README | 47 assembler/.gitignore | 18 assembler/Makefile.am| 51 assembler/README |9 assembler/TODO | 14 assembler/brw_compat.h | 67 assembler/brw_context.c | 44 assembler/brw_context.h | 78 assembler/brw_defines.h | 1642 assembler/brw_disasm.c | 1348 assembler/brw_eu.c | 268 assembler/brw_eu.h | 427 + assembler/brw_eu_compact.c | 810 ++ assembler/brw_eu_debug.c | 92 assembler/brw_eu_emit.c | 2627 +++ assembler/brw_eu_util.c | 125 assembler/brw_reg.h | 808 ++ assembler/brw_structs.h | 1493 assembler/disasm-main.c | 172 assembler/doc/Makefile.am|3 assembler/doc/examples/packed_yuv_sf.g4a | 17 assembler/doc/examples/packed_yuv_wm.g4a | 161 assembler/gen4asm.h | 227 assembler/gram.y | 3051 + assembler/intel-gen4asm.pc.in| 10 assembler/lex.l | 441 + assembler/main.c | 520 + assembler/ralloc.c | 482 + assembler/ralloc.h | 407 + assembler/test/.gitignore| 24 assembler/test/Makefile.am | 93 assembler/test/break.expected|1 assembler/test/break.g4a |6 assembler/test/cont.expected |1 assembler/test/cont.g4a |6 assembler/test/declare.expected |3 assembler/test/declare.g4a |5 assembler/test/else.expected |1 assembler/test/else.g4a |1 assembler/test/endif.expected|1 assembler/test/endif.g4a |1 assembler/test/frc.expected |1 assembler/test/frc.g4a |1 assembler/test/halt.expected |1 assembler/test/halt.g4a |1 assembler/test/if.expected |1 assembler/test/if.g4a|1 assembler/test/iff.expected |1 assembler/test/iff.g4a |1 assembler/test/immediate.expected|3 assembler/test/immediate.g4a |3 assembler/test/jmpi.expected |1 assembler/test/jmpi.g4a |1 assembler/test/lzd.expected |1 assembler/test/lzd.g4a |1 assembler/test/mov.expected |1 assembler/test/mov.g4a |1 assembler/test/not.expected |1 assembler/test/not.g4a |1 assembler/test/rndd.expected |1 assembler/test/rndd.g4a |1 assembler/test/rnde-intsrc.expected |1 assembler/test/rnde-intsrc.g4a |2 assembler/test/rnde.expected |1 assembler/test/rnde.g4a |1 assembler/test/rndu.expected |1 assembler/test/rndu.g4a |1 assembler/test/rndz.expected |1 assembler/test/rndz.g4a |1 assembler/test/run-test.sh | 11 assembler/test/wait.expected |1 assembler/test/wait.g4a |1 assembler/test/while.expected|1 assembler/test/while.g4a |1 autogen.sh |2 configure.ac | 189 debian/changelog |4 debian/control |6 debian/rules |3 debugger/Makefile.am |1 debugger/system_routine/Makefile.am |4 demos/intel_sprite_on.c | 1395 +--- lib/Makefile.am |1 lib/drmtest.c| 1890 - lib/drmtest.h| 295 lib/gen7_render.h| 1496 +++- lib/i830_reg.h |3 lib/intel_batchbuffer.c | 62 lib/intel_batchbuffer.h |7 lib/intel_chipset.h | 374 - lib/intel_drm.c | 16 lib/intel_gpu_tools.h| 11 lib/intel_iosf.c | 85 lib/intel_mmio.c | 54 lib/intel_pci.c
Re: intel-gpu-tools 1.3
On 04.10.2013 11:05, Timo Aaltonen wrote: > On 02.10.2013 23:47, Tormod Volden wrote: >> Hi, >> >> Timo prepared intel-gpu-tools 1.3-1 in git a long time ago. It has >> been used in Ubuntu since then, so I guess it is pretty well tested. >> Can somebody please release this to unstable? >> >> I can take a stab at packaging 1.4 "soon" but meanwhile 1.3 would be a >> blessing to users stuck at 1.2. Maybe it even fixes the current RC >> bug. > > I'm actually updating the packaging right now, looking good. Actually, I'm not sure what to do with usr/lib/I915ChipsetPython.so, put it in a separate package or what, and don't have time to figure that out right now. So anyone can pick up from here.. but at least it builds -- t -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/524e7bd0.2000...@ubuntu.com
Re: intel-gpu-tools 1.3
On 02.10.2013 23:47, Tormod Volden wrote: > Hi, > > Timo prepared intel-gpu-tools 1.3-1 in git a long time ago. It has > been used in Ubuntu since then, so I guess it is pretty well tested. > Can somebody please release this to unstable? > > I can take a stab at packaging 1.4 "soon" but meanwhile 1.3 would be a > blessing to users stuck at 1.2. Maybe it even fixes the current RC > bug. I'm actually updating the packaging right now, looking good. -- t -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/524e76bc.8040...@ubuntu.com
libxdamage: Changes to 'debian-unstable'
debian/changelog |6 ++
debian/control |1 +
2 files changed, 7 insertions(+)
New commits:
commit 8c1f98bb7153bd4f6f5b2dcdcce752e5d56be0f7
Author: Timo Aaltonen
Date: Fri Oct 4 10:12:15 2013 +0300
control: Mark -dev as M-A: same. (LP: #1230252)
diff --git a/debian/changelog b/debian/changelog
index dd4e17c..f5ed7df 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libxdamage (1:1.1.4-1ubuntu1) UNRELEASED; urgency=low
+
+ * control: Mark -dev as M-A: same. (LP: #1230252)
+
+ -- Timo Aaltonen Fri, 04 Oct 2013 10:12:08 +0300
+
libxdamage (1:1.1.4-1) unstable; urgency=low
* New upstream release.
diff --git a/debian/control b/debian/control
index cfe9f8f..12dc683 100644
--- a/debian/control
+++ b/debian/control
@@ -64,6 +64,7 @@ Package: libxdamage-dev
Section: libdevel
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, libxdamage1 (=
${binary:Version}), libx11-dev, libxfixes-dev, x11proto-damage-dev (>= 1.1)
+Multi-Arch: same
Description: X11 damaged region extension library (development headers)
libXdamage provides an X Window System client interface to the DAMAGE
extension to the X protocol.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1vrzyh-0008f0...@vasks.debian.org
