Ryan, can you add some debug dump of the size the window is being set
to? On OSX and Ubuntu I've tried it sets things as expected, so there
might be some issue either with the width not being reported correctly
to inkscape, or the size setting not being accepted by the window
manager. It does seem
Patch committed in revision #12315.
** Changed in: inkscape
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/830663
Title:
default window size is too small
Applied modified patch in revision #11407.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/43730
Title:
inkscape 'export bitmap' dialog should indicate success and close
after export
To
Added close checkbox item in revision #11409.
** Changed in: inkscape
Status: In Progress = Fix Committed
** Changed in: inkscape
Milestone: None = 0.49
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
: (unassigned) = Jon A. Cruz (jon-joncruz)
** Changed in: inkscape
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/43730
Title:
inkscape 'export bitmap' dialog
** Changed in: inkscape
Status: New = In Progress
** Changed in: inkscape
Assignee: (unassigned) = Jon A. Cruz (jon-joncruz)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to libkdcraw in Ubuntu.
https://bugs.launchpad.net/bugs
Fixed in revision #10969.
** Changed in: inkscape
Status: In Progress = Fix Committed
** Changed in: inkscape
Milestone: None = 0.49
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to libkdcraw in Ubuntu.
** Changed in: inkscape
Status: Confirmed = In Progress
** Changed in: inkscape
Milestone: None = 0.48.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778951
Title:
Enable build against
Trunk now should build against 0.1.x or 0.2.x, whichever is detected, as
of revision 10266.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778951
Title:
Enable build against libwpg-0.2
To manage
Backported to the 0.48.x branch as revision 9788.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778951
Title:
Enable build against libwpg-0.2
To manage notifications about this bug go to:
** Changed in: inkscape
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/778951
Title:
Enable build against libwpg-0.2
To manage notifications about this
** Changed in: inkscape
Assignee: (unassigned) = Jon A. Cruz (jon-joncruz)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778951
Title:
Enable build against libwpg-0.2
To manage notifications
** Changed in: inkscape
Assignee: (unassigned) = Jon A. Cruz (jon-joncruz)
** Changed in: inkscape
Importance: Wishlist = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/780659
Title
I've poked at this a few times in the past... but I'm thinking that we
want to do this in C++, not C. A minor shift in approach could be
helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/170225
** Changed in: inkscape
Status: Fix Committed = In Progress
** Changed in: inkscape
Assignee: Krzysztof Kosinski (tweenk) = Jon A. Cruz (jon-joncruz)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Confirmed that the change in r9909 is a temporary work-around, and that
the true fix is to determine if the icon lives in the IconTheme or as a
Stock item. Instead of try/catch a simple check of IconTheme::has_icon()
can be done and stock items loaded when needed.
--
You received this bug
for them.
** Changed in: inkscape
Assignee: (unassigned) = Jon A. Cruz (jon-joncruz)
** Changed in: inkscape
Status: Confirmed = In Progress
** Changed in: inkscape
Milestone: None = 0.48.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Fixed in trunk revision 9745. Now shows the correct icon for document
properties, not the generic fallback.
** Changed in: inkscape
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fix backported to the 0.48.x branch as revision 9937.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/658055
Title:
inkscape crashes when opening document properties
--
ubuntu-bugs mailing list
Simple work-around to get copies of the renamed file and directory icons
in so that the recent manager will not crash.
** Patch added: Workaround for renamed file and directory icons.
https://bugs.launchpad.net/inkscape/+bug/651678/+attachment/1756950/+files/copy_renamed_icons.patch
--
You
Fix committed in trunk revision 9939 and 0.48.x revision 9747.
** Changed in: inkscape
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/651678
Title:
What Inkscape does is install it's own icons as fallback versions for
what it has, then later on asks GTK via its standard loading mechanism
to load the given icon by string name. From that point it's up to GTK
and the themes involved to resolve things and return the proper one.
Sounds like it
This is not as simple as it may appear. The immediate difference from
the paradigm Captain Chaos is used to is that Inkscape is currently a
*single* threaded application, and there is not UI event dispatch thread
different from a main execution thread.
--
Displayed value in spinner boxes not
It's not.
GTK+ has an event-driven, cross-platform object oriented GUI toolkit.
Circumventing the designed flow is not easy, can negatively impact
performance and can cause hard to address bugs that might show up only
on certain platforms, with certain themes or with certain engines and
backends.
using cp437 really sounds like a work-around and not a full solution. We
should look into that aspect.
--
SVG with media output fails with special characters
https://bugs.launchpad.net/bugs/456248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Instead of magic numbers, you might want to look at having things return
an enum. That can make the code more legible and maintainable.
--
inkscape 'export bitmap' dialog should indicate success and close after export
https://bugs.launchpad.net/bugs/43730
You received this bug notification
As-described, this is not really a bug. It is a wishlist/feature
request.
** Changed in: inkscape
Importance: High = Wishlist
--
markers must take object's stroke color (SVG 1.2 feature)
https://bugs.launchpad.net/bugs/165865
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 257685 ***
https://bugs.launchpad.net/bugs/257685
** This bug has been marked a duplicate of bug 257685
Inkscape color chooser widget's maximum limited to 245 instead of 255
--
Can't use an opaque color: Alpha, Lightness, Saturation, etc to more than
This is fixed in what will be 0.47, not back in 0.46.
There is a fix in. It is just that a release has not yet been made and
pushed downstream
--
Inkscape color chooser widget's maximum limited to 245 instead of 255
https://bugs.launchpad.net/bugs/257685
You received this bug notification
I've added a work-around for this in the latest Inkscape SVN, however it
is a bug in the gtk-qt-engine theme engine.
It appears that gtk_paint_shadow() was not implemented correctly, and
instead of just outlining a box it fills the box completely, wiping out
any contents. It also does not appear
It turns out that the gtk-qt-engine theme has problems with
gtk_paint_shadow. The documentation is that it draws around a box, but
that engine fills the area completely, painting over anything already
there.
I added a work-around to draw the colors on top of the shadow. This will
be ugly with
** Changed in: inkscape
Assignee: (unassigned) = Jon A. Cruz (jon-joncruz)
--
no pics for color sliders in Inkscape
https://bugs.launchpad.net/bugs/281809
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 168648 ***
https://bugs.launchpad.net/bugs/168648
** This bug has been marked a duplicate of bug 168648
Minimum window size is too large
--
window doesn't maximize
https://bugs.launchpad.net/bugs/325709
You received this bug notification because you are
I believe this is what I encountered with bug 212737
https://bugs.launchpad.net/ubuntu/+source/wacom-tools/+bug/212737
--
mouseemu breaks wacom tablet drivers
https://bugs.launchpad.net/bugs/261385
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Compiled and installed wacom drivers myself, but did not help.
However, in searching I came across some mention of mouseemu interfering
with a wacom installation. I checked and did have it running. Removed it
via synaptic, restarted X11 and the wacom tablet started working
properly.
--
Wacom
This might be related to or worked-around by #221676
https://bugs.launchpad.net/inkscape/+bug/221676
--
Problems maximizing Inkscape 0.46 on Ubuntu Hardy
https://bugs.launchpad.net/bugs/213140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
/dev/input/wacom exists and appears to be linked to the proper event.
Also when pointing wacdump at either /dev/input/wacom or the linked
event*, the expected tablet info is displayed (only non-functional).
Pointing wacdump to the other devices there does not show any recognized
device.
It also appears that there was more wacom info in dmesg on the live-CD
boot than on the boot from install on HD.
** Attachment added: dmesg output from working livecd run
http://launchpadlibrarian.net/13196763/dmesg.from_CD
--
Wacom tablet works from LiveCD but not installed hardy
** Attachment added: dmesg output from non-working HD run
http://launchpadlibrarian.net/13196772/dmesg.from_HD
--
Wacom tablet works from LiveCD but not installed hardy
https://bugs.launchpad.net/bugs/212737
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I tried Hardy beta with a MacBook Pro and Wacom Intuos3. Things worked
from a LiveCD session once I added manual wacom entries to xorg.conf.
(I'd previously setup the tablet on a PC running 7.10)
However, once I used that CD to install to the laptop, the tablet did
not work.
40 matches
Mail list logo
