Re: Ubuntu falling behind?
On Sat, Jun 26, 2010 at 18:50, Chris Jones chrisjo...@comcen.com.au wrote: I guess I also have to remind myself that lucid is a LTS release. Which I hadn't thought of when I first posted. Still, this very issue seems to be apparent with all Ubuntu releases and Firefox updates. We always seem to be the last ones to receive it. Regards -- Chris Jones Photographic Imaging Professional and Graphic Designer ABN: 98 317 740 240 It isn't like no one is trying. The following email from 25 days ago outlines the plan and requests help/testers. -rich -- from: Sebastien Bacher seb...@ubuntu.com reply-to: ubuntu-devel-discuss@lists.ubuntu.com to: ubuntu-devel-annou...@lists.ubuntu.com date: Tue, Jun 1, 2010 at 05:59 subject: New firefox support model and coming changes in stable updates Hello Ubuntu Developers, The desktop team has been working since the Karmic UDS on the following blueprint: https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-lucid-new-firefox-support-model The upshot of the blueprint is that there will be some changes to users' desktops if they are currently Hardy, Jaunty or Karmic users. In Lucid, we put in a lot of effort to ensure these updates will be easier in the future (Firefox now uses bundled libraries rather than system libraries, we have reduced the number of applications in the archive using xulrunner, and dropped a lot of extensions too). The update for Lucid is quite trivial, but the update in Hardy, Jaunty and Karmic is not quite as simple. When we roll out the new version, we also need to update the following: * All the Firefox extensions that we ship in the archive * Language packs In addition to this, we are going to be porting some applications which are currently using xulrunner 1.9 to either the latest version of xulrunner (1.9.2.4) or Webkit. However, this can happen after the Firefox rollout, as the 2 xulrunner versions can be installed in parallel. We have a list of the affected applications [2]. We won't be porting all of the applications on that list, but will be focusing on the applications which are exposed to insecure content (at the bottom of the page). Why: Firefox 3.0 (and xulrunner 1.9) are now unsupported by Mozilla. Rather than backporting security fixes to these now, we are moving to a support model where we will be introducing major new upstream versions in stable releases. The reason for this is the support periods from Mozilla are gradually becoming shorter, and it will be more and more difficult for us to maintain our current support model in the future (see [1] for information). When: Next week, Mozilla will release Firefox 3.6.4 as a minor update to the 3.6 series. This will be rolled out to Lucid, Hardy, Jaunty and Karmic (along with xulrunner 1.9.2.4). Call for Testing: Packages will be hosted in the Ubuntu Mozilla Security team PPA [2]. As this is being rolled out as a security update (rather than a SRU), there is no bug report tracking this. The rollout is being covered (and will be announced) by USN-930-1. Clearly, there are significant risks associated with the update. In addition to ensuring that Firefox and all the extensions still function correctly after the update, we also need to ensure: 1. All the Firefox plugins (eg, Flash) still work 2. The actual upgrade to the latest version goes smoothly 3. We don't break Hardy - Lucid and Jaunty - Karmic upgrades 4. The upgrade works with the *-updates pocket disabled Applications that are ported to the latest version of xulrunner (or to Webkit) will also need testing. However, we will also need to test every application on the list in [3] (even the ones which aren't being updated), with the latest version of xulrunner installed on the system. The reason for this is that most applications dynamically load one of the GRE's on the system, and some of these applications will load 1.9.2.4 if it is present. I already know of 1 API change in 1.9.2.4 which had been causing me problems with applications I've been porting, so it's possible that the same issue will affect applications we aren't porting if they load the newest GRE. You can help testing the upgrade by following the instruction on https://lists.ubuntu.com/archives/ubuntu-devel/2010-June/030811.html Thank you, Sebastien Bacher On behalf of the Ubuntu Desktop team [1] https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/FirefoxNewSupportModel [2] https://edge.launchpad.net/~ubuntu-mozilla-security/+archive/ppa [3] https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/FirefoxNewSupportModel/xulrunner-list -- ubuntu-devel-announce mailing list ubuntu-devel-annou...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce - -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at:
Ethernet driver problem fixed?
Did yesterday's update From: 2.6.27-4.5 To: 2.6.27-4.6 fix the problem - or are the cards still at risk? tnx -rich -- 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: libc borked
On Mon, Mar 17, 2008 at 11:40 AM, Brian Murray [EMAIL PROTECTED] wrote: One thing this, and some other events, has made me think about is - how are new community members supposed to know who someone is and what their contributions to Ubuntu have been? We have a developer responsibilities wiki page[1] perhaps we should publicize it more and flesh it out. As I personally have a hard time keeping people's irc nicks, launchpad usernames and real names connected, I'm adding irc nicks to that page too. What other ways can we help new community members identify people involved in Ubuntu development? senders email signature line ... short description of responsibilities and area of expertise - this will help all list members place value on the reply [1] https://wiki.ubuntu.com/DeveloperResponsibilities -- Brian Murray @ubuntu.com -rich -- 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 Alpha-4 jockey-gtk
I have been told to use bug tracker, not this list to report problems. But what if the problem can't be reported (per Ubuntu)? -- Problem in jockey-gtk The problem cannot be reported: This is not a genuine Ubuntu package -- This had to be installed by the official Ubuntu disc because (as reported earlier) I can't run the Package Manager. -rich -- 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: Hardy Alpha-4 synaptic error
On Feb 3, 2008 9:13 AM, Lars Wirzenius [EMAIL PROTECTED] wrote: On su, 2008-02-03 at 09:05 -0600, Richard Mancusi wrote: [EMAIL PROTECTED]:~$ gksu update-manager warning: could not initiate dbus You don't need to run update-manager as root. It will switch to root (and ask for username then) when it needs it. This should at least fix the dbus initialization problem. (I don't know about the other problems, which may be unrelated.) That fixed the dbus problem. The password works, gui comes up showing the available updates, then back to a window with my initial error: -- An error occured The following details are provided: E:ERROR: could not create configuration directory /home/root/.synaptic - mkdir (2 No such file or directory) -- Terminal output = current dist not found in meta-release file -rich -- 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: Hardy Alpha-4 synaptic error
On Feb 2, 2008 10:59 PM, scott [EMAIL PROTECTED] wrote: Try opening a terminal and typing 'gksu synaptic' or 'gksu update-manager'. Regards, Scott The administrative tasks password box comes up and accepts the password. Then update manager gui appears showing 32 updates. However the terminal shows: -- [EMAIL PROTECTED]:~$ gksu update-manager warning: could not initiate dbus Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put ORBIIOPIPv4=1 in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf current dist not found in meta-release file -- Terminal output from attempting to close the update manager: -- Traceback (most recent call last): File /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py, line 357, in lambda self.button_close.connect(clicked, lambda w: self.exit()) File /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py, line 830, in exit self.save_state() File /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py, line 838, in save_state gconf.VALUE_INT, gconf.VALUE_INT, x, y) gobject.GError: No database available to save your configuration: Unable to store a value at key '/apps/update-manager/window_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put ORBIIOPIPv4=1 in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf -- A crash report warning is issued - however it can't be reported: -- Problem in update-manager The problem cannot be reported: You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs: libgcc1, xinit, cpp-4.2, libffi4, libxml2, libsasl2-2, coreutils, libsasl2-modules, gcc-4.2-base, libstdc++6 -- This was a clean install in the manner I believed the average user would do. Use entire disk, allow Ubuntu to partition, everything very basic. hth -rich -- 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
Fwd: Hardy Alpha-4 synaptic error
-- Forwarded message -- From: Richard Mancusi [EMAIL PROTECTED] Date: Feb 3, 2008 9:46 AM Subject: Re: Hardy Alpha-4 synaptic error To: Jason Crain [EMAIL PROTECTED] On Feb 3, 2008 9:35 AM, Jason Crain [EMAIL PROTECTED] wrote: Could you run this and tell us what it shows: sudo -H bash -c 'echo $HOME' /home/root -- 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: Hardy Alpha-4 synaptic error
On Feb 3, 2008 10:15 AM, Jason Crain [EMAIL PROTECTED] wrote: On Feb 3, 2008 9:35 AM, Jason Crain [EMAIL PROTECTED] wrote: Could you run this and tell us what it shows: sudo -H bash -c 'echo $HOME' /home/root That's pretty strange. Try running sudo usermod -d /root root to set root's home dir. If that doesn't work, you may have to look at root's .bash* or .profile files to see if $HOME is being set anywhere. Okay - that did it, sudo -H bash -c 'echo $HOME' now shows /root and I was able to do the updates and I added build-essential as a test via Synaptic Package Manager. Thank you for fixing my problem - I hope it is localized to me and not a Ubuntu problem. I know everything I did post install and may research this some more. tnx -rich -- 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: Hardy Alpha-4 synaptic error
On Feb 3, 2008 10:32 AM, Richard Mancusi [EMAIL PROTECTED] wrote: On Feb 3, 2008 10:15 AM, Jason Crain [EMAIL PROTECTED] wrote: On Feb 3, 2008 9:35 AM, Jason Crain [EMAIL PROTECTED] wrote: Could you run this and tell us what it shows: sudo -H bash -c 'echo $HOME' /home/root That's pretty strange. Try running sudo usermod -d /root root to set root's home dir. If that doesn't work, you may have to look at root's .bash* or .profile files to see if $HOME is being set anywhere. Okay - that did it, sudo -H bash -c 'echo $HOME' now shows /root and I was able to do the updates and I added build-essential as a test via Synaptic Package Manager. Thank you for fixing my problem - I hope it is localized to me and not a Ubuntu problem. I know everything I did post install and may research this some more. tnx -rich Okay, I did another clean install and can repeat the problem. On a test system I always set a root password and allow root logon. Yes, I know that isn't a great idea, but it comes in handy on a test system. As soon as I set a root password in System/Administration/Users and Groups the root user Home directory moved from /root to /home/root. I guess it's a matter of opinion as to whether this is a bug. Ubuntu and common sense tells you to not set a root password. But if you are going to allow it, it should work correctly. I leave that to the developers. -rich -- 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 Alpha-4 synaptic error
After a clean install (i386 desktop) I receive an error when attempting either: 1. System/Administration/Update Manager 2. System/Administration/Synaptic Package Manager An error occured The following details are provided: E:ERROR: could not create configuration directory /home/root/.synaptic - mkdir (2 No such file or directory) I do have a directory /root/.synaptic and obviously there is no such thing as /home/root where it appears to be looking. -rich -- 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: Hardy Alpha-3 networking
The problem shown below appears to have been resolved with tonight's update. tnx -rich On Jan 15, 2008 9:39 PM, Richard Mancusi [EMAIL PROTECTED] wrote: On Jan 15, 2008 8:40 PM, Richard Mancusi [EMAIL PROTECTED] wrote: On Jan 15, 2008 6:43 PM, Emilio Pozuelo Monfort [EMAIL PROTECTED] wrote: (``-_-´´) -- Fernando wrote: On Monday 14 January 2008 17:14:29 Brian Murray wrote: You should have to authenticate before modifying the network configuration. On my Hardy systems and a daily build of the Live CD, there is an Unlock button and selections remain greyed out until I unlock the application. If your system is fully up to date and the Unlock button is not there then you should submit a bug report. Your issues regarding changing the network configuration are probably a direct result of your not being authenticated. Thanks, I'm up to date, and using the menus, I just get a full grayed window and cant manage my networks options. If I try the old Network Monitor 2.12.1, it just says that the interface (either and both eth0 and eth1) doesnt exist. That sounds like bug 176060. Now that gnome-system-tools uses PolicyKit, you need to run it as a normal user, and not through gksu. Could you verify that you have network-manager-gnome 0.6.5-0ubuntu11, which fixed this issue, and that running 'gksu network-admin' keeps it greyed out, and that running 'network-admin' you can unlock it? Regards, Emilio Tonight's upgrade included several PolicyKit pkgs and I did verify that I am running network-manager-gnome 0.6.5-0ubuntu11 and network-manager 0.6.5-0ubuntu17. Now clicking on Unlock yields a window stating: Could not authenticate An unexpected error has occurred. This occurs by simply clicking on the Unlock button - not given the chance to enter a password. -rich I need to reply to my own email to add info. I attempted to re-start a service and received the same error - so it has nothing to do with networking but rather authentication. You had already assumed that, I am simply proving it. System/Administration/Services click on Unlock and receive the following message Could not authenticate An unexpected error has occurred. -rich -- 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: Hardy Alpha-3 networking
On Jan 15, 2008 6:43 PM, Emilio Pozuelo Monfort [EMAIL PROTECTED] wrote: (``-_-´´) -- Fernando wrote: On Monday 14 January 2008 17:14:29 Brian Murray wrote: You should have to authenticate before modifying the network configuration. On my Hardy systems and a daily build of the Live CD, there is an Unlock button and selections remain greyed out until I unlock the application. If your system is fully up to date and the Unlock button is not there then you should submit a bug report. Your issues regarding changing the network configuration are probably a direct result of your not being authenticated. Thanks, I'm up to date, and using the menus, I just get a full grayed window and cant manage my networks options. If I try the old Network Monitor 2.12.1, it just says that the interface (either and both eth0 and eth1) doesnt exist. That sounds like bug 176060. Now that gnome-system-tools uses PolicyKit, you need to run it as a normal user, and not through gksu. Could you verify that you have network-manager-gnome 0.6.5-0ubuntu11, which fixed this issue, and that running 'gksu network-admin' keeps it greyed out, and that running 'network-admin' you can unlock it? Regards, Emilio Tonight's upgrade included several PolicyKit pkgs and I did verify that I am running network-manager-gnome 0.6.5-0ubuntu11 and network-manager 0.6.5-0ubuntu17. Now clicking on Unlock yields a window stating: Could not authenticate An unexpected error has occurred. This occurs by simply clicking on the Unlock button - not given the chance to enter a password. -rich -- 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: Hardy Alpha-3 networking
On Jan 15, 2008 8:40 PM, Richard Mancusi [EMAIL PROTECTED] wrote: On Jan 15, 2008 6:43 PM, Emilio Pozuelo Monfort [EMAIL PROTECTED] wrote: (``-_-´´) -- Fernando wrote: On Monday 14 January 2008 17:14:29 Brian Murray wrote: You should have to authenticate before modifying the network configuration. On my Hardy systems and a daily build of the Live CD, there is an Unlock button and selections remain greyed out until I unlock the application. If your system is fully up to date and the Unlock button is not there then you should submit a bug report. Your issues regarding changing the network configuration are probably a direct result of your not being authenticated. Thanks, I'm up to date, and using the menus, I just get a full grayed window and cant manage my networks options. If I try the old Network Monitor 2.12.1, it just says that the interface (either and both eth0 and eth1) doesnt exist. That sounds like bug 176060. Now that gnome-system-tools uses PolicyKit, you need to run it as a normal user, and not through gksu. Could you verify that you have network-manager-gnome 0.6.5-0ubuntu11, which fixed this issue, and that running 'gksu network-admin' keeps it greyed out, and that running 'network-admin' you can unlock it? Regards, Emilio Tonight's upgrade included several PolicyKit pkgs and I did verify that I am running network-manager-gnome 0.6.5-0ubuntu11 and network-manager 0.6.5-0ubuntu17. Now clicking on Unlock yields a window stating: Could not authenticate An unexpected error has occurred. This occurs by simply clicking on the Unlock button - not given the chance to enter a password. -rich I need to reply to my own email to add info. I attempted to re-start a service and received the same error - so it has nothing to do with networking but rather authentication. You had already assumed that, I am simply proving it. System/Administration/Services click on Unlock and receive the following message Could not authenticate An unexpected error has occurred. -rich -- 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: Hardy Alpha-3 networking
On Jan 14, 2008 11:14 AM, Brian Murray [EMAIL PROTECTED] wrote: On Sat, Jan 12, 2008 at 11:45:22PM -0600, Richard Mancusi wrote: Desktop i386 install Is the following a bug or can anyone change network settings via System/Administration/Network And can you verify it really changed by looking in the appropriate file. You should have to authenticate before modifying the network configuration. On my Hardy systems and a daily build of the Live CD, there is an Unlock button and selections remain greyed out until I unlock the application. If your system is fully up to date and the Unlock button is not there then you should submit a bug report. Your issues regarding changing the network configuration are probably a direct result of your not being authenticated. Thanks, -- Brian Murray @ubuntu.com The Unlock button is there and works exactly as you state ... all greyed out until my password is accepted. However, I still get the same results. Any change sends the gui into a status bar loop - back and forth never stopping. I killed it. I was curious to see if the Unlock button was actually doing anything so open it back up and fed it the wrong password. It was refused. Opened the Details tab hoping to find an error but it only states: Application: /usr/bin/network-admin Action: org.freedesktop.systemtoolsbackends.set My system was up to date, but there were more updates tonight. The following occurred: Could not install 'libflickrnet2.1.5-cil' Could not install the upgrades. The upgrade aborts now. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a) Re-running Update Manager showed the following 5 updates remaining. evolution, evolution-common, evolution-plugins, gdb, libglib2.0-0 I tried Network Settings again - same problems, nothing changed. Since you are not experiencing this problem it implies that there is something different between our systems. Either you are benefiting from residual, non-clean install data or I am missing something. Is it possible for me to get a download of exactly what you are using? I would be happy to test it with a clean installation. -rich -- 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 Alpha-3 networking
Desktop i386 install Is the following a bug or can anyone change network settings via System/Administration/Network And can you verify it really changed by looking in the appropriate file. Install took a DHCP address. When completed I tried to change the settings to a static with different DNS, etc. The box came up stating Changing Interface Configuration and the status bar went back and forth for 10 min before I killed it. In order to properly config my network connection it was necessary to edit: /etc/network/interface /etc/resolv.conf /etc/hosts Notes: 1. This is the same problem I had with Alpha-2. 2. Same results installing on 3 different computers at two locations 20 miles apart. -rich -- 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
