[Ubuntustudio-bugs] [Bug 1732322] Re: package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to shotwell in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1732322 Title: package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in shotwell package in Ubuntu: New Bug description: I tried to update the environment by running the apt-get update command, it keeps giving me some error such as /var/lib/dpkg ... message. I've researched online as to resolving this issue, its all to no avail. I restarted the server and I saw so many crash messages and it suggested that I report the message. Please I need your help on this matter. Thanks Best regards, Kay Ade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: linux-libc-dev: Install linux-libc-dev: Configure python3-jwt: Configure shotwell: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Nov 14 01:30:15 2017 DuplicateSignature: package:shotwell:0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 Setting up linux-libc-dev:amd64 (4.4.0-98.121) ... dpkg: error processing package python3-jwt (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-14 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: shotwell Title: package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1732322/+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 1732322] [NEW] package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befor
Public bug reported: I tried to update the environment by running the apt-get update command, it keeps giving me some error such as /var/lib/dpkg ... message. I've researched online as to resolving this issue, its all to no avail. I restarted the server and I saw so many crash messages and it suggested that I report the message. Please I need your help on this matter. Thanks Best regards, Kay Ade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: linux-libc-dev: Install linux-libc-dev: Configure python3-jwt: Configure shotwell: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Nov 14 01:30:15 2017 DuplicateSignature: package:shotwell:0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 Setting up linux-libc-dev:amd64 (4.4.0-98.121) ... dpkg: error processing package python3-jwt (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-14 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: shotwell Title: package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to shotwell in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1732322 Title: package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in shotwell package in Ubuntu: New Bug description: I tried to update the environment by running the apt-get update command, it keeps giving me some error such as /var/lib/dpkg ... message. I've researched online as to resolving this issue, its all to no avail. I restarted the server and I saw so many crash messages and it suggested that I report the message. Please I need your help on this matter. Thanks Best regards, Kay Ade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: linux-libc-dev: Install linux-libc-dev: Configure python3-jwt: Configure shotwell: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Nov 14 01:30:15 2017 DuplicateSignature: package:shotwell:0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 Setting up linux-libc-dev:amd64 (4.4.0-98.121) ... dpkg: error processing package python3-jwt (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-14 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: shotwell Title: package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1732322/+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
I tested Fedora 27 live session (Gnome 3.26) today and the bug is not present. It seems Ubuntu specific. -- 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 1731044] Re: Musescore 2.0.3 problem in UM 16.04 LTS
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to musescore in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1731044 Title: Musescore 2.0.3 problem in UM 16.04 LTS Status in ubuntu-mate: Invalid Status in musescore package in Ubuntu: New Bug description: As per title. This problem exists irrespective of whether installed from the software boutique or from a terminal First issue: Musescore locks up on launch when trying to select initial type of score. It does this the majority of the time. Sometimes it eventually unlocks and allows one to continue. Sometimes it crashes completely and closes Second issue: Assuming one has got past the initial lock up and has got Musescore fully open, many of the menu items are fantastically tiny such that they are impossible to visually identify or use. This seems to be a problem limited to the version that UM 16.04 is using: I have just installed Lubuntu 16.04 in a VM and installed Musescore from a terminal. It turns out the version it is using is 2.0.2. So, one iteration below the one used by UM. I can confirm none of these problems are present in the Lubuntu version of Musescore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1731044/+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
