maemo.org Bugzilla – Full Text Bug Listing
|Summary:||Placing a call in portrait mode gets desktop stuck in portrait mode upon exit.|
|Product:||[Maemo Official Applications] Chat & Call & SMS||Reporter:||twoboxen|
|Component:||Call Application UI||Assignee:||rtcomm <rtcomm>|
|Status:||RESOLVED FIXED||QA Contact:||call-ui-bugs|
|Priority:||Unspecified||CC:||andre_klapper, chemist, jon.hedemann, m, maemo, mb, nix900|
|Bug Depends on:|
SOFTWARE VERSION: (Settings > General > About product) Version: 2.2009.51-1.002 EXACT STEPS LEADING TO PROBLEM: (Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message Connection Failed appears)) 1. Place an outbound call in portrait orientation. 2. End call. 3. Close phone application while still in portrait orientation. EXPECTED OUTCOME: The normal landscape-oriented desktop. ACTUAL OUTCOME: A messed up portrait-oriented desktop. REPRODUCIBILITY: (always, less than 1/10, 5/10, 9/10) always EXTRA SOFTWARE INSTALLED: OTHER COMMENTS: Here is forum link with other users having the same issue. http://talk.maemo.org/showthread.php?p=488520 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6
(In reply to comment #0) > REPRODUCIBILITY: > always Couldn't reproduce even once after 5 attempts. Extra software installed? (Note to self: sounds related to bug 5353).
*** This bug has been confirmed by popular vote. ***
I can confirm this bug. After placing a call from the contacts list with the phone application in portrait mode, and ending the call, the task switcher appears in portrait mode. Open applications (right now when this bug happened): MæPad, gPodder, Contacts. As a workaround, I lock the screen, then press the power button and swipe to unlock, after which the "3D flip" animation appears and switches to landscape mode.
I had the same thing like Thomas and the same workaround. It is gone now. Somehow I have the feeling it has to to with the refelect theme I had installed. but thats a very wild guess and I don't feel like trying to reproduce it because its a royal pain in the neck. Regards Markus
Can somebody provide a screenshot? (Please remove the displayed number if possible, for privacy reasons)
screenshots to be found http://talk.maemo.org/showthread.php?t=43049
I still have this problem after upgrading to latest firmware 3.2008.02-8. I am wondering if bug 9158 should be marked as a duplicate of this bug though it is filed for the latest firmware update.
*** Bug 9158 has been marked as a duplicate of this bug. ***
I know this is quite offtopic, but why do I get mails regarding this bug? I am not subscribed to it.
(In reply to comment #9) > I know this is quite offtopic, but why do I get mails regarding this bug? I am > not subscribed to it. Explained at the bottom of every bugmail you receive... For future discussion please feel free to send me a private email. Thanks.
This issue should be fixed in the next public update. To answer popular followup questions: * Nokia does not announce release dates of public updates in advance. * There is currently no access to these internal, non-public build versions. A Brainstorm proposal to change this exists at http://maemo.org/community/brainstorm/view/undelayed_bugfix_releases_for_nokia_open_source_packages-002/
Setting explicit PR1.2 milestone (so it's clearer in which public release the fix will be available to users). Sorry for the bugmail noise (you can filter on this message).