Unable to login in Yammer, Login screen stuck

Bug #1088826 reported by Alexandru Armean
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lament
Incomplete
Undecided
Hans Oesterholt

Bug Description

original description by Brandon Lyon, i have the same behaviour:
"
I've installed lament (after installing libappindicator1 and required libraries) using lament_0.0.7.precise.6_amd64.deb, and executed the application successfully.
The first page has the Yammer logo and a Login button, after clicking on the Login button another window opens. The title contains a percentage that climbs up to about 49% then reverts back to: [0%] Yammer. I was able to enter the network and move on the login page, but when I click "Log In" nothing happens. I've verified my username/password is correct.

os: Linux Mint Debian Edition
kernel: 3.2.0-3-amd64
"

in addition to that i can say that the CPU usage goes to 100% for Xorg and to 22% for lament-bin. If i close the login window, i can see a process "apport" using 100% cpu for about 10 seconds. After that, the whole Lament app closes and i get the Ubuntu message "The application Lament has closed unexpectedly".

In the error report, the Title says "lament-bin crashed with SIGSEGV in g_type_check_instance_cast(). The SegvReason is "reading unknown VMA" . StacktraceTop says it was using "g_type_check_instance_cast() from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 .

My OS: Ubuntu 12.04 , x64, gnome with compiz

Revision history for this message
Hans Oesterholt (0k-hans-f8) wrote :

I cannot confirm it's not working. Or maybe it stopped working temporarily?

Changed in lament:
assignee: nobody → Hans Oesterholt (0k-hans-f8)
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.