[ubuntu-studio-devel] Numix Blue theme error

[daniel]

Hi All,

I am using ubuntu studio 18.04 2018-04-10 iso and tested my usual apps 
like openshot and pitivi


#1. When I launched openshot and pivit apps from terminal, i could see 
below theme error. But changing to Numix or greybird works without any error


openshot error

(python3:24626): Gtk-*WARNING*  **:11:02:47.725: Theme parsing error: 
gtk.css:597:14: not a number

(python3:24626): Gtk-*WARNING*  **:11:02:47.726: Theme parsing error: 
gtk.css:597:14: Expected a string.

(python3:24626): Gtk-*WARNING*  **:11:02:47.726: Theme parsing error: 
gtk.css:600:17: Expected a string.

Pitivi Error

(pitivi:24320): Gtk-*WARNING*  **:10:57:32.643: Theme parsing error: 
gtk.css:67:29: The style property GtkStatusbar:shadow-type is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(pitivi:24320): Gtk-*WARNING*  **:10:57:32.647: Theme parsing error: 
gtk.css:597:14: not a number

(pitivi:24320): Gtk-*WARNING*  **:10:57:32.647: Theme parsing error: 
gtk.css:597:14: Expected a string.

#2. Openshot help tutorial next and hide tutorial buttons are not working.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Numix Blue theme error

[daniel]

Hi All,

I am using ubuntu studio 18.04 2018-04-10 iso. Package selection at 
installer times works fine to me.


Also I have tested my usual apps like openshot, pitivi & kdenlive and 
below are my findings


#1. When I launched openshot and pitivi apps from terminal, i could see 
below theme error. But changing to Numix or greybird works without any error


openshot error

(python3:24626): Gtk-*WARNING*  **:11:02:47.725: Theme parsing error: 
gtk.css:597:14: not a number

(python3:24626): Gtk-*WARNING*  **:11:02:47.726: Theme parsing error: 
gtk.css:597:14: Expected a string.

(python3:24626): Gtk-*WARNING*  **:11:02:47.726: Theme parsing error: 
gtk.css:600:17: Expected a string.

pitivi error
- GSound not found on the system
-> enables sound notifications when rendering is complete

(pitivi:24320): Gtk-*WARNING*  **:10:57:32.643: Theme parsing error: 
gtk.css:67:29: The style property GtkStatusbar:shadow-type is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(pitivi:24320): Gtk-*WARNING*  **:10:57:32.647: Theme parsing error: 
gtk.css:597:14: not a number

(pitivi:24320): Gtk-*WARNING*  **:10:57:32.647: Theme parsing error: 
gtk.css:597:14: Expected a string.

(pitivi:24320): Gtk-*WARNING*  **:10:57:32.647: Theme parsing error: 
gtk.css:600:17: Expected a string.

#2. Unable to close the help tutorial window in openshot. Tried many ways but 
no luck.

Despite these error messages, I have successfully edited and exported videos in 
both Openshot and Pitivi

please let me know in case you guys need more details.

Thanks,
Daniel

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Numix Blue theme error

[daniel]

Hi All,

I am using ubuntu studio 18.04 2018-04-10 iso. Package selection at 
installer times works fine to me.


Also I have tested my usual apps like openshot, pitivi & kdenlive and 
below are my findings


#1. When I launched openshot and pitivi apps from terminal, i could see 
below theme error. But changing to Numix or greybird works without any error


openshot error

(python3:24626): Gtk-*WARNING*  **:11:02:47.725: Theme parsing error: 
gtk.css:597:14: not a number

(python3:24626): Gtk-*WARNING*  **:11:02:47.726: Theme parsing error: 
gtk.css:597:14: Expected a string.

(python3:24626): Gtk-*WARNING*  **:11:02:47.726: Theme parsing error: 
gtk.css:600:17: Expected a string.

pitivi error
- GSound not found on the system
-> enables sound notifications when rendering is complete

(pitivi:24320): Gtk-*WARNING*  **:10:57:32.643: Theme parsing error: 
gtk.css:67:29: The style property GtkStatusbar:shadow-type is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(pitivi:24320): Gtk-*WARNING*  **:10:57:32.647: Theme parsing error: 
gtk.css:597:14: not a number

(pitivi:24320): Gtk-*WARNING*  **:10:57:32.647: Theme parsing error: 
gtk.css:597:14: Expected a string.

(pitivi:24320): Gtk-*WARNING*  **:10:57:32.647: Theme parsing error: 
gtk.css:600:17: Expected a string.

#2. Unable to close the help tutorial window in openshot. Tried many ways but 
no luck.

Despite these error messages, I have successfully edited and exported videos in 
both Openshot and Pitivi

please let me know in case you guys need more details.

Thanks,
Daniel

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Numix Blue Theme

[Set Hallstrom]

tisdagen den 4:e oktober 2016 kl. 19:29:35 CEST, Ross Gammon 
 skrev:

Done - Laney has sponsored it for us \o/



\o/ <3



On 03/10/16 15:19, Set Hallstrom wrote:

Thanks Ross:)  I guess Krytarik and I didn't expect the reverts to be
necessary


Well, I just thought that it was a smaller diff file, and easier for a 
sponsor to review. We could have tried for the full transition, but 
there was a risk that they would suggest deferring it until the next 
release cycle.




That makes a lot of sense! Put like that it's a great move :) On the 
fringes of social-engineering lol! I was thinking /inside/ the box in terms 
of double-work.



I'm told:
>>without it (Provides) and the ability to drop 
-lightdm-theme off the seed/meta

>>simultaneously, 1.) the image build would start failing, and 2.) the
>>meta would become uninstallable (-desktop, -core).


Good point. I didn't think to check the impact on the metapackages. I 
will add a task to the bug to remember to take care of that. Hopefully 
we can cover that problem by uploading new metapackages first, but if 
the builds fail for a while early in the release cycle it shouldn't 
matter too much. This happens regularly anyway, when Debian do 
transitions that don't take care of our seeds :-)




Awesome! Next cycle, 17.04 is Ubuntu Studio 10 year anniversary so lets 
make it tidy ! :)



Yours,


--
Set Hallström
Sent from my Ubuntu pocket computer

--
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Numix Blue Theme

[Ross Gammon]

Done - Laney has sponsored it for us \o/


On 03/10/16 15:19, Set Hallstrom wrote:

Thanks Ross:)  I guess Krytarik and I didn't expect the reverts to be
necessary


Well, I just thought that it was a smaller diff file, and easier for a 
sponsor to review. We could have tried for the full transition, but 
there was a risk that they would suggest deferring it until the next 
release cycle.



I'm told:

>>without it (Provides) and the ability to drop -lightdm-theme off the seed/meta
>>simultaneously, 1.) the image build would start failing, and 2.) the
>>meta would become uninstallable (-desktop, -core).


Good point. I didn't think to check the impact on the metapackages. I 
will add a task to the bug to remember to take care of that. Hopefully 
we can cover that problem by uploading new metapackages first, but if 
the builds fail for a while early in the release cycle it shouldn't 
matter too much. This happens regularly anyway, when Debian do 
transitions that don't take care of our seeds :-)
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Numix Blue Theme

[Set Hallstrom]

On 2016-10-02 14:49, Ross Gammon wrote:
> So, I have reverted the merge of default-settings & lightdm-theme, 
> uploaded debdiffs to the FFE bug, and tested the theme works using or
> devel testing ppa.
> 

Thanks Ross :) I guess Krytarik and I didn't expect the reverts to be
necessary, but i take responsibility for failing to better synchronize
the team efforts and I add an entry to my
"why-i-need-to-learn-more-about-packaging"-list :) Anyways, now
everything the -release team asks for is there and i thank you for your
time and effort. Hopefully, despite being deprived of an up-loader in
the team, now that we know where we stand in that regard we will be able
to better anticipate this kind of situation.

> Hopefully the Release Team look at it soon. It may pay to ping them 
> on IRC in the next day or so.

I will poke them this afternoon and also try my luck in #u-devel

> Later I will submit bugs so that we remember to pull Krytarik's 
> package merge back in for the next release.

Yes, thank you! This reminds me that i need to inform you of the
following piece of knowledge I've been given:

You wrote in OP:

>>> 2. We have updated debian/control to also provide the
>>> us-lightdm-theme package. I don't think creating a virtual
>>> package is appropriate here. It is probably sufficient to just
>>> have breaks/replaces so that us-lightdm-theme is removed on
>>> upgrade.

I'm told:
>> without it (Provides) and the ability to drop -lightdm-theme off the 
>> seed/meta
>> simultaneously, 1.) the image build would start failing, and 2.) the
>> meta would become uninstallable (-desktop, -core).

I haven't been notified about the bug yet, so I'm assuming its underway,
but it might be good to put it there so we remember.

Thank you very much Ross,

-- 
Set Hallstrom aka sakrecoer



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Numix Blue Theme

[Ross Gammon]

So, I have reverted the merge of default-settings & lightdm-theme, 
uploaded debdiffs to the FFE bug, and tested the theme works using or 
devel testing ppa.


Hopefully the Release Team look at it soon. It may pay to ping them on 
IRC in the next day or so.


Later I will submit bugs so that we remember to pull Krytarik's package 
merge back in for the next release.


Cheers,

Ross


On 01/10/16 18:00, Ross Gammon wrote:


On 01/10/16 17:16, Set Hallstrom wrote:

I hope Krytarik wants to step in here because i know neither what are
the pros nor what are the cons of "virtual package" and 
"breaks/replaces" :/


A virtual package is normally used when two packages provide similar 
functionality, and the user can chose which package to install, and it 
will "provide" the virtual package that other packages will depend 
upon. It is also used in other complicated transitional arrangements. 
But this is a simple case of moving files from one package to another, 
for which a breaks/replaces is normally sufficient. See:

https://www.debian.org/doc/manuals/maint-guide/dreq.en.html#control
https://www.debian.org/doc/debian-policy/ch-relationships.html


xubuntu-icon-theme was a depend of -lightdm-theme, hence they were moved
over with it.


Perfect, that was what I was missing. A changelog entry (or a separate 
bzr commit & message) would have helped :-)



I truly hope i'm not making things more complicated with my interaction
and that we will be able to find a good solution in time.


No problems. I think a simpler diff (only the default settings 
changes) will be easier to review and generate less questions/delay 
from the sponsor. And it will get us the new theme. It is pretty 
simple to replay the commits back in later.


Cheers,

Ross




--
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Numix Blue Theme

[Ross Gammon]

On 01/10/16 17:16, Set Hallstrom wrote:

I hope Krytarik wants to step in here because i know neither what are
the pros nor what are the cons of "virtual package" and "breaks/replaces" :/


A virtual package is normally used when two packages provide similar 
functionality, and the user can chose which package to install, and it 
will "provide" the virtual package that other packages will depend upon. 
It is also used in other complicated transitional arrangements. But this 
is a simple case of moving files from one package to another, for which 
a breaks/replaces is normally sufficient. See:

https://www.debian.org/doc/manuals/maint-guide/dreq.en.html#control
https://www.debian.org/doc/debian-policy/ch-relationships.html


xubuntu-icon-theme was a depend of -lightdm-theme, hence they were moved
over with it.


Perfect, that was what I was missing. A changelog entry (or a separate 
bzr commit & message) would have helped :-)



I truly hope i'm not making things more complicated with my interaction
and that we will be able to find a good solution in time.


No problems. I think a simpler diff (only the default settings changes) 
will be easier to review and generate less questions/delay from the 
sponsor. And it will get us the new theme. It is pretty simple to replay 
the commits back in later.


Cheers,

Ross

--
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Numix Blue Theme

[Set Hallstrom]

Hi Ross,
Thank you for taking a look at this. Most of your questions and the
details are unfortunately beyond reach of my skills, but I'll do my best
to address the little i know about it bellow:

On 2016-10-01 14:01, Ross Gammon wrote:
> Hi All,
> 
> I sat down this morning to review where we are with implementing the new
> theme. It was a little tricky to follow what was done where, and why. It
> would be more helpful to reviewers and potential sponsors if we
> submitted a bug on launchpad, then carried out discussions there, and
> created a task for the required actions on each package so we can track
> when they are all complete. For example, we have the theme uploaded in
> ubuntustudio-look, but we haven't changed the default settings in
> ubuntustudio-default-setttings yet.
> 
> So where are we we with each package?
> 
> ubuntustudio-look:
> 
> Kaj uploaded Version 0.54 to yakkety, and this appears to now depend on
> numix-gtk-theme, and numix-blue-gtk-theme. Numix-blue-gtk-theme is a new
> binary package (of ubuntustudio-look) and contains the bundled source of
> the upstream tarball. It would have been better to create a separate
> source package for this, but I suppose doing it this way avoided the
> need to get sponsorship outside of the team. And a note for Set for next
> time - the commit bundling numix-blue included a lot of other changes
> that probably should have been committed separately to bzr. But no harm
> done. We should probably:
> 
> 1. Submit bug to remind ourselves to see of we can drop some theme
> packages now to save space (or has this already been done?).

I don't know. But i guess if there are unnecessary packages that haven't
been drop, it would be a good idea to do it.

> 
> 2. Submit a bug to remind ourselves to explain the inclusion of the
> numix-blue source in a debian/README.source file at the next upload.

There were three options identified:
1.) Package NumixBlue properly in Debian, 2.) Package it separately in
Ubuntu, and 3.) Add it temporarily to -look until we can do the first.
We chose the only sensible option there in terms of timing.

> 
> ubuntustudio-default-settings:
> 
> This has not been uploaded yet (currently version 0.62 in Yakkety), but
> Krytarik has prepared the required changes to make numix blue the
> default, which without a full check look fine. Unfortunately, there is
> also a commit to move the lightdm configuration to
> ubuntu-default-settings from the separate source package
> (ubuntustudio-lightdm-theme). This is probably the right thing to do,
> because the us-lightdm-theme package is practically empty now (except
> for this one configuration file). But the timing is unfortunate (so
> close to release), and the changelog entry could have been a bit more
> verbose, explaining that we are moving the config file from one source
> package to another (in preparation for dropping the lightdm package one
> day).
> 
> 1. We should also have a launchpad bug for this change, so we can track
> the eventual removal of the lightdm package (and mention it in the
> changelog).

Good point. I would love to file it so i can unload work-burden for you,
but the level of my confusion in this issue is.. palpable to say the least.

> 
> 2. We have updated debian/control to also provide the us-lightdm-theme
> package. I don't think creating a virtual package is appropriate here.
> It is probably sufficient to just have breaks/replaces so that
> us-lightdm-theme is removed on upgrade.

I hope Krytarik wants to step in here because i know neither what are
the pros nor what are the cons of "virtual package" and "breaks/replaces" :/

> 
> 3. We also seem to have added a dependency on xubuntu-icon-theme, which
> is not explained in the changelog. Do we know why this is required?

xubuntu-icon-theme was a depend of -lightdm-theme, hence they were moved
over with it.

> 
> ubuntustudio-lightdm-theme (currently version 0.9 9n yakkety & xenial):
> 
> As I said above, us-lightdm is practically empty, except for this one
> config file that we should move to default-settings. However, I notice
> at the last upload we changed to a tidier way of using a maintainer
> script to remove the old config file (which was renamed at this
> version). I am not 100% sure, but by setting the lastversion that the
> config file existed to 0.9, the config file may not be removed in an
> upgrade to Xenial. It probably should have said 0.8. This maintainer
> script should probably also be moved to the default-settings package in
> the merge above, so that us-lightdm-theme can be removed eventually.
> This theory needs some testing.

This is very hard for me to assimilate, but what i know is that
ubuntustudio-lightdm-theme 0.9 was already released in Xenial

> 
> Summary:
> 
> Krytarik has done a good job here (as things certainly were a little
> messy before), but at this stage I think we should revert the commit
> that moves the config to default-settings, and just upload the changes
> to make 

[ubuntu-studio-devel] Numix Blue Theme

[Ross Gammon]

Hi All,

I sat down this morning to review where we are with implementing the new
theme. It was a little tricky to follow what was done where, and why. It
would be more helpful to reviewers and potential sponsors if we
submitted a bug on launchpad, then carried out discussions there, and
created a task for the required actions on each package so we can track
when they are all complete. For example, we have the theme uploaded in
ubuntustudio-look, but we haven't changed the default settings in
ubuntustudio-default-setttings yet.

So where are we we with each package?

ubuntustudio-look:

Kaj uploaded Version 0.54 to yakkety, and this appears to now depend on
numix-gtk-theme, and numix-blue-gtk-theme. Numix-blue-gtk-theme is a new
binary package (of ubuntustudio-look) and contains the bundled source of
the upstream tarball. It would have been better to create a separate
source package for this, but I suppose doing it this way avoided the
need to get sponsorship outside of the team. And a note for Set for next
time - the commit bundling numix-blue included a lot of other changes
that probably should have been committed separately to bzr. But no harm
done. We should probably:

1. Submit bug to remind ourselves to see of we can drop some theme
packages now to save space (or has this already been done?).

2. Submit a bug to remind ourselves to explain the inclusion of the
numix-blue source in a debian/README.source file at the next upload.

ubuntustudio-default-settings:

This has not been uploaded yet (currently version 0.62 in Yakkety), but
Krytarik has prepared the required changes to make numix blue the
default, which without a full check look fine. Unfortunately, there is
also a commit to move the lightdm configuration to
ubuntu-default-settings from the separate source package
(ubuntustudio-lightdm-theme). This is probably the right thing to do,
because the us-lightdm-theme package is practically empty now (except
for this one configuration file). But the timing is unfortunate (so
close to release), and the changelog entry could have been a bit more
verbose, explaining that we are moving the config file from one source
package to another (in preparation for dropping the lightdm package one
day).

1. We should also have a launchpad bug for this change, so we can track
the eventual removal of the lightdm package (and mention it in the
changelog).

2. We have updated debian/control to also provide the us-lightdm-theme
package. I don't think creating a virtual package is appropriate here.
It is probably sufficient to just have breaks/replaces so that
us-lightdm-theme is removed on upgrade.

3. We also seem to have added a dependency on xubuntu-icon-theme, which
is not explained in the changelog. Do we know why this is required?

ubuntustudio-lightdm-theme (currently version 0.9 9n yakkety & xenial):

As I said above, us-lightdm is practically empty, except for this one
config file that we should move to default-settings. However, I notice
at the last upload we changed to a tidier way of using a maintainer
script to remove the old config file (which was renamed at this
version). I am not 100% sure, but by setting the lastversion that the
config file existed to 0.9, the config file may not be removed in an
upgrade to Xenial. It probably should have said 0.8. This maintainer
script should probably also be moved to the default-settings package in
the merge above, so that us-lightdm-theme can be removed eventually.
This theory needs some testing.

Summary:

Krytarik has done a good job here (as things certainly were a little
messy before), but at this stage I think we should revert the commit
that moves the config to default-settings, and just upload the changes
to make numix blue the default. Then we should implement the config move
early in the next release cycle to get maximum upgrade testing from
previous releases.

If there are no mistakes/comments in this analysis (and I could do with
an answer on the xubuntu-icon-theme question above), I will probably
start on this later today/tomorrow.

Regards,

Ross


-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel