Bug 269593 - sysutils/xfce4-power-manager: XFCE Power Manager Plugin, required by x11-wm/xfce4, fails on launch
Summary: sysutils/xfce4-power-manager: XFCE Power Manager Plugin, required by x11-wm/x...
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-xfce (Nobody)
URL:
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2023-02-16 18:29 UTC by Michael Dexter
Modified: 2023-09-02 09:34 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Dexter 2023-02-16 18:29:18 UTC
Tested on FreeBSD 13.2-BETA1 and 14-CURRENT (early 2023): the xfce meta package includes and automatically installs a "Power Management Plugin" that, upon 'startxfce4' fails with:

"Plugin "Power Manager Plugin" unexpectedly left the panel, do you want to restart it?

The plugin restarted more than once in 60 seconds. If you press Execute the panel will try to restart the plugin otherwise it will be permanently removed from the panel.

Execute | Remove"

"Execute" repeats the behavior and "Remove" works as expected.

Workaround for battery reporting: Install the xfce4-battery-plugin package and add the "Battery Monitor" item to the panel.

Hardware: Lenovo ThinkPad T480, X1 Carbon Gen 1, X220i

Suspect port: xfce4-power-manager

Possible solution: replace xfce4-power-manager with xfce4-battery-plugin in the meta package.

Confusion: https://www.freshports.org/x11-wm/xfce is marked as deprecated while 'xfce4' is not found on 13.2-BETA1 but installs 'xfce' if specified as 'x11-wm/xfce4'
Comment 1 Guido Falsi freebsd_committer freebsd_triage 2023-02-16 18:41:10 UTC
Hi,

This is not happening on my laptop or desktop PC.

I can add the power manager panel plugin and it works (shows the battery icon and the percent of battery on the laptop, for example)

Maybe not all laptops are the same and some confuse the xfce power manager.

Could you try to collect some debug information?

Maybe something from Xorg log files, messages, to understand what is happening on your PC?


Regarding the "naming" issue, there used to exist and "xfce" meta port that has been removed more than 10 years ago, it's not just deprecated.

At the time a new "xfce4" port was created for the new version of xfce. Unluckily since then the actual name of the package differed from the name of the port. This is not easily changed without forcing all existing users to modify their installations. We try to avoid such disruption.
Comment 2 Guido Falsi freebsd_committer freebsd_triage 2023-02-16 18:48:15 UTC
I'd also like to add that the only way to properly debug a crash is to get a backtrace of the crash using gdb (or similar debugger) from a DEBUG build of the binary.

If I were able to reproduce the crash I'd gather such a backtrace myself, but since the crash is not happening for me I need to ask you (or anyone else experiencing the crash) to provide that.