Gnome login screen art is too bright.

2008-04-17 Thread Marc Baas
Ok, just before the final release I would like to point the attention to
a small but in my opinion important detail.

During beta the login screen art was changed to make it brighter. I
filed a bug about this in launchpad since on a LCD/TFT screen this looks
really bad. The bug is here:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-gdm-themes/+bug/211740

Unfortunately on the eve of release, no one bothered to have a look at
this and I fear that this will leave a bad impression of the
distribution as far as art design goes.
Maybe not a critical bug, but it is the representation of how Ubuntu
wants to advertise itself. The change would be minor (just switching
back to the original art of earlier in beta) and the effects would be
positive for the overall impression Ubuntu would give on new and old
users alike.

Could you guys please fix this annoying bug, it really looks very
unprofessional the way it is now. The original art earlier in beta (or
maybe it was alpha, I don't recall) looked so much better than what is
in the distro right now.

Thanks for your attention in these last hectic moments before the
release of the final.

Marc

ps. Aside from this I do would like to compliment all on the great
product that has been made. Albeit some small bugs that are still to be
found here and there, overall Ubuntu gives a very solid and stable
impression on me. Congratulations on this.



-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: [Bulk] Re: Gnome login screen art is too bright.

2008-04-17 Thread Marc Baas
On Thu, 2008-04-17 at 13:08 -0400, Mackenzie Morgan wrote:
 On Thu, 2008-04-17 at 18:38 +0200, Marc Baas wrote: 
  During beta the login screen art was changed to make it brighter. I
  filed a bug about this in launchpad since on a LCD/TFT screen this looks
  really bad. The bug is here:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-gdm-themes/+bug/211740
 
 Can you show what the old one and new one looked like?  I use
 HumanList,and I just compared the background.png for each of them like
 this:
 eog /usr/share/gdm/themes/Human*/background.png
 
 and WOW the regular Human theme has really light bursts.  It looks
 nearly white, which I agree is way too light.  Does HumanList use
 Human's old background?  If so, I agree it should go back to that one.
 

It's the same for me as for you, I really think this needs to be
changed. The older one was so much better.



-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: anyone else seeing X breakage with this AM's hardy updates?

2008-04-08 Thread Marc Baas
Yes, I'm having issues as well. I just now applied the updates and for
starters transparency is not working well. 
Applets that have transparency show thin white borders. I'm still
looking into what else is not working properly, but there are definately
issues.

Marc

On Tue, 2008-04-08 at 10:39 -0700, David Meyer wrote:
   From .xsession-errors on any of my hosts:
 
 /usr/bin/compiz.real (core) - Warn: Unable to parse XML metadata from file 
 ccp.xml
 Throttle level is 5
 Starting gtk-window-decorator
 /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling 
 YV12 image format
 I/O warning : failed to load external entity 
 /home/asw/.compiz/session/default0
 gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X 
 server :0.0.
 
   Dave



-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Problems with SELinux

2008-04-07 Thread Marc Baas
Dear all,

Since I don't know where else to put this problem I ran into and I
cannot specify it clearly enough to file a bug report, I'm sending it to
this mail group.

I've been testing Hardy since early alpha 6. I also tried installing
SELinux according to the specifications of the Ubuntu SELinux wiki (run
sudo apt-get install selinux) and it worked flawlessly for me at the
time.

Today I tried it again on a current up to date beta of hardy. I call it
a clean install since I haven't manually changed anything and have only
installed packages with apt that I normally do by default through a
script, to not have to do everything manually.
This time however, after rebooting and having the labeling finish, I was
welcomed with a message telling me HAL failed to initialize. On top of
that, while it was first loading, the whole gnome menu disappeared and
left me with nothing but an empty desktop. Immagine Alt+F2 didn't work
either.

I managed to work around this and get a terminal going, tried to restart
HAL, but got permission errors from SELinux telling me that this user
was not allowed to, etc.

Needless to say, lots of things were not working (at some point even my
ethernet adapter was blocked) and in the end, I removed SELinux in order
to be able to use my system. Hence I don't have all the detailed info
one could wish for in order to file a bug report.
Due to lack of time and wanting to be sure things would run properly I
went ahead and did a reinstall.

As a result of this I'm under the impression that the policies that came
with alpha 6, which worked fine for me, must have been changed one way
or another and now don't work for me anymore.
Is this something that can be confirmed by the ones that are working on
the implementation of SELinux?

Together with that, when can we expect configuration tools for SELinux
like the ones one finds in Fedora? It really is very user unfriendly and
complex to work with SELinux and try to configure it with the tools, let
alone without those.

Thanks in advance for your time and attention.

Marc



-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Hardy: After update of yesterday jockey-gtk crashes while trying to install proprietary driver.

2008-04-04 Thread Marc Baas
I'm using this mail group to focus on a certain bug that surfaced after
one of the updates from yesterday and it seems to be quite common.

The Hardware Driver manager in Ubuntu crashes when trying to install
drivers and effectively doesn't install anything.

Could someone please have a look at this Bug #186883 bug report,
because the list of confirms is growing rapidly and no one of the devs
has looked at it yet, by the looks of it.

I just installed my hardware ATI driver manually, but I recon that many
people must be stuck trying to install it at this point.

Marc



-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss