#16653 closed bug (invalid)
WonderBrush: fix amd64 saving
| Reported by: | nephele | Owned by: | nobody |
|---|---|---|---|
| Priority: | high | Milestone: | R1 |
| Component: | Applications | Version: | R1/beta2 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | x86-64 |
Description
WonderBrush crashes on saving on 64bit, I attempted to fix this a couple of times but was unsucessfull. :)
filing this here because it is included in the OS image and fairly important imo.
Change History (9)
comment:1 by , 4 years ago
| Milestone: | R1/beta3 → R1 |
|---|
comment:2 by , 4 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:4 by , 4 years ago
I disagree with closing this, we ship this application, and upstream explicitly doesn't support amd64, that was added in Haiku itself.
We should really fix it on amd64, since that is a pretty major usecase regression that it can't be used there but can on x86. (on the default install)
comment:6 by , 4 years ago
How is it? it's a bug that's specific to one of our architectures, with an application we ported to that architecture, which we ship in the default install.
This seems no different to me than opening bugs with our libraries here instead of the respective upstream.
comment:7 by , 4 years ago
This seems no different to me than opening bugs with our libraries here instead of the respective upstream.
Correct, this is also not the place for that. Bugs with applications and libraries are either handled at haikuports, or directly at the upstream if it's their fault.
In this case, the bug is in the application and not in Haiku, until proven otherwise. So, again, this has nothing to do here. We cannot fix it. Only people working with the Wonderbrush sources can.
And you may have noticed that we do NOT ship the 64bit version for this very reason. Which is all we can do on Haiku side.
comment:8 by , 4 years ago
Correct, this is also not the place for that. Bugs with applications and libraries are either handled at haikuports, or directly at the upstream if it's their fault.
I should report issues to gnu for our version of glibc? or did you only mean unmodifed libraries?
In this case, the bug is in the application and not in Haiku, until proven otherwise. So, again, this has nothing to do here. We cannot fix it. Only people working with the Wonderbrush sources can.
And you may have noticed that we do NOT ship the 64bit version for this very reason. Which is all we can do on Haiku side.
The application is shipped in the install image, how is it that we cannot fix it? surely we have control over the finished instalation media?
In any case, Wonderbrush does fulfill a specific usecase that is now broken on amd64 Haiku, is it okay to have an issue for this then? like a "no pressure sensitive tablet client" bug or so.
as a side note, the whole part of pulling in packages to the install image of haiku seems really strange to me since it makes regression testing that much harder.
comment:9 by , 4 years ago
I should report issues to gnu for our version of glibc? or did you only mean unmodifed libraries?
You can easily see what is Haiku sourcecode (at git.haiku-os.org) and what isn't. If it isn't Haiku sourcecode this is not the right bugtracker. With only one exception for WebKit.
In any case, Wonderbrush does fulfill a specific usecase that is now broken on amd64 Haiku, is it okay to have an issue for this then? like a "no pressure sensitive tablet client" bug or so.
That is an useless issue. We provide the OS, we cannot be expected to maintain and develop also all applications. Again, please report the problem to the application developer and see there about fixing it.
Please report this on github to the Wonderbrush bugtracker. It has nothing to do here.