Re: Welcome XFCE 4.14
On 24/09/19 11:13, Marko Cupać wrote: > On Sun, 22 Sep 2019 08:38:15 +0200 > Olivier Duchateau wrote: > >> Le Sat, 21 Sep 2019 23:29:48 +0200, >> Marko Cupać a écrit : >>> ...a few problems: >>> - I was using greybird theme on 4.12 as well, but now after the >>>upgrade I have ugly black background in title bar of each window >>>(window manager). It seem to affect other themes as well. > >> Are you using DRM kernel module? Or X.org drivers? > > Sorry for late reply, took me a few days to come back to office from > this year's eurobsdcon. > > I'm using latest DRM kernel module, drm-fbsd12.0-kmod-4.16.g20190814. > > This is on FreeBSD 12.0-RELEASE-p10 GENERIC amd64, with yesterday's > ports (I build them myself in poudriere). My hardware is ThinkPad T440, > here's how display adapter looks to pciconf: > > vgapci0@pci0:0:2:0: class=0x03 card=0x220c17aa chip=0x0a168086 rev=0x0b > hdr=0x00 > vendor = 'Intel Corporation' > device = 'Haswell-ULT Integrated Graphics Controller' > class = display > subclass = VGA > > Regards, > Hi, I was skimming upstream commits, to try to see if there is something that could affect us. Sometimes this gives hints and solutions some others it does not. While this is a complex issue and it's difficult to find a fix without specific knowledge, I noticed a recent commit [1] that maybe could help. This is a shot in the dark, but worth a try, so, someone affected should apply the patch at [2] to x11-wm/xfce4-wm and report back. I only tested this patch in poudriere and it compiles. Thanks in advance. [1] https://github.com/xfce-mirror/xfwm4/commit/e5462de37a4b0a18c051e9a92ea6dce7cd7b79a8 [2] https://people.freebsd.org/~madpilot/xfce4-wm.diff -- Guido Falsi ___ freebsd-xfce@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xfce To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"
[Bug 206196] x11-wm/xfce4-panel dumps core
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206196 Guido Falsi changed: What|Removed |Added Resolution|--- |Overcome By Events Status|Open|Closed --- Comment #32 from Guido Falsi --- (In reply to Marko Cupać from comment #31) Great, then I'm closing this myself. Overcome by events looks reasonable in this case. Thanks for the feedback! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xfce@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xfce To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"
[Bug 206196] x11-wm/xfce4-panel dumps core
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206196 --- Comment #31 from Marko Cupać --- (In reply to Guido Falsi from comment #30) I visited all the problematic links I posted above, in both Firefox and Chromium, on two boxes. Both are 12.0-RELEASE-p10 amd64, but one is still on xfce-4.12_1, while the other is already on xfce-4.14. Also, I don't have x11-fonts/droid-fonts-ttf installed on either of the two machines, it appears Chromium dropped it as a dependency. No panels crashed, yay! :) As far as I am concerned, this one has been squashed. Feel free to close it, or instruct me what is the best reason for closing (FIXED? Overcome By Events?) Thanx everyone. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xfce@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xfce To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"
[Bug 240804] x11/xfce4-screensaver: Newly Installed via pkg upgrade Does Not Allow Password Input and xscreensaver No Longer Function Forcing User to Reboot Frequently and/or Data Loss
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240804 --- Comment #12 from Guido Falsi --- (In reply to John from comment #10) Please don't rush things. You created 3 bug reports for the same issue, one referencing a port which is only marginally related to the issue (xscreensaver), since it's not installing any file causing it. This is strictly an XFCE problem. Please let's keep the conversation in one place only. This is one bug. with two strictly related problems. - xfce installs two .desktop files (one via xfce4-session port and one via the xfce4-screensaver port) which launch screensaver applications and, if both are installed, both are lunched simultaneously. This setup cannot work - to make things worse, the GUI to choose which one is enabled ends up with the same description for both of them. I already filed a bug report upstream with xfce4-screensaver [1] asking to change the name in the desktop file. That's enough. I think that your changes are too invasive and would not be accepted upstream. Also you patch is touching the wrong file. Anyway if you want to push to upstream for your changes, I'd suggest you followup to my bug report there with a correct patch relative to their sources. My plan is to change the description with a little brutal (in relation to the translations [2]) patch to the xfce4-screensaver .desktop file, so as to get different descriptions, and make xfce4-session install the xscreensaver .desktop file disabled, and add a note in UPDATING. This logic is due to the fact that the xfce metaport installs xfce4-screensaver by default, so having the default xscreensaver.desktop file enabled by default would cause the issue to appear for everybody. I need some time to test all this and I'll also be away for a few days, so I don't think I'll be able to commit a fix before monday. The other option is to revert the xfce metaport to depending on xscreensaver as before and let people manually install xfce4-screensaver if they want to. But since xfce now has it's own screensaver component this does not look optimal. Somewhere in your messages you ask me not to disable xscreensaver by default...why? Having BOTH enabled cannot work. [1] https://bugzilla.xfce.org/show_bug.cgi?id=15991, referenced in bug #240811 [2] we can't only patch the English version and wait for xfce to translate it, this would require a lot of time, and in the while translated versions would get the same text anyway. Also any proposed name/description change we send to xfce for inclusion needs to be accepted there, which we can't force -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xfce@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xfce To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/x...@freebsd.org.html Port| Current version | New version +-+ x11-wm/xfce4-panel | 4.14.0 | 4.14.1 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-xfce@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xfce To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"
