Bug#859217: closed by "Steinar H. Gunderson" <sgunder...@bigfoot.com> (Re: Bug#859217: nageru: just segfaults)
On Sat, Apr 01, 2017 at 08:46:34PM +0200, Steinar H. Gunderson wrote: > I found a relatively clean fix and uploaded it to unstable. Please test if it > works for you before I send it on to the release team. Seemingly it was unblocked without any action on my behalf: Migration status: OK: Will attempt migration (Any information below is purely informational) Maintainer: Steinar H. Gunderson 2 days old (needed 2 days) Ignoring block request by freeze, due to unblock request by nthykier Overriding age needed from 10 days to 2 by nthykier Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nageru.html Valid candidate I suppose that means someone tested it and found it working for them. :-) /* Steinar */ -- Homepage: https://www.sesse.net/
Bug#859217: closed by "Steinar H. Gunderson" <sgunder...@bigfoot.com> (Re: Bug#859217: nageru: just segfaults)
On Sat, Apr 01, 2017 at 08:58:11AM +0200, Steinar H. Gunderson wrote: > While I agree failing to show a friendly message is a bug, I'm not sure > whether it fits the definition of grave (“makes the package in question > unusable or mostly so”). I'll try to investigate how easy it is to show > something friendlier -- I honestly don't know, and it would probably require > poking a bit around into Qt implementation details. At that point, it will > be up to the release team to see if they will accept an upload to stretch to > fix this bug. I found a relatively clean fix and uploaded it to unstable. Please test if it works for you before I send it on to the release team. /* Steinar */ -- Homepage: https://www.sesse.net/
Bug#859217: closed by "Steinar H. Gunderson" <sgunder...@bigfoot.com> (Re: Bug#859217: nageru: just segfaults)
severity 859217 important thanks On Sat, Apr 01, 2017 at 02:34:13AM +0300, Adrian Bunk wrote: > I am also getting segfaults when trying to start Nageru on my computer > (old AMD card). > > Whether Nageru is ever expected to work on my or Antonios computer is > one thing. > > But failing with a segfault is clearly a bug in the error handling. > > It is fine to display a window "Sorry, your hardware is not supported", > segfaulting just causes user confusion. [1] Hi, While I agree failing to show a friendly message is a bug, I'm not sure whether it fits the definition of grave (“makes the package in question unusable or mostly so”). I'll try to investigate how easy it is to show something friendlier -- I honestly don't know, and it would probably require poking a bit around into Qt implementation details. At that point, it will be up to the release team to see if they will accept an upload to stretch to fix this bug. /* Steinar */ -- Homepage: https://www.sesse.net/
Bug#859217: closed by "Steinar H. Gunderson" <sgunder...@bigfoot.com> (Re: Bug#859217: nageru: just segfaults)
Control: reopen -1 On Fri, Mar 31, 2017 at 09:09:10PM +, Debian Bug Tracking System wrote: >... > On Fri, Mar 31, 2017 at 05:51:51PM -0300, Antonio Terceiro wrote: > > Thread 1 "nageru" received signal SIGSEGV, Segmentation fault. > > 0x5557eea1 in MainWindow::relayout (this=0x7fffddc0) at > > mainwindow.cpp:877 > > 877 double preview_label_height = > > previews[0]->title_bar->geometry().height() + > > (gdb) quit > > A debugging session is active. > > > > Inferior 1 [process 2821] will be killed. > > OK, so at this point, basically Qt failed to initialize any OpenGL widgets. > > > OpenGL vendor string: Intel Open Source Technology Center > > OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile > > OpenGL version string: 2.1 Mesa 13.0.6 > > Here's essentially your problem. Ironlake is the very first series of Intel's > HD Graphics; it's six full architecture generations behind the curve. It > doesn't > have the features Nageru needs, nor the performance to actually process HD > video at the quality point Nageru aims for. > > >> FWIW, Nageru requires support for OpenGL 3.1, which is now eight years old > >> (and lots of hardware older than eight years support it by means of newer > >> drivers). > > I guess my hardware sucks and that's it? > > Unfortunately, yes. Thanks for reporting the issue and helping to track it > down so quickly, but this isn't supported, and isn't going to be. Thus, I'm > closing this. >... I am also getting segfaults when trying to start Nageru on my computer (old AMD card). Whether Nageru is ever expected to work on my or Antonios computer is one thing. But failing with a segfault is clearly a bug in the error handling. It is fine to display a window "Sorry, your hardware is not supported", segfaulting just causes user confusion. [1] cu Adrian [1] and when Ubuntu zesty is released in 2 weeks with Nageru, they might start getting many automated crash reports -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
