Sorry for not getting back, but I realized that it was a kernel setting,
something to do with (relatively old) glibc compatibility. I can't remember
the name exact option, but I'm pretty sure no standard distro kernel
disables that. As soon as I recompiled my custom kernel with the option
back on a
control: tag -1 unreproducible
control: severity -1 important
* shirish शिरीष:
>> I can reproduce the bug on neither amd64 (4.9.0-1-amd64) nor i386
>> (4.9.0-1-686-pae).
>
> Could you share what attempts you did to see if the error occurs ?
Sure. I created a fresh rar archive containing just my
at bottom :-
On 25/02/2017, Hilko Bengen wrote:
> Hi,
>
> I can reproduce the bug on neither amd64 (4.9.0-1-amd64) nor i386
> (4.9.0-1-686-pae).
>
> Cheers,
> -Hilko
>
> --
> To unsubscribe, send mail to 820381-unsubscr...@bugs.debian.org.
>
Could you share what attempts you did to see if the er
Hi,
I can reproduce the bug on neither amd64 (4.9.0-1-amd64) nor i386
(4.9.0-1-686-pae).
Cheers,
-Hilko
control: tag -1 moreinfo
I tried rar on up to date i386 and amd64 stretch systems. Versions
5.3 and 5.4 both work fine for me.
I am not sure if this is related or not, but linux 4.8.15-1 changes
vsyscall, which was mentioned in message #25.
Has anyone else tested this lately?
Best wishes,
Mike
A very good question. I remember building this, I remember signing
and uploading this... I think I even remember sitting around waiting
for the emails for it.
When I get back to my dev machine on Monday, I'll try and remember to
have a look, though I think I recently deleted the files.
If so, I'
Dear Martin,
I see this issue on RC bug list.
> I've just pushed a new version of rar to the repo, can you let me know
> if this has fixed the issue?
I don't see there's a Vcs-* in debian/control [0].
And latest release in debian was on year 2015 [1].
[0] https://sources.debian.net/src/rar/2:5.
Package: rar
Version: 2:5.3.b2-1
Followup-For: Bug #820381
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the
I've just pushed a new version of rar to the repo, can you let me know
if this has fixed the issue?
Regarding it crashing, tehre's not much I can do now other than pass
back the issue to the developers... The troubles with non-free :(
Package: rar
Version: 2:5.3.b2-1
Followup-For: Bug #820381
Sure, I'll attach a dump.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimenta
Package: rar
Version: 2:5.3.b2-1
Followup-For: Bug #820381
Btw,I have this in syslog:
[152168.040770] rar[8954] vsyscall attempted with vsyscall=none
ip:ff600400 cs:33 sp:7fffcfb4a928 ax:ff600400 si:0
di:7fffcfb4a948
-- System Information:
Debian Release: stretch/sid
APT
Any chance you can run rar with strace or similar to provide a backtrace?
On 7 April 2016 at 20:26, Alexandre Pereira Nunes wrote:
> Package: rar
> Version: 2:5.3.b2-1
> Severity: serious
>
> Rar crashes in all evocations.
>
>
> -- System Information:
> Debian Release: stretch/sid
> APT prefers
Package: rar
Version: 2:5.3.b2-1
Severity: serious
Rar crashes in all evocations.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures:
13 matches
Mail list logo
