Bug 202356
| Summary: | x11-wm/windowmaker 0.95.6_4 crashes while trying to launch google chrome | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Anindya Mukherjee <anindya49> |
| Component: | Individual Port(s) | Assignee: | Hiroki Sato <hrs> |
| Status: | Closed Feedback Timeout | ||
| Severity: | Affects Some People | CC: | anindya49, arved, mbeis, w.schwarzenfeld |
| Priority: | --- | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
assign to maintainer Is this still relevant? No maintainer feedback! hrs maintains 221 (!) ports. Which seems a lot to me. As I use Windowmaker myself I'd be happy to take x11-wm/windowmaker over from him to maintain. Thanks! No problem. But how does this work? Do I have to send a request to portmgr@ or hrs@ ? Yes, please send a request to portmgr@. (In reply to w.schwarzenfeld from comment #6) No, In order to take maintainership, please attach a patch updating just the MANTAINER line. It has to be assigned to the port maintainer. If the maintainer doesn't reject it in 14 days, you will become a maintainer. Please create a new bug for this, subject should begin with "x11-wm/windowmaker:" Yuri Already talked to hrs@ himself and he said he wanted to keep maintaining x11-wm/windowmaker for now. I'm going to close this with feedback timeout as the actual issue from comment #0 has not been discussed since 2015 or confirmed after comment #2. If this is actually still a problem feel free to reopen this bug. |
windowmaker 0.95.6_4 crashes while trying to launch google chrome. Steps to reproduce: 1. Google Chrome (Chromium) does not produce an application icon in windowmaker. So I enabled the "Emulate application icon" option under the chrome window attributes. 2. If I now right-click on the application icon and click "Launch", while Chrome is already running, windowmaker crashes immediately. I think a possible reason may be that Chrome creates an odd application launch command. Instead of it being "chrome", it's ("chrome: "). It may be not what windowmaker expects and causes it to crash. I see this behaviour in both i386 and x64 versions of FreeBSD.