GNOME3 Staging PPA

[VinDSL]

Been getting this error, for the past week_or_so:

E: /var/cache/apt/archives/colord_0.1.30-0ubuntu3_i386.deb: trying to overwrite '/usr/share/colord/icons/color-munki-photo-ambient.svg', which is also in package libcolord-common 0.1.28-0ubuntu1~13.04~ricotz0

I've tried various tricks, to get rid of it, but no joy.

It's more of an annoyance than anything, but...

Anyone know how to fix this problem?!?!?

[jbicha]

Uninstall libcolord-common

[Harry33]

Been getting this error, for the past week_or_so:

E: /var/cache/apt/archives/colord_0.1.30-0ubuntu3_i386.deb: trying to overwrite '/usr/share/colord/icons/color-munki-photo-ambient.svg', which is also in package libcolord-common 0.1.28-0ubuntu1~13.04~ricotz0

I've tried various tricks, to get rid of it, but no joy.

It's more of an annoyance than anything, but...

Anyone know how to fix this problem?!?!?

Where did you get the package libcolord-common (0.1.28-0ubuntu1) from?
There is no such package in RR repos.
Perhaps you could remove that one first.

[VinDSL]

Uninstall libcolord-common

I'll give it a toss... Thanks!

Where did you get the package libcolord-common (0.1.28-0ubuntu1) from?
There is no such package in RR repos.
Perhaps you could remove that one first.

Looks like it was from Ricotz Testing (only Ricotz PPA I have enabled)...

vindsl@Zuul:~$ apt-cache policy libcolord-common
libcolord-common:
  Installed: 0.1.28-0ubuntu1~13.04~ricotz0
  Candidate: 0.1.28-0ubuntu1~13.04~ricotz0
  Version table:
 *** 0.1.28-0ubuntu1~13.04~ricotz0 0
        100 /var/lib/dpkg/status
vindsl@Zuul:~$

BBL

[VinDSL]

Worked a treat!

I got rid of that library. Then, on the next go_around, colord upgraded without error.

Maybe that lib flew in, under the radar, last week -- a case of bad timing, on my part, or whatever.

Sometimes... something sneeks into a package that shouldn't be there. It gets corrected almost immediately, but if you upgraded at (say) 9:00 AM, instead of 10:00 AM, you get the "surprise package".

I *suspect* something like that happened here...

[VinDSL]

Hrm.

Well, I wanted to wait n' see -- do a few restarts, cold boots -- et cetera, but...

Ever since I removed libcolord-common, I haven't seen any more caribou-antler virtual keyboards.

Coincidence? Maybe.

If you'll remember (a few posts above) I purged the caribou-antler package, but the keyboards kept popping up, on every login.

I had a gut feeling one of the libraries/scripts/binaries/whatever had the antler keyboards hard-coded into it.

Anyway, *fingers crossed*. Hopefully, the virtual keyboards are gone for good...

[mc4man]

For the most part seems ok here in Gs session, 2 small oddities - org.gnome.desktop.interface gtk-color-scheme has no affect anymore & Videos always opens small, resizing, closing, re-opening has no effect (will have to put up a 3.7 Videos & see there

In an ubuntu session things are fairly good until g-c-c & g-s-d are upgraded, those do cause issues. Prior to with everything else default installed/shared updated only a few -
gnome-terminal looks bad in ambiance theme
gnome-screenshot doesn't work, produces an unclosable white window the size of screenshot
gtk2 (gtkrc) apps are not themed right in ambiance
(maybe a few more, nm-applet crash is one

After g-c-c/g-s-d -
always has an undetermined g-s-d crash on log in
custom keyboard shortcuts are non-functional
occasionally unity launcher get whacked out with no icons
(probably a bit more, as time permits

On a positive gtk-3.7+ & nautilus-3.7.+ seem fine

[VinDSL]

In an ubuntu session [...]

My Unity sessions have been trashed, ever since I started running Gnome Staging. The thing is, Unity looks/acts horrible, only when I do a conventional login via GDM or LightDM.

However, I discovered that if I load Unity from inside a GS session (replace the Gnome-Shell DE with Unity) then Unity looks/works great -- never been better, actually. Go figure!

All I do is:

• Login to GS via GDM
• Wait for GS to fully load (takes a minute or two on this rig)
• Open a terminal, type:
  

  unity --replace

Unity will start replacing GS.

At some point, the terminal dialog will lag-out (and eventually timeout) on a warning message complaining:

Compiz (decor) - Warn: No default decoration found, placement will not be correct.

I simply close the terminal window when that happens -- Unity continues to load -- and life is good.

Kind of a convoluted way of starting Unity, but it works.

I'm at a loss to explain why Unity is so janky, when I start it from GDM or LightDM -- but, it works perfectly from inside a GS session.

[mc4man]

My Unity sessions have been trashed, ever since I started running Gnome Staging. The thing is, Unity looks/acts horrible, only when I do a conventional login via GDM or LightDM.

However, I discovered that if I load Unity from inside a GS session (replace the Gnome-Shell DE with Unity) then Unity looks/works great -- never been better, actually. Go figure!

Will have to give that a curiosity try, - dumped the install I commented on above, may put a new *ppa one in later

At least here the unity session was sorta ok, especially with older g-c-c & g-s-d.

[hugmenot]

Using the Gnome3 and the Ricotz Testing PPAs I now get very choppy rendering in Gnome Shell and even a very choppy mouse cursor. It’s fine in mutter alone and metacity, and it’s even fine in the GS based GDM login screen.

Is anyone else seeing this? I have Intel graphics.