While I could successfully install net-im/teams, running teams (from a terminal) results in: * no output in the terminal * immediate return to the terminal (with exit code 0!) * no Window with the Teams client opening. This is under Wayland using Sway as compositor. On another system running X using x11-wm/spectrwm as window manager, the first two points are the same (i.e. it appears to be normal for teams to successfully return to the terminal without any text output) but a window with the Teams client pops up. Reproducible: Always Steps to Reproduce: 1. Install Teams client: emerge -1 net-im/teams 2. Try launching Teams client: teams Actual Results: Launcher command (teams) returns to the shell with exit code 0. No window spawns. Expected Results: Launcher command (teams) returns to the shell with exit code 0. Teams client window spawns. gui-wm/sway-1.5.1-r1
Created attachment 702339 [details] emerge --info emerge --info net-im/teams gui-wm/sway gui-libs/wlroots
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis. We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3]. I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4]. Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://forums.gentoo.org/ [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html [4] https://www.gentoo.org/support/
Dear Jonas, Thank you for taking the time to look into my issue and getting back at me (especially in such a timely manner). But frankly, I am dissapointed to be told off like this after making an effort to report an issue where an application not launching after installing an official package using my distros official package manager. If there would have been any error message, I'd included it. > The situation seems to be a bit more complicate and requires some analysis. What is this statement based on? Did you try to reproduce the issue but failed to do so on your system? What kind of analyses are required? You clearly seem to know more than me and since you already took the time to respond, why not at least give me some pointers what else to check so I can submit a more useful report o the other channels you refer me to? > The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. If I'd know the specific issue with the ebuild, I'd probably be able to fix it myself. So I read this as bugs without patches being not welcome. Is this official Gentoo policy? Whre can I find this information? Don't get me wrong: I am genuinly trying to understand why this is considered 'resolved' and which 'need[ed ]info' I failed to provide. My experience on the forums is that unless it's an error on my side (unlike here since I just emerge a package that shouldn't require any additional configuration to run), it either boils down to either being told to report a bug (which I would agree with in this case, but apparently that is not correct) or no response at all (besides maybe some questions making sure I didn't make some obvious mistake). I can try my luck on IRC though I prefer solving problems on more accessible platform so others can benefit from my struggle as well. Also, on IRC I am limited to getting help from people who are awake and have time at the same time as me (which I rarely do these times). The mailing list is a better alternative since at least it has an easily searchable archive but I feel bad bothering everyone on that list where 95% of recipents probably have no interest in net-im/teams when there is a system to report issues with specific packages that specifically targets the maintainer(s) of said package. Finally, I'd be perfectly fine with Teams depending on X (if that is the issue here) in which case I'd simply not install it. I can live without this application. But I lost time trying it get it to work and I felt obliged to report it so that others won't have to waste there time repeating what I already did. By marking this resolved, you have ensured people checking for known issues with MS Teams on Gentoo won't have any indication that is might not work on their system: https://bugs.gentoo.org/buglist.cgi?quicksearch=net-im%2Fteams. I simply don't understand what would have been the problem with (either of): 1. Emerging net-im/teams (if you didn't already) and reporting if you can reproduce this or not (along with your system information. The very least this would give me some pointers what part(s) of my system are to likely to blame. 2. If it runs fine on your system and you feel gratious, emerging gui-wm/sway with USE=-X and report the result. This would help to confirm (or not!) my hunch that Wayland is triggerin this. 3. Telling me what additional info might re useful to track this down. Note that you could still easily suggest the other channels to follow up if you feel those to be more appropriate (or maybe just convenient, which is perfectly fine as far as I am concerned). 4. Leaving this bug open so others that might be affected (or care) to help can find it more easily instead of hiding it behind a fake resolution. I know you don't owe me anything and I am not trying to come across demanding or attack anyone. Neither does this change my personal opionion on Gentoo (after running it for over a decade). But I think especially about people new to Gentoo, who just managed to setup their first system by themselves, installed a package they need (for example for their job), find it fail, research how to fix it, give up, research how to report issues, file their very first bug report, and then get put off like this - that's a really bad experience and one of the worst possible introductions to the Gentoo community. They did their best, are told it's there fault, and - with no further informantion - pointed to several other channels they are unfamiliar with. How many of those would risk being told off again on a mailing list or IRC? How many of those (potentially younger) users are familiar with IRC and mailing list? And how many of those would simply install Arch to get their software to run? ;-) If Gentoo wants to succeed in the long run (and I know I want it to), it will require a new generation of maintainers and developers. Not being able to report issues on GitHub is already a hurdle some might not be willing to take. But at least those who are willing to try 'the Gentoo way' should receive a warm welcome if you ask me. Sorry for this overly long rant but thanks to this bug being 'resolved' already, it is unlikely anyone will hear the noise. ;-) Best, Marcel
