Also, why is it that as soon as a new package version is available the old one is immediately removed from the repos? In a situation like this I'd like to downgrade back to abrowser 38 but can't. I had to go back to 33.1 instead.
What is the quickest way to get this problem fixed? It seems like a major
issue like this should be dealt with more quickly.
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... cooloutac
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... lakbk89
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... greatgnu
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... cooloutac
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... gramex
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... cyberhawk
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... matt . ivie
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... matt . ivie
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... strypey
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... greatgnu
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... cooloutac
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... franparpe
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... dhood
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... jbh . tech
- Re: [Trisquel-users] 'Abrowser' behaves strangely after a s... anthonypineiro
