Bug 1346811
| Summary: | Hibernation fails when Google Chrome is running, not otherwise | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Patrick O'Callaghan <poc> | ||||
| Component: | hibernate | Assignee: | gil cattaneo <puntogil> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 23 | CC: | java-sig-commits, puntogil, rdieter | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-06-15 12:19:18 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This is a Java package. What has that to do with the issues reported? Nothing. Please, select the correct component. This bug will be closed. If I recall correctly too, this is a chrome feature, to inhibit sleep/shutdown if there are active downloads. (In reply to Rex Dieter from comment #2) > If I recall correctly too, this is a chrome feature, to inhibit > sleep/shutdown if there are active downloads. Sorry, this is not the right component. This library provides "object/relational persistence and query service for Java" (In reply to gil cattaneo from comment #3) > (In reply to Rex Dieter from comment #2) > > If I recall correctly too, this is a chrome feature, to inhibit > > sleep/shutdown if there are active downloads. > > Sorry, this is not the right component. > This library provides "object/relational persistence and query service for > Java" In that case I would appreciate a pointer to what would be the correct component. Since it's unclear exactly what is failing, I simply searched for "hibernate" in the bug reporting tool and got this. Apologies if that's wrong. (In reply to Rex Dieter from comment #2) > If I recall correctly too, this is a chrome feature, to inhibit > sleep/shutdown if there are active downloads. I've been using Chrome for years and hibernation for several months now, but this has never happened before. However, best leave discussion to whatever is the correct component. (In reply to Patrick O'Callaghan from comment #4) > (In reply to gil cattaneo from comment #3) > > (In reply to Rex Dieter from comment #2) > > > If I recall correctly too, this is a chrome feature, to inhibit > > > sleep/shutdown if there are active downloads. > > > > Sorry, this is not the right component. > > This library provides "object/relational persistence and query service for > > Java" > > In that case I would appreciate a pointer to what would be the correct > component. Since it's unclear exactly what is failing, I simply searched for > "hibernate" in the bug reporting tool and got this. Apologies if that's > wrong. run "locate hibernate" after run "rpm -qf /usr/sbin/pm-hibernate" maybe could help for the next time correct component would be "chrome" (not in fedora) (In reply to Rex Dieter from comment #7) > correct component would be "chrome" (not in fedora) then this bug is useless Yes it is, though as mentioned, I suspect this is a feature not a bug (in chrome) (In reply to Rex Dieter from comment #9) > Yes it is, though as mentioned, I suspect this is a feature not a bug (in > chrome) Take a look here, if you are not aware: https://bugzilla.redhat.com/show_bug.cgi?id=1270322 I do understand that Chrome is not a Fedora component. I reported the bug because I didn't realise that a non-privileged process could inhibit hibernation (the fact that it was Chrome wasn't really the point). I'm still somewhat surprised at that, but if it's system policy then there's nothing to be done. However the journal message quoted earlier doesn't say anything about policy, it reports the non-hibernation as a failure with no explanation. I'll report this under systemd, which is where it should probably go. if you click on the plasma powermanagement/battery applet, it should display all current/active inhibitors. other examples of where this inhibitor feature can be used: media players: you don't want your computer to go to sleep with playing a video, for example (In reply to Rex Dieter from comment #12) > if you click on the plasma powermanagement/battery applet, it should display > all current/active inhibitors. I haven't been using that since this is a desktop system with no battery. I'll check it out. > other examples of where this inhibitor feature can be used: > media players: you don't want your computer to go to sleep with playing a > video, for example I understand that, however there's a difference between automatic power-saving and deliberate hibernation. If I use a manual control to hibernate the system I actually want it to turn off. In any case, I reported this under: https://bugzilla.redhat.com/show_bug.cgi?id=1346908 |
Created attachment 1168334 [details] Section of journal showing hibernation failure Description of problem: On selecting Hibernate from the KDE menu when Google Chrome is running, the screen blanks for a few seconds and then comes back up as before. If Chrome is not running, the system hibernates correctly (and restores correctly). Version-Release number of selected component (if applicable): kernel-4.4.9-300.fc23.x86_64 google-chrome-stable-51.0.2704.84-1.x86_64 systemd-222-14.fc23.x86_64 How reproducible: 100% Steps to Reproduce: 1. Run Chrome 2. Select Hibernate from KDE menu Actual results: Screen blanks, then returns to normal. Expected results: System hibernates. Additional info: The first time this happened, journalctl showed an error (see attachment), but on subsequent occasions there is nothing related to hibernation, just many SElinux violations for Chrome. However these have been going on for months now with no obvious effect, while the present bug started only on a recent system update.