** Changed in: libcairo
Status: Confirmed => Fix Released
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubunt
this was fixed upstream, thanks for reporting.
** Changed in: cairo (Ubuntu)
Status: Triaged => Fix Committed
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
the new version is in intrepid now
** Changed in: cairo (Ubuntu)
Status: Fix Committed => Fix Released
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desk
Do you still get the issue? Could you describe a way to trigger the bug?
** Changed in: libcairo (Ubuntu)
Status: Confirmed => Triaged
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
I haven't had this issue in a long time, but here was what we discussed
when I discovered it using CodeBlocks:
http://forums.codeblocks.org/index.php?topic=3921.0
And here is the issue noted severity CRITICAL upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Sorry I couldn't be more he
True. I hate to say it, but they were a rather miserable bunch to have
to deal with. At least as far as those who were around in their irc
channel back when I tried to explain it to them. Basically it went
something like this, "there is a problem, here is what is happening,
here is a stack trace, s
The upstream bug has got no recent comment though
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://l
Their issue is that they need those informations to work on the bug
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ub
They have all of that information. They even know which font was the
culprit and which line the signal was being raised.
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Could be useful to have a small testcase though and verify if that's
still happening, there is lot of people using this font and only a small
number of users who ran into the bug
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are
It was difficult to reproduce and we only had it happen on dual core
systems. In any case, ability to reproduce isn't as important as it
sounds since that is usually the method to track down the problem. But I
already know the problem and exactly where the signal is raised.
--
Assertion Fails at
** Changed in: cairo (Ubuntu)
Sourcepackagename: libcairo => cairo
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubu
There is an upstream task opened, marking confirmed, the bug is known
upstream
** Bug watch added: Freedesktop Bugzilla #8104
https://bugs.freedesktop.org/show_bug.cgi?id=8104
** Also affects: libcairo (upstream) via
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Importance: Unknown
** Changed in: libcairo (upstream)
Status: Unknown => Confirmed
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Thanks for your bug report. How can I try to reproduce the error?
** Changed in: libcairo (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
de
Hey man,
Check out the thread we have going on libCairo:
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Kip
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: libcairo
Status: Confirmed => Fix Released
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubunt
this was fixed upstream, thanks for reporting.
** Changed in: cairo (Ubuntu)
Status: Triaged => Fix Committed
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
the new version is in intrepid now
** Changed in: cairo (Ubuntu)
Status: Fix Committed => Fix Released
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desk
** Changed in: cairo (Ubuntu)
Sourcepackagename: libcairo => cairo
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubu
Do you still get the issue? Could you describe a way to trigger the bug?
** Changed in: libcairo (Ubuntu)
Status: Confirmed => Triaged
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
I haven't had this issue in a long time, but here was what we discussed
when I discovered it using CodeBlocks:
http://forums.codeblocks.org/index.php?topic=3921.0
And here is the issue noted severity CRITICAL upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Sorry I couldn't be more he
True. I hate to say it, but they were a rather miserable bunch to have
to deal with. At least as far as those who were around in their irc
channel back when I tried to explain it to them. Basically it went
something like this, "there is a problem, here is what is happening,
here is a stack trace, s
The upstream bug has got no recent comment though
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://l
Their issue is that they need those informations to work on the bug
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ub
They have all of that information. They even know which font was the
culprit and which line the signal was being raised.
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Could be useful to have a small testcase though and verify if that's
still happening, there is lot of people using this font and only a small
number of users who ran into the bug
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are
It was difficult to reproduce and we only had it happen on dual core
systems. In any case, ability to reproduce isn't as important as it
sounds since that is usually the method to track down the problem. But I
already know the problem and exactly where the signal is raised.
--
Assertion Fails at
Thanks for your bug report. How can I try to reproduce the error?
** Changed in: libcairo (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
de
Hey man,
Check out the thread we have going on libCairo:
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Kip
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
There is an upstream task opened, marking confirmed, the bug is known
upstream
** Bug watch added: Freedesktop Bugzilla #8104
https://bugs.freedesktop.org/show_bug.cgi?id=8104
** Also affects: libcairo (upstream) via
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Importance: Unknown
** Changed in: libcairo (upstream)
Status: Unknown => Confirmed
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: libcairo
Status: Confirmed => Fix Released
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubunt
this was fixed upstream, thanks for reporting.
** Changed in: cairo (Ubuntu)
Status: Triaged => Fix Committed
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
the new version is in intrepid now
** Changed in: cairo (Ubuntu)
Status: Fix Committed => Fix Released
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desk
Do you still get the issue? Could you describe a way to trigger the bug?
** Changed in: libcairo (Ubuntu)
Status: Confirmed => Triaged
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
I haven't had this issue in a long time, but here was what we discussed
when I discovered it using CodeBlocks:
http://forums.codeblocks.org/index.php?topic=3921.0
And here is the issue noted severity CRITICAL upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Sorry I couldn't be more he
True. I hate to say it, but they were a rather miserable bunch to have
to deal with. At least as far as those who were around in their irc
channel back when I tried to explain it to them. Basically it went
something like this, "there is a problem, here is what is happening,
here is a stack trace, s
The upstream bug has got no recent comment though
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://l
Their issue is that they need those informations to work on the bug
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ub
They have all of that information. They even know which font was the
culprit and which line the signal was being raised.
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Could be useful to have a small testcase though and verify if that's
still happening, there is lot of people using this font and only a small
number of users who ran into the bug
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are
It was difficult to reproduce and we only had it happen on dual core
systems. In any case, ability to reproduce isn't as important as it
sounds since that is usually the method to track down the problem. But I
already know the problem and exactly where the signal is raised.
--
Assertion Fails at
** Changed in: cairo (Ubuntu)
Sourcepackagename: libcairo => cairo
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubu
Thanks for your bug report. How can I try to reproduce the error?
** Changed in: libcairo (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
de
Hey man,
Check out the thread we have going on libCairo:
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Kip
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
There is an upstream task opened, marking confirmed, the bug is known
upstream
** Bug watch added: Freedesktop Bugzilla #8104
https://bugs.freedesktop.org/show_bug.cgi?id=8104
** Also affects: libcairo (upstream) via
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Importance: Unknown
** Changed in: libcairo (upstream)
Status: Unknown => Confirmed
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: libcairo
Status: Confirmed => Fix Released
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubunt
this was fixed upstream, thanks for reporting.
** Changed in: cairo (Ubuntu)
Status: Triaged => Fix Committed
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
the new version is in intrepid now
** Changed in: cairo (Ubuntu)
Status: Fix Committed => Fix Released
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desk
** Changed in: cairo (Ubuntu)
Sourcepackagename: libcairo => cairo
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubu
Do you still get the issue? Could you describe a way to trigger the bug?
** Changed in: libcairo (Ubuntu)
Status: Confirmed => Triaged
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
I haven't had this issue in a long time, but here was what we discussed
when I discovered it using CodeBlocks:
http://forums.codeblocks.org/index.php?topic=3921.0
And here is the issue noted severity CRITICAL upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Sorry I couldn't be more he
True. I hate to say it, but they were a rather miserable bunch to have
to deal with. At least as far as those who were around in their irc
channel back when I tried to explain it to them. Basically it went
something like this, "there is a problem, here is what is happening,
here is a stack trace, s
The upstream bug has got no recent comment though
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://l
Their issue is that they need those informations to work on the bug
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ub
They have all of that information. They even know which font was the
culprit and which line the signal was being raised.
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Could be useful to have a small testcase though and verify if that's
still happening, there is lot of people using this font and only a small
number of users who ran into the bug
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are
It was difficult to reproduce and we only had it happen on dual core
systems. In any case, ability to reproduce isn't as important as it
sounds since that is usually the method to track down the problem. But I
already know the problem and exactly where the signal is raised.
--
Assertion Fails at
There is an upstream task opened, marking confirmed, the bug is known
upstream
** Bug watch added: Freedesktop Bugzilla #8104
https://bugs.freedesktop.org/show_bug.cgi?id=8104
** Also affects: libcairo (upstream) via
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Importance: Unknown
** Changed in: libcairo (upstream)
Status: Unknown => Confirmed
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Thanks for your bug report. How can I try to reproduce the error?
** Changed in: libcairo (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
de
Hey man,
Check out the thread we have going on libCairo:
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Kip
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Thanks for your bug report. How can I try to reproduce the error?
** Changed in: libcairo (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
de
Hey man,
Check out the thread we have going on libCairo:
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Kip
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: libcairo
Status: Confirmed => Fix Released
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubunt
this was fixed upstream, thanks for reporting.
** Changed in: cairo (Ubuntu)
Status: Triaged => Fix Committed
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
the new version is in intrepid now
** Changed in: cairo (Ubuntu)
Status: Fix Committed => Fix Released
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desk
** Changed in: cairo (Ubuntu)
Sourcepackagename: libcairo => cairo
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubu
Do you still get the issue? Could you describe a way to trigger the bug?
** Changed in: libcairo (Ubuntu)
Status: Confirmed => Triaged
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
I haven't had this issue in a long time, but here was what we discussed
when I discovered it using CodeBlocks:
http://forums.codeblocks.org/index.php?topic=3921.0
And here is the issue noted severity CRITICAL upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Sorry I couldn't be more he
True. I hate to say it, but they were a rather miserable bunch to have
to deal with. At least as far as those who were around in their irc
channel back when I tried to explain it to them. Basically it went
something like this, "there is a problem, here is what is happening,
here is a stack trace, s
The upstream bug has got no recent comment though
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://l
Their issue is that they need those informations to work on the bug
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ub
They have all of that information. They even know which font was the
culprit and which line the signal was being raised.
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Could be useful to have a small testcase though and verify if that's
still happening, there is lot of people using this font and only a small
number of users who ran into the bug
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are
It was difficult to reproduce and we only had it happen on dual core
systems. In any case, ability to reproduce isn't as important as it
sounds since that is usually the method to track down the problem. But I
already know the problem and exactly where the signal is raised.
--
Assertion Fails at
There is an upstream task opened, marking confirmed, the bug is known
upstream
** Bug watch added: Freedesktop Bugzilla #8104
https://bugs.freedesktop.org/show_bug.cgi?id=8104
** Also affects: libcairo (upstream) via
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Importance: Unknown
** Changed in: libcairo (upstream)
Status: Unknown => Confirmed
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Do you still get the issue? Could you describe a way to trigger the bug?
** Changed in: libcairo (Ubuntu)
Status: Confirmed => Triaged
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
I haven't had this issue in a long time, but here was what we discussed
when I discovered it using CodeBlocks:
http://forums.codeblocks.org/index.php?topic=3921.0
And here is the issue noted severity CRITICAL upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Sorry I couldn't be more he
True. I hate to say it, but they were a rather miserable bunch to have
to deal with. At least as far as those who were around in their irc
channel back when I tried to explain it to them. Basically it went
something like this, "there is a problem, here is what is happening,
here is a stack trace, s
The upstream bug has got no recent comment though
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://l
Their issue is that they need those informations to work on the bug
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ub
They have all of that information. They even know which font was the
culprit and which line the signal was being raised.
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Could be useful to have a small testcase though and verify if that's
still happening, there is lot of people using this font and only a small
number of users who ran into the bug
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are
It was difficult to reproduce and we only had it happen on dual core
systems. In any case, ability to reproduce isn't as important as it
sounds since that is usually the method to track down the problem. But I
already know the problem and exactly where the signal is raised.
--
Assertion Fails at
Thanks for your bug report. How can I try to reproduce the error?
** Changed in: libcairo (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
de
Hey man,
Check out the thread we have going on libCairo:
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Kip
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
There is an upstream task opened, marking confirmed, the bug is known
upstream
** Bug watch added: Freedesktop Bugzilla #8104
https://bugs.freedesktop.org/show_bug.cgi?id=8104
** Also affects: libcairo (upstream) via
https://bugs.freedesktop.org/show_bug.cgi?id=8104
Importance: Unknown
** Changed in: libcairo (upstream)
Status: Unknown => Confirmed
--
Assertion Fails at Runtime
https://launchpad.net/bugs/58519
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: libcairo
Status: Confirmed => Fix Released
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubunt
this was fixed upstream, thanks for reporting.
** Changed in: cairo (Ubuntu)
Status: Triaged => Fix Committed
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
the new version is in intrepid now
** Changed in: cairo (Ubuntu)
Status: Fix Committed => Fix Released
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desk
** Changed in: cairo (Ubuntu)
Sourcepackagename: libcairo => cairo
--
Assertion Fails at Runtime
https://bugs.launchpad.net/bugs/58519
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubu
96 matches
Mail list logo