| Summary: | xsane doesn't work in kde | ||
|---|---|---|---|
| Product: | unknown | Reporter: | Tom Gufler <tom.gufler> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | andresbajotierra, zaai |
| Priority: | NOR | Keywords: | investigated, triaged |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Tom Gufler
2009-01-18 20:58:26 UTC
What GTK style are you using? If you are using gtk-qt-engine this may cause the fault Anyways, this seems to be totally unrelated to KDE Same problem here. xsane works fine in xfce, but aborts in KDE. I suspect a xsane problem though.
Last few lines o fstrace:
open("/usr/local/Brother/sane/Brsane2.ini", O_RDONLY) = 182
fstat64(182, {st_mode=S_IFREG|0644, st_size=1536, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb4f0f000
read(182, "[Support Model]\n0x0161,10,1,\"MFC-"..., 4096) = 1536
open("/usr/local/Brother/sane/Brsane2.ini", O_RDONLY) = 183
fstat64(183, {st_mode=S_IFREG|0644, st_size=1536, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb4f0e000
read(183, "[Support Model]\n0x0161,10,1,\"MFC-"..., 4096) = 1536
select(1024, NULL, [178], NULL, {3, 0}) = 1 (out [178], left {3, 0})
send(178, "\33Q\n\200"..., 4, 0) = 4
gettimeofday({1234075096, 57638}, {0, 0}) = 0
gettimeofday({1234075096, 57660}, {0, 0}) = 0
select(1024, [178], NULL, NULL, {20, 0}) = 1 (in [178], left {19, 980000})
recv(178, "\301\0\16\3\377?\6\0\6\0\0\6\0\1\4\1"..., 272, 0) = 16
close(178) = 0
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(15174, 15174, SIGABRT) = 0
--- SIGABRT (Aborted) @ 0 (0) ---
+++ killed by SIGABRT +++
The USB connection requires the user to be a member of the scanner group. The network connection aborts as shown above. This may be related to bug 182973 Is this still happening with a recent and stable KDE version ? If it is still happening, can you provide a backtrace of the crash? (KDE unstable versions modify a glib env var that may cause the applications to crash: bug 196207 Thanks Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |