Thank you for your time, I really appreciate it. Reported as #1452581.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448775
Title:
Unable to login after upgrade from 14.10 to 15.04 possible XOrg
Since Compiz is a victim of bad microcode, I'm going to mark this
Invalid. I'm glad you were able to track down the offending package.
If you feel compelled to get intel-microcode fixed, please open a new
bug report against that package.
Thanks!
** Changed in: compiz
Status: New =
I have removed Intel microcode driver from my machine and installed
Nvidia driver and unity with Compiz went up and running. Should I thank
Nvidia or blame Intel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It was installed by jockey (tool which detects what additional drivers
can be installed), I didn't installed it by purpose. I think during
update it auto installed all drivers and it caused issues. Or it is
preloaded by default on all Intel machines. (I do not remember why I
diverged from my
Oh, maybe you mean the intel-microcode package. If so, I wonder what is
pulling that package in to be installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448775
Title:
Unable to login
Hmm, what do you mean by the Intel microcode driver? That definitely
sounds suspicious...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448775
Title:
Unable to login after upgrade from 14.10 to
Done.
** Attachment added: compiz-gdb-log.txt
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1448775/+attachment/4388911/+files/compiz-gdb-log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tried, same effect. Compiz will crash at every one login attempt. Is
there a way to fire compiz with debugging in such situation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448775
Title:
Unable
Can you try to boot with upstart? You should be able to do that from
grub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448775
Title:
Unable to login after upgrade from 14.10 to 15.04 possible
Installed gnome-shell (it's ugly and complicated), was able to start gdb
with compiz inside and it crashed right after loading opengl plugin, it
has also warned about corrupted shared library list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
To be more specific: it loaded opengl plugin, informed that it's fully
supported and then creashed right after starting plugin (creation of new
thread).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NVA8
OpenGL version string: 3.0 Mesa 10.5.2
Not software rendered:yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program:yes
Ok, so the OpenGL plugin is doing something the hardware doesn't like.
The biggest change in OpenGL for 15.04 is the X11 Sync objects. I'm
wondering if the driver is saying it's supported, but the GPU can't
handle it.
Could you try opening CCSM and go to the OpenGL tab and uncheck X11
sync
No effect - also other switches from OpenGL does not helped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448775
Title:
Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash
To
Did you start unity from a tty?
On 30 Apr 2015 19:35, Jakub Nietrzeba 1448...@bugs.launchpad.net wrote:
To be more specific: it loaded opengl plugin, informed that it's fully
supported and then creashed right after starting plugin (creation of new
thread).
--
You received this bug
Yes. Started gnome-shell, switched to first console, logged in, started unity
with --replace and --advanced-debug, gdb has started, pressed 'r', it loaded
some plugins and died. There are two additional warnings:
Glib-warning: In call to g_spawn_sync(), exist status of child process was
Can you post here the full gdb log? You can use set logging file.
2015-04-30 21:32 GMT+02:00 Jakub Nietrzeba 1448...@bugs.launchpad.net:
Yes. Started gnome-shell, switched to first console, logged in, started
unity with --replace and --advanced-debug, gdb has started, pressed 'r', it
loaded
Jakub, you can actually install metacity and run unity from a tty using
unity --advanced-debug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448775
Title:
Unable to login after upgrade from 14.10
Also you can try to install gnome-shell (or similar) and run from a terminal:
/usr/lib/nux/unity_support_test -p
And post here the output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448775
** No longer affects: xorg (Ubuntu)
** Also affects: compiz
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448775
Title:
Unable to login after upgrade
If you feel comfortable doing so, could you please attach the Compiz
core dump for when this occurs? It may help give us some clues about
what's going on.
Also, it appears you had the nvidia binary driver installed at one time
and now you are using nouveau. I'm wondering if there is still some
I can try, but it does not looks like it can be upgraded. This laptop
works fine on 14.10 and does not seems to be supported by Toshiba
anymore.
For me most interesting in call stack is this:
#4 0x
it's NULL, istn't? It looks like there is some callback, thread or
signal catcher
Yes, that is a NULL address. I tried sending a SIGILL to compiz on my
test system and I got a valid stacktace out of it. I really wish we
could at least get something useful out of your dump.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
SIGILL looks like sirens call of executing data segment after hitting
some null at execution path. Problem must be somwhere else. I can
reproduce it every time (at each login attempt) and I'm not affraid of
compilating packages from the sources. If I can help somehow (maybe some
usefull gcc
Added those sources, but those packages does not exists. apt-get is
unable to locate them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448775
Title:
Unable to login after upgrade from 14.10 to
Interesting, created another stack trace and it looks almost identical:
long garbage, short garbage, long garbage, seven, zero. Array overflow?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448775
Maybe just installing the ddeb for the compiz packages is enough to get
a decent stacktrace.
If you don't know how to do this already, then please follow the
instructions on https://wiki.ubuntu.com/DebuggingProgramCrash#Non-built-
in_debug_symbol_packages_.28.2A-dbgsym.29 on adding the ddebs
I was sure that it was caused by nvidia graphics, removed it but problem
persisted, blamed configuration and brought in livecd and the same
problem appeared. I can reproduce it on LiveCD, so in a moment I will
attach crash file.
--
You received this bug notification because you are a member of
I missed your comments about having tried this on a LiveCD:)
Great, thanks for the crash file. I'll see if I can glean any useful
info out of it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is a crash file with coredump and all other info, created from
Ubuntu 15.10 LiveCD.
** Attachment added: _usr_bin_compiz.999.crash
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1448775/+attachment/4387566/+files/_usr_bin_compiz.999.crash
--
You received this bug notification
Well, I've looked at the crash dump and I'm not sure what symbols gdb
can't find. I've loaded debug symbols for compiz-core and it still
complains, so I'm at a loss.
I have been reading up on what the kernel trap means and basically it's
saying that a process is performing something the hardware
Tell me how, and it will be delivered.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448775
Title:
Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash
To manage notifications
I have used apport-cli to dive directly into GDB (with symbols) and
found this:
#0 0x7f03bf4205f5 in ?? ()
#1 0x0098cdc0 in ?? ()
#2 0x7ffd079aa8c0 in ?? ()
#3 0x0007 in ?? ()
#4 0x in ?? ()
It has just yelled that it cannot find public key for
Tried to boot from freshly created live cd, and received the same error.
So it looks like it is not corelated to configuration of my computer,
but rather an Ubuntu itself.
Can I have some help how to at least try to find a source of this error?
Or any workaround for similar bug to look at?
**
demesg contains several dups of the following error.
[ 637.133657] traps: compiz[5430] trap invalid opcode ip:7fe2bd6f05f5
sp:7fff0b63f0b8 error:0
[ 868.799930] traps: compiz[6021] trap invalid opcode ip:7f0fab07c5f5
sp:7fff64019268 error:0
It would be helpful if a stacktrace of compiz could
35 matches
Mail list logo
