[Desktop-packages] [Bug 1476907] Re: Abrowser 39 crashes (segmentation fault).
Tyler, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1476907 Title: Abrowser 39 crashes (segmentation fault). Status in firefox package in Ubuntu: Fix Released Bug description: This is the same bug that has appeared on the Trisquel GNU/Linux forums: https://trisquel.info/en/forum/abrowser-behaves-strangely-after-system-update I've installed (from the legimet/abrowser-kde ppa) and tested Abrowser on three machines. On one of them, running Ubuntu 14.04 x64, everything is fine. On the other two, both running 14.04 x32, there is an almost instant segmentation fault. Interestingly, the segmentation fault is NOT instant if I load a non-default profile using something like: mkdir ~/Desktop/FF-Temp ; abroswer --profile ~/Desktop/FF-Temp When I load new profiles, I can still trigger the bug by visiting certain websites (DuckDuckGo, Startpage, Google). So, perhaps visiting pages that execute certain HTML elements, javascript, etc. is what is setting this bug off. PS: for whatever it may be worth, after finding, downloading, and installing a .deb package from the FSF mirror of the Trisquel repos, I can confirm that this bug doesn't affect version 38, just 39. Also: to my knowledge, the bug doesn't affect Firefox (although I've removed Firefox from my system in favor of abrowser, so I can't say for sure). For this reason, I've tried to add abrowser to the list of packages, but the website has insisted on changing it to Firefox: "'abrowser' is a binary package. This bug has been assigned to its source package 'firefox' instead." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1476907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1476907] Re: Abrowser 39 crashes (segmentation fault).
I haven't experienced this bug quite some time. It's safe to say this bug has been fixed. If admin could make this bug as closed, that would be great. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1476907 Title: Abrowser 39 crashes (segmentation fault). Status in firefox package in Ubuntu: Confirmed Bug description: This is the same bug that has appeared on the Trisquel GNU/Linux forums: https://trisquel.info/en/forum/abrowser-behaves-strangely-after-system-update I've installed (from the legimet/abrowser-kde ppa) and tested Abrowser on three machines. On one of them, running Ubuntu 14.04 x64, everything is fine. On the other two, both running 14.04 x32, there is an almost instant segmentation fault. Interestingly, the segmentation fault is NOT instant if I load a non-default profile using something like: mkdir ~/Desktop/FF-Temp ; abroswer --profile ~/Desktop/FF-Temp When I load new profiles, I can still trigger the bug by visiting certain websites (DuckDuckGo, Startpage, Google). So, perhaps visiting pages that execute certain HTML elements, javascript, etc. is what is setting this bug off. PS: for whatever it may be worth, after finding, downloading, and installing a .deb package from the FSF mirror of the Trisquel repos, I can confirm that this bug doesn't affect version 38, just 39. Also: to my knowledge, the bug doesn't affect Firefox (although I've removed Firefox from my system in favor of abrowser, so I can't say for sure). For this reason, I've tried to add abrowser to the list of packages, but the website has insisted on changing it to Firefox: "'abrowser' is a binary package. This bug has been assigned to its source package 'firefox' instead." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1476907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1476907] Re: Abrowser 39 crashes (segmentation fault).
FWIW, Abrowser 43 does not seem to have this issue. I guess this bug has been fixed? There is another possibly-related bug: Abrowser crashes (segfault) when attempting to play HTML 5 MP4 videos. As a workaround, one can enter about:config, set "media.fragmented-mp4.gmp.enabled" to false, and set "media.fragmented-mp4.ffmpeg.enabled" to true. You'll probably have to install ffmpeg to play HTML 5 MP4 videos. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1476907 Title: Abrowser 39 crashes (segmentation fault). Status in firefox package in Ubuntu: Confirmed Bug description: This is the same bug that has appeared on the Trisquel GNU/Linux forums: https://trisquel.info/en/forum/abrowser-behaves-strangely-after-system-update I've installed (from the legimet/abrowser-kde ppa) and tested Abrowser on three machines. On one of them, running Ubuntu 14.04 x64, everything is fine. On the other two, both running 14.04 x32, there is an almost instant segmentation fault. Interestingly, the segmentation fault is NOT instant if I load a non-default profile using something like: mkdir ~/Desktop/FF-Temp ; abroswer --profile ~/Desktop/FF-Temp When I load new profiles, I can still trigger the bug by visiting certain websites (DuckDuckGo, Startpage, Google). So, perhaps visiting pages that execute certain HTML elements, javascript, etc. is what is setting this bug off. PS: for whatever it may be worth, after finding, downloading, and installing a .deb package from the FSF mirror of the Trisquel repos, I can confirm that this bug doesn't affect version 38, just 39. Also: to my knowledge, the bug doesn't affect Firefox (although I've removed Firefox from my system in favor of abrowser, so I can't say for sure). For this reason, I've tried to add abrowser to the list of packages, but the website has insisted on changing it to Firefox: "'abrowser' is a binary package. This bug has been assigned to its source package 'firefox' instead." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1476907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1476907] Re: Abrowser 39 crashes (segmentation fault).
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1476907 Title: Abrowser 39 crashes (segmentation fault). Status in firefox package in Ubuntu: Confirmed Bug description: This is the same bug that has appeared on the Trisquel GNU/Linux forums: https://trisquel.info/en/forum/abrowser-behaves-strangely-after-system-update I've installed (from the legimet/abrowser-kde ppa) and tested Abrowser on three machines. On one of them, running Ubuntu 14.04 x64, everything is fine. On the other two, both running 14.04 x32, there is an almost instant segmentation fault. Interestingly, the segmentation fault is NOT instant if I load a non-default profile using something like: mkdir ~/Desktop/FF-Temp ; abroswer --profile ~/Desktop/FF-Temp When I load new profiles, I can still trigger the bug by visiting certain websites (DuckDuckGo, Startpage, Google). So, perhaps visiting pages that execute certain HTML elements, javascript, etc. is what is setting this bug off. PS: for whatever it may be worth, after finding, downloading, and installing a .deb package from the FSF mirror of the Trisquel repos, I can confirm that this bug doesn't affect version 38, just 39. Also: to my knowledge, the bug doesn't affect Firefox (although I've removed Firefox from my system in favor of abrowser, so I can't say for sure). For this reason, I've tried to add abrowser to the list of packages, but the website has insisted on changing it to Firefox: "'abrowser' is a binary package. This bug has been assigned to its source package 'firefox' instead." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1476907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1476907] Re: Abrowser 39 crashes (segmentation fault).
** Description changed: This is the same bug that has appeared on the Trisquel GNU/Linux forums: https://trisquel.info/en/forum/abrowser-behaves-strangely-after-system-update - I've tested Abrowser on three machine. On one of them (running Ubuntu - 14.04 x64) , everything is fine. On the other two (both running 14.04 - x32), there is an almost instant segmentation fault. Interestingly, the - segmentation fault is NOT instant if I load a non-default profile using - something like: + I've installed (from the legimet/abrowser-kde ppa) and tested Abrowser + on three machines. On one of them, running Ubuntu 14.04 x64, everything + is fine. On the other two, both running 14.04 x32, there is an almost + instant segmentation fault. Interestingly, the segmentation fault is NOT + instant if I load a non-default profile using something like: mkdir ~/Desktop/FF-Temp ; abroswer --profile ~/Desktop/FF-Temp - Although visiting certain website (DuckDuckGo, Startpage, Google) gives - me the crash. So, perhaps visiting pages that execute certain HTML - elements, javascript, etc. is what is setting this bug off. + When I load new profiles, I can still trigger the bug by visiting + certain websites (DuckDuckGo, Startpage, Google). So, perhaps visiting + pages that execute certain HTML elements, javascript, etc. is what is + setting this bug off. PS: for whatever it may be worth, after finding, downloading, and installing a .deb package from the FSF mirror of the Trisquel repos, I can confirm that this bug doesn't affect version 38, just 39. Also: to my knowledge, the bug doesn't affect Firefox (although I've removed Firefox from my system in favor of abrowser, so I can't say for - sure). I've tried to add abrowser to the list of packages, but the - website has insisted on changing it to Firefox. + sure). For this reason, I've tried to add abrowser to the list of + packages, but the website has insisted on changing it to Firefox: + + "'abrowser' is a binary package. This bug has been assigned to its + source package 'firefox' instead." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1476907 Title: Abrowser 39 crashes (segmentation fault). Status in firefox package in Ubuntu: New Bug description: This is the same bug that has appeared on the Trisquel GNU/Linux forums: https://trisquel.info/en/forum/abrowser-behaves-strangely-after-system-update I've installed (from the legimet/abrowser-kde ppa) and tested Abrowser on three machines. On one of them, running Ubuntu 14.04 x64, everything is fine. On the other two, both running 14.04 x32, there is an almost instant segmentation fault. Interestingly, the segmentation fault is NOT instant if I load a non-default profile using something like: mkdir ~/Desktop/FF-Temp ; abroswer --profile ~/Desktop/FF-Temp When I load new profiles, I can still trigger the bug by visiting certain websites (DuckDuckGo, Startpage, Google). So, perhaps visiting pages that execute certain HTML elements, javascript, etc. is what is setting this bug off. PS: for whatever it may be worth, after finding, downloading, and installing a .deb package from the FSF mirror of the Trisquel repos, I can confirm that this bug doesn't affect version 38, just 39. Also: to my knowledge, the bug doesn't affect Firefox (although I've removed Firefox from my system in favor of abrowser, so I can't say for sure). For this reason, I've tried to add abrowser to the list of packages, but the website has insisted on changing it to Firefox: "'abrowser' is a binary package. This bug has been assigned to its source package 'firefox' instead." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1476907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1476907] Re: Abrowser 39 crashes (segmentation fault).
** Description changed: This is the same bug that has appeared on the Trisquel GNU/Linux forums: https://trisquel.info/en/forum/abrowser-behaves-strangely-after-system-update I've tested Abrowser on three machine. On one of them (running Ubuntu 14.04 x64) , everything is fine. On the other two (both running 14.04 x32), there is an almost instant segmentation fault. Interestingly, the segmentation fault is NOT instant if I load a non-default profile using something like: mkdir ~/Desktop/FF-Temp ; abroswer --profile ~/Desktop/FF-Temp Although visiting certain website (DuckDuckGo, Startpage, Google) gives me the crash. So, perhaps visiting pages that execute certain HTML elements, javascript, etc. is what is setting this bug off. PS: for whatever it may be worth, after finding, downloading, and installing a .deb package from the FSF mirror of the Trisquel repos, I - can confirm that this bug doesn't effect version 38, just 39. + can confirm that this bug doesn't affect version 38, just 39. + + Also: to my knowledge, the bug doesn't affect Firefox (although I've + removed Firefox from my system in favor of abrowser, so I can't say for + sure). I've tried to add abrowser to the list of packages, but the + website has insisted on changing it to Firefox. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1476907 Title: Abrowser 39 crashes (segmentation fault). Status in firefox package in Ubuntu: New Bug description: This is the same bug that has appeared on the Trisquel GNU/Linux forums: https://trisquel.info/en/forum/abrowser-behaves-strangely-after-system-update I've installed (from the legimet/abrowser-kde ppa) and tested Abrowser on three machines. On one of them, running Ubuntu 14.04 x64, everything is fine. On the other two, both running 14.04 x32, there is an almost instant segmentation fault. Interestingly, the segmentation fault is NOT instant if I load a non-default profile using something like: mkdir ~/Desktop/FF-Temp ; abroswer --profile ~/Desktop/FF-Temp When I load new profiles, I can still trigger the bug by visiting certain websites (DuckDuckGo, Startpage, Google). So, perhaps visiting pages that execute certain HTML elements, javascript, etc. is what is setting this bug off. PS: for whatever it may be worth, after finding, downloading, and installing a .deb package from the FSF mirror of the Trisquel repos, I can confirm that this bug doesn't affect version 38, just 39. Also: to my knowledge, the bug doesn't affect Firefox (although I've removed Firefox from my system in favor of abrowser, so I can't say for sure). For this reason, I've tried to add abrowser to the list of packages, but the website has insisted on changing it to Firefox: "'abrowser' is a binary package. This bug has been assigned to its source package 'firefox' instead." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1476907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
