Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#21635 - [gamin] gam_server refuses to freeze when suspending to disk
Attached to Project:
Community Packages
Opened by squal (squal) - Monday, 08 November 2010, 10:13 GMT
Last edited by Jakob Gruber (schuay) - Wednesday, 04 May 2011, 18:50 GMT
Opened by squal (squal) - Monday, 08 November 2010, 10:13 GMT
Last edited by Jakob Gruber (schuay) - Wednesday, 04 May 2011, 18:50 GMT
|
DetailsDescription:gamin (gam_server) refuses to freeze when trying to suspend to disk
Additional info: * package version(s) : 0.1.10-4 x86_64 * config and/or log files etc. I'm running xfce + cairo_dock as a graphical environnment, i'm connected to other computers on a samba net - but no directory browsed or files open at the moment I try to suspend. Suspend has worked for 3 years with no problem, and with gamin (not fam) I downgraded to gamin 0.1.10-3 : it seems to solve the problem entirely. Here is the dmesg after suspend fails : --------- PM: Marking nosave pages: 000000000009f000 - 0000000000100000 PM: Basic memory bitmaps created PM: Syncing filesystems ... done. Freezing user space processes ... Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze): gam_server D 0000000000000000 0 2123 1 0x00800004 ffff88006c497bb8 0000000000000086 ffffffff814ef020 0000000000000246 0000000000014f40 0000000000014f40 ffff88006c497fd8 ffff88006c497fd8 ffff88006c497fd8 ffff88007c37be70 ffff88006c497fd8 0000000000014f40 Call Trace: [<ffffffff81071c4b>] ? prepare_to_wait+0x5b/0x90 [<ffffffffa12b1375>] fuse_request_send+0x225/0x290 [fuse] [<ffffffff810719b0>] ? autoremove_wake_function+0x0/0x40 [<ffffffffa12b8282>] fuse_do_open+0xd2/0x170 [fuse] [<ffffffffa12b840f>] fuse_open_common+0x6f/0x90 [fuse] [<ffffffff811390ce>] ? __d_lookup+0x15e/0x180 [<ffffffffa12b3690>] ? fuse_dir_open+0x0/0x10 [fuse] [<ffffffffa12b369e>] fuse_dir_open+0xe/0x10 [fuse] [<ffffffff8112229b>] __dentry_open+0x11b/0x3c0 [<ffffffff811a2c5a>] ? security_inode_permission+0x1a/0x20 [<ffffffff811234d4>] nameidata_to_filp+0x54/0x70 [<ffffffff81131800>] do_last+0x480/0x740 [<ffffffff81131cad>] do_filp_open+0x1ed/0x680 [<ffffffff811311cd>] ? user_path_at+0x5d/0xa0 [<ffffffff8113d284>] ? alloc_fd+0xf4/0x150 [<ffffffff81123554>] do_sys_open+0x64/0x130 [<ffffffff8112363b>] sys_open+0x1b/0x20 [<ffffffff81009e82>] system_call_fastpath+0x16/0x1b Restarting tasks ... done. --------- Steps to reproduce: 1. Check that gam_server is running 2. suspend to disk (I push a button, uing the command does the same) 3. wait 20 seconds 4. the screen returns to previous state, browse dmesg to see the message above |
This task depends upon
Closed by Jakob Gruber (schuay)
Wednesday, 04 May 2011, 18:50 GMT
Reason for closing: Upstream
Additional comments about closing: Bug report sent upstream
Wednesday, 04 May 2011, 18:50 GMT
Reason for closing: Upstream
Additional comments about closing: Bug report sent upstream
As previously stated, I downgraded to release 3, it seemed to work again. But then, a few days ago, it failed to freeze again !
I still can't find the precise steps to reproduce this case : it works, I freeze / unfreeze with no problem, but then one day, it refuses until I kill gam_server.
There must be a specific thing I do that put gamin in a special state, or maybe another application has strange side effects, but still no idea which one.
I "stripped" my actions lately to : run xfce+cairo-dock, open thunar, open a video with vlc, use firefox. Quod-libet is always open.
I may add that a ntfs partition is mounted permanently, in read only. Lately I tried not even to access files on this partition.
In order to make further tests, could you explain hwo to start gam_server properly after I kill it ? (I tried to launch it "as is" but thunar seemed not aware of files modifications. I may try to logon/logoff but it's seriously a pain ;-) )
(btw : I have python2, even if this piece of info seems irrelevant now)
Opened an upstream bug report at https://bugzilla.gnome.org/show_bug.cgi?id=634900 .