libunity testing

[Gerald B. Cox]

Rex,

Thanks for putting libunity out on copr for F23 testing... but unless I am
mistaken, to really test out the functionality I also need plasma-workspace
5.6 - and looks like that is only available for F24+.

Do you have a timeframe when plama-workspace 5.6 will be out in the testing
repo for F23?  Not trying to rush you... I'm sure you have other things
with a higher priority.... just asking.

For those of you who don't know what this is all about:
http://blog.broulik.de/2016/01/on-being-more-convenient/

[Colin J Thomson]

On Friday 15 Apr 2016 13:41:52 Gerald B. Cox wrote:
>  Rex,
>  
>  Thanks for putting libunity out on copr for F23 testing... but unless I am
>  mistaken, to really test out the functionality I also need plasma-workspace
>  5.6 - and looks like that is only available for F24+. 
Plasma 5.6.x is in the kde-unstable repo for F23 Gerald and running very well 
indeed on this box.

Thanks for the heads-up on libunity

Colin
-- 
Fedora 23 (Twenty Three)
Registered Linux user number #342953

[Rex Dieter]

Colin J Thomson wrote:

>  On Friday 15 Apr 2016 13:41:52 Gerald B. Cox wrote:
> > Rex,
> > 
> > Thanks for putting libunity out on copr for F23 testing... but unless I
> > am mistaken, to really test out the functionality I also need
> > plasma-workspace 5.6 - and looks like that is only available for F24+.
>  
>  Plasma 5.6.x is in the kde-unstable repo for F23 Gerald and running very
>  well indeed on this box.
>  
>  Thanks for the heads-up on libunity 
link for everyone else:
https://copr.fedorainfracloud.org/coprs/rdieter/libunity/

hoping that it's existence can facilitate it's review and get it into fedora 
sooner'ish:
https://bugzilla.redhat.com/show_bug.cgi?id=libunity

As far as plasma-5.6.x for f23 goes, now that we finally have both qt-5.6.x 
and kf5-5.21.0 in stable updates, progress (and bodhi updates) will come 
soon.

-- Rex

[Colin J Thomson]

On Friday 15 Apr 2016 17:10:41 Rex Dieter wrote:
>  Colin J Thomson wrote: 
>  > Thanks for the heads-up on libunity
>  
>  link for everyone else:
>  https://copr.fedorainfracloud.org/coprs/rdieter/libunity/
>  
>  hoping that it's existence can facilitate it's review and get it into fedora
>  sooner'ish:
>  https://bugzilla.redhat.com/show_bug.cgi?id=libunity 
I can report that libunity works well with Chrome on this F23 box, I'll try 
and find more to test later.

Colin
-- 
Fedora 23 (Twenty Three)
Registered Linux user number #342953

[Gerald B. Cox]

On Sat, Apr 16, 2016 at 1:53 AM, Colin J Thomson <colin.thomson(a)g6avk.co.uk&gt;
wrote:

>  I can report that libunity works well with Chrome on this F23 box, I'll try
>  and find more to test later. 

Yes, please let me know.  As soon as the repo becomes available, I'll try
again.

[Gerald B. Cox]

On Sat, Apr 16, 2016 at 9:13 AM, Gerald B. Cox <gbcox(a)bzb.us&gt; wrote:

>  Yes, please let me know.  As soon as the repo becomes available,
> I'll try
>  again. 

ok, something happened with the whole xdg-settings, mime, with 5.6.  If I
use 5.5 Chrome works fine, if I try 5.6, it doesn't recognize the default.

Under 5.6:
$ xdg-settings get default-web-browser
chrome-app-list.desktop

So, I need to change this to google-chrome-unstable.desktop
I then enter:

$ xdg-settings set default-web-browser google-chrome-unstable.desktop
xdg-mime: application argument missing
Try 'xdg-mime --help' for more information.

If you check the doc for xdg-settings, the syntax above is correct (and
works with 5.5).  In fact,
the documentation even gives an example using Chrome.  Now it doesn't work.

Am I missing something... ???

[Gerald B. Cox]

On Sat, Apr 16, 2016 at 9:49 AM, Gerald B. Cox <gbcox(a)bzb.us&gt; wrote:

>  ok, something happened with the whole xdg-settings, mime, with 5.6.  If I
>  use 5.5 Chrome works fine, if I try 5.6, it doesn't recognize the default.
>
>  Under 5.6:
>  $ xdg-settings get default-web-browser
>  chrome-app-list.desktop
>
>  So, I need to change this to google-chrome-unstable.desktop
>  I then enter:
>
>  $ xdg-settings set default-web-browser google-chrome-unstable.desktop
>  xdg-mime: application argument missing
>  Try 'xdg-mime --help' for more information.
>
>  If you check the doc for xdg-settings, the syntax above is correct (and
>  works with 5.5).  In fact,
>  the documentation even gives an example using Chrome.  Now it doesn't work.
>
>  Am I missing something... ???
>  
Just switched back to 5.5 and noticed that chrome-app-list.desktop also is
working fine under 5.5, and verified that the xdg-settings command works
under 5.5; which tells me something is going on with 5.6 in this regard.

[Gerald B. Cox]

On Sat, Apr 16, 2016 at 9:58 AM, Gerald B. Cox <gbcox(a)bzb.us&gt; wrote:

>  Just switched back to 5.5 and noticed that chrome-app-list.desktop also is
>  working fine under 5.5, and verified that the xdg-settings command works
>  under 5.5; which tells me something is going on with 5.6 in this regard. 

Also just noticed that Chrome provides it's own copy of xdg-settings; which
of course is different from what is provided by Fedora... so as soon as the
repo comes back online (getting
the: Failed to synchronize cache for repo 'kde-unstable', disabling.
message again)
I will do some more testing.

[Colin J Thomson]

On Saturday 16 Apr 2016 09:49:31 Gerald B. Cox wrote:
 
>  ok, something happened with the whole xdg-settings, mime, with 5.6. 
> If I
>  use 5.5 Chrome works fine, if I try 5.6, it doesn't recognize the default.
>  
>  Under 5.6:
>  $ xdg-settings get default-web-browser
>  chrome-app-list.desktop 
I get:

xdg-settings get default-web-browser
chromium-browser.desktop

>  So, I need to change this to google-chrome-unstable.desktop
>  I then enter:
>  
>  $ xdg-settings set default-web-browser google-chrome-unstable.desktop
>  xdg-mime: application argument missing
>  Try 'xdg-mime --help' for more information. 
Just FYI I can confirm the same behaviour/error on this box when trying to 
set/change to another browser. As far as I can tell the syntax is right.

xdg-settings set default-web-browser qupzilla.desktop
xdg-mime: application argument missing
Try 'xdg-mime --help' for more information.

Colin
-- 
Fedora 23 (Twenty Three)
Registered Linux user number #342953

[Gerald B. Cox]

On Sat, Apr 16, 2016 at 12:45 PM, Colin J Thomson <colin.thomson(a)g6avk.co.uk
>  wrote: 
>  Just FYI I can confirm the same behaviour/error on this box when
> trying to
>  set/change to another browser. As far as I can tell the syntax is right.
>
>  xdg-settings set default-web-browser qupzilla.desktop
>  
Colin, can you check to see if Chromium installed another version of
xdg-settings on your machine?  Chrome installs a version - not sure if it's
older, newer or
modified in some way.   Also, not sure if it makes a difference one way or
another.  I wanted to test, but still waiting for the kde-unstable repo to
become
available again.

[Gerald B. Cox]

On Sat, Apr 16, 2016 at 12:50 PM, Gerald B. Cox <gbcox(a)bzb.us&gt; wrote:

>  Colin, can you check to see if Chromium installed another version of
>  xdg-settings on your machine?  Chrome installs a version - not sure if it's
>  older, newer or
>  modified in some way.   Also, not sure if it makes a difference one way or
>  another.  I wanted to test, but still waiting for the kde-unstable repo to
>  become
>  available again.
>  
xdg-mime also...

[Colin J Thomson]

On Saturday 16 Apr 2016 12:50:58 Gerald B. Cox wrote:
 
>  Colin, can you check to see if Chromium installed another version of
>  xdg-settings on your machine?  Chrome installs a version - not sure if it's
>  older, newer or modified in some way.    
As mentioned I use Russian Fedora's Chromium not that it should matter at all, 
but I don't have the package xdg-settings or xdg-mime installed.

>  Also, not sure if it makes a difference one way or
>  another.  I wanted to test, but still waiting for the kde-unstable repo to
>  become available again. 
Hmm, the repo's seem to be working OK here.

Colin
-- 
Fedora 23 (Twenty Three)
Registered Linux user number #342953

[Gerald B. Cox]

On Sat, Apr 16, 2016 at 1:24 PM, Colin J Thomson <colin.thomson(a)g6avk.co.uk&gt;
wrote:

>  As mentioned I use Russian Fedora's Chromium not that it should matter at
>  all,
>  but I don't have the package xdg-settings or xdg-mime installed.
>
>  > Also, not sure if it makes a difference one way or
>  > another.  I wanted to test, but still waiting for the kde-unstable repo
>  to
>  > become available again.
>
>  Hmm, the repo's seem to be working OK here. 

Yes, working here again also... from what I gather there is some kind of
dnf bug which causes intermittent failures.  On try three I was able to
test both the xdg-* stuff from chrome and from Fedora... both had the same
error.  I think backed out again... dnf history undo last - and chrome
default was back... then I once again got the repo error.... I tried again
and the repo was working... and now chrome is the default browser under 5.6
- not exactly sure what is going on - but the xdg-mime; xdg-settings stuff
is extremely flaky... it was under LXQt, and apparently under Plasma 5.6.
Not an expert on it by any means, perhaps someone who knows more about it
can comment.

[Colin J Thomson]

On Saturday 16 Apr 2016 14:00:49 Gerald B. Cox wrote:

>  > Hmm, the repo's seem to be working OK here.
>  
>  Yes, working here again also... from what I gather there is some kind of
>  dnf bug which causes intermittent failures.  On try three I was able to
>  test both the xdg-* stuff from chrome and from Fedora... both had the same
>  error.  I think backed out again... dnf history undo last - and chrome
>  default was back... then I once again got the repo error.... I tried again
>  and the repo was working... and now chrome is the default browser under 5.6
>  - not exactly sure what is going on - but the xdg-mime; xdg-settings stuff
>  is extremely flaky... it was under LXQt, and apparently under Plasma 5.6.
>  Not an expert on it by any means, perhaps someone who knows more about it
>  can comment. 
I am no expert either on xdg, just trying to provide some usefull feedback. 
Lets hope Rex or someone can chip in and help you.

Goodluck

Colin
-- 
Fedora 23 (Twenty Three)
Registered Linux user number #342953

[Gerald B. Cox]

On Sat, Apr 16, 2016 at 2:15 PM, Colin J Thomson <colin.thomson(a)g6avk.co.uk&gt;
wrote:

>  I am no expert either on xdg, just trying to provide some usefull feedback.
>  Lets hope Rex or someone can chip in and help you. 

Yes, and thanks!  Appreciate your feedback and assistance... Rex just put
some new builds out... will test those.

[Colin J Thomson]

On Saturday 16 Apr 2016 14:17:05 Gerald B. Cox wrote:
>  On Sat, Apr 16, 2016 at 2:15 PM, Colin J Thomson
> <colin.thomson(a)g6avk.co.uk&gt;
>  wrote:
>  > I am no expert either on xdg, just trying to provide some usefull
>  > feedback.
>  > Lets hope Rex or someone can chip in and help you.
>  
>  Yes, and thanks!  Appreciate your feedback and assistance... Rex just put
>  some new builds out... will test those. 
Oh that's great, I will watch with interest..

Colin
-- 
Fedora 23 (Twenty Three)
Registered Linux user number #342953

[Gerald B. Cox]

 xdg-settings get default-web-browser
On Fri, Apr 15, 2016 at 2:49 PM, Colin J Thomson <colin.thomson(a)g6avk.co.uk&gt;
wrote:

>  Plasma 5.6.x is in the kde-unstable repo for F23 Gerald and running
> very
>  well
>  indeed on this box.
>
>  Thanks for the heads-up on libunity
>  
I went ahead and upgraded from the kde-unstable repo.  The only issue I've
encountered is setting Chrome as the default browser.  I've had this issue
on and off before with both Plasma and LXQt.  Not a showstopper by any
means (at least not for me) - but it's just annoying.  I've checked
$XDG_DATA_HOME/applications/mimeapps.list and xdg-settings get
default-web-browser
and both appear to correctly point to
google-chrome-unstable.desktop - but of course every time I start chrome,
it always says it is not the default now.  Something apparently happened
during the upgrade to 5.6 which triggered it.  I did wipe out the Chrome
settings and started again from scratch, but that didn't help. I then did a
dnf history undo last to go back to 5.5 and everything is working fine
again.... the chrome default is working.

I then thought I'd test it out again and now receiving:
Failed to synchronize cache for repo 'kde-unstable', disabling.

So can't go back, at least for now.

Has anyone else noticed this that was testing 5.6 from unstable or have an
idea of what might be happening?

Thanks!

[Colin J Thomson]

On Friday 15 Apr 2016 21:01:57 Gerald B. Cox wrote:

>  I went ahead and upgraded from the kde-unstable repo.  The only issue
> I've
>  encountered is setting Chrome as the default browser.  I've had this issue
>  on and off before with both Plasma and LXQt.   
I use Russian Fedora's Chrome but I had seen this before and assumed it was a 
general chrome issue.

>  Not a showstopper by any
>  means (at least not for me) - but it's just annoying.  I've checked
>  $XDG_DATA_HOME/applications/mimeapps.list and xdg-settings get
>  default-web-browser and both appear to correctly point to
>  google-chrome-unstable.desktop - but of course every time I start chrome,
>  it always says it is not the default now.   
I seem to remember in that "nag" screen there was an option never to show that 
message again which I chose to do. 

Colin
-- 
Fedora 23 (Twenty Three)
Registered Linux user number #342953

[Rex Dieter]

Gerald B. Cox wrote:

>  Has anyone else noticed this that was testing 5.6 from unstable or
> have an
>  idea of what might be happening? 
Please test the following 2 related updates:
kde-cli-tools-5.6.2-2
xdg-utils-1.1.1-3

-- Rex

[Gerald B. Cox]

On Sat, Apr 16, 2016 at 2:06 PM, Rex Dieter <rdieter(a)math.unl.edu&gt; wrote:

>  Please test the following 2 related updates:
>  kde-cli-tools-5.6.2-2
>  xdg-utils-1.1.1-3 

Rex, thanks!
The error using xdg-settings is resolved.  I tested with both the copy
provided by chrome and that provided by xdg-utils and both are now working;
so
guessing whatever changed in kde-cli-tools fixed it.  In fact, I believe on
my forth try I had picked up kde-cli-tools-5.6.2-2 so that was why my
chrome defaults
started working on the forth try.