Bug 968027 - Unable to logging into gnome on Fedora-Live-Desktop-x86_64-19-Beta
Unable to logging into gnome on Fedora-Live-Desktop-x86_64-19-Beta
Product: Fedora
Classification: Fedora
Component: gnome-bluetooth (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-05-28 15:49 EDT by Markus Mayer
Modified: 2013-06-05 22:26 EDT (History)
1 user (show)

See Also:
Fixed In Version: gnome-bluetooth-3.8.1-1.fc19
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-06-05 22:26:46 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Markus Mayer 2013-05-28 15:49:26 EDT
Description of problem:
After booting up from the 'Fedora-Live-Desktop-x86_64-19-Beta.iso' gnome shows an error message that it has crash (and give me the option to log out and try it again)

As I am running the live media without gui I wasn't able to get further information. But it looks quite similar to RHBZ #963808, which I encountered at the same machine running f18
Comment 1 Fedora Update System 2013-06-03 09:27:53 EDT
gnome-bluetooth-3.8.1-1.fc19 has been submitted as an update for Fedora 19.
Comment 2 Fedora Update System 2013-06-04 22:33:41 EDT
Package gnome-bluetooth-3.8.1-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-bluetooth-3.8.1-1.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Comment 3 Fedora Update System 2013-06-05 22:26:46 EDT
gnome-bluetooth-3.8.1-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.