I love having pt as units because my work is mostly for print, and it was a
real pain to calculate the type size from pixels for every text object, every
time.
However I found that when I add a viewBox to documents stored with current
trunk with pt as units, the size of SVG text is wrong when vi
I'm having the same problem with classic desktop without effects, so I
assume it's not related to compiz, but nVidia drivers.
I experience the same rendering artifacts in two different machines
using Ubuntu Natty (64-bit) with nVidia binary drivers from jockey
(current). One machine has a GeForce
As was stated above by Tom Davidson, there's a couple of ways to convert
between inkscape pixels and points. And both are tedious :-p
You can manually change the size of every type object using the XML editor, or
use a factor of 1.25 to convert the desired point size into pixels.
Inkscape uses a
Inkscape uses a resolution of 90dpi for the "real-size"
representation. So, if you create a 90x90px square it will be 1x1
inches in "real" units.
A typographic point is 1/72 of an inch, which is equal to a resolution
of 72 dpi.
90/72=1.25. So 1.25 is the factor you can use to translate between
inks
Confirmed in Ubuntu 10.10 beta. Inkscape 0.48 from repositories.
However, the problem doesn't show up in Ubuntu 10.04 (I'm using a build from
Nightly Builders PPA)
--
Ghosts of pointer's past (ruler refreshing problem)
https://bugs.launchpad.net/bugs/627134
You received this bug notification bec
I've been having similar problems. I read somewhere that this is caused by
dropbox daemon.
Could you please confirm if you have dropbox installed or if it occurs in an
installation without that application?
--
Ubuntu9.04 Nautilus Crash using "cut & paste" with hd-usb
https://bugs.launchpad.net/
*** This bug is a duplicate of bug 208079 ***
https://bugs.launchpad.net/bugs/208079
I meant, you can disable the snapping toolbar if you use 0.47 pre and
you still haven't enough space in your screens (even though the UI was
fixed for small screens, there are some problems in very small
resol
*** This bug is a duplicate of bug 208079 ***
https://bugs.launchpad.net/bugs/208079
btw, you can disable the snapping toolbar. It may help.
--
Problem with Maximizing
https://bugs.launchpad.net/bugs/435042
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ubuntu
Status: New => Fix Committed
--
Vertical ruler issue on Ubuntu 9.04 amd64
https://bugs.launchpad.net/bugs/371156
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.
When I suggested to keep related reports in one single bug report I
meant about inkscape having problems with small screens. There were a
couple of bugs related to the screen size and was pointless (in my
oppinion) to have them separated, since the origin was the same:
inkscape UI didn't fit in sma
Tim, it's fixed in SVN. The fix will be included in Inkscape 0.47, which will
be released in june.
Meanwhile, you can try a development version (Tobias Wolf has a PPA in
launchpad with a recent build for Jaunty).
--
Inkscape color chooser widget's maximum limited to 245 instead of 255
https://b
I guess we should close it too. Inkscape crashes in a very particular situation
and if this report had not much followups, maybe it's not that frequent.
Since Ubuntu guys don't think it's worth to fix cairo for Hardy and the bug is
caused by Cairo, maybe the offending feature should be disabled (
Can't reproduce this bug in Inkscape SVN (Ubuntu 8.10 - 64 bit)
--
Crash when selecting Pattern for fill/stroke in the Fill&Stroke dialog
https://bugs.launchpad.net/bugs/245301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
It doesn't hang anymore for me in Ubuntu Intrepid.
--
disabling compositing-manager freezers the computer
https://bugs.launchpad.net/bugs/232128
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Hi.
I'd mark this request as invalid. Most of the points you mention have a
workaround
- You can pan the image pressing the middle button (weel) of the mouse and
dragging. That's extremely convenient and fast (since you can draw and pan with
a hand, without needing any keyboard shortcut). GIMP
It's an nVidia problem. It only happens with the nVidia drivers.
It's something about the default value that nvidia X server settings assign to
the hue. Changing the hue value in individual applications is in my opinion the
wrong approach.
I think it's better to change the hue value in the nvidia
I guess that some minor changes would improve the usability of that window:
- Progress bar should appear in the same window, no popups.
- The progress bar area should change to "export succeded" when the export
finished, until the user clicks on another object in the canvas that wasn't
exported y
I think that Ubuntu already respects their trademark, but If what they want is
more a notice than technically an EULA (afaik you can still use the browser
even if you don't accept it), why not adding those terms in the page displayed
as default?
Mozilla trademark and legal people could help to d
** Changed in: metacity (Ubuntu)
Status: Incomplete => Confirmed
--
disabling compositing-manager freezers the computer
https://bugs.launchpad.net/bugs/232128
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
My configuration seems to be the same that Tiede posted, so please refer to his
lspci output.
The problem reported is the same.
Since compositing isn't on by default, it's not a high priority bug, and won't
affect an inexperienced user.
Anyway, this bug along bug #232128 make things look pretty
Confirmed. I have the same problem here.
--
disabling compositing-manager freezers the computer
https://bugs.launchpad.net/bugs/232128
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.
Public bug reported:
Binary package hint: metacity
Video playback presents artifacts when the composite manager is enabled.
Problems are: black window, dissappearing video when the window is moved, black
sectors when the window is maximized or switched to full screen.
Video works correctly with
I have the same problem, but in my case Metacity doesn't crash, it freezes. The
only way to recover control is killing X and restarting the session.
If I do that, the compositing manager is off when the session is restarted.
I think the original report was about the same issue, but maybe seanh use
Amd64 too here. I have the new metacity compositing effects activated,
and it produces some artifacts apart of the crashes
--
totem-gstreamer crashed with SIGSEGV in pa_stream_update_timing_info()
https://bugs.launchpad.net/bugs/203770
You received this bug notification because you are a member o
No problems with recen SVN here. Running Ubuntu Gutsy too and exporting to PNG
daily without a single crash.
Notice that the latest autopackages (all november's) don't install properly.
Use a previous compilation or dl from here:
http://alexv3d.blogspot.com/2007/11/inkscape-compilacin-svn-noviemb
25 matches
Mail list logo