Curious changelog entry
Changelog from today's geoclue-0.11.1.1-0.9.1.20091026git73b6729.fc11 update: -- **2009-10-24** Peter Robinson 0.11.1.1-0.9 - New git snapshit, enable NetworkManager support for WiFi location, gsmloc and new Skyhook plugin -- snapshit, eh? :p -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: [Test-Announce] Graphics Test Week (ATI, NVIDIA and Intel graphics Test Days)
On 09/10/2009 09:10 AM, Adam Williamson wrote: On Thu, 2009-09-10 at 08:49 -0600, Dariusz J. Garbowski wrote: On 09/08/2009 03:26 PM, Adam Williamson wrote: Yes, it is now that legendary time, well loved by the hearts of men for millennia(*): Graphics Test Week! Tomorrow - 2009-09-09 - is ATI/AMD Radeon graphics card Test Day (1). Using 2009-09-09 ISO, when passing 'radeon.modeset=1' as boot param, I get Unknown boot option 'radeon.modeset=1'. Ignoring... Is that expected? (sending to all lists as this is #1 Top Question...) Yes, it is. The 'science bit' is that the kernel itself truly doesn't understand the parameter, which is why you see this message - but the radeon. prefix means it gets automatically passed on to the radeon module, which _does_ understand (and interprets) it. Personally I consider this a kernel bug, it shouldn't display this message for parameters which will be passed to modules. Thanks to all who responded with explanation. This indeed is confusing and I agree with you that this deserves a bug status... radeon.modeset=1 is a no-op, though, modesetting is now default for Radeon chips. So only radeon.modeset=0 (to disable it) makes any sense. Did I leave radeon.modeset=1 in one of the test cases? Errr... I thought I saw it there yesterday but I might be wrong (I have taken a not of this the day before). I can't see it anywhere today. BTW: my test report on wiki. -- thufor -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: dhclient and dhcp update require restart?
On 09/02/2009 02:33 PM, David Cantrell wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 2 Sep 2009, Dennis J. wrote: On 08/27/2009 07:49 PM, David Cantrell wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 26 Aug 2009, Dariusz J. Garbowski wrote: Hi, something that bothers me a bit... More and more system restart requests with each update (even if one doesn't use the package at the time). Is this necessary for dhclient and dhcp update packages to require restart? Wouldn't service network restart and service dhcpd restart in the install/upgrade scripts do the trick (after checking that the service is actually running)? Ssh used to do that since, well, as far as I remember. Yes, 'service dhcpd restart' will work fine for dhcpd. For dhclient, it's not necessarily as simple as restarting the network service. If you are using the network service, that will work fine. If you are using NetworkManager, you'll need to either restart NetworkManager or have it down the connection you're using dhclient on and bring it back up. Why is a restart of NetworkManager necessary in this case? If dhclient reinitializes the interface and gets the old dhcp data then nothing really changes and NetworkManager shouldn't have to care. If e.g. der IP changes then NetworkManager should detect that and reinitialize the connection info on its end (after all the new interface might not be connected to anything and thus have to be marked as down anyway). It doesn't work that way. dhclient isn't a service with an init.d script. If you are using NetworkManager, dhclient is a child process of NetworkManager. You can't just restart dhclient since NetworkManager is controlling it. You have to either tell NetworkManager to down the interface, stop dhclient, and bring it back up -- or restart NetworkManager. Either way, the result is the same. If you are using the network service, dhclient is run when the interface is ifup'ed (so either restart the network service or ifup/ifdown the interface in that case). Yeah, dhclient works even if you don't use NetworkManager (I don't). So ifup/ifdown is necessary, which may or not be a good idea if something else running on the system relies on e.g. files open on NFS/SMB. Yet, can something similar to sshd be done to dhcpd? -- thufor - -- David Cantrell dcantr...@redhat.com Red Hat / Honolulu, HI -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqe1pUACgkQ5hsjjIy1VklGugCgxHxszZp60PHjRN5UpRfP59qD dOkAoLMk8WXoyXnsRaiIWIdwLn6u8mdp =5WWs -END PGP SIGNATURE- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Reboot madness? [Was: Re: dhclient and dhcp update require restart?]
I'm starting to be really bothered by this. Today kdenetwork requires restart due to... fix Bug 515586 - Kopete: New Messages from changed resource arrive in new tab/window. Wouldn't login/logout sequence do? And that only if the user really cared, i.e. was using Kopete and this bug was really irritating him. Before that imsettings required restart... kpackagekit required restart... I'm with Matthew on this: This is a real shame. One of the selling points of Linux is that you *don't* need to reboot for every little upgrade (unlike a certain other OS I shan't name). Is this something that should be bugzilla'd? Cheers, thufor -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
dhclient and dhcp update require restart?
Hi, something that bothers me a bit... More and more system restart requests with each update (even if one doesn't use the package at the time). Is this necessary for dhclient and dhcp update packages to require restart? Wouldn't service network restart and service dhcpd restart in the install/upgrade scripts do the trick (after checking that the service is actually running)? Ssh used to do that since, well, as far as I remember. Cheers, Dariusz -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Visiting webpage causes ~hard lock - round 2!
On 08/17/2009 07:24 PM, Sam Varshavchik wrote: Dr. Diesel writes: Please save your work and visit (tech website): URL:http://hardforum.com/showthread.php?t=1391450amp;page=13http://hardf orum.com/showthread.php?t=1391450page=13 Screen freezes, mouse has jerky movement, vt switch fails. Loads fine for me. Same here. Though I have ATI gfx. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Clipboard manager by default in Fedora 12
On 07/27/2009 07:49 AM, Casey Dahlin wrote: The Firefox issue was always Firefox's fault. Its designed to keep information from leaking out of the browser. Seriously? Do you have any reference source for this information? AFAIK, the real truth is that this behaviour is a a result of how X protocol is designed: http://www.pixelbeat.org/docs/xclipboard.html Note it's the X application itself that maintains the storage for what it puts on the buffers, which makes a lot of sense when you think about it, especially considering X's network transparency. But that means when you close the application the content of the clipboard and selection buffer are lost. You can get around this behaviour by using an external application to manage the storage for the clipboard, the standard one being xclipboard. Note this is the reason why it's awkward to get a command line program to paste to the clipboard. It has to fork and run until no longer required (someone else pastes to the clipboard). See xsel http://www.vergenet.net/%7Econrad/software/xsel/ for an example of this. -- thufor -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: FESCo meeting summary for 2009-06-26
On 06/28/2009 01:12 PM, Seth Vidal wrote: 2. I've yet to see this majority you speak of. Here I am, part of the silent KDE-users majority, who uses Fedora because it provides great KDE experience. I am frustrated however by the fact that even finding Fedora KDE download page is experience similar to looking for Linux laptops on Dell website... I have been using Red Hat Linux since RH 4.2 through 9 and then following Fedora... Attitudes I see from Fedora Gnome camp are exactly what makes KDE users (and I presume developers too) wary of the distro. It certainly worries me. Looks like you are afraid of actually getting bigger KDE majority for some reason. -- thufor -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: dropdown menu's
On 03/05/2006 12:15 AM, Leszek Matok wrote: Dnia 05-03-2006, nie o godzinie 00:37 +0100, Erwin Rol napisał(a): This is something that already bothers me a while, i think it never really worked as expected, but i am not sure if it is a my machine only kind of problem. From http://www.gtk.org/api/2.6/gtk/GtkComboBox.html The style in which the selected value is displayed, and the style of the popup is determined by the current theme. It may be similar to a GtkOptionMenu, or similar to a Windows-style combo box. So probably it can be changed in the theme (or only the look and color, but not that behavior), but all themes I have here (Fedora 3) have it the way you experience and dislike. The purpose is to have the currently selected option right in the place where the option menu is, so you can click it to see other options and click in the same place again not changing anything (instead of clicking somewhere else in the window or hitting Esc). Anyways, it's not Fedora-specific. It's silly -- you click on the combobox to see what other options are and yet you don't see them! util of course you move the mouse to the bottom of the screen, wait for the whole list to scroll up (never mind that there was enough space on screen to display all option in the first place) and only then you can decide whether you actually want to change the option. Now how on Earth can you save any time or effort of moving cursor some place else in the window to click to cancel? Very smart... I dislike this design too :( Dariusz ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
