compiz (core) - Warn: failed to receive ConfigureNotify event on...

[James Jeppesen]

On compiz restart there are some worrying warnings:
compiz (core) - Warn: failed to receive ConfigureNotify event on 0xa00004
compiz (core) - Warn: unhandled ConfigureNotify on 0x300009e!

ORIGINAL DESCRIPTION:
lsb_release -rd

Description: Ubuntu 12.04 LTS
Release: 12.04

Unable to locate package pkgname

I am attempting to fix desktop issues causing my Ubuntu desktop to be blank. I run the command unity --reset and get output

Warning: Unity currently default profile, so swithching to metacity while resetting the values
unity-panel-service: no process found
checking if settings need to be migrated ...no
checking if internal files need to be migrated ... no
Backend :gconf
Integration :true
Profile :unity
Adding plugins
/usr/share/compiz/regex.xml:63:parser error : Premature end of data in tag long line 63
    <long xml:lang="uk"> (some words in russian language)

/usr/share/compiz/regex.xml:63:parser error : Premature end of data in tag plug in line 3
    <long xml:lang="uk"> (some words in russian language)

/usr/share/compiz/regex.xml:63:parser error : Premature end of data in tag compiz line 2
    <long xml:lang="uk"> (some words in russian language)

Initializing core options...done
compiz (core) - Warn: failed to receive ConfigureNotify event on 0x1000004

compiz (core) - Warn: failed to receive ConfigureNotify event on 0x22000d6

compiz (core) - Warn: failed to receive ConfigureNotify event on 0xa00004

compiz (core) - Warn: unhandled ConfigureNotify on 0x300009e!

compiz (core) - Warn: this should never happen. you should probably file a bug about this.

compiz (core) - Warn: unhandled ConfigureNotify on 0x30000a1!

compiz (core) - Warn: this should never happen. you should probably file a bug about this.

compiz (core) - Warn: unhandled ConfigureNotify on 0x30000a4!

compiz (core) - Warn: this should never happen. you should probably file a bug about this.

I would expect unity to reset and be able to use my desktop instead my desktop is blank with only firefox and terminal shortcut. I am unable to login regularly instead I have a flashing screen with various errors like stopping kernel and mountall stopping plymouth etc. After a time I get this to stop using ctrl alt f1 and can use startx to get to incorrectly operating desktop.

This began with update failures about 10 days ago resulting in ubuntu system errors. I had a hdd fail and grub was reloaded causing me to not be able to use gnome desktop.

[Daniel van Vugt (vanvugt)]

Those warnings are mostly normal. Although the regex.xml warning looks like a simple failure of the XML parser to handle UTF-8 encoding of Ukrainian. But that should be harmless.

Could you please clarify what the main problem is? Is it "unable to login regularly instead I have a flashing screen with various errors like stopping kernel and mountall stopping plymouth etc" ?

[James Jeppesen (jrjeppesen)]

Daniel,

I haven't submitted a bug for Ubuntu before so I am unsure of the process.
 I hope its ok to email you directly with a response to your inquiry. Just
to clarify I was not seeing a login screen. Just so you know I had been
using Gnome desktop for quite a long time since 11.04 I believe, and I
upgraded to 11.10 and then to 12.04. I never had any issues but I am
guessing this is why I am having trouble now. I had some problems with
grub due to a failed hard drive. I also had some trouble with automatic
updates causing errors as recent as mid July although I can't really
specify their cause as I didn't dig into them. I am guessing there are logs
somewhere that might be parsed but I don't know if its worth your time for
these xml parser errors. Due to the grub issue and the other errors I had
some desktop environment issues and started playing with settings and
installed and removed various packages. I made many changes and lost the
ability to log in to my system. I used chroot from live usb to attempt to
correct my problems but I wasn't successful. When I finally figured out
that if I waited at the flashing screen that was displaying "Stopping the
kernel and mountall... something plymouth" and used the Ctrl Alt F1 or F2 I
could drop to a command prompt and use StartX to load an unstable desktop.
 At that point when I was trying to get a login screen to display instead
of the flashing screen I tried to run the "unity --reset" command and got
the xml parser errors. I had to install Kubuntu to get a login screen then
I was able to login and update some packages to get a mostly stable desktop
environment although my system probably won't be stable until I reload the
OS.

I just wanted to submit the bug because the message from compiz said if you
see this you probably should file a bug. I know from previous testing
experience that sometimes when systems are all messed up like mine is you
can get a lot of strange errors. I also know that its best to let the devs
or someone knowledgable decide whether the report of the error can be used
for future fixes. Let me know if I can attempt to clarify anything.

Thanks,

JR

On Sun, Jul 29, 2012 at 9:13 PM, Daniel van Vugt <
<email address hidden>> wrote:

> Those warnings are mostly normal. Although the regex.xml warning looks
> like a simple failure of the XML parser to handle UTF-8 encoding of
> Ukrainian. But that should be harmless.
>
> Could you please clarify what the main problem is? Is it "unable to
> login regularly instead I have a flashing screen with various errors
> like stopping kernel and mountall stopping plymouth etc" ?
>
> ** Changed in: unity (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1030445
>
> Title:
> unity reset results in compiz error
>
> Status in “unity” package in Ubuntu:
> Incomplete
>
> Bug description:
> lsb_release -rd
>
> Description: Ubuntu 12.04 LTS
> Release: 12.04
>
> Unable to locate package pkgname
>
>
> I am attempting to fix desktop issues causing my Ubuntu desktop to be
> blank. I r...

[Daniel van Vugt (vanvugt)]

OK, thanks. This bug will be about the ConfigureNotify warnings then. Which I can confirm.