Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 299371 - sys-libs/gdbm-1.8.3-r4 breaks pulseaudio
Summary: sys-libs/gdbm-1.8.3-r4 breaks pulseaudio
Status: RESOLVED DUPLICATE of bug 299390
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-02 16:07 UTC by Victor Mataré
Modified: 2010-01-05 04:37 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Victor Mataré 2010-01-02 16:07:39 UTC 
after upgrading to gdbm-1.8.3-r4:
Jan  2 16:30:39 pentium-m-test pulseaudio[22206]: module-device-restore.c: Failed to open volume database '/home/matare/.pulse/866956fe5267412a51f6fa544a19b790-device-volumes': Invalid argument
Jan  2 16:30:39 pentium-m-test pulseaudio[22206]: module.c: Failed to load  module "module-device-restore" (argument: ""): initialization failed.
Jan  2 16:30:39 pentium-m-test pulseaudio[22206]: main.c: Module load failed.
Jan  2 16:30:39 pentium-m-test pulseaudio[22206]: main.c: Failed to initialize daemon.
Jan  2 16:30:39 pentium-m-test pulseaudio[22204]: main.c: Daemon startup failed.

Downgrading to gdbm-1.8.3-r3 fixes it.

Reproducible: Always

Steps to Reproduce:
Comment 1 Rafał Mużyło 2010-01-03 13:53:13 UTC 
You can also delete your pulseaudio gdbm files,
but you're going to loose your pulseaudio volume settings
(among other).

Probably enforcing LARGEFILE_SOURCE is responsible for this.

I  wonder how many other apps silently fail in this case.
Comment 2 Rafał Mużyło 2010-01-03 18:23:11 UTC 
Well, and here's bug 299390.
Who's next ?
Is there a tool that could dump the content of old files
and import them later ?
Comment 3 SpanKY gentoo-dev 2010-01-05 04:37:44 UTC 

*** This bug has been marked as a duplicate of bug 299390 ***