Re: [Bug 670369] Re: sqliteodbc/amd64 does not compile with unixodbc-dev-2.2.14p2-1ubuntu1
I'm not using Ubuntu anymore, so I cannot test. On 07/28/2015 06:53 PM, Rolf Leggewie wrote: does this ever occur in trusty or later? ** Changed in: sqliteodbc (Ubuntu) Status: New = Incomplete ** Changed in: sqliteodbc (Ubuntu) Assignee: (unassigned) = Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/670369 Title: sqliteodbc/amd64 does not compile with unixodbc-dev-2.2.14p2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqliteodbc/+bug/670369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 416421]
Created attachment 57155 reorder Bresenham error correction to avoid overshoot. When fbBresSolid draws a line, it can happen that after the last pixel, the Bresenham error term overflows, and fbBresSolid paints another pixel before adjusting the error term. However, if this happens on the last pixel (len=0), this extra pixel might overshoot the boundary, and, in rare cases, lead to a segfault. Fix this issue by adjusting for the Bresenham error term before drawing the main pixel, not after. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/416421 Title: [gm45] X crash on X200s with dual monitors (using DisplayPort) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/416421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 415357]
Created attachment 57155 reorder Bresenham error correction to avoid overshoot. When fbBresSolid draws a line, it can happen that after the last pixel, the Bresenham error term overflows, and fbBresSolid paints another pixel before adjusting the error term. However, if this happens on the last pixel (len=0), this extra pixel might overshoot the boundary, and, in rare cases, lead to a segfault. Fix this issue by adjusting for the Bresenham error term before drawing the main pixel, not after. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/415357 Title: [gm45] Xorg consistently crashing when using some applications To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/415357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 416421]
The problem seems to be that there are negative coordinates being passed
in to ProcPolySegment:
(gdb) p/x *(xSegment*)((xPolySegmentReq *)0x2918e1c)[1]
$11 = {x1 = 0x24, y1 = 0x10, x2 = 0xfffe, y2 = 0x}
I don't know who is supposed to catch this. Looking at the call
sequence, nobody really makes sure that these values are in bounds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/416421
Title:
[gm45] X crash on X200s with dual monitors (using DisplayPort)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/416421/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 416421]
Created attachment 56113 gdb backtrace gdb backtrace of the bug. dst is out of bounds. I can provide core file and binaries if required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/416421 Title: [gm45] X crash on X200s with dual monitors (using DisplayPort) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/416421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 416421]
Ah. I believe this is the problem, or at least very closely related: http://cgit.freedesktop.org/xorg/xserver/tree/fb/fbseg.c#n693: if (clip2 != 0 || drawLast) len++; in combination with these variables: new_x1 = 36 new_x2 = 0 new_y1 = 16 new_y2 = 0 clip2 = 10 len = 37 This incremented len to 37, extending (in reverse) the line below (0, 0), which leads to a segmentation fault. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/416421 Title: [gm45] X crash on X200s with dual monitors (using DisplayPort) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/416421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 416421]
Ok, I see what is going on there.
The len++ is to make the end coordinates inclusive, which they should be
if drawLast is set, or if we clipped the end.
Now, we changed the end coordinates, but we keep the Bresenham error
terms, because we want the same angle (I suppose).
However, if we look at fbBresSolid, we see this sequence:
while (len--)
{
...
/// (1) ///
WRITE(dst, FbDoMaskRRop (READ(dst), and, xor, bits));
bits = 0;
dst += signdx;
...
e += e1;
/// (2) ///
if (e = 0)
{
/// (3) ///
WRITE(dst, FbDoMaskRRop (READ(dst), and, xor, bits));
bits = 0;
dst += dstStride;
e += e3;
}
}
Now assume we have arrived at len = 1. We start the last iteration for
the last pixel, at (x2,y2). We draw the pixel (location (1)), and we
*should* be done. However, because of the previously unmodified
Bresenham error terms, it can happen that the error total overflows
(location (2)), and we will draw another pixel, now at (x2+signdx,y2),
before adjusting the error terms and exiting the loop.
In short, it might happen that (I'm using signdx=-1, just because my
case happens to be that way):
- (orig_x2, orig_y2) get clipped
- the algorithm then goes on to draw:
(x1,y1), (x1-1,y1), ..., (x2,y2), (x2-1,y2)
Now, if x2 = 0, y2 = 0, then we overshoot into negative address land
(-1,0) and might segfault (actually do).
Solutions
=
I don't directly see how this could be fixed:
a) Check dst for every Bresenham error pixel, but that seems excessive.
b) Adjust the error terms, but that would change the slope of the line
(slightly)
c) Check for this case in advance and reduce len, but then you'd lose one pixel
at the end
d) Rewrite fbseg to draw the error pixel in the next iteration, instead of in
the same. This touches central code though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/416421
Title:
[gm45] X crash on X200s with dual monitors (using DisplayPort)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/416421/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 416421]
Just a follow-up to say that solution (d) seems to work for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/416421 Title: [gm45] X crash on X200s with dual monitors (using DisplayPort) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/416421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 415357]
Created attachment 56113 gdb backtrace gdb backtrace of the bug. dst is out of bounds. I can provide core file and binaries if required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/415357 Title: [gm45] Xorg consistently crashing when using some applications To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/415357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 415357]
The problem seems to be that there are negative coordinates being passed
in to ProcPolySegment:
(gdb) p/x *(xSegment*)((xPolySegmentReq *)0x2918e1c)[1]
$11 = {x1 = 0x24, y1 = 0x10, x2 = 0xfffe, y2 = 0x}
I don't know who is supposed to catch this. Looking at the call
sequence, nobody really makes sure that these values are in bounds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/415357
Title:
[gm45] Xorg consistently crashing when using some applications
To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/415357/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 415357]
Ok, I see what is going on there.
The len++ is to make the end coordinates inclusive, which they should be
if drawLast is set, or if we clipped the end.
Now, we changed the end coordinates, but we keep the Bresenham error
terms, because we want the same angle (I suppose).
However, if we look at fbBresSolid, we see this sequence:
while (len--)
{
...
/// (1) ///
WRITE(dst, FbDoMaskRRop (READ(dst), and, xor, bits));
bits = 0;
dst += signdx;
...
e += e1;
/// (2) ///
if (e = 0)
{
/// (3) ///
WRITE(dst, FbDoMaskRRop (READ(dst), and, xor, bits));
bits = 0;
dst += dstStride;
e += e3;
}
}
Now assume we have arrived at len = 1. We start the last iteration for
the last pixel, at (x2,y2). We draw the pixel (location (1)), and we
*should* be done. However, because of the previously unmodified
Bresenham error terms, it can happen that the error total overflows
(location (2)), and we will draw another pixel, now at (x2+signdx,y2),
before adjusting the error terms and exiting the loop.
In short, it might happen that (I'm using signdx=-1, just because my
case happens to be that way):
- (orig_x2, orig_y2) get clipped
- the algorithm then goes on to draw:
(x1,y1), (x1-1,y1), ..., (x2,y2), (x2-1,y2)
Now, if x2 = 0, y2 = 0, then we overshoot into negative address land
(-1,0) and might segfault (actually do).
Solutions
=
I don't directly see how this could be fixed:
a) Check dst for every Bresenham error pixel, but that seems excessive.
b) Adjust the error terms, but that would change the slope of the line
(slightly)
c) Check for this case in advance and reduce len, but then you'd lose one pixel
at the end
d) Rewrite fbseg to draw the error pixel in the next iteration, instead of in
the same. This touches central code though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/415357
Title:
[gm45] Xorg consistently crashing when using some applications
To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/415357/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 415357]
Ah. I believe this is the problem, or at least very closely related: http://cgit.freedesktop.org/xorg/xserver/tree/fb/fbseg.c#n693: if (clip2 != 0 || drawLast) len++; in combination with these variables: new_x1 = 36 new_x2 = 0 new_y1 = 16 new_y2 = 0 clip2 = 10 len = 37 This incremented len to 37, extending (in reverse) the line below (0, 0), which leads to a segmentation fault. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/415357 Title: [gm45] Xorg consistently crashing when using some applications To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/415357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 415357]
Just a follow-up to say that solution (d) seems to work for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/415357 Title: [gm45] Xorg consistently crashing when using some applications To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/415357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 416421]
I experience a related bug when using KiCad: [ 2507.868] Backtrace: [ 2507.868] 0: /usr/bin/X (xorg_backtrace+0x26) [0x566a86] [ 2507.868] 1: /usr/bin/X (0x40+0x16a6e9) [0x56a6e9] [ 2507.868] 2: /lib/libpthread.so.0 (0x7fa9d12c8000+0xf8a0) [0x7fa9d12d78a0] [ 2507.868] 3: /usr/lib/xorg/modules/libfb.so (fbBresSolid+0x21c) [0x7fa9cd94a1cc] [ 2507.868] 4: /usr/lib/xorg/modules/libfb.so (fbSegment+0x3f7) [0x7fa9cd94b667] [ 2507.868] 5: /usr/lib/xorg/modules/libfb.so (fbPolySegment32+0x4bd) [0x7fa9cd93f88d] [ 2507.868] 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fa9ce38+0x380cc) [0x7fa9ce3b80cc] [ 2507.868] 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fa9ce38+0x2f1ec) [0x7fa9ce3af1ec] [ 2507.868] 8: /usr/bin/X (0x40+0xf9a3f) [0x4f9a3f] [ 2507.868] 9: /usr/bin/X (0x40+0x302a3) [0x4302a3] [ 2507.868] 10: /usr/bin/X (0x40+0x33cb9) [0x433cb9] [ 2507.868] 11: /usr/bin/X (0x40+0x22eea) [0x422eea] [ 2507.868] 12: /lib/libc.so.6 (__libc_start_main+0xed) [0x7fa9d017f38d] [ 2507.868] 13: /usr/bin/X (0x40+0x231dd) [0x4231dd] [ 2507.868] Segmentation fault at address 0x7fa9cc816ffc It is reproducible. No idea why the intel driver symbols don't show up, but addr2line shows me: 0x380cc = xf86-video-intel-2.17.0/uxa/uxa-unaccel.c:24 = uxa_check_poly_segment() 0x2f1ec = xf86-video-intel-2.17.0/uxa/uxa-accel.c:624 = uxa_poly_segment() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/416421 Title: [gm45] X crash on X200s with dual monitors (using DisplayPort) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/416421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 415357]
I experience a related bug when using KiCad: [ 2507.868] Backtrace: [ 2507.868] 0: /usr/bin/X (xorg_backtrace+0x26) [0x566a86] [ 2507.868] 1: /usr/bin/X (0x40+0x16a6e9) [0x56a6e9] [ 2507.868] 2: /lib/libpthread.so.0 (0x7fa9d12c8000+0xf8a0) [0x7fa9d12d78a0] [ 2507.868] 3: /usr/lib/xorg/modules/libfb.so (fbBresSolid+0x21c) [0x7fa9cd94a1cc] [ 2507.868] 4: /usr/lib/xorg/modules/libfb.so (fbSegment+0x3f7) [0x7fa9cd94b667] [ 2507.868] 5: /usr/lib/xorg/modules/libfb.so (fbPolySegment32+0x4bd) [0x7fa9cd93f88d] [ 2507.868] 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fa9ce38+0x380cc) [0x7fa9ce3b80cc] [ 2507.868] 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fa9ce38+0x2f1ec) [0x7fa9ce3af1ec] [ 2507.868] 8: /usr/bin/X (0x40+0xf9a3f) [0x4f9a3f] [ 2507.868] 9: /usr/bin/X (0x40+0x302a3) [0x4302a3] [ 2507.868] 10: /usr/bin/X (0x40+0x33cb9) [0x433cb9] [ 2507.868] 11: /usr/bin/X (0x40+0x22eea) [0x422eea] [ 2507.868] 12: /lib/libc.so.6 (__libc_start_main+0xed) [0x7fa9d017f38d] [ 2507.868] 13: /usr/bin/X (0x40+0x231dd) [0x4231dd] [ 2507.868] Segmentation fault at address 0x7fa9cc816ffc It is reproducible. No idea why the intel driver symbols don't show up, but addr2line shows me: 0x380cc = xf86-video-intel-2.17.0/uxa/uxa-unaccel.c:24 = uxa_check_poly_segment() 0x2f1ec = xf86-video-intel-2.17.0/uxa/uxa-accel.c:624 = uxa_poly_segment() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/415357 Title: [gm45] Xorg consistently crashing when using some applications To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/415357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711678] Re: Double entry of event in the OWA, for an event created with Lightning
Should be fixed in 0.17. I'll try to update the changelog -- that's a good idea. Yes, addons.mozilla.org takes quite a long time to review new versions. Unfortunately there is nothing I can do about this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711678 Title: Double entry of event in the OWA, for an event created with Lightning To manage notifications about this bug go to: https://bugs.launchpad.net/lightning-exchange-provider/+bug/711678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711678] Re: Double entry of event in the OWA, for an event created with Lightning
** Changed in: lightning-exchange-provider Status: Confirmed = 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/711678 Title: Double entry of event in the OWA, for an event created with Lightning To manage notifications about this bug go to: https://bugs.launchpad.net/lightning-exchange-provider/+bug/711678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711678] Re: Double entry of event in the OWA, for an event created with Lightning
** Changed in: lightning-exchange-provider Status: Fix Committed = 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/711678 Title: Double entry of event in the OWA, for an event created with Lightning To manage notifications about this bug go to: https://bugs.launchpad.net/lightning-exchange-provider/+bug/711678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711678] Re: Double entry of event in the OWA, for an event created with Lightning
Good news, I found the bug! The problem is that if you click Save+Close, Thunderbird will do this in exactly this sequence. The save triggers an update XMLHttpRequest which also gets sent. The subsequent close, however, will cancel the XMLHttpRequest (even though it already was sent and was received by the server). That makes the request return a bogus error, and the request gets retried. Voila, 2 events created. I'll look into how to fix this, but any help is appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711678 Title: Double entry of event in the OWA, for an event created with Lightning To manage notifications about this bug go to: https://bugs.launchpad.net/lightning-exchange-provider/+bug/711678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711678] Re: Double entry of event in the OWA, for an event created with Lightning
** Changed in: lightning-exchange-provider Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711678 Title: Double entry of event in the OWA, for an event created with Lightning To manage notifications about this bug go to: https://bugs.launchpad.net/lightning-exchange-provider/+bug/711678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711678] Re: Double entry of event in the OWA, for an event created with Lightning
Perfectly valid, just not related to the Ubuntu distribution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711678 Title: Double entry of event in the OWA, for an event created with Lightning To manage notifications about this bug go to: https://bugs.launchpad.net/lightning-exchange-provider/+bug/711678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 249958] Re: touching a fullscreen application with the mousepointer puts it in front
I can reproduce this bug. However, only one of my machines exhibits this behavior. ** Also affects: metacity via https://bugzilla.gnome.org/show_bug.cgi?id=356829 Importance: Unknown Status: Unknown ** Changed in: metacity (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/249958 Title: touching a fullscreen application with the mousepointer puts it in front To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/249958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711678] Re: Double entry of event in the OWA, for an event created with Lightning
** Changed in: ubuntu Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711678 Title: Double entry of event in the OWA, for an event created with Lightning To manage notifications about this bug go to: https://bugs.launchpad.net/lightning-exchange-provider/+bug/711678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 670369] [NEW] sqliteodbc/amd64 does not compile with unixodbc-dev-2.2.14p2-1ubuntu1
Public bug reported: debuild compiler output: sqliteodbc.c: At top level: sqliteodbc.c:7076: error: conflicting types for 'SQLSetStmtOption' /usr/include/sql.h:796: note: previous declaration of 'SQLSetStmtOption' was here This is because SQLSetStmtOption uses the SQLROWCOUNT type which does not exist in /usr/include/sqltypes.h for 64 bit systems: /* * These are not supprted on 64bit ODBC according to MS, removed, so use at your peril * typedef SQLULEN SQLROWCOUNT; typedef SQLULEN SQLROWSETSIZE; typedef SQLULEN SQLTRANSID; typedef SQLLEN SQLROWOFFSET; */ SQLSetStmtOption is instead declared with SQLULEN in /usr/include/sql.h. ** Affects: sqliteodbc (Ubuntu) Importance: Undecided Status: New -- sqliteodbc/amd64 does not compile with unixodbc-dev-2.2.14p2-1ubuntu1 https://bugs.launchpad.net/bugs/670369 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 670369] Re: sqliteodbc/amd64 does not compile with unixodbc-dev-2.2.14p2-1ubuntu1
** Patch added: no-sqlrowcount.patch https://bugs.launchpad.net/bugs/670369/+attachment/1721698/+files/no-sqlrowcount.patch -- sqliteodbc/amd64 does not compile with unixodbc-dev-2.2.14p2-1ubuntu1 https://bugs.launchpad.net/bugs/670369 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 670369] Re: sqliteodbc/amd64 does not compile with unixodbc-dev-2.2.14p2-1ubuntu1
you can also pull from my branch, it contains another fix that is required for erlang-odbc. This other fix has been submitted upstream and was integrated in 0.86. -- sqliteodbc/amd64 does not compile with unixodbc-dev-2.2.14p2-1ubuntu1 https://bugs.launchpad.net/bugs/670369 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510483] Re: Gnome-terminal ignores /usr/share/vte/termcap/xterm
This is the wrong fix. If you can configure the size in the terminal/profile preferences, you don't need to modify the termcap entry anymore. -- Gnome-terminal ignores /usr/share/vte/termcap/xterm https://bugs.launchpad.net/bugs/510483 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510483] Re: Gnome-terminal ignores /usr/share/vte/termcap/xterm
(referring to the current Lucid version) -- Gnome-terminal ignores /usr/share/vte/termcap/xterm https://bugs.launchpad.net/bugs/510483 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613700] Re: kernel BUG at /build/buildd/linux-2.6.32/drivers/char/tty_ldisc.c:707!
I can confirm this BUG: [ 233.292555] hub 8-0:1.0: port 1 disabled by hub (EMI?), re-enabling... [ 233.292562] usb 8-1: USB disconnect, address 2 [ 233.292685] [ cut here ] [ 233.292688] kernel BUG at /build/buildd/linux-2.6.32/drivers/char/tty_ldisc.c:707! [ 233.292691] invalid opcode: [#1] SMP [ 233.292695] last sysfs file: /sys/devices/pci:00/:00:1f.3/local_cpus [ 233.292698] CPU 2 [ 233.292701] Modules linked in: vboxnetadp vboxnetflt vboxdrv binfmt_misc kvm_intel kvm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 deflate zlib_deflate ctr twofish twofish_common camellia serpent blowfish cast5 des_generic xcbc rmd160 sha1_generic crypto_null af_key snd_hda_codec_via snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device ppdev ftdi_sio joydev tpm_tis tpm usbserial parport_pc asus_atk0110 snd tpm_bios xpad led_class ff_memless soundcore snd_page_alloc lp parport sha256_generic cryptd aes_x86_64 aes_generic dm_crypt raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx raid1 raid0 multipath linear fbcon tileblit font bitblit softcursor vga16fb vgastate usbhid hid i915 drm_kms_helper drm i2c_algo_bit ahci video output intel_agp e1000e [ 233.292788] Pid: 44, comm: khubd Not tainted 2.6.32-24-generic #39-Ubuntu System Product Name [ 233.292791] RIP: 0010:[81333d80] [81333d80] tty_ldisc_reinit+0x50/0x60 [ 233.292801] RSP: 0018:880222663a90 EFLAGS: 00010202 [ 233.292804] RAX: ffea RBX: 880209b23000 RCX: 0002 [ 233.292807] RDX: 0002 RSI: 81a1ca80 RDI: 00e0 [ 233.292810] RBP: 880222663aa0 R08: 0001ce53 R09: 00883a08 [ 233.292813] R10: 00866bb5 R11: R12: 00e0 [ 233.292816] R13: 880209b23020 R14: R15: 0001 [ 233.292820] FS: () GS:88002830() knlGS: [ 233.292823] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b [ 233.292826] CR2: 7f620ca3b000 CR3: 0001f08d5000 CR4: 26e0 [ 233.292829] DR0: DR1: DR2: [ 233.292832] DR3: DR6: 0ff0 DR7: 0400 [ 233.292835] Process khubd (pid: 44, threadinfo 880222662000, task 8802226596f0) [ 233.292838] Stack: [ 233.292839] 880209b23000 880222663ad0 81333f50 [ 233.292844] 0 8801e0e90480 880209b23208 880209b23000 880209b231d8 [ 233.292850] 0 880222663b30 8132b9c6 880209b23208 810397a9 [ 233.292855] Call Trace: [ 233.292860] [81333f50] tty_ldisc_hangup+0x1c0/0x1f0 [ 233.292866] [8132b9c6] do_tty_hangup+0x146/0x400 [ 233.292872] [810397a9] ? default_spin_lock_flags+0x9/0x10 [ 233.292877] [8132bc95] tty_vhangup+0x15/0x20 [ 233.292885] [a024b72d] usb_serial_disconnect+0xad/0x1a0 [usbserial] [ 233.292891] [813dbdf4] usb_unbind_interface+0x124/0x170 [ 233.292898] [8136b64f] __device_release_driver+0x6f/0xe0 [ 233.292902] [8136b7bd] device_release_driver+0x2d/0x40 [ 233.292906] [8136a7da] bus_remove_device+0x9a/0xc0 [ 233.292911] [81368937] device_del+0x127/0x1d0 [ 233.292915] [813d85a8] usb_disable_device+0xa8/0x130 [ 233.292920] [813d2342] usb_disconnect+0xd2/0x170 [ 233.292925] [813d29af] hub_port_connect_change+0x8f/0x980 [ 233.292930] [81541645] ? printk+0x41/0x44 [ 233.292934] [813d3ca2] hub_events+0x3b2/0x5a0 [ 233.292938] [81541cb0] ? thread_return+0x48/0x418 [ 233.292943] [813d3ee5] hub_thread+0x55/0x190 [ 233.292948] [81085430] ? autoremove_wake_function+0x0/0x40 [ 233.292953] [813d3e90] ? hub_thread+0x0/0x190 [ 233.292957] [810850b6] kthread+0x96/0xa0 [ 233.292961] [810141ea] child_rip+0xa/0x20 [ 233.292965] [81085020] ? kthread+0x0/0xa0 [ 233.292969] [810141e0] ? child_rip+0x0/0x20 [ 233.292971] Code: c7 43 40 00 00 00 00 44 89 e7 e8 7c fe ff ff 48 3d 00 f0 ff ff 77 14 48 89 43 40 44 89 e6 48 89 df e8 15 fa ff ff 5b 41 5c c9 c3 0f 0b eb fe 66 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 41 [ 233.293015] RIP [81333d80] tty_ldisc_reinit+0x50/0x60 [ 233.293020] RSP 880222663a90 [ 233.293024] ---[ end trace 97c726107f759b8b ]--- ** Changed in: linux-backports-modules-2.6.31 (Ubuntu) Status: New = Confirmed -- kernel BUG at /build/buildd/linux-2.6.32/drivers/char/tty_ldisc.c:707! https://bugs.launchpad.net/bugs/613700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list
[Bug 566788] Re: /dev/shm isn't writable, causing problems with glibc 2.2+ apps such as chromium
Is there anything we can help to fix this bug? What are the temporary fix options? -- /dev/shm isn't writable, causing problems with glibc 2.2+ apps such as chromium https://bugs.launchpad.net/bugs/566788 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518653] Re: libopie exports conflicting symbols
** Patch added: fix: rename all internal md5_* functions to opiemd5_* http://launchpadlibrarian.net/38889077/opie_2.40%7Edfsg-0ubuntu2_md5_names.diff -- libopie exports conflicting symbols https://bugs.launchpad.net/bugs/518653 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to opie in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 518653] Re: libopie exports conflicting symbols
** Patch added: fix: rename all internal md5_* functions to opiemd5_* http://launchpadlibrarian.net/38889077/opie_2.40%7Edfsg-0ubuntu2_md5_names.diff -- libopie exports conflicting symbols https://bugs.launchpad.net/bugs/518653 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518653] [NEW] libopie exports conflicting symbols
Public bug reported: libopie.a exports the functions md5_init, md5_append and md5_finish. These are quite common names that should be avoided by a central library. The problem arises when any binary that also uses these symbol names is linked to libopie.a, especially when this happens indirectly. Concretely, I ran into a problem when trying to use dovecot with libpam- opie. pam_opie.so contains (part of) libopie.a, and thus also the global functions md5_init, etc. Dovecot contains md5_init, md5_update and md5_finish as global functions. Note that libopie and dovecot differ in md5_append vs md5_update, yet share the other function names. As a result, pam_opie.so will use part dovecot functions (per standard plt resolution), and part its own (since md5_append is not defined my dovecot). That results in an invalid md5 calculation and thus in failed authentication. Possible solution: libopie.a should not export such common names, and instead prefix them appropriately. Alternatively use hidden visibility if applicable. Description:Ubuntu 9.10 Release:9.10 libopie-dev: Installed: 2.40~dfsg-0ubuntu1 Candidate: 2.40~dfsg-0ubuntu1 Version table: *** 2.40~dfsg-0ubuntu1 0 500 http://ch.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status libpam-opie: Installed: 0.21-8build2 Candidate: 0.21-8build2 Version table: *** 0.21-8build2 0 500 http://ch.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status ** Affects: opie (Ubuntu) Importance: Undecided Status: New -- libopie exports conflicting symbols https://bugs.launchpad.net/bugs/518653 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to opie in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 518653] [NEW] libopie exports conflicting symbols
Public bug reported: libopie.a exports the functions md5_init, md5_append and md5_finish. These are quite common names that should be avoided by a central library. The problem arises when any binary that also uses these symbol names is linked to libopie.a, especially when this happens indirectly. Concretely, I ran into a problem when trying to use dovecot with libpam- opie. pam_opie.so contains (part of) libopie.a, and thus also the global functions md5_init, etc. Dovecot contains md5_init, md5_update and md5_finish as global functions. Note that libopie and dovecot differ in md5_append vs md5_update, yet share the other function names. As a result, pam_opie.so will use part dovecot functions (per standard plt resolution), and part its own (since md5_append is not defined my dovecot). That results in an invalid md5 calculation and thus in failed authentication. Possible solution: libopie.a should not export such common names, and instead prefix them appropriately. Alternatively use hidden visibility if applicable. Description:Ubuntu 9.10 Release:9.10 libopie-dev: Installed: 2.40~dfsg-0ubuntu1 Candidate: 2.40~dfsg-0ubuntu1 Version table: *** 2.40~dfsg-0ubuntu1 0 500 http://ch.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status libpam-opie: Installed: 0.21-8build2 Candidate: 0.21-8build2 Version table: *** 0.21-8build2 0 500 http://ch.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status ** Affects: opie (Ubuntu) Importance: Undecided Status: New -- libopie exports conflicting symbols https://bugs.launchpad.net/bugs/518653 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
