tagtool doesn't start, Failed to read preferences file

[ar3ac]

Binary package hint: tagtool

$ tagtool
I/O warning : failed to load external entity "/home/ar3ac/.tagtoolrc"

** (tagtool:6332): WARNING **: Failed to read preferences file
Segmentation fault (core dumped)

[Curtis (cgminardi-gmail)]

I can confirm this bug in Hardy Heron (8.04) Alpha 6 running the latest packages. To generate this bug, simply install tagtool and its dependencies. Then attempt to run it and it will crash with a segmentation fault. Here are the specific package version numbers:

tagtool: 0.12.3-3ubuntu2 (hardy)
libid3-3.8.3c2a: 3.8.3-7ubuntu2 (hardy)

All other packages required by tagtool and libid3... are standard libraries of the GNOME desktop environment, Linux, the GCC, or other shared libraries for numerous working applications.

It seems like during a rebuild of the package that something was left out, namely the code to generate a ".tagtoolrc" file in a user's local directory or just to package the file. It is a simple packaging error and a minor regression as far as I can tell.

I have tried installing older versions from the Gutsy package archives but they have the same error. Something went awry with the build.

[Brandon S Hosey (bshosey-deactivatedaccount)]

Fresh install of Hardy with all the update and I still get this bug as well

[Cesare Tirabassi (norsetto)]

The .tagtoolrc preferences file is not packaged, but created at the first startup (if not existing already).
The warning message is normal and should not appear anymore after the first start.

[Murat Gunes (mgunes)]

The message appears every time, and tagtool segfaults every time, perhaps failing to create the file.

[Cesare Tirabassi (norsetto)]

I don't have any evidence that the segfault is related to the .tagtoolrc file. I can't reproduce this on my machine, so it would really help if anyone could provide a backtrace:

https://wiki.ubuntu.com/Backtrace

Try also the attached one and see if it finds it and/or segfaults again.

[Cesare Tirabassi (norsetto)]

Just in case, the file should be owned by you and your group and permission flags set to 644.

[Brandon S Hosey (bshosey-deactivatedaccount)]

OK. I created a file with the attachment you sent me. I made sure my
user account had right and read access to the file. Then I ran tagtool
again. I did the same. But it does create a file .tagtoolrc~ every time
it tries to start

Thanks.

On Sun, 2008-04-06 at 09:00 +0000, Cesare Tirabassi wrote:
> I don't have any evidence that the segfault is related to the .tagtoolrc
> file. I can't reproduce this on my machine, so it would really help if
> anyone could provide a backtrace:
>
> https://wiki.ubuntu.com/Backtrace
>
> Try also the attached one and see if it finds it and/or segfaults again.
>
> ** Changed in: tagtool (Ubuntu)
> Importance: High => Undecided
>

[Cesare Tirabassi (norsetto)]

I really need a backtrace to be able to debug this properly; I start wondering if this isn't the same as bug 201631 after all. Do you have something mounted in /media which is not a "normal" device?

[Murat Gunes (mgunes)]

Looks like the same bug.

[Cesare Tirabassi (norsetto)]

Good, marking this as duplicate of 201631 then.