Bug#919081: kio-gdrive: Unable to create io-slave. klauncher said: error loading gdrive.so

2019-01-12 Thread Benoît Merlet
Package: kio-gdrive
Version: 1.2.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After installing kio-gdrive and configuring a Google account in systemsettings5,
I cannot connect to my Google Drive:

$ LANG=C kioclient5 exec gdrive:/
kf5.kio.core: couldn't create slave: "klauncher said: Error loading « 
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/gdrive.so »."
kf5.kio.widgets: KRun(0xa1c13a10) ERROR 173 "Unable to create io-slave. 
klauncher said: Error loading « 
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/gdrive.so »."

I am not sure how to further debug the problem, but as you can see the
package is quite unusable.

Best regards,
Benoît


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kio-gdrive depends on:
ii  kaccounts-integration  4:17.08.3-1
ii  kio5.51.0-1
ii  libaccounts-qt5-1  1.15-2
ii  libc6  2.28-2
ii  libkaccounts1  4:17.08.3-1
ii  libkf5coreaddons5  5.51.0-1
ii  libkf5i18n55.51.0-1
ii  libkf5kiocore5 5.51.0-1
ii  libkf5kiowidgets5  5.51.0-1
ii  libkf5notifications5   5.51.0-1
ii  libkpimgapicore5abi1   18.08.1-1
ii  libkpimgapidrive5  18.08.1-1
ii  libqt5core5a   5.11.3+dfsg-2
ii  libqt5widgets5 5.11.3+dfsg-2
ii  libstdc++6 8.2.0-13

kio-gdrive recommends no packages.

kio-gdrive suggests no packages.

-- no debconf information


Bug#521860: libpam-modules: libdb upgrade silently breaks pam_userdb.so

2009-04-02 Thread Benoît MERLET
Steve Langasek a écrit :
> If db4.7_dump works at all, I would expect pam_userdb to be able to handle
> the file as well.  Do you get any useful information out of pam_userdb using
> the 'debug' option when using this old db file?

I don't know where to put the 'debug' option...  I have generated the
file attached for you to reproduce.

# cat file.txt
foo
bar

# db3_load -T -t hash -f file.txt file.db
# ls -l
total 16
-rw--- 1 root root 12288 avr  2 10:47 file.db
-rw--- 1 root root 9 avr  2 10:47 file.txt

Hope this will be useful,

Benoît


file.db
Description: Binary data


Bug#521860: libpam-modules: libdb upgrade silently breaks pam_userdb.so

2009-03-30 Thread Benoît MERLET

Raphael Rigo a écrit :

Steve Langasek wrote:

tags 521860 moreinfo
thanks

On Mon, Mar 30, 2009 at 04:49:09PM +0200, Raphael Rigo wrote:

Package: libpam-modules
Version: 1.0.1-9
Severity: grave
Justification: renders package unusable
A recent upgrade in libpam-modules makes it depend on libdb4.7, unfortunately
it seems DB files created with a previous version are NOT compatible with
version 4.7. This makes pam logins based on userdb break silently, with no
error message whatsoever. It would seem this setup is most commonly used for
vsftpd virtual users.
The only apparent solution is to recreate the database file with the newer db
tools.

How did you create the db file initially?  There are not supposed to be any
on-disk incompatibilities with any recent versions of BDB unless you use
transactions, which we don't.



I created it a long time ago (read "years"), probably using db3_load.

Unfortunately, it seems I overwrited the backup I had of the non working
file with a manipulation error. I will check if I have another backup of
it somewhere this evening.

Raphaël


I ran into the same bug.

I have a backup of the inital db file which was created years ago with 
this command :


db3_load -T -t hash -f login.txt login.db

The workaround was to re-generate the db file using db4.7_load.

Here are some information about the former db file :

# db4.7_dump login.db.bkp
VERSION=3
format=bytevalue
type=hash
db_pagesize=4096
HEADER=END
DATA=END

# db4.7_dump -d a login.db.bkp
In-memory DB structure:
hash: 0x48000 (open called, read-only)
meta_pgno: 0
h_ffactor: 0
h_nelem: 0
h_hash: 0xb7fe02b0
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
page 0: hash metadata: LSN [0][0]: level 0
magic: 0x61561
version: 7
pagesize: 4096
type: 8
keys: 0 records: 0
free list: 0
last_pgno: 0
flags: 0
uid: aa f3 19 0 1 8 0 0 30 f5 cf 49 40 15 0 0 0 0 0 0
max_bucket: 1
high_mask: 0x1
low_mask:  0
ffactor: 0
nelem: 0
h_charkey: 0x5e688dd1
	spare points: 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0


Benoît




--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org