Without a crash or other Info, a bug report is not possible
Sure it is. Just add all the info and details you have. Watch the output when starting Web+ from Terminal, see if there is anything interesting in Web+ Script console, state the exact error you see, etc.
Itâs kinda hard to believe that nobody has been able to log in over the years, and thereâs not a single bug report about thatâŚ
This is not really correct, i do a bug report
https://dev.haiku-os.org/ticket/13560
But I never understand at this time to do a bug report on git, so i let it be.
A bugreport at a github is easy:
- Go to GitHub and log into github account.
- Go to the project, e.g. GitHub - haiku/haikudepotserver: Haiku Depot Server
- At the top, click on âIssuesâ.
- On the Issue page, click on âNew issueâ at the top right.
- Enter a meaning full title an the text of your ticket.
Be aware that the current Web+ wonât upload files to a ticketâŚ
Not all projects have this issues Button. I tried a scribus. I only can commit like you told me on begeistert läĂt year
Some projects (for example, Haiku) decide to track their issues elsewhere, and so they disable the Github issue tracker. this is not the case for haikudepotserver, however.
Thanks again Lelldorin for the great Icon-O-Matic beginners tutorial. I finally got around to try and make an icon yesterday and it worked. Iâm still very much limited by my complete lack of talent in graphic design
But now at least I know what to do on the technical side of things.
New tutorials are online:
How to add Haiku into the Windows menu using EasyBCD
http://www.besly.de/index.php/de/system/systemstartup/haiku-im-windows-bootmenue-einfuegen
Alex the Allegator - How to play
http://www.besly.de/index.php/de/spiele/fang-und-flucht/alex-the-allegator-4
Alex the Allegator 4 (Alex4) - How to create a own level
http://www.besly.de/index.php/de/spiele/169-alex-the-allegator-4-alex-4-der-level-editor
!! We use a auto-translate fuction of the website and it look some time a little bit strange if i read the englsh translation. I hope i translate it, or any other around translate it for in the future.
Alex4custom docu
http://besly.de/index.php/de/spiele/jump-and-run/alex-the-allegator-4/alex4customs
No one have interest to translate my icon-o-matic tutorial (all languages are welcome)?
Ok i do it by myself, starting with WB:
How to edit a screenshot with WonderBrush
http://www.besly.de/index.php/en/painting/wonderbrush/218-wonderbrush-how-to-edit-screenshots
Now i have done the tranlsation of my icon-o-matic tutorial:
http://besly.de/index.php/en/painting/icon-o-matic/creating-a-simple-icon
The link for icon-o-matic not working.
The article now moved into the menu structure.
http://besly.de/index.php/en/painting/icon-o-matic/creating-a-simple-icon
I create a little tutorial about porting a program to haiku, with the focus on add files right (writeable/protected areas)
http://www.besly.de/index.php/en/package-system/274-porting-to-haiku
And a second one for blacklist driver:
http://www.besly.de/index.php/de/28-systemeinstellungen-1/275-blacklist-ignore-problematic-hardware
hey great read⌠good to know⌠well done lelldorin.
Nice work lelldorin!
Past a long time i am coming up with two new tutorials:
2Pow game by 3Deyes: BeSly â Haisly
** Hello 3Deyes: please make a 64bit port. Very great game, thanks!
eduke - Duke Nukem 3D: BeSly â Haisly
** a little bit older by lorglas:
Wie kann man einen Mauszeiger in C/C++ anpassen? BeSly â Haisly (german)
I just noticed with shock that I havenât shown any status here for a long time.
I should do it more often, because it happens again and again that people do not know our knowledge base.
Love2D create executeable files
https://besly.de/index.php/en/development/244-love2d/313-love2d-generiere-ausfuehrbare-dateien-2
Playground Editor Documentation
https://besly.de/index.php/en/development/playground-editor-2/dokumentation-2
GhostscriptGUI documentation
https://besly.de/index.php/en/85-sonstiges-7/362-ghostscript-gui
HPKGCreator Documentation (Rework) - english
https://besly.de/index.php/en/package-system/hpkg-creator
BeSly System Analysis Tool - Hardware List
https://besly.de/index.php/en/hardware/besly-system-analysis-tool-2
I keep seeing people who fix problems or conjure up nice extensions. it would be nice if these things, well described, would flow into our knowledge base. then such information is not lost when users leave the system. Unfortunately, many of these tricks and extras are not always understandable, there are problems with haiku at every corner. programmers also keep asking for more background information.
so I wanted to draw attention to our knowledge base again. we are happy about every tip, every trick, every tutorial or instructions. what is important is that it is from you and works. no information that comes from pure memory, because this is the only way we can collect information and pass it on to other users.
Unfortunately, there are always gaps in various Linux instructions, gaps due to information that is not complete or based on âthoughtâ knowledge. this is one of the points we always try to avoid on the knowledge base. so nobody can just write and publish something there.
But that shouldnât stop anyone from giving us their contributions. we check these and adapt them to our site so that we maintain our standard.
Please help us to expand this knowledge of our small community.
I started laying out some groundwork on my wiki page, itâs still wip.
But aside that, from problems that arise, some would be easy to fix, things to check when you encounter issues.
- configure --help (gives you options that you can enable/disable/set)
- Makefiles (some sources donât provide build tools, so read through the makefile provided, some hints can be found in there too)
- cmake -L (gives you the list of options to use when running a cmake build)
- meson (check meson-options.txt/meson.build for pointers you can enable/disable/set)
There are other build systems around, usually they also provide information you can use.