Which version of GTK2 do you have installed?
… and which version of cairo?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1049250
Title:
When i want to print a file, Inkscape crashes
To manage
Till Kamppeter wrote:
(…) we should take the patch from that bug (…) into Ubuntu's
GTK+3.0 package.
Is this all to fix this bug? Or is there anything to do on GIMP, Inkscape,
and Firefox?
At least Inkscape and GIMP are still GTK2 apps - AFAIU a change in the
cups printbackend in
So we could close this report and mark it as fix committed?
IMHO no - the issue with fonts hasn't been resolved yet. Unfortunately,
someone decided last year to merge the two distinct issues which we had
tried to track in separate reports into one (by linking other reports as
duplicates). I
I wonder why couldn't inkscape cache them to config dir on first
start?
Caching of icons on disk is already implemented in current trunk (will
be available in the next major stable version 0.49).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Apparently the changes were introduced in Poppler 0.18 (at least it doesn't
compile
on Crunchbang 11, based on Debian Wheezy, Poppler 0.18.4-3).
Current trunk compiles fine for me both with poppler 0.18.4 and with
poppler 2.20.3 (no poppler-specific local changes to configure.ac) on OS
X
John Smith wrote:
Commit r11671 should fix the problem with duplicates
When quitting Inkscape after having changed the color of a duplicate, I now get
these kinds of console warnings:
** (inkscape:89410): CRITICAL **: void Inkscape::GC::Anchored::release() const:
assertion `_anchor' failed
Same unexpected behavior (r11664, default prefs) with these steps:
1) Draw multiple paths
2) select all, add marker (arrow)
3) deselect all
4) select a single path and change the stroke color
-- all markers from step 2 change color
5) select a different path
-- all markers change color to the
Possibly this is similar to
- Bug #937835 “inkscape crashed with SIGSEGV in
Inkscape::Preferences::_getNode()”
(and Bug #983843 “inkscape crashed with SIGSEGV in
Inkscape::Preferences::_getNode()”)
a duplicate of
- Bug #941317 “inkscape crashed with SIGSEGV in getObject()”
Which desktop are you using, and which gtk theme / theme engine (for
Inkscape, or GTK2 applications in general)?
Possibly related:
Bug #1049179 “Inkscape crashes when Save as or Save a copy... is pressed”
(Invalid)
(apparently upstream issue in (undisclosed) gtk theme under KDE - most likely
** Tags added: crash printing
** Also affects: inkscape (Ubuntu)
Importance: Undecided
Status: New
** Changed in: inkscape
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: performance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1019147
Title:
Inkscape high cpu usage
To manage notifications about this bug go to:
** Also affects: inkscape
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044064
Title:
inkscape freezes in 12.10 after clicking on fonts button (see the
(…) and allows power users to hit grand slams (when they choose)...
What exactly is the benefit of hardcoding (and thus mixing) relative and
(seemingly) absolute units in the same document?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Should we encourage users to not use these standard SVG units
because some other programs don't render those units correctly
Some other SVG renderers (i.e. all tested web browsers as well as
Inkscape's reference SVG implementation batik) being incorrect is not
the underlying issue AFAIU:
ScislaC wrote:
~suv: complimentary preference to write hardcoded units, just defaulted to
off?
I can't claim to be an SVG expert myself, and do hope that others with
more insight and experience with SVG will chime in: the issue with units
(SVG user units 'px' vs real (absolute) units
Inkscape welcome to the world on text points !
A. Hard-coding the units (r11608) in the style attribute of text objects
potentially does cause trouble if the SVG file is rendered by other
viewers (e.g. web browsers). Text with units other than 'px' apparently
may scale differently than the rest
** Tags removed: backport-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005565
Title:
poppler 0.20 breaks build
To manage notifications about this bug go to:
** Tags removed: backport-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/944077
Title:
inkscape crashed with SIGSEGV in
Inkscape::Extension::Implementation::Script::effect()
To manage
** Changed in: inkscape
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/1001997
Title:
inkscape crashes ubuntu
To manage notifications about this bug go to:
Duplicate of Bug #966441 “inkscape crashed with SIGSEGV in
sp_dtw_color_profile_event()”?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025317
Title:
inkscape crashed with SIGSEGV
To manage
Newly created custom markers are not added to list of available markers
I will fix this is a separate patch (probably bug #903671)
Thx, much appreciated - I filed bug #1030239 yesterday about the
regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
AFAICT current patch breaks Custom markers (menu 'Object Objects to
Marker'):
- Newly created custom markers are not added to list of available markers
anymore (can't be applied).
My mistake - this broke much earlier in current trunk (between r11072
and r11084, based on tests with archived
Testing 165865.v1.patch with Inkscape 0.48+devel r11573 on OS X 10.7.4:
John Smith wrote:
svg:marker top level group fill and stroke attributes both set
to line stroke color
Doesn't work well with stock markers which use a custom fill color (e.g.
white), or open unfilled stroked paths, or
** Changed in: inkscape
Milestone: None = 0.49
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908392
Title:
Initial size of palette dialog on Ubuntu too small
To manage notifications about this
$ ldd `which inkscape` | grep gtk
That returns the soname/soversion of the installed lib, but does not
tell which version of GTK+ you have installed (e.g. 2.24.8 or 2.24.10) -
the library soversion does not change with dot releases (usually).
Try this:
$ pkg-config --modversion gtk+-2.0
--
Also reported as affecting project Inkscape here:
Bug #1023004 xorg crashes when clicking in inkscape work area
Based on the provided feedback (it seems that the last xserver update
fixed the problem.), bug #1023004 had been closed for project Inkscape,
and probably could be marked as duplicate
Similar to
- Bug #975972 Inkscape sends jobs with zero page size
https://bugs.launchpad.net/inkscape/+bug/975972
this could be another duplicate of
- Bug #998156 'GTK Print dialog sends broken custom page size attribute:
PageSize=Custom.Custom.widthxlength'
Thanks for the update - closing as 'Invalid' for project 'Inkscape'.
** Changed in: inkscape
Status: Fix Released = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023004
Title:
xorg
** Tags added: printing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975972
Title:
Inkscape sends jobs with zero page size
To manage notifications about this bug go to:
Please verify that this is not actually a duplicate of bug #998156 as
mentioned in comment #19 (upstream bug/regression in GTK+ = 2.24.10).
See also
http://article.gmane.org/gmane.comp.graphics.inkscape.devel/38078/match=custom
where the same issue with GTK+ 2.24.10 was described affecting
Which version of GTK+ do you have installed?
Similar to
- Bug #975972 Inkscape sends jobs with zero page size
https://bugs.launchpad.net/inkscape/+bug/975972
this could well be another duplicate of
- Bug #998156 'GTK Print dialog sends broken custom page size attribute:
Possibly triggered by a recent upgrade of xserver-related packages as
described in this forum topic:
http://forums.linuxmint.com/viewtopic.php?f=59t=106911? Seems to
affect not only Inkscape, but GIMP as well.
off-topic
It also reminds me of a similar crash which occurred with a recent
Duplicate of Bug #964726 “epson print filter fails when printing”?
https://bugs.launchpad.net/inkscape/+bug/964726
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021635
Title:
Fails to print to
Possibly duplicate of
Bug #964726 “epson print filter fails when printing”
https://bugs.launchpad.net/inkscape/+bug/964726
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020499
Title:
Fail to
~suv wrote on 2011-08-10:
Probably fixed in r10491
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/10491
Reproduced with r10490, not reproduced with r10493 and later revisions
(tested with archived builds).
** Changed in: inkscape
Status: Confirmed = Fix Committed
Remaining issues with new default font 'sans-serif' in trunk (marked with Font
not found on system) are tracked in
Bug #1002757 Regressions with new default font 'sans-serif' (r11393)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
off-topic
Could you please let me know the svn link of latest trunk
Inkscape no longer uses SVN - current trunk uses BZR and is hosted here
at launchpad (you can easily find the sources following the links on
inkscape's main page here at launchpad:
https://launchpad.net/inkscape).
If that
I just installed a fresh copy of inkscape on Ubuntu 10.04 LTS
Note that Lucid is no longer supported for Inkscape trunk (too many outdated
versions of required dependencies).
http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies#Distros
--
You received this bug notification because
There are daily snapshot builds offered for Lucid by Cafuego:
https://launchpad.net/~cafuego/+archive/inkscape
which include newer versions of at least gtk2, cairo, cairomm, and are built
with a patched version of GCC.
--
You received this bug notification because you are a member of Ubuntu
There are daily snapshot builds offered for Lucid by Cafuego:
These daily builds for Lucid will probably stop once Bug #1020494 Drop
GTK+ 2.20 support has been resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: inkscape (Ubuntu)
Importance: Undecided
Status: New
** Tags added: printing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020499
Title:
Fail to print to a HP Laserjet
** Also affects: inkscape (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1019147
Title:
Inkscape high cpu usage
To manage notifications about
*** This bug is a duplicate of bug 1019147 ***
https://bugs.launchpad.net/bugs/1019147
** This bug has been marked a duplicate of bug 1019147
Inkscape high cpu usage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 790130 ***
https://bugs.launchpad.net/bugs/790130
Linking as duplicate to bug #790130 “no pressure sensitivity with wacom
tablet in inkscape”.
** This bug has been marked a duplicate of bug 790130
no pressure sensitivity with wacom tablet in inkscape
--
I just installed a fresh copy of inkscape on Ubuntu 10.04 LTS via
synaptic package manage
Which version is available for Ubuntu 10.04? (see Inkscape menu 'Help
About Inkscape')
However If i set outline mode of drawing, it works perfectly fine on
both the system.
Does hiding the status bar
Since another bug-fix release (0.48.4) is planned, this needs to be
backported to the 0.48.x branch AFAIU.
** Changed in: inkscape
Status: Fix Released = Fix Committed
** Changed in: inkscape
Milestone: None = 0.49
** Tags added: backport-proposed
--
You received this bug
Probably a duplicate of
Bug #790130 “no pressure sensitivity with wacom tablet in inkscape ”
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/790130
It turned out that the overlay scrollbars under Unity break pressure
sensitivity for Inkscape.
Workaround:
Workaround in Inkscape 0.48.3.1 for affected files to avoid a crash when
running an extension:
rename the id of namedview to base.
Steps:
1) open affected file
2) open 'Edit XML Editor…'
3) select the node sodipodi:namedview … in the list on the left
4) select the attribute 'id' in the upper
Steps to reproduce a crash (unclear to me though whether this is what happened
to the reporter):
1) open 'todos.svg'
2) select the group of connectors for the bottom-left diagram
(note: only one of them initially appears to connect two of the circles, the
others have zero-length at the SVG
Could the fix for this bug be reviewed?
AFAICT the crash occurs when running extensions in documents which use
an arbitrary ID for the node namedview (other than what is used in
default templates) - e.g. when opening PDF files, Plain SVG files, or
other SVG documents which originally didn't have
*** This bug is a duplicate of bug 944077 ***
https://bugs.launchpad.net/bugs/944077
Linking as duplicate to Bug #944077 inkscape crashed with SIGSEGV in
Inkscape::Extension::Implementation::Script::effect().
Please add a comment here and revert the duplicate status if you don't agree
and
Unfortunately earlier commenters could not agree about the scope of this
report (which was originally about a specific issue of Inkscape with the
win32 backend of GTK+: artifacts (leftovers) on the canvas area when
dragging a floating dialog), and decided to use it as (unrelated) kind
of
Duplicate of Bug #944077 inkscape crashed with SIGSEGV in
Inkscape::Extension::Implementation::Script::effect()?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985412
Title:
inkscape crashed with
Like bug #937835 “inkscape crashed with SIGSEGV in
Inkscape::Preferences::_getNode()” a duplicate of Bug #941317 “inkscape
crashed with SIGSEGV in getObject()”?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Alex Valavanis wrote:
Possible duplicates..?
bug #965051 inkscape hangs when edit/cut objects
bug #837631 Crash when grouping objects+connectors across different layers
Based on the backtrace, possibly - but without the SVG file the reported
crash cannot be further investigated (a screenshot
Luca Bruno wrote:
As we're using older poppler libs on various architecture
(prominently 0.12 in windows devlibs), I'd suggest going for
conditional building instead.
The attached patch works both with newer and older poppler version,
and it's up for review. If no objections received, I'm
*** This bug is a duplicate of bug 944077 ***
https://bugs.launchpad.net/bugs/944077
Duplicate of
Bug #944077 “inkscape crashed with SIGSEGV in
Inkscape::Extension::Implementation::Script::effect() ”
https://bugs.launchpad.net/inkscape/+bug/944077
** This bug has been marked a duplicate of
*** This bug is a duplicate of bug 944077 ***
https://bugs.launchpad.net/bugs/944077
Reproduced with Inkscape 0.48.3.1 on OS X 10.7.4:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x01d8
0x0001002412a8 in
** Attachment added: 1004856-r11417-osx-Ambiance-theme.png
https://bugs.launchpad.net/inkscape/+bug/1004856/+attachment/3163963/+files/1004856-r11417-osx-Ambiance-theme.png
** Also affects: inkscape (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
there is no way I can do vertically resize in the panel.
At the bottom of the docked dialog is a handle - grab it and drag it
downwards to increase the height of the dialog window: this will also
increase the height of the scrollable window with the glyphs.
** Attachment added:
** Tags added: shortcuts
** Also affects: inkscape (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998276
Title:
Keyboard shortcuts not appearing
Probably related to
Bug #775702 Some menu icons missing in Inkscape since upgrade to 11.04
https://bugs.launchpad.net/bugs/775702
On screenshots provided by Ubuntu (Unity) users affected by the missing
menu icons, the keyboard shortcuts are also missing.
--
You received this bug notification
Alex Valavanis wrote
Confirmed with lp:inkscape r11404 on Ubuntu 12.04 amd64
Could you test/confirm that the keyboard shorctcuts (as well as the menu icons
loaded from Inkscape's icons.svg file) are present on Ubuntu using the
workarounds mentioned in bug #775702:
- using the Gnome desktop
Is not this request not something for scour?
Not necessarily - see for example the recent merge of last year's GSoC project
into trunk:
http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/37649
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 775702 ***
https://bugs.launchpad.net/bugs/775702
** This bug has been marked a duplicate of bug 775702
Some menu icons missing in Inkscape since upgrade to 11.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 752674 ***
https://bugs.launchpad.net/bugs/752674
Duplicate of Bug #752674 “GtkRecentChooserMenu always selects first
entry”
** This bug has been marked a duplicate of bug 752674
GtkRecentChooserMenu always selects first entry
--
You received this bug
** Tags added: extensions-plugins
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/944077
Title:
inkscape crashed with SIGSEGV in
Inkscape::Extension::Implementation::Script::effect()
To manage
PetaMem wrote :
Albeit openclipart.org is not down/maintenance, inkscape crashes.
openclipart.org is not down, but its feeds are currently broken (see also bug
#989257):
Bug #988844 “Feeds are no longer valid”
https://bugs.launchpad.net/openclipart/+bug/988844
--
You received this bug
The bug also appears in Fedora 16, with no .recently-used file in the
home directory.
Recent versions of Gtk+ have changed the location of the file storing entries
for recently used files on linux (Gtk+/win32 uses a different location for the
same file): on linux it is now saved as
@ScislaC - can you confirm the workaround / underlying trigger for the
tablet regression (no pressure sensitivity) on Ubuntu described by Ben?
ScislaC wrote on 2012-03-06:
One issue is that it hasn't been completely messed
up since Natty, during the Oneiric dev cycle at one
point I seem to
Based on the latest comments in
https://bugs.kde.org/show_bug.cgi?id=295803 - can we close this report
as 'Invalid' for the project 'Inkscape'?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948178
or as fixed. yes. i can not reproduce this anymore
There had been no changes in Inkscape's code base - the fix was upstream
in the Oxygen gtk2-engine.
Closing as 'Invalid' for Inkscape - feel free to reopen if you have
additional information that the conflict in Oxygen's gtk2 theme engine
with
** Tags added: backport-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973174
Title:
inkscape crashed with SIGSEGV in
Inkscape::Extension::Output::get_extension()
To manage notifications
** Tags added: backport-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941317
Title:
inkscape crashed with SIGSEGV in getObject()
To manage notifications about this bug go to:
Changed in inkscape:
status: New → Confirmed
Please clarify for upstream report: What exactly got confirmed?
The bug as originally reported, is not a bug:
1) Inkscape's toolbars are not and never have been freely relocatable nor
rotatable. To change the toolbar layout, choose between
Changed in inkscape:
importance: Undecided → High
Should be lowered to 'Medium' IMHO: it's only the separately spawned
python process which crashes (on Ubuntu 12.04) - i.e. executing the
extension fails. The main Inkscape process itself is not affected, and
there is no risk of data loss
Export to jpg borker
Not supported by Inkscape - feature request tacked in:
Bug #171390 (sf1516747) “Extended Raster export support please”
https://bugs.launchpad.net/inkscape/+bug/171390
I tried to save a copy of a file as a jpg, using the guess type by
extension option.
ProblemType:
Got this crash again when closing Inkscape after saving my file as a
.xcf.
Testing on OS X 10.7.2:
- Not reproduced with Inkscape 0.48.2: Inkscape quits without crash
- Reproduced with Inkscape 0.48.3.1 and 0.48+devel r11146
** Tags added: regression saving
** Changed in: inkscape
Related:
Bug #740843 “Really slow to start because of .recently-used”
https://bugs.launchpad.net/inkscape/+bug/740843
Bug #703517 “Inskscape slows down when an external drive is connected”
https://bugs.launchpad.net/inkscape/+bug/703517
--
You received this bug notification because you are a
- Reproduced with Inkscape 0.48.3.1 and 0.48+devel r11146
More tests with archived trunk builds indicate that the regression was
introduced between r10819 and 10828 (lp:inkscape):
- not reproduced with = r10819
- reproduced with = r10828
Possibly a side-effect of the fix for the win32 saving
** Also affects: inkscape-devlibs
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/813886
Title:
Save as EPS or PS incomplete with cairo = 1.10
To manage
This bug is still present in Inkscape 0.48.3.1 r9886.
As explained in duplicate Bug #967902, it is not a bug in Inkscape itself - it
depends on which version of cairo Inkscape uses.
The installer of Inkscape 0.48.3.1 for Windows was created _before _ the
release of cairo 1.12.0 (it ships with
Not reproduced on OS X 10.7.2 with Inkscape 0.48.3.1 and current trunk
r11129, Python 2.7.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946599
Title:
lindenmayer.py crashed with IOError in
[Expired for inkscape (Ubuntu) because there has been no activity for
60 days.]
Closing as 'Invalid' for Inkscape due to lack of feedback. Feel free to
reopen if you can provide more information (see comment #5 for details
about additional information requested).
** Changed in: inkscape
fixing this problem in Inkscape should be as simple as bumping
the version requirement of libgc to =7.1. Is this likely to cause
any problems for anyone?
@Alex - this question came up yesterday on irc (whether to close this report or
not), and kaeso has added the dependency to
@madbiologist - see comment #10 (this report was neither kept open nor
marked as 'Critical' in Inkscape because of the Windows port of
Inkscape, but because of Ubuntu apparently being late with updating
cairo). From my POV it is ok to close it as 'Invalid' - Cairo 1.10.0 had
been released 15
madbiologist wrote:
Ubuntu does not track bugs in the Windows port of Inkscape.
Changed in inkscape:
status: Confirmed → Invalid
@madbiologist - that's the wrong reason to close this report: Inkscape's
bug tracer is certainly _not_ limited to Inkscape on Ubuntu (there's a
separate
Which Inkscape version?
What does this report differ from Bug #790130 no pressure sensitivity with
wacom tablet in inkscape?
https://bugs.launchpad.net/inkscape/+bug/790130
** Tags added: tablet
** Also affects: inkscape (Ubuntu)
Importance: Undecided
Status: New
--
You received
s/What/How/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947577
Title:
Precise pressure sensitivity
To manage notifications about this bug go to:
Did someone switch it off?
Not in Inkscape itself - pressure sensitivity works ok with stable and
trunk on some other platforms. Issues on Ubuntu (apparently since Natty)
have been reported (bug #790130), but not addressed yet.
--
You received this bug notification because you are a member of
@ScislaC - I still don't see how this is a different issue than already
tracked in bug #790130 (which does include comments confirming the
problem on Oneiric), but I'll have to trust you on that one if you think
these are two unrelated bugs, in Inkscape itself.
** Summary changed:
- Precise
Related report:
Bug #884368 unable to edit attributes in Inkscape XML Editor (Ubuntu
overlay-scrollbar issues)
https://bugs.launchpad.net/inkscape/+bug/884368
(see comment #12)
** Tags added: ui
** Also affects: inkscape (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
** Description changed:
If I select an attribute in the XML editor, the edit box below shows the
attribute name, not its value. If I change the attribute and hit 'set',
a new attribute is created with this name. There is no apparent way to
change an existing value. I'm using 0.48.2 from
waiting on bug #946715
quote from #946715
in inkscape, if libgnomevfs2-extra is not installed, the import from
openclipart.org will fail.
/quote #946715
Note: in the next major stable Inkscape 0.49, the (just recently merged) new
dialog for 'Import Clip Art…' will no longer depend on
@TK - a crash when browsing files in Import From Open Clip Art Library… is
not related with the reported issue here (bug #810238), which was described as:
Crash when trying to edit a shadow filter
Bug status for the 'Inkscape' project will not be changed - see comment
#5.
--
You received
@Krzysztof - can we close this report as 'Invalid' for Inkscape now?
Stable cairo 1.10.2 had been released more than one year ago on
2010-12-25.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/681512
Just for the record (I am aware that the report was closed as 'Fix
Released')
~suv wrote in comment #8
Tweaking things to not look for the platform but to instead test the linker
support.
That's not what was committed in r10078 as far as I can tell - it just
renames
the variable which
Inkscape 0.48.2 (tarball) and 0.48.x (r9860) builds on OS X 10.7.2 Lion with
attached patch applied to the sources - I haven't had the chance yet to verify
the changes with Apple's GCC 4.2.1 nor with llvm-gcc-4.2. The patch seems save
though:
1) AFAIU the older GCC version simply dropped the
Correction:
- Inkscape 0.48.2 (tarball) and 0.48.x (r9860) builds on OS X 10.7.2 Lion with
attached patch applied to the sources
+Inkscape 0.48.2 (tarball) and 0.48.x (r9860) builds with GCC 4.6.2 on OS X
10.7.2 Lion with attached patch applied to the sources
--
You received this bug
Do you think this is good enough to commit ?
Based on my tests, yes - AFAICT it restores the old and expected
behavior of the node tool in prior releases.
Local tests have been done using Inkscape with keyboard and external
mouse/internal trackpad (laptop) - maybe feedback by advanced tablet
201 - 300 of 742 matches
Mail list logo
