On Tue, Oct 4, 2011 at 04:01, Camilo Mesias wrote:
> On Mon, Oct 3, 2011 at 5:22 PM, Ralf Corsepius wrote:
>> The XP I occasionally can not avoid to use, in its system control menus
>> has controls to switch between "normal", "big" "very big" fonts and
>> "expert/advanced controls" one can specif
On Sun, Oct 2, 2011 at 02:02, Hans de Goede wrote:
> Imagine I'm running a screen session with my irc client in there on my Fedora
> box,
There has perhaps never been a better sentence written demonstrating
why software engineers are not the target audience of any software
development. :-)
> an
On Fri, Jul 29, 2011 at 06:28, David Woodhouse wrote:
> On Fri, 2011-07-29 at 11:15 +0200, drago01 wrote:
>> >> Distro packaged extensions are frowned upon upstream.
>> >
>> > [citation needed]
>>
>> https://mail.gnome.org/archives/gnome-shell-list/2011-June/msg00164.html
>
> Seriously, who cares?
On Fri, Jun 17, 2011 at 11:43, Adam Williamson wrote:
>> Currently, when I open the giant application grid, I get oversized
>> meaningless pictures (yes, oversized - to even see the grid I had to
>> click on the "Applications" label, which is much smaller than the
>> icons),
>
> Yeah, I don't like
On Thu, Jun 16, 2011 at 22:15, seth vidal wrote:
> On Thu, 2011-06-16 at 18:59 -0700, Adam Williamson wrote:
>> On Tue, 2011-06-14 at 01:19 +0200, Henrik Wejdmark wrote:
>>
>> > My impression is that GNOME3 is trying to compete with Android and
>> > FrontRow,
>> > but have forgotten all of us who
On Thu, Jun 16, 2011 at 21:35, John Reiser wrote:
> This is because clicking [Button1 down up] does not temporarily "pin" the
> clicked sub-menu. ... The current behavior
> does not match the expectations of users.
Have you seen GNOME 3's Network Manager menu? When a large number of
WiFi networks
2011/5/9 Miloslav Trmač :
> Is the tradeoff really "correctness vs. saving a few seconds when
> booting a server"?
You know that's not what has been said and it's not really fair of
you. You want a server to fail on network failure; fine. Why don't you
just say that instead of characterizing it as
On May 7, 2011 5:00 AM, "Frank Murphy" wrote:
>
> On 06/05/11 23:51, Jason D. Clinton wrote:
> > On Fri, May 6, 2011 at 09:03, Frank Murphy > <mailto:frankl...@gmail.com>> wrote:
> >
> > Any plans for a gui replacement for gnome-schedule?
On Fri, May 6, 2011 at 09:03, Frank Murphy wrote:
> Any plans for a gui replacement for gnome-schedule?
>
It doesn't appear to be abandoned:
http://git.gnome.org/browse/gnome-schedule/log/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Fri, May 6, 2011 at 08:58, Denys Vlasenko wrote:
> Gnome 3 is a usability disaster. It added some useful things, yes,
> but it also REMOVED some useful things - what a hell!?
> Since when is that a valid development practice?
> Do we hate our users or what?
>
If you have some constructive fee
2011/4/14 Bruno Wolff III
> On Thu, Apr 14, 2011 at 16:53:00 +0200,
> Michał Piotrowski wrote:
> > "Fixed a rare condition that could cause the drive to reset and clear the
> data"
> >
> > I begin to wonder if it was the right decision to change main drive to
> SSD :)
> >
> > Maybe it's time to
On Mon, Mar 7, 2011 at 08:56, Christian Weiß wrote:
> Consider an installation of about ~600 low budget thin-clients (with almost
> no 3D support from the graphics chip) running as X-Terminals. Those
> thin-client stations are serviced by a host computer for 25-30 stations
> each. This infrastruct
On Tue, Jan 18, 2011 at 10:02, Dan Williams wrote:
> dependencies don't randomly change your networking setup. NM should
> only be started when explicitly enabled, which we do in the installer
> and the LiveCD explicitly when your system is initially installed.
> systemd didn't originally handle
On Mon, Jan 17, 2011 at 22:01, Jason D. Clinton wrote:
> This interesting though:
> $ ls -l /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service
> lrwxrwxrwx. 1 root root 42 Oct 22 13:33
> /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service ->
> /
On Mon, Jan 17, 2011 at 15:09, Lennart Poettering wrote:
> > getting default adapter: Activation of org.bluez timed out
>
> Smells like a bluez problem. Note sure what is going on there.
>
> It might be a good idea to pass systemd.log_level=debug and
> systemd.log_target=kmsg on the kernel cmdline
On Sun, Jan 16, 2011 at 09:48, Clyde E. Kunkel wrote:
> On 01/16/2011 02:32 AM, Jason D. Clinton wrote:
> > There's a twenty second pause in my boot sequence, shown below, before
> GDM
> > starts and I'm not certain if it's in NetworkManager waiting on
> org.
There's a twenty second pause in my boot sequence, shown below, before GDM
starts and I'm not certain if it's in NetworkManager waiting on org.bluez,
bluez itself or the bluez systemd unit file. (Or maybe I'm completely off.)
Later on, the bluetooth.service starts normally and Bluetooth is working
17 matches
Mail list logo
