[Ubuntustudio-bugs] [Bug 1728364] Re: gnome-color-manager wrong calibration due to transparent patches
** Tags added: color-calibration -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to gnome-color-manager in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1728364 Title: gnome-color-manager wrong calibration due to transparent patches Status in gnome-color-manager package in Ubuntu: New Bug description: When performing display color calibration through gnome-color-manager using hardware colorimeter (pantone huey in my case) odd profile results are obtained and sometimes the process fails. The problem is probably due to the test on-screen color patches that are rendered in a full screen window but have a trasparent layer applied to them instead of being opaque as expected (see atteched screenshot). This does not appear to be an argyll problem as the calibration with the same setup can be performed sussessfully installing and using DisplayCAL app that also uses argyll. The bug is also present in the X session. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-color-manager 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 29 10:52:26 2017 InstallationDate: Installed on 2017-10-26 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-color-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/1728364/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1728364] Re: gnome-color-manager wrong calibration due to transparent patches
Bug is still present in Bionic 18.04.1. ** Tags added: bionic ** Tags removed: wayland-session -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to gnome-color-manager in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1728364 Title: gnome-color-manager wrong calibration due to transparent patches Status in gnome-color-manager package in Ubuntu: New Bug description: When performing display color calibration through gnome-color-manager using hardware colorimeter (pantone huey in my case) odd profile results are obtained and sometimes the process fails. The problem is probably due to the test on-screen color patches that are rendered in a full screen window but have a trasparent layer applied to them instead of being opaque as expected (see atteched screenshot). This does not appear to be an argyll problem as the calibration with the same setup can be performed sussessfully installing and using DisplayCAL app that also uses argyll. The bug is also present in the X session. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-color-manager 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 29 10:52:26 2017 InstallationDate: Installed on 2017-10-26 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-color-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/1728364/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 788407] Re: Unable to shrink "Document Settings" window if closed while super stretched out.
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to lyx in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/788407 Title: Unable to shrink "Document Settings" window if closed while super stretched out. Status in lyx package in Ubuntu: Confirmed Bug description: Binary package hint: lyx I opened the document properties/settings dialog. I stretched it extra wide to edit the Latex preamble. I closed it. I opened it. Was suprised that it remembered saved dimensions. Tried to shrink it back. It won't. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: lyx 2.0.0~rc3-1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4 Uname: Linux 2.6.38-9-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Wed May 25 20:23:06 2011 ExecutablePath: /usr/bin/lyx ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: lyx UpgradeStatus: Upgraded to natty on 2011-04-30 (25 days ago) XsessionErrors: (gnome-panel:2302): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x1796980 (gnome-panel:2302): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x1796980 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/788407/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1772414] Re: Justifying Syriac text creates clutter in LibreOffice Writer
Fix available in 6.1. ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Released ** No longer affects: xfonts-scalable-nonfree (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to xfonts-scalable-nonfree in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1772414 Title: Justifying Syriac text creates clutter in LibreOffice Writer Status in libreoffice package in Ubuntu: Fix Released Bug description: Justifying a paragraph in LibreOffice Writer with text written in the Syriac script (Unicode block U+0700-U+074F) creates graphic clutter between every word. See the attached screenshot where the first paragraph is justified and the second is right-aligned. The second paragraph looks as it should, whereas the first paragraph shows a small line added at the end of each word. If you zoom in or out, some of the lines may disappear, but when you create a PDF, they are all there. The same problem occurs with nearly all the Syriac fonts I have tried, including Serto Batnan, Estrangelo Antioch, East Syriac Ctesiphon and Serto Urhoy (all part of the ttf-xfree86-nonfree-syriac package). For the last two, the clutter is not visible on screen but shows up if you create a PDF. With East Syriac Adiabene, the problem doesn't seem to occur. I have attached a screenshot, a PDF and the document used to create them. Description: Ubuntu 17.10 Release: 17.10 libreoffice-writer: Installed: 1:5.4.6-0ubuntu0.17.10.1 Candidate: 1:5.4.6-0ubuntu0.17.10.1 Version table: *** 1:5.4.6-0ubuntu0.17.10.1 500 500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:5.4.5-0ubuntu0.17.10.5 500 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 1:5.4.1-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 21 13:26:09 2018 InstallationDate: Installed on 2017-02-13 (462 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772414/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1769654] Re: Ubuntu 18.04 embedded fonts Liberation have corrupted metrics
Successfully tested fonts-liberation 1:1.07.4-7~18.04.1 and fonts- liberation2 2.00.1-7~18.04.1 against libreoffice 1:6.0.6-0ubuntu0.18.04.1 (in bionic-proposed). ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to fonts-liberation in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1769654 Title: Ubuntu 18.04 embedded fonts Liberation have corrupted metrics Status in fonts-liberation package in Ubuntu: Fix Released Status in fonts-liberation2 package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Confirmed Status in fonts-liberation source package in Bionic: Fix Committed Status in fonts-liberation2 source package in Bionic: Fix Committed Status in libreoffice source package in Bionic: Confirmed Status in fonts-liberation package in Debian: Fix Released Status in fonts-liberation2 package in Debian: Fix Released Bug description: [Impact] fonts-liberation and fonts-liberation2 in bionic have skewed font metrics. This is causing visible formatting issues in any program rendering text using those fonts, most notably libreoffice (recent versions fail to build because some unit tests that check the rendered layout fail). This was fixed in debian and synced in cosmic (https://salsa.debian.org/fonts-team/fonts-liberation/blob/master/debian/patches/unset_OS2_UseTypoMetrics.patch). Backporting to bionic is a prerequisite to backporting a recent version of libreoffice (6.0.6, bug #1785679). [Test Case] See original description (at the bottom of the description) for example text documents and their expected layout when opened in libreoffice. A good test case is whether libreoffice 6.0.6 builds successfully (all unit tests pass - some unit tests exercise text layout and they fail with the broken version of fonts-liberation2). [Regression Potential] Rendering of text across a variety of programs (especially word processors and web browsers) should be checked to ensure that this doesn't introduce regressions. [Other Info] This is backported straight from Debian, no Ubuntu-specific modifications. [Original description] Ubuntu/Xubuntu 18.04 package includes fonts "Liberation Sans" (etc "Liberation") with sligtly shrinked font metrics. This issue leads to all office documents typed in Liberation Sans fonts have corrupted formatting in Ubuntu 18.04 (but these documents correctly opened in other OS's, for example Ubuntu 17.10). Documents with corrupted formatting can not print properly: all paragraphs are shifted up, embedded tables in text - splitted on page breaks. Document circulation in system based on Ubuntu 18.04 operating systems temporarily paralized, because Liberation fonts are basic fonts for open-source document circulation. In attachment I have type a example office document with 2 pages and enumerated strings. On normal ordinary conditions this document have 54 strings on first page and 54 string on second page. But if this document open in Ubuntu 18.04, it's found than 5 strings from second page moves to first page. Compare font versions embedded with Ubuntu packages we can see that versions are different (sudo apr search fonts-liberation* command): Ubuntu 17.10 - 1:1.07.4-2, 2.00.1-3 Ubuntu 18.04 - 1:1.07.4-5, 2.00.1-5 I have create a bug 117411 "Font metrics slightly changed after update OS to Ubuntu 18.04", see https://bugs.documentfoundation.org/show_bug.cgi?id=117411, but I think that this bug concerns a Ubuntu/Xubuntu 18.04 package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-liberation/+bug/1769654/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1793270] Re: After upgrading to cosmic, GIMP python plugins no longer work
** Changed in: gimp-plugin-registry (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to gimp-plugin-registry in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1793270 Title: After upgrading to cosmic, GIMP python plugins no longer work Status in gimp-plugin-registry package in Ubuntu: New Status in gimp-plugin-registry package in Debian: New Bug description: When starting GIMP, messages similar to this are shown in the console: --- GIMP-Error: Unable to run plug-in "plugin-resynth-sharpen.py" (/usr/lib/gimp/2.0/plug-ins/plugin-resynth-sharpen.py) Failed to execute child process “python” (No such file or directory) --- This message is repeated for each python file in /usr/lib/gimp-2.0/plugins, and none of the plugins for which this error shows appear in the GIMP menus. The problem is fixed after installing gimp-python ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gimp-plugin-registry 9.20180625 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: KDE Date: Wed Sep 19 11:19:45 2018 InstallationDate: Installed on 2017-08-17 (397 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725) SourcePackage: gimp-plugin-registry UpgradeStatus: Upgraded to cosmic on 2018-09-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp-plugin-registry/+bug/1793270/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1793270] [NEW] After upgrading to cosmic, GIMP python plugins no longer work
Public bug reported: When starting GIMP, messages similar to this are shown in the console: --- GIMP-Error: Unable to run plug-in "plugin-resynth-sharpen.py" (/usr/lib/gimp/2.0/plug-ins/plugin-resynth-sharpen.py) Failed to execute child process “python” (No such file or directory) --- This message is repeated for each python file in /usr/lib/gimp-2.0/plugins, and none of the plugins for which this error shows appear in the GIMP menus. The problem is fixed after installing gimp-python ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gimp-plugin-registry 9.20180625 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: KDE Date: Wed Sep 19 11:19:45 2018 InstallationDate: Installed on 2017-08-17 (397 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725) SourcePackage: gimp-plugin-registry UpgradeStatus: Upgraded to cosmic on 2018-09-17 (1 days ago) ** Affects: gimp-plugin-registry (Ubuntu) Importance: Undecided Status: New ** Affects: gimp-plugin-registry (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug cosmic third-party-packages ** Bug watch added: Debian Bug tracker #907178 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907178 ** Also affects: gimp-plugin-registry (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907178 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to gimp-plugin-registry in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1793270 Title: After upgrading to cosmic, GIMP python plugins no longer work Status in gimp-plugin-registry package in Ubuntu: New Status in gimp-plugin-registry package in Debian: Unknown Bug description: When starting GIMP, messages similar to this are shown in the console: --- GIMP-Error: Unable to run plug-in "plugin-resynth-sharpen.py" (/usr/lib/gimp/2.0/plug-ins/plugin-resynth-sharpen.py) Failed to execute child process “python” (No such file or directory) --- This message is repeated for each python file in /usr/lib/gimp-2.0/plugins, and none of the plugins for which this error shows appear in the GIMP menus. The problem is fixed after installing gimp-python ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gimp-plugin-registry 9.20180625 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: KDE Date: Wed Sep 19 11:19:45 2018 InstallationDate: Installed on 2017-08-17 (397 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725) SourcePackage: gimp-plugin-registry UpgradeStatus: Upgraded to cosmic on 2018-09-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp-plugin-registry/+bug/1793270/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
