Bug 8499 - XSane crashes during scanning
Summary: XSane crashes during scanning
Status: RESOLVED DUPLICATE of bug 8473
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Tomas Kindl
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-25 13:42 CET by Vit Brezina
Modified: 2014-02-05 23:32 CET (History)
1 user (show)

See Also:
Source RPM: xsane-0.998-2.mga3
CVE:
Status comment:


Attachments

Description Vit Brezina 2012-12-25 13:42:36 CET
Description of problem:
After run scanning or preview scanning, XSane crashed
Error:
process 4451: arguments to dbus_connection_send() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3261.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace 

When XSane runs as root, scanning works correctly.
Scanner: HP Officejet 6500 plus


Version-Release number of selected component (if applicable):
xsane-0.998-2.mga3
dbus-1.6.8-2.mga3
hplip-3.12.9-2.mga3

How reproducible:

Steps to Reproduce:
1.Star XSane
2.Run preview or scan
Manuel Hiebel 2012-12-25 14:13:39 CET

Assignee: bugsquad => supp

Comment 1 Bit Twister 2012-12-25 23:29:59 CET
(In reply to comment #0)

> When XSane runs as root, scanning works correctly.

Usually runs as root, fails as user is a priv problem. 

I would try adding the "saned" group to the user's account. Be careful that you do not change the users primary group. 

There is a known dbus limit problem on 64 bit installs. I would suggest installing my solution just to rule out a dbus problem.
https://bugs.mageia.org/show_bug.cgi?id=8473#c2

CC: (none) => junk_no_spam

Comment 2 Vit Brezina 2012-12-26 21:39:59 CET
Group "saned" is not standard linux group after instalation.
I created this group and add it to user. But without solution. 
(I'm not sure I created a group correctly)
Comment 3 Bit Twister 2012-12-26 22:28:38 CET
(In reply to comment #2)
> Group "saned" is not standard linux group after instalation.

Well I always install the saned rpm and wind up with an entry in passwd and group.
If you have not installed the saned rpm remove your saned group and do so. If you did install the saned rpm, you should have something like

$ grep sane /etc/passwd
saned:x:481:414:system user for saned:/home/saned:/bin/false
saned:x:414:

uid/gid is variable depending on what is installed before the  installation of saned rpm.


There is a bug report against the /home/snaned. After install I 
mkdir -p /var/saned
and change /home/saned to /var/saned
Comment 4 Vit Brezina 2012-12-27 00:38:06 CET
Not solution. I still have error.

I make this steps

1. remove created group saned
2. check /etc/group and /etc/passwd - saned not found
3. install rpm saned-1.0.23-2.mga3
4. check /etc/passwd - found:
saned:x:489:482:system user for saned:/home/saned:/bin/false
5. check /etc/group - found:
saned:x:482:
6. add group saned to user
7. in /etc/passwd changed /home/saned to /var/saned
8. create mkdir -p /var/saned
Comment 5 Bit Twister 2012-12-27 01:09:23 CET
(In reply to comment #4)
> Not solution. I still have error.

> 6. add group saned to user

I hope you logged out/in before testing. Anytime you change group for a user,
that user has to log out/in to get the group change.

If you made the change I suggested in comment 1, and have rebooted, and test fails, I have no other suggestions.
Comment 6 Vit Brezina 2012-12-27 09:58:30 CET
(In reply to comment #5)
> I hope you logged out/in before testing. Anytime you change group for a user,
> that user has to log out/in to get the group change.

Ofcourse. My last step (after step 6) was rebooting all computer. I forgot to write.

> If you made the change I suggested in comment 1, and have rebooted, and test
> fails, I have no other suggestions.

Thank you for your efforts.
Comment 7 Vit Brezina 2012-12-27 10:02:08 CET
(In reply to comment #6)
> Ofcourse. My last step (after step 6) was rebooting all computer. I forgot to
> write.
Excuse me. I make reboot after step 8.
Comment 8 Vit Brezina 2012-12-29 10:40:21 CET
The problem is solved.
I went back to comment #1. The solution is described in the bug 8473.
Add group "saned" to user is not required.

> (In reply to comment #1)
> 
> There is a known dbus limit problem on 64 bit installs. I would suggest
> installing my solution just to rule out a dbus problem.
> https://bugs.mageia.org/show_bug.cgi?id=8473#c2
Comment 9 Vit Brezina 2014-02-05 23:32:47 CET
I am closing as duplicate

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.