|
Bugzilla – Full Text Bug Listing |
| Summary: | gnome: gnome-screenshot can not save image files | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Casual J. Programmer <casualprogrammer> |
| Component: | GNOME | Assignee: | E-mail List <gnome-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | casualprogrammer |
| Version: | Alpha 6 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | manager review | ||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | output from strace | ||
|
Description
Casual J. Programmer
2007-07-30 11:31:32 UTC
could you stop filing every problem you find as blocker bug? Many thanks Sure I could, although I only report blocked items as blocker. Taking a screenshot is blocked, isn't it ? Btw, when logging in as root, gnome-screenshot can save the image normally. I'm currently unable to replicate this. If you run gnome-screenshot on the command line, can you see any warnings/errors? No, alas not, it just sits there until terminated. Doing it as root works though. Using the -debuginfo is of little help, as no error is taking place, or can I make it log something ? Do an strace on the program. From a terminal: cjp@workstation6l:~> gnome-screenshot GTK Accessibility Module initialized Bonobo accessibility support initialized from a second one: cjp@workstation6l:~> ps -A | grep screen 8202 pts/0 00:00:00 gnome-screensho cjp@workstation6l:~> ps -A | grep screen 8219 pts/0 00:00:00 gnome-screensho cjp@workstation6l:~> strace -o Desktop/gnomeshot.txt -p 8219 Process 8219 attached - interrupt to quit Process 8219 detached Then activating "Save" in the screenshot menu, waiting a minute or so, then terminating. gnomeshot.txt see attachment. Seem to be missing the attachment. Created attachment 154654 [details]
output from strace
OK, had to remove some entries as file too large. there were endless repetitions of the same lines:
read(23, "\1\0\0\0\2\0\0\0\0\0\0\0\20\0\0\0gnomeshot.txt\0\0\0", 1024) = 32
.
.
gettimeofday({1185905137, 648635}, NULL) = 0
.
.
gettimeofday({1185905137, 736857}, NULL) = 0
time(NULL) = 1185905137
which I "condensed" somwewhat.
You mention in other bugs about using LDAP, are you using it here? I am using LDAP generally for logging in as "normal" user ( server & client on same workstation ) but this also happens for local users. I can't figure out how do trip this, nor can Mark. I'm going to make it normal for now CJP since we've got no other reports. Can you think of anything else particular to your setup? Well, I suspect it has to do with setting up the installation with LDAP users. With the latest "clean" install I ran into some weird problems when no local user, but only LDAP users ( my usual setup ) are configured. After doing the umpteenth "clean" install from beta1 DVD, I decided to leave the LDAP stuff alone for the moment. Having only local users seems to solve( rather avoid ) some of the problems I keep experiencing. Presently taking a screenshot works nicely. CJP, I'm going mark this as a duplicate of 299135. If after following up there this is still and issue, please re-open. *** This bug has been marked as a duplicate of bug 299135 *** |