Bug 1184453
Summary: | mouse cursor is invisible for 1 minute after log in, g-s-d seems to be stuck waiting for cups | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||||||
Component: | cups | Assignee: | Tim Waugh <twaugh> | ||||||||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | rawhide | CC: | awilliam, bnocera, bochecha, bugzilla, danofsatx, eblake, fmuellner, jpopelka, kalevlember, mkasik, ofourdan, robatino, rstrode, russel, tiagomatos, twaugh | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | AcceptedBlocker | ||||||||||||
Fixed In Version: | cups-2.0.1-2.fc22 | Doc Type: | Bug Fix | ||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2015-01-27 13:05:32 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: | |||||||||||||
Bug Depends On: | |||||||||||||
Bug Blocks: | 1043125 | ||||||||||||
Attachments: |
|
Description
Kamil Páral
2015-01-21 12:49:48 UTC
Created attachment 982304 [details]
system journal after the 1 minute timeout has passed
Created attachment 982305 [details]
rpm -qa output
Created attachment 982307 [details]
gnome terminal before timeout - graphical glitch
Created attachment 982308 [details]
gnome-terminal after timeout - no glitch
I'm proposing this as an F22 Alpha Blocker, because it violates all our desktop-related criteria - you can hardly operate e.g. a web browser or the very gnome-shell interface without a cursor. I'd appreciate more testing from other people without a different environment, maybe this can be caused by some local network printers or something. I'm seeing the same bug on my Rawhide laptop. I have no printers here, neither local nor on the network. Oh, someone finally tracked this down? Good. I see it in a clean VM, but not on my daily-use desktop (which does have a printer). I'm not totally sure I'd agree it's an Alpha blocker as the cursor *does* appear after a fairly short delay, but it'd certainly be good to have it fixed, and I'd definitely be +1 Final and possibly Beta. Just to chip in a few observations in the hope it helps someone solve the problem: I see the problem on my laptops (Lenovo T500 and Lenovo X201), but not on my workstation (Dell Precision T5400, GeForce 610 graphics card). All have my two printers defined. The workstation has to run kernel 3.18 because the NVIDIA driver will not install in 3.19-rcX, the laptops are running 3.19-rc5. I haven't tried with 3.18 on the laptops. Brightness control does not work during the "no cursor" period. As soon as the cursor appears, brightness control works fine. Whilst early adopters can cope with a short period of missing cursor, I feel this should be treated as an immediate blocker as it is really infuriating even to early adopters. I see it on a Dell XPS 9333 laptop, it's a problem so I'm +1 as alpha blocker. This is a bug in cups. I can reproduce the problem using "lpstat -s" from console. It is probably a problem in activating of cups via socket. Second run of "lpstat -s" is not delayed even when run during run of the first one. It worked with cups-1.7.5-7. I'm reassigning this bug to cups. Discussed a Fedora Blocker Review Meeting 2015-01-26 http://meetbot.fedoraproject.org/fedora-blocker-review/2015-01-26/f22-blocker-review.2015-01-26-17.00.log.txt AcceptedBlocker for Beta - This bug conditionally violates the Alpha criterion ""It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments." by making it difficult/impossible to do anything within the GUI, the violation is considered serious enough to block Beta but not Alpha The systemd notify support had broken in the port to 2.0.0. Great, this new build fixes the problem for me! Can somebody else confirm? Yup, confirmed here also. (I think it also fixed https://bugzilla.gnome.org/show_bug.cgi?id=741683 , for me...) |