| Summary: | app-admin/keepass printing does not work | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mark Reiche <mr20.gentoo> |
| Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | dotnet, fearedbliss, jstein, mgorny, mr20.gentoo, proxy-maint |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Mark Reiche
2012-11-30 19:04:21 UTC
Message on the console "libgluezilla not found. To have webbrowser support, you need libgluezilla installed", so I am guessing that it is using gecko to create the printed page? If that's the case, I'm not sure what we can do - libgluezilla was dropped from the tree because it depends on xulrunner which was also dropped from the tree. Maybe Alessandro has some insight? The problem is that the Mono WebBrowser component is based on Gecko, through libgluezilla, which has you said has been removed with xulrunner [1]. Since the WinForms project on Mono has been abandoned I think that submitting a bug to request to update to npapi-sdk would be useless (if possible). However looks like there's an alternative implementation for the WebBrowser backend using WebKit [2] and we have a dev-dotnet/webkit-sharp ebuild in Portage. I'll try to install that package and see if it works out-of-the-box (don't think so). If it doesn't I'll take a look if it's possible to patch KeePass for using WebKit and then I'll submit the patch upstream. [1] https://bugs.gentoo.org/show_bug.cgi?id=xulrunner [2] http://www.mono-project.com/WebBrowser I've found there's a environment variable used to set the web browser backend, MONO_BROWSER_ENGINE. If it's set to webkit, it should use webkit, however it requires the mono-webkit library [1] which is not in Portage. I'll see if I'm able to write an ebuild for that. Micahel, do you think that inlcuding that small library in dev-dotnet/webkit-sharp is an option? Ale [1] https://github.com/mono/mono-webbrowser (In reply to comment #3) > I've found there's a environment variable used to set the web browser > backend, MONO_BROWSER_ENGINE. If it's set to webkit, it should use webkit, > however it requires the mono-webkit library [1] which is not in Portage. > I'll see if I'm able to write an ebuild for that. > > Micahel, do you think that inlcuding that small library in > dev-dotnet/webkit-sharp is an option? > > Ale > > [1] https://github.com/mono/mono-webbrowser I do not see any problem with adding this. @dotnet team, thoughts/objections? Ping. (In reply to Michał Górny from comment #5) > Ping. As far as I know, nothing here has changed. I understand that some dotnet packaging changes are required to support printing from mono-based applications. It seems that this hasn't been important enough for anyone to push it forward any further. |
