[Desktop-packages] [Bug 1687817] Re: Inkscape 0.92.1-1 always reverts display units to px
** Changed in: inkscape Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1687817 Title: Inkscape 0.92.1-1 always reverts display units to px Status in Inkscape: Incomplete Status in inkscape package in Ubuntu: New Bug description: Files created in Inkscape 0.92 no longer respect user's display units. Inkscape 0.91 didn't have this problem. Expected results: 1. Open Inkscape 2. Set File → Document Properties → Display Units to mm 3. Edit and save the file, then quit Inkscape 4. Reopen the docuemnt in Inkscape, and the Display Units value in the object toolbar and the Document Properties should remain as mm. Actual results: 1. Open Inkscape 2. Set File → Document Properties → Display Units to mm 3. Edit and save the file, then quit Inkscape 4. Reopen the docuemnt in Inkscape, and the Display Units value in the object toolbar and the Document Properties are set to px. 5. Alternatively, File → Save As… immediately changes Display units to px. I work with laser cut patterns made in Inkscape, and maintaining document size is critical. I know about the recent 90/96 px/inch change, and this shouldn't be affected by that ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: inkscape 0.92.1-1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Tue May 2 19:37:46 2017 InstallationDate: Installed on 2015-03-08 (786 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: inkscape UpgradeStatus: Upgraded to zesty on 2017-04-15 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1687817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1687817] Re: Inkscape 0.92.1-1 always reverts display units to px
*** This bug is a duplicate of bug 1671691 *** https://bugs.launchpad.net/bugs/1671691 ** This bug has been marked a duplicate of bug 1671691 Display units in document properties not respected for converted old files -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1687817 Title: Inkscape 0.92.1-1 always reverts display units to px Status in Inkscape: New Status in inkscape package in Ubuntu: New Bug description: Files created in Inkscape 0.92 no longer respect user's display units. Inkscape 0.91 didn't have this problem. Expected results: 1. Open Inkscape 2. Set File → Document Properties → Display Units to mm 3. Edit and save the file, then quit Inkscape 4. Reopen the docuemnt in Inkscape, and the Display Units value in the object toolbar and the Document Properties should remain as mm. Actual results: 1. Open Inkscape 2. Set File → Document Properties → Display Units to mm 3. Edit and save the file, then quit Inkscape 4. Reopen the docuemnt in Inkscape, and the Display Units value in the object toolbar and the Document Properties are set to px. 5. Alternatively, File → Save As… immediately changes Display units to px. I work with laser cut patterns made in Inkscape, and maintaining document size is critical. I know about the recent 90/96 px/inch change, and this shouldn't be affected by that ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: inkscape 0.92.1-1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Tue May 2 19:37:46 2017 InstallationDate: Installed on 2015-03-08 (786 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: inkscape UpgradeStatus: Upgraded to zesty on 2017-04-15 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1687817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735363] Re: inkscape: Port to Python 3
Some work has been done on this by doctormo during the Hackfest, as far as I understand. However, the Python3 port has been combined with moving extensions out of the main repo for that branch, so not sure about compatibility and usefulness with/for current Inkscape versions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1735363 Title: inkscape: Port to Python 3 Status in Inkscape: Triaged Status in inkscape package in Ubuntu: Confirmed Status in inkscape package in Debian: Confirmed Bug description: inkscape: Use/Port of Python3 needed, or considering demotion. Currently seeded in usb (???), owned by desktop-packages. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735363] Re: inkscape: Port to Python 3
Thank you for the explanation, Bryce and Mattia! But until 2020, this should be solved, as far as I understand, regardless of this? We've only got 2 hackfests until then... time flies. I found that these depend on python scripts, but there may be more, hope others will fill in the blanks (I've also got no clue of how easy or hard it's to port these): - several python export and import routines (that use extensions, e.g. save as optimized SVG via scour (how's scour doing with Python3, @Eduard?), dxf. What about uniconvertor? Does it have a python3 version?... We don't include it, but it needs to work with the rest... :-/ Or I think there was talk about dropping it...? - the customizable templates (those with dots in the 'New from Template' dialog). - everything aside from Tutorials in the Help menu (probably very quick to port, if anything needs to be done at all) - couldn't find what 'prepare_file_save_as.py' is currently used for, weirdly - but I think it was needed for export to dxf... - there seem to be several i18n-generation scripts in various subdirectories of the /share/... directory tree - guess they are used to internationalize the svg files (filters, markers,...) there - several packaging scripts, for win and some Cmake scripts - (extension tests) - dpi switcher extension (not needed when opening files, intended for switching manually later) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1735363 Title: inkscape: Port to Python 3 Status in Inkscape: Triaged Status in inkscape package in Ubuntu: New Status in inkscape package in Debian: Confirmed Bug description: inkscape: Use/Port of Python3 needed, or considering demotion. Currently seeded in usb (???), owned by desktop-packages. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735363] Re: inkscape: Port to Python 3
@valavanisalex Sorry, I don't know much about it. su_v is often around on IRC, please ask her there about the status or send her an email. As far as I know, there is no other place tracking this. Do you think this might become one focus for the Hackfest? Being 'demoted' doesn't sound so good in my ears, tbh. (Found this only by chance, I definitely need to remember to subscribe here when I comment...) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1735363 Title: inkscape: Port to Python 3 Status in Inkscape: Triaged Status in inkscape package in Ubuntu: New Status in inkscape package in Debian: Confirmed Bug description: inkscape: Use/Port of Python3 needed, or considering demotion. Currently seeded in usb (???), owned by desktop-packages. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735363] Re: inkscape: Use/Port of Python3 needed, or considering demotion
For the person who wants to work on this: Some (a lot of?) work on this has already been done by su_v: https://gitlab.com/su-v/inx-fork (not sure about current status) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1735363 Title: inkscape: Use/Port of Python3 needed, or considering demotion Status in Inkscape: New Status in inkscape package in Ubuntu: New Status in inkscape package in Debian: Unknown Bug description: inkscape: Use/Port of Python3 needed, or considering demotion. Currently seeded in usb (???), owned by desktop-packages. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04
Yes, who knows. I'll wait until 18.1 is available, and if it's not solved, then I'll investigate further. Thank you, @Gunnar Hjalmarsson! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1573755 Title: Compose and dead keys stopped working with XIM after upgrade to 16.04 Status in firefox package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in ibus package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: After upgrading to 16.04, entering characters using dead keys and using the Compose key stopped working in Gnome Terminal, acting like they are normal (non-dead) keys. Other applications, even those who use the same libvte (e.g. ROXTerm), don't have this issue. This happens with both the "Belgian" and "English international with AltGr dead keys" layouts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:45:33 2016 InstallationDate: Installed on 2013-12-16 (857 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1573755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04
Thank you, @Gunnar Hjalmarsson. I'm still on LM18, maybe update to 18.1 when available for Xfce version will take up those changes. Unfortunately, fixing this caused a different kate problem now... Can't paste with Ctrl+V (just in case anyone encounters the same as a result of following my path: pasting works for me when kate's snippet dialog isn't visible). Now I'll need to decide which problem is the one that bugs me more - no accents, or no pasting with snippet dialog open... Seems these input methods are entangled with very unexpected things. Must be a programmer's hell...! I think I'll create a snippet with accented letters and go with XIM :-\ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1573755 Title: Compose and dead keys stopped working with XIM after upgrade to 16.04 Status in firefox package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in ibus package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: After upgrading to 16.04, entering characters using dead keys and using the Compose key stopped working in Gnome Terminal, acting like they are normal (non-dead) keys. Other applications, even those who use the same libvte (e.g. ROXTerm), don't have this issue. This happens with both the "Belgian" and "English international with AltGr dead keys" layouts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:45:33 2016 InstallationDate: Installed on 2013-12-16 (857 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1573755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04
@Gunnar Hjalmarsson: It was set to 'none' before, so maybe mine is a different bug, then? (XIM wasn't available for choice in the LM settings dialog for input method, I didn't know how to find out if it was used, but not displayed.). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1573755 Title: Compose and dead keys stopped working with XIM after upgrade to 16.04 Status in firefox package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in ibus package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: After upgrading to 16.04, entering characters using dead keys and using the Compose key stopped working in Gnome Terminal, acting like they are normal (non-dead) keys. Other applications, even those who use the same libvte (e.g. ROXTerm), don't have this issue. This happens with both the "Belgian" and "English international with AltGr dead keys" layouts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:45:33 2016 InstallationDate: Installed on 2013-12-16 (857 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1573755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04
Installing IBus and setting to use it fixed it for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1573755 Title: Compose and dead keys stopped working with XIM after upgrade to 16.04 Status in firefox package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in ibus package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: After upgrading to 16.04, entering characters using dead keys and using the Compose key stopped working in Gnome Terminal, acting like they are normal (non-dead) keys. Other applications, even those who use the same libvte (e.g. ROXTerm), don't have this issue. This happens with both the "Belgian" and "English international with AltGr dead keys" layouts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:45:33 2016 InstallationDate: Installed on 2013-12-16 (857 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1573755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04
I've got this problem on Linux Mint 18 Xfce (sorry...), German keyboard, for kde based apps, ever since I upgraded from 14.04 to 16.04. konsole and kate are the applications where it hurts most. Neither Compose key+accent+char nor typing the accent, then the char, work for me (I only need ^, ´ and `, which work fine in other apps. I'd like to be able to use regexes in kate and write the occasional French translation...). @Pierre: our problems appear similar. Did you find a solution? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1573755 Title: Compose and dead keys stopped working with XIM after upgrade to 16.04 Status in firefox package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in ibus package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: After upgrading to 16.04, entering characters using dead keys and using the Compose key stopped working in Gnome Terminal, acting like they are normal (non-dead) keys. Other applications, even those who use the same libvte (e.g. ROXTerm), don't have this issue. This happens with both the "Belgian" and "English international with AltGr dead keys" layouts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:45:33 2016 InstallationDate: Installed on 2013-12-16 (857 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1573755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty
Yay :D Thank you, Alex and Mattia! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1638373 Title: End marker/start marker drop-down menus are empty Status in Inkscape: Triaged Status in inkscape package in Ubuntu: Fix Released Status in inkscape source package in Yakkety: In Progress Status in inkscape source package in Zesty: Fix Released Bug description: [ Impact ] The dropdown menus for start marker, end marker and mid markers do not contains any arrows to select. I have clean up all local settings and run inkscape fresh but the same problem. This is caused by scour being called during the build, a change inadvertently added in the 0.91-11 upload. The fix used it to just not call scour. [ Test case ] Compare the file /usr/share/inkscape/markers/markers.svg from the built package with upstream's http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_91_BRANCH/download/nicoduf%40yahoo.fr-20110829175757-0rzahc4xhhr2l6u5/markers.svg-20091128124040-aej0x7yhxng1m6ly-449/markers.svg - it should be at the very least equivalent (if not equal), currently it contains only comments. [Regression Potential] noe really Seen in in: - Inkscape 0.91 r13725 on Ubuntu 16.10 - Inkscape 0.91-11 r13725 on Ubuntu 16.10 (official package from yakkety) - DistroRelease: Ubuntu 16.10, Package: inkscape 0.91-11 - Inkscape 0.92, ubuntu 16.04 LTS - Ubuntu 16.04 - upgrade today to 0.92 - Kubuntu 14.04, and recently updated Inkscape to version 0.92.0 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1638373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty
Ah, thanks! Good that they reported right away :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1638373 Title: End marker/start marker drop-down menus are empty Status in Inkscape: New Status in inkscape package in Ubuntu: In Progress Status in inkscape source package in Yakkety: In Progress Status in inkscape source package in Zesty: In Progress Bug description: The dropdown menus for start marker, end marker and mid markers do not contains any arrows to select. I have clean up all local settings and run inkscape fresh but the same problem. Inkscape 0.91, Ubuntu 16.10 = From the duplicate reports: - Inkscape 0.91 r13725 on Ubuntu 16.10 - Inkscape 0.91-11 r13725 on Ubuntu 16.10 - DistroRelease: Ubuntu 16.10, Package: inkscape 0.91-11 - Inkscape 0.92, ubuntu 16.04 LTS - Ubuntu 16.04 - upgrade today to 0.92 - Kubuntu 14.04, and recently updated Inkscape to version 0.92.0 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1638373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty
Where did those two people get their 0.92 builds for 16.04 from? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1638373 Title: End marker/start marker drop-down menus are empty Status in Inkscape: New Status in inkscape package in Ubuntu: Triaged Status in inkscape source package in Yakkety: Triaged Status in inkscape source package in Zesty: Triaged Bug description: The dropdown menus for start marker, end marker and mid markers do not contains any arrows to select. I have clean up all local settings and run inkscape fresh but the same problem. Inkscape 0.91, Ubuntu 16.10 = From the duplicate reports: - Inkscape 0.91 r13725 on Ubuntu 16.10 - Inkscape 0.91-11 r13725 on Ubuntu 16.10 - DistroRelease: Ubuntu 16.10, Package: inkscape 0.91-11 - Inkscape 0.92, ubuntu 16.04 LTS - Ubuntu 16.04 - upgrade today to 0.92 - Kubuntu 14.04, and recently updated Inkscape to version 0.92.0 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1638373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty
There's a snap package for 0.92 available now in Ubuntu App center, and a deb package in the ppa. Do these solve the problems from this thread for everyone? (i.e. does the snap package have all markers, and does the ppa deb install without a problem on standard Yakkety?) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1638373 Title: End marker/start marker drop-down menus are empty Status in Inkscape: New Status in inkscape package in Ubuntu: Confirmed Bug description: The dropdown menus for start marker, end marker and mid markers do not contains any arrows to select. I have clean up all local settings and run inkscape fresh but the same problem. Inkscape 0.91, Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1638373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty
Could one of you turn this into a separate report? It's unrelated to the main issue here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1638373 Title: End marker/start marker drop-down menus are empty Status in Inkscape: New Status in inkscape package in Ubuntu: Confirmed Bug description: The dropdown menus for start marker, end marker and mid markers do not contains any arrows to select. I have clean up all local settings and run inkscape fresh but the same problem. Inkscape 0.91, Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1638373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639527] Re: inkscape_0.91.0+51~ubuntu16.10.1 from ppa:inkscape.dev/stable is not installable
Could this be the same bug as: https://bugs.launchpad.net/inkscape/+bug/1635855 ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1639527 Title: inkscape_0.91.0+51~ubuntu16.10.1 from ppa:inkscape.dev/stable is not installable Status in Inkscape: New Status in inkscape package in Ubuntu: New Bug description: When trying to install the package I get: The following packages have unmet dependencies: inkscape : Depends: libpoppler58 (>= 0.41.0) but it is not installable E: Unable to correct problems, you have held broken packages. Ubuntu 16.10 has no libpoppler58 in the repository. There is libpoppler61 instead. I've been told that Ubuntu 16.04 has no libpoppler61, so both versions should be allowed: https://bugs.launchpad.net/inkscape/+bug/1638373/comments/12 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1639527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty
@rot13: Ah, that's unfortunate... Can you post this as a new bug report? It's a problem on the Inkscape side of the ppa / build process, and not a downstream packaging problem (and also add this info: for Ubuntu 16.04, libpoppler58 is available, while 61 is not, so hopefully it is not exchanged, but rather both versions should be allowed - else it won't work on the LTS version anymore). You can also just copy the whole share/... folder from the repo, meanwhile (and remove the ppa, use the version from Ubuntu repos). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1638373 Title: End marker/start marker drop-down menus are empty Status in Inkscape: New Status in inkscape package in Ubuntu: Confirmed Bug description: The dropdown menus for start marker, end marker and mid markers do not contains any arrows to select. I have clean up all local settings and run inkscape fresh but the same problem. Inkscape 0.91, Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1638373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty
@Filip and Jakub: It appears that almost all svg files in the /usr/share/inkscape directory have been modified in the package for your version of Ubuntu. So if you're missing a filter, or a symbol set, a pattern or whatever, you can apply the same solution, only copying a different file from the repo into a different directory. Location for the files: http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_91_BRANCH/files/head:/share/ Or you can use the Inkscape version from the ppa: https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1638373 Title: End marker/start marker drop-down menus are empty Status in Inkscape: New Status in inkscape package in Ubuntu: Confirmed Bug description: The dropdown menus for start marker, end marker and mid markers do not contains any arrows to select. I have clean up all local settings and run inkscape fresh but the same problem. Inkscape 0.91, Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1638373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty
Could it be that someone 'cleaned' all svg files in the /usr/share directory? They are all significantly smaller. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1638373 Title: End marker/start marker drop-down menus are empty Status in Inkscape: New Status in inkscape package in Ubuntu: New Bug description: The dropdown menus for start marker, end marker and mid markers do not contains any arrows to select. I have clean up all local settings and run inkscape fresh but the same problem. Inkscape 0.91, Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1638373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty
(referring to the Ubuntu 0.91-11 package) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1638373 Title: End marker/start marker drop-down menus are empty Status in Inkscape: New Status in inkscape package in Ubuntu: New Bug description: The dropdown menus for start marker, end marker and mid markers do not contains any arrows to select. I have clean up all local settings and run inkscape fresh but the same problem. Inkscape 0.91, Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1638373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty
Jakub, is that the complete file? It's basically empty. If so, the solution to your problem is to download the linked file from comment #2, and use it to replace the file you have pasted here. You need to do the replacing as root user. Reinstalling won't help, as it appears that the Ubuntu package is damaged. Can you post the output of $ apt-cache policy inkscape please? This will tell us where the package you are using stems from (I'd assume the official Ubuntu 16.10 repos, but who knows...). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1638373 Title: End marker/start marker drop-down menus are empty Status in Inkscape: New Status in inkscape package in Ubuntu: New Bug description: The dropdown menus for start marker, end marker and mid markers do not contains any arrows to select. I have clean up all local settings and run inkscape fresh but the same problem. Inkscape 0.91, Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1638373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 418242] Re: Incorrect call to output plugins (with persistent error message) on copy
Sonya, I've just taken a look (so you can delete the file if you need to). The reason why it still doesn't work is that the number nodes extension only works on a single path. Your image, however, consists of a group of 331 objects and paths. If you *really* want to number all nodes in the treasure chest, you need to ungroup everything first, then then select everything, convert everything to path by doing 'Path -> Object to path', then combine everything into a single path (Path -> Combine). The numbering you will get then will, however, not be the most logical one for drawing from node to node (if that's what you want as an end result). The path will consist of 3157 nodes, which is a bit complex, and choosing a font size for this may become difficult... The treasure chest image is not an ideal object for draw-by-numbers, I think - better to choose something simpler. You can draw it yourself if you use the Bezier tool and the original chest as a 'template' to copy (manually, by drawing) from. Kind Regards, Maren -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/418242 Title: Incorrect call to output plugins (with persistent error message) on copy Status in Inkscape: Triaged Status in inkscape package in Ubuntu: Triaged Status in inkscape package in Arch Linux: New Status in inkscape package in Debian: Confirmed Status in Gentoo Linux: Unknown Bug description: UPDATE: After further investigation it turned out to be a problem related to the copy operation, in combination with a totally unrelated running Java program (FreeRapid). Reading some followups and other bug reports, it seems to be caused by the new clipboard management system (introduced as a fix for the bug #170185), as reported in bug #421597 So far these applications are known to randomly trigger an input/output extension (on linux): - FreeRapid Downloader - jDownloader - xfce4-clipman-plugin 1.1.3 - Netbeans - xfce4-settings-helper (Xfce 4.8) - Team Viewer (teamviewerd 10.0.36) - The original report was this: I'm getting this error when I try to edit a text object created previously with a font that's not available in this system. It looks like Inkscape has problems to resolve the font substitution and displays the error message in a popup window that keeps appearing again and again, leaving no other remedy than closing inkscape and reopening it. The error message is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/418242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 418242] Re: Incorrect call to output plugins (with persistent error message) on copy
Today, one of my workshop participants had the same problem (tried to copy something, got an error message, on a Linux system). Worse than the error message, however, was that no object was copied, so many things we wanted to practice couldn't work at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/418242 Title: Incorrect call to output plugins (with persistent error message) on copy Status in Inkscape: Triaged Status in inkscape package in Ubuntu: Triaged Status in inkscape package in Arch Linux: New Status in inkscape package in Debian: Confirmed Status in Gentoo Linux: Unknown Bug description: UPDATE: After further investigation it turned out to be a problem related to the copy operation, in combination with a totally unrelated running Java program (FreeRapid). Reading some followups and other bug reports, it seems to be caused by the new clipboard management system (introduced as a fix for the bug #170185), as reported in bug #421597 So far these applications are known to randomly trigger an input/output extension (on linux): - FreeRapid Downloader - jDownloader - xfce4-clipman-plugin 1.1.3 - Netbeans - xfce4-settings-helper (Xfce 4.8) - Team Viewer (teamviewerd 10.0.36) - The original report was this: I'm getting this error when I try to edit a text object created previously with a font that's not available in this system. It looks like Inkscape has problems to resolve the font substitution and displays the error message in a popup window that keeps appearing again and again, leaving no other remedy than closing inkscape and reopening it. The error message is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/418242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 180708] Re: TWEAK / INSET / OUTSET TOOLS: Break paths / dissappearing paths
Inset problem still present in 0.91 and in 0.91 devel version from Nov 10 2015 from Ubuntu ppa (see linked question: https://answers.launchpad.net/inkscape/+question/279051). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/180708 Title: TWEAK / INSET / OUTSET TOOLS: Break paths / dissappearing paths Status in Inkscape: Triaged Status in inkscape package in Ubuntu: Triaged Bug description: Summary: Various tools including but not limited to the "Tweak Tool", "Inset / Outset Tool", and "Pattern Along Path" will break the target paths dramatically. In some cases this results in entire closed areas being deleted. With "Pattern Along Path", strokes are often missing in many areas. Platform: Ubuntu Linux 7.10 amd64. Version: .45+devel January 5, 2008. Frequency: Always (5/5 tries for manifestation.) Reproduction: Create a text object of several characters. Use the tweak tool to distort the object. After a movement, some shapes should disappear. Using the same text, convert to a path and apply as the "Pattern Along Path". Strokes will disappear in various areas. Comments: The manifestation of this bug appears to be related in some way. If not, the "Pattern Along Path" bug can be re-registered as a separate bug if required by the developers. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/180708/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 781397] Re: Help opens web browser (Epiphany, Konqueror), Inkscape stays in modal state .
Getting the same (but longer :) ) error message with Inkscape 0.91pre3 opening firefox for manual/other websites on LM17: (process:2824): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Error: No running window found (process:2828): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed (firefox:2828): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised (firefox:2828): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised (firefox:2828): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised (firefox:2828): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/781397 Title: Help opens web browser (Epiphany, Konqueror), Inkscape stays in modal state . Status in Inkscape: A Vector Drawing Tool: Confirmed Status in inkscape package in Ubuntu: Triaged Status in inkscape package in Debian: Confirmed Bug description: Debian Linux only + Gnome. Inkscape versions tested: 0.46, 0.47, 0.48 When I do select Manual, Keys and mouse reference and etc. form Help menu Inkscape pops-up a modal dialog: Inkscape manual working... please wait and opens web browser with a link to a site containing a manual. However I do find this kind of approach unreasonable ( some people do work off-line you know ) it is not a subject of this bug report. The problem is, that as long as a web browser is opened this modal dialog do not close and CANNOT be closed neither by cancel or close icon. Any attempt to click Cancel leads to Inkscape hanging till browser window is closed. Closing browser window makes Inkscape usable again. This is rather an inconvenience than a bug but less experienced users may do not figure out how to access manual while working with a program. Investigation: In my config (debian+gnome) a default browser is Epiphany. If I do set System-preferences-preferred applications-Internet-web browser to iceweasel or links2 in terminal help works as expected. If I do set it to: Epiphany or Konquerror bug is exposed and Inkscape awaits for browser to be closed. If I do however select: Konqueror in terminal help works as expected but additional terminal pops-up. This suggests, that script showing help assumes that called process will fork and return immediately. They do not. A simple test with a terminal shows, that iceweasel command forks and returns but konqueror and epiphany do not. Links2 neither - it's even worse, since when set as a system browser without a terminal it does not pop-up a window but performs display i/o on stdin/stdout and in effect inkscape hangs. Please detach from a child process when rising a help window by calling an external program. Info: When I do start Inkscape from a console I can see a stream of: (inkscape:3504): Gtk-CRITICAL **: gtk_misc_set_alignment: assertion `GTK_IS_MISC (misc)' failed I hope it is intended. With regards, Tomasz Sztejka To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/781397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
