[wip] Xfce 4.14pre1

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

[wip] Xfce 4.14pre1

Landry Breuil-5
Hi,

since some years now i've been maintaining x11/xfce4 in the portstree,
with an alternate repo at https://cgit.rhaalovely.net/xfce4/?h=next
tracking upstream devel releases. This repo now contains all the bits
composing 4.14pre1 (cf
https://simon.shimmerproject.org/2019/05/19/xfce-4-14pre1-released/ for
the details, the main thing being of course the complete port to Gtk+3),
the final release being targeted at sometimes during the summer.

as an upstream developer i've of course been running it during the
development cycle on most of my boxes, but now would be a good time for
other Xfce users on OpenBSD to give it a shot and eventually report some
bugs to https://bugzilla.xfce.org.

The main OpenBSD-specific change is
https://bugzilla.xfce.org/show_bug.cgi?id=14722 (needs testing !)
which will make the consolekit/policykit/messagebus dependency
completely optional, allowing an user in the operator group to shutdown
the machine (ie can run the shutdown binary), or suspend/hibernate if in
the wheel group (ie has access to apmdev), instead of relying on 3
daemons running as root. The previous mode of needing messagebus
running + spawning startxfce4 within consolekit should still work.

amd64 -current packages for all core xfce pkgs (and some others i'm
using) are available at https://packages.rhaalovely.net/wip/amd64/
(signed with https://packages.rhaalovely.net/landry-mozilla-pkg.pub)

barring delays, this should make 6.6, but it's better if it's been
"widely" tested before..

Landry

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14pre1

Robert Klein
Hi,

thank you very much for your effort.

On Sat, 25 May 2019 18:43:49 +0200
Landry Breuil <[hidden email]> wrote:

> Hi,
>
> The main OpenBSD-specific change is
> https://bugzilla.xfce.org/show_bug.cgi?id=14722 (needs testing !)
> which will make the consolekit/policykit/messagebus dependency
> completely optional, allowing an user in the operator group to
> shutdown the machine (ie can run the shutdown binary), or
> suspend/hibernate if in the wheel group (ie has access to apmdev),
> instead of relying on 3 daemons running as root. The previous mode of
> needing messagebus running + spawning startxfce4 within consolekit
> should still work.

I didn't test this, yet.

>
> amd64 -current packages for all core xfce pkgs (and some others i'm
> using) are available at https://packages.rhaalovely.net/wip/amd64/
> (signed with https://packages.rhaalovely.net/landry-mozilla-pkg.pub)

Is the dependency to glade necessary?


PS, I got several messages during install:

Couldn't find dbus-glib-1 in second signature
Couldn't find dbus-1 in second signature
Couldn't find atspi in second signature
Error: xfce4-clipman-1.4.3 exists in two non-comparable versions
Someone forgot to bump a REVISION

Couldn't find dbus-1 in second signature
Couldn't find atspi in second signature
Error: xfce4-mpc-0.5.1 exists in two non-comparable versions
Someone forgot to bump a REVISION

Couldn't find fribidi in first signature
Error: xfce4-notes-1.8.1p4 exists in two non-comparable versions
Someone forgot to bump a REVISION

and so on...


OS version:

OpenBSD 6.5-current (GENERIC.MP) #39: Fri May 24 17:04:25 MDT 2019




Best regards
Robert

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14pre1

Landry Breuil-5
On Mon, May 27, 2019 at 11:43:33AM +0200, Robert Klein wrote:

> Hi,
>
> thank you very much for your effort.
>
> On Sat, 25 May 2019 18:43:49 +0200
> Landry Breuil <[hidden email]> wrote:
>
> > Hi,
> >
> > The main OpenBSD-specific change is
> > https://bugzilla.xfce.org/show_bug.cgi?id=14722 (needs testing !)
> > which will make the consolekit/policykit/messagebus dependency
> > completely optional, allowing an user in the operator group to
> > shutdown the machine (ie can run the shutdown binary), or
> > suspend/hibernate if in the wheel group (ie has access to apmdev),
> > instead of relying on 3 daemons running as root. The previous mode of
> > needing messagebus running + spawning startxfce4 within consolekit
> > should still work.
>
> I didn't test this, yet.
>
> >
> > amd64 -current packages for all core xfce pkgs (and some others i'm
> > using) are available at https://packages.rhaalovely.net/wip/amd64/
> > (signed with https://packages.rhaalovely.net/landry-mozilla-pkg.pub)
>
> Is the dependency to glade necessary?

Yes.

> PS, I got several messages during install:
>
> Couldn't find dbus-glib-1 in second signature
> Couldn't find dbus-1 in second signature
> Couldn't find atspi in second signature
> Error: xfce4-clipman-1.4.3 exists in two non-comparable versions
> Someone forgot to bump a REVISION
>
> Couldn't find dbus-1 in second signature
> Couldn't find atspi in second signature
> Error: xfce4-mpc-0.5.1 exists in two non-comparable versions
> Someone forgot to bump a REVISION
>
> Couldn't find fribidi in first signature
> Error: xfce4-notes-1.8.1p4 exists in two non-comparable versions
> Someone forgot to bump a REVISION

Yeah, nothing to worry about. It's just me being lazy.

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14pre2

Landry Breuil-5
In reply to this post by Landry Breuil-5
On Sat, May 25, 2019 at 06:43:49PM +0200, Landry Breuil wrote:

> Hi,
>
> since some years now i've been maintaining x11/xfce4 in the portstree,
> with an alternate repo at https://cgit.rhaalovely.net/xfce4/?h=next
> tracking upstream devel releases. This repo now contains all the bits
> composing 4.14pre1 (cf
> https://simon.shimmerproject.org/2019/05/19/xfce-4-14pre1-released/ for
> the details, the main thing being of course the complete port to Gtk+3),
> the final release being targeted at sometimes during the summer.
>
> as an upstream developer i've of course been running it during the
> development cycle on most of my boxes, but now would be a good time for
> other Xfce users on OpenBSD to give it a shot and eventually report some
> bugs to https://bugzilla.xfce.org.
>
> The main OpenBSD-specific change is
> https://bugzilla.xfce.org/show_bug.cgi?id=14722 (needs testing !)
> which will make the consolekit/policykit/messagebus dependency
> completely optional, allowing an user in the operator group to shutdown
> the machine (ie can run the shutdown binary), or suspend/hibernate if in
> the wheel group (ie has access to apmdev), instead of relying on 3
> daemons running as root. The previous mode of needing messagebus
> running + spawning startxfce4 within consolekit should still work.
>
> amd64 -current packages for all core xfce pkgs (and some others i'm
> using) are available at https://packages.rhaalovely.net/wip/amd64/
> (signed with https://packages.rhaalovely.net/landry-mozilla-pkg.pub)
>
> barring delays, this should make 6.6, but it's better if it's been
> "widely" tested before..

Fwiw, all updated to 4.14pre2, per
https://wiki.xfce.org/releng/4.14/xfce_4.14pre2.
Feedback & testing still welcome.

Landry

Reply | Threaded
Open this post in threaded view
|

[wip] Xfce 4.14 final

Landry Breuil-5
On Mon, Jul 01, 2019 at 09:33:04AM +0200, Landry Breuil wrote:

> On Sat, May 25, 2019 at 06:43:49PM +0200, Landry Breuil wrote:
> > Hi,
> >
> > since some years now i've been maintaining x11/xfce4 in the portstree,
> > with an alternate repo at https://cgit.rhaalovely.net/xfce4/?h=next
> > tracking upstream devel releases. This repo now contains all the bits
> > composing 4.14pre1 (cf
> > https://simon.shimmerproject.org/2019/05/19/xfce-4-14pre1-released/ for
> > the details, the main thing being of course the complete port to Gtk+3),
> > the final release being targeted at sometimes during the summer.
> >
> > as an upstream developer i've of course been running it during the
> > development cycle on most of my boxes, but now would be a good time for
> > other Xfce users on OpenBSD to give it a shot and eventually report some
> > bugs to https://bugzilla.xfce.org.
> >
> > The main OpenBSD-specific change is
> > https://bugzilla.xfce.org/show_bug.cgi?id=14722 (needs testing !)
> > which will make the consolekit/policykit/messagebus dependency
> > completely optional, allowing an user in the operator group to shutdown
> > the machine (ie can run the shutdown binary), or suspend/hibernate if in
> > the wheel group (ie has access to apmdev), instead of relying on 3
> > daemons running as root. The previous mode of needing messagebus
> > running + spawning startxfce4 within consolekit should still work.
> >
> > amd64 -current packages for all core xfce pkgs (and some others i'm
> > using) are available at https://packages.rhaalovely.net/wip/amd64/
> > (signed with https://packages.rhaalovely.net/landry-mozilla-pkg.pub)
> >
> > barring delays, this should make 6.6, but it's better if it's been
> > "widely" tested before..
>
> Fwiw, all updated to 4.14pre2, per
> https://wiki.xfce.org/releng/4.14/xfce_4.14pre2.
> Feedback & testing still welcome.

The same wip repo at https://packages.rhaalovely.net/wip/amd64/ now has
4.14 final (cf https://xfce.org/about/news/?post=1565568000), packages
built against 6.6-beta. Got very few reports from testers, sadly.. now
is the time to test before i commit it soon.

Landry

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14 final

Edd Barrett-3
Hi Landry,

Thanks for this update!

Comments below.

On Tue, Aug 13, 2019 at 07:57:54PM +0200, Landry Breuil wrote:
> The same wip repo at https://packages.rhaalovely.net/wip/amd64/ now has
> 4.14 final (cf https://xfce.org/about/news/?post=3D1565568000), packages
> built against 6.6-beta. Got very few reports from testers, sadly.. now
> is the time to test before i commit it soon.

During upgrade, I got the following:
---8<---
=2E..
fce4-appfinder-4.12.0p4->4.14.0: ok
xfce4-battery-1.1.2->1.1.3: ok
Couldn't find x11/dbus-glib in first signature
Error: xfce4-mixer-4.11.0p7 exists in two non-comparable versions
Someone forgot to bump a REVISION
xfce4-mixer-4.11.0p7,5,@desktop-file-utils-0.24p0,@gstreamer-0.10.36p13,@gs=
treamer-plugins-base-0.10.36p19,@gstreamer-plugins-good-0.10.31p25v0,@libun=
ique-1.1.6p13,@xfce4-panel-4.12.2p3,ICE.11.0,SM.9.0,X11-xcb.2.0,X11.17.0,Xc=
omposite.4.0,Xcursor.5.0,Xdamage.4.0,Xext.13.0,Xfixes.6.0,Xi.12.1,Xinerama.=
6.0,Xrandr.7.1,Xrender.6.0,atk-1.0.21809.3,c.95.1,cairo.13.0,dbus-1.11.2,db=
us-glib-1.5.0,expat.12.0,ffi.1.2,fontconfig.12.0,freetype.29.0,fribidi.3.0,=
gdk-x11-2.0.2400.0,gdk_pixbuf-2.0.3200.1,gio-2.0.4200.9,glib-2.0.4201.2,gmo=
dule-2.0.4200.9,gobject-2.0.4200.9,graphite2.2.0,gstaudio-0.10.2.6,gstbase-=
0.10.3.0,gstinterfaces-0.10.2.6,gstpbutils-0.10.2.6,gstreamer-0.10.3.0,gthr=
ead-2.0.4200.9,gtk-x11-2.0.2400.0,harfbuzz.14.4,iconv.7.0,intl.6.0,lzma.2.1=
,m.10.1,pango-1.0.3800.2,pangocairo-1.0.3800.1,pangoft2-1.0.3800.1,pcre.3.0=
,pixman-1.38.4,png.18.0,pthread.26.1,startup-notification-1.2.0,unique-1.0.=
2.0,xcb-render.1.1,xcb-shm.1.1,xcb-util.0.0,xcb.4.0,xfce4panel-1.0.1.0,xfce=
4ui-1.0.1,xfce4util.4.0,xfconf-0.0.1,xml2.16.1,z.5.0 vs. xfce4-mixer-4.11.0=
p7,5,@dbus-glib-0.110p1v0,@desktop-file-utils-0.24p0,@gstreamer-0.10.36p13,=
@gstreamer-plugins-base-0.10.36p19,@gstreamer-plugins-good-0.10.31p25v0,@li=
bunique-1.1.6p13,@xfce4-panel-4.14.0,ICE.11.0,SM.9.0,X11-xcb.2.0,X11.17.0,X=
composite.4.0,Xcursor.5.0,Xdamage.4.0,Xext.13.0,Xfixes.6.0,Xi.12.1,Xinerama=
=2E6.0,Xrandr.7.1,Xrender.6.0,atk-1.0.21809.3,c.95.1,cairo.13.0,dbus-1.11.2=
,dbus-glib-1.5.0,expat.12.0,ffi.1.2,fontconfig.12.0,freetype.29.0,fribidi.3=
=2E0,gdk-x11-2.0.2400.0,gdk_pixbuf-2.0.3200.1,gio-2.0.4200.9,glib-2.0.4201.=
2,gmodule-2.0.4200.9,gobject-2.0.4200.9,graphite2.2.0,gstaudio-0.10.2.6,gst=
base-0.10.3.0,gstinterfaces-0.10.2.6,gstpbutils-0.10.2.6,gstreamer-0.10.3.0=
,gthread-2.0.4200.9,gtk-x11-2.0.2400.0,harfbuzz.14.4,iconv.7.0,intl.6.0,lzm=
a.2.1,m.10.1,pango-1.0.3800.2,pangocairo-1.0.3800.1,pangoft2-1.0.3800.1,pcr=
e.3.0,pixman-1.38.4,png.18.0,pthread.26.1,startup-notification-1.2.0,unique=
-1.0.2.0,xcb-render.1.1,xcb-shm.1.1,xcb-util.0.0,xcb.4.0,xfce4panel-1.0.1.1=
,xfce4ui-1.0.2,xfce4util.4.1,xfconf-0.1.0,xml2.16.1,z.5.0
Couldn't find x11/dbus-glib in first signature
--->8---

Even so, it updated OK.

I noticed the panel flickering a lot until I disabled the compositor in "wi=
ndow
manager tweaks".

The release notes say that the WM got HDPI support. Do I have to do somethi=
ng
to enable it? I was expecting all of the various window manager themes to
scale up for HDPI. Maybe I was wrong...

That's all for now. I'll continue to test over the next few days.

--=20
Best Regards
Edd Barrett

http://www.theunixzoo.co.uk

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14 final

Matthieu Herrb-3
On Wed, Aug 14, 2019 at 03:30:01PM +0100, Edd Barrett wrote:
> Hi Landry,
>
> Thanks for this update!

[...]

> I noticed the panel flickering a lot until I disabled the compositor in "wi=
> ndow
> manager tweaks".

Hi,

I guess you are using the modesetting driver in X.

Can you try to change vlank mode to 'xpresent':

xfconf-query -c xfwm4 -p /general/vblank_mode -s xpresent

And restart your session ?

--
Matthieu Herrb

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14 final

Micah Muer-2
In reply to this post by Landry Breuil-5
On Tue, Aug 13, 2019, at 09:58, Landry Breuil wrote:
>
> The same wip repo at https://packages.rhaalovely.net/wip/amd64/ now has
> 4.14 final (cf https://xfce.org/about/news/?post=1565568000), packages
> built against 6.6-beta. Got very few reports from testers, sadly.. now
> is the time to test before i commit it soon.
>
> Landry
>

I'm not a regular xfce user, but I did try out as many settings, options,
and  features as I would normally use under gnome. In a few hours of
testing on a 1920x1080 Thinkpad X1 Carbon (6th gen)  I've noticed
only one small issue:

* In Settings -> Appearance -> Settings tab, I changed "Window
   Scaling" to "2x" then back to "1x." Everything returned to the normal
   1x size except for the text of some panel items, like the power
   manager plugin. To fix this, I just logged out and logged back in.

Other than that, everything seems to work as advertised. Thanks for your
work on this.

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14 final

Landry Breuil-5
In reply to this post by Matthieu Herrb-3
On Wed, Aug 14, 2019 at 05:25:04PM +0200, Matthieu Herrb wrote:

> On Wed, Aug 14, 2019 at 03:30:01PM +0100, Edd Barrett wrote:
> > Hi Landry,
> >
> > Thanks for this update!
>
> [...]
>
> > I noticed the panel flickering a lot until I disabled the compositor in "wi=
> > ndow
> > manager tweaks".
>
> Hi,
>
> I guess you are using the modesetting driver in X.
>
> Can you try to change vlank mode to 'xpresent':
>
> xfconf-query -c xfwm4 -p /general/vblank_mode -s xpresent
>
> And restart your session ?

same thing for me on x200s and x1c3 with modesetting driver and
compositing enabled, and forcing xpresent fixed it - thanks matthieu for
the hint, it's actually documented upstream in
https://git.xfce.org/xfce/xfwm4/tree/COMPOSITOR?h=master#n114 so i'll
refer users to that page in the README.

Landry

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14 final

Edd Barrett-3
In reply to this post by Matthieu Herrb-3
Hi,

On Wed, Aug 14, 2019 at 05:25:04PM +0200, Matthieu Herrb wrote:
> Can you try to change vlank mode to 'xpresent':
>
> xfconf-query -c xfwm4 -p /general/vblank_mode -s xpresent
>
> And restart your session ?

This works for me! Thanks.

Shall we put this in the package README?

--
Best Regards
Edd Barrett

http://www.theunixzoo.co.uk

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14 final

Edd Barrett-3
In reply to this post by Edd Barrett-3
On Wed, Aug 14, 2019 at 03:30:01PM +0100, Edd Barrett wrote:
> The release notes say that the WM got HDPI support. Do I have to do
> something to enable it? I was expecting all of the various window
> manager themes to scale up for HDPI. Maybe I was wrong...

About this. There is (and was in the last release) a HDPI theme, but
sadly I don't like it (not enough contrast between active and inactivve
windows). It's not a biggie, as you can download more HDPI themes from
the internetz.

I did find a window scaling option (settings->appearance->settings),
which sadly doesn't scale the border, and the fonts only scale on GTK
(and maybe QT) apps by the look of it. For example, the font in an xterm
is teensy with window scaling.

I guess I'll stick with a custom DPI (settings->appearance->fonts) and
the 2x hack for firefox (about:config then search for
layout.css.devPixelsPerPx, set to 2).

Settings->display doesn't seem to work:

---8<---
fremen:edd> xfce4-display-settings
xfce4-display-settings(68635) in free(): bogus pointer (double free?)
0xdfdfdfdfdfdfdfdf
zsh: abort (core dumped)  xfce4-display-settings
--->8---

--
Best Regards
Edd Barrett

http://www.theunixzoo.co.uk

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14 final

Landry Breuil-5
On Thu, Aug 15, 2019 at 09:51:03AM +0100, Edd Barrett wrote:

> On Wed, Aug 14, 2019 at 03:30:01PM +0100, Edd Barrett wrote:
> > The release notes say that the WM got HDPI support. Do I have to do
> > something to enable it? I was expecting all of the various window
> > manager themes to scale up for HDPI. Maybe I was wrong...
>
> About this. There is (and was in the last release) a HDPI theme, but
> sadly I don't like it (not enough contrast between active and inactivve
> windows). It's not a biggie, as you can download more HDPI themes from
> the internetz.
>
> I did find a window scaling option (settings->appearance->settings),
> which sadly doesn't scale the border, and the fonts only scale on GTK
> (and maybe QT) apps by the look of it. For example, the font in an xterm
> is teensy with window scaling.
>
> I guess I'll stick with a custom DPI (settings->appearance->fonts) and
> the 2x hack for firefox (about:config then search for
> layout.css.devPixelsPerPx, set to 2).
>
> Settings->display doesn't seem to work:
>
> ---8<---
> fremen:edd> xfce4-display-settings
> xfce4-display-settings(68635) in free(): bogus pointer (double free?)
> 0xdfdfdfdfdfdfdfdf
> zsh: abort (core dumped)  xfce4-display-settings
> --->8---

Its been worked around with
http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/x11/xfce4/xfce4-settings/patches/patch-common_display-profiles_c?rev=1.1&content-type=text/x-cvsweb-markup

as for the vblank stuff, a blurb about compositing was added to the
README in
http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/meta/xfce/pkg/README-main?rev=1.14&content-type=text/x-cvsweb-markup

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14 final

Edd Barrett-3
On Thu, Aug 15, 2019 at 02:27:18PM +0200, Landry Breuil wrote:
> Its been worked around with...
>
> as for the vblank stuff, a blurb about compositing was added to the
> README in...

Cool, thanks.

One other nit I just noticed (that you may have already fixed too) is
that in settings->appearance->style, selecting different styles doesn't
make a difference.

Thanks!

--
Best Regards
Edd Barrett

http://www.theunixzoo.co.uk

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14 final

Landry Breuil-5
On Fri, Aug 16, 2019 at 10:59:19AM +0100, Edd Barrett wrote:

> On Thu, Aug 15, 2019 at 02:27:18PM +0200, Landry Breuil wrote:
> > Its been worked around with...
> >
> > as for the vblank stuff, a blurb about compositing was added to the
> > README in...
>
> Cool, thanks.
>
> One other nit I just noticed (that you may have already fixed too) is
> that in settings->appearance->style, selecting different styles doesn't
> make a difference.

Well it totally does here, so maybe you dont have xfconf or xfsettingsd
running for some reason. Or you've only tried broken styles :)

Landry

Reply | Threaded
Open this post in threaded view
|

Re: [wip] Xfce 4.14 final

Edd Barrett-3
In reply to this post by Edd Barrett-3
On Fri, Aug 16, 2019 at 10:59:19AM +0100, Edd Barrett wrote:
> One other nit I just noticed (that you may have already fixed too) is
> that in settings->appearance->style, selecting different styles doesn't
> make a difference.

And one more: a couple of times the whole desktop session has locked up.
The mouse moves but you can't focus or interact with any windows or the
status bar. Keyboard bindings are also ineffectual.

Not sure what causes it. Bad bug report, I know :\

--
Best Regards
Edd Barrett

http://www.theunixzoo.co.uk