LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-29-2012, 05:55 AM   #1
t35t
LQ Newbie
 
Registered: Mar 2012
Posts: 18

Rep: Reputation: Disabled
Slackware64-current GPG Bug


There seems to be a bug in Slackware64-current gpa package that doesn't let the file manager to open to encrypt/decrypt some files.

Open gpa and click FIle manager at the above menu there I suddenly get a Segmentation Fault and the application closes immediately.

On the other hand, there are lots of certificates which I have never added and don't even know where they came from which can also cannot be deleted with an error says 'GPGME library returned an error and the error was ; No Public key'. This doesn't even make sense, this is a clean install.

Anyone can confirm this ?
 
Old 08-29-2012, 06:34 AM   #2
t35t
LQ Newbie
 
Registered: Mar 2012
Posts: 18

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by t35t View Post
There seems to be a bug in Slackware64-current gpa package that doesn't let the file manager to open to encrypt/decrypt some files.

Open gpa and click FIle manager at the above menu there I suddenly get a Segmentation Fault and the application closes immediately.

On the other hand, there are lots of certificates which I have never added and don't even know where they came from which can also cannot be deleted with an error says 'GPGME library returned an error and the error was ; No Public key'. This doesn't even make sense, this is a clean install.

Anyone can confirm this ?
Unidentified certificates I mentioned turned out to be X.509 root certificates. Running with "gpa --disable-x509" solves the listing issue of these unwanted certificates. But on the other hand file manager still crashes, waiting for inputs to get over this...
 
Old 08-29-2012, 06:44 AM   #3
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,447

Rep: Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875
upgrade it to 0.9.3 using the slackbuild.

P.S. (If Pat read this) there are some occurrences of PRGNAM in the slackbuild, instead of PKGNAM

Last edited by ponce; 08-29-2012 at 06:54 AM.
 
Old 08-29-2012, 07:06 AM   #4
t35t
LQ Newbie
 
Registered: Mar 2012
Posts: 18

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ponce View Post
upgrade it to 0.9.3 using the slackbuild.

P.S. (If Pat read this) there are some occurrences of PRGNAM in the slackbuild, instead of PKGNAM
0.9.3 did the trick, thanks. However it would be good to understand the exact problem causing the segfault.
 
Old 08-29-2012, 07:13 AM   #5
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,447

Rep: Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875
If you're curious, you can rebuild 0.9.2 with debug symbols on, avoid the stripping of the binary and investigate with gdb. Personally I don't care that much.

I simply tried the upgrade and worked, one problem less.

EDIT: I made an small effort (but you can do that too ) and read the ChangeLog
Code:
2012-07-13  Daniel Leidert  <dleidert@debian.org>

        Fix a segmentation fault opening file-manager mode.
        * src/fileman.c (file_list_new): s/select/sel, which is undefined.

Last edited by ponce; 08-29-2012 at 07:46 AM.
 
1 members found this post helpful.
Old 08-29-2012, 11:44 PM   #6
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,447

Rep: Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875
sorry t35t, re-reading my answer,it seems to me that I might have sounded a little harsh, but it was not my intention: it's just that I'm very busy ATM so I'm starting to hurry on things (but I shouldn't).
 
Old 08-30-2012, 05:56 AM   #7
t35t
LQ Newbie
 
Registered: Mar 2012
Posts: 18

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ponce View Post
sorry t35t, re-reading my answer,it seems to me that I might have sounded a little harsh, but it was not my intention: it's just that I'm very busy ATM so I'm starting to hurry on things (but I shouldn't).
don't worry about it mate I know you replied with good intentions. Thanks for the help, cheers.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware64-Current Bug in lxc 0.7.5 Jack128 Slackware 7 08-25-2012 12:53 PM
[SOLVED] [Xorg-1.7.5 in Slackware64 -current] still no workie.. Xorg bug? GrapefruiTgirl Slackware 94 07-28-2010 08:23 AM
slackware64-current glibc resolver bug? fancylad Slackware 8 01-31-2010 04:47 PM
Updating from Slackware64-current to Slackware64 13. glore2002 Slackware 4 08-28-2009 06:50 PM
GPG: Bad session key gpg between gpg on linux and gpg gui on windows XP konqi Linux - Software 1 07-21-2009 09:37 AM


All times are GMT -5. The time now is 08:11 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration