Re: Does metacity compositor use acceleration?
Jerone Young wrote: I'm curious on how do you cut on compositing in metacity. Would love to use it. Would much rather use it then Compiz. From http://library.gnome.org/misc/release-notes/2.22/ gconftool-2 -s --type bool /apps/metacity/general/compositing_manager true Be aware that Not all graphics hardware reliably supports compositing, so this feature is currently turned off by default and not yet exposed in the preferences Cheers, Emilio signature.asc Description: OpenPGP digital signature -- 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: Hardware Database and Client - Dohickey
Mackenzie Morgan wrote: Wouldn't it go in Universe? I thought Multiverse was for stuff like Real Player--free of cost but not free software. Dohickey's all open source, right? So it'd go in Universe. Free software != Open Source Universe is for open source and free software. Being open source isn't enough, it needs to be redistributable and modifiable... signature.asc Description: OpenPGP digital signature -- 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: Accepted: ubuntu-vm-builder 0.2 (source)
Sarah Hobbs wrote: I can't see the point in doing additional paperwork for bugfix-only releases, which will automatically get accepted either. Totally agreed. I also raised my disagreement, but the explanation to this policy was that this would mean that MOTUs (btw note that this also affects core-devs uploading to universe) will think about the upload twice, and will read the changelog and ensure it's a bug-fix only release. I understood it at that moment, but thinking about it again I can't agree with it, for 2 main reasons: 1) If we trust MOTUs to upload anything to the archive, why don't we trust them to just upload bug fixes before FeatureFreeze? I also see this similar to the self-freeze for the Hardy alphas. The Release Managers don't require core-devs filling a bug with the changelog. They just trust them, and everything should be working fine so far, as otherwise they wouldn't have done it for 5 alphas. 2) After uploading these two [1] [2] changelogs (specially the first one) from [3] I feel somewhat stupid :) After seeing multiple complaints about this new system, i'd suggest bringing it up at the MOTU meeting, but as I am in the MOTU release minority on this issue, my hands are somewhat tied. I'll try to make the meeting and raise this there too. But I'd like to propose this: 1) We don't require any paperwork at all. If it's bug-fix only, just upload (or request a sync). 2) If there are problems with this (as in people uploading non-bugfix-only releases) we reconsider it. Thoughts? Emilio [1] http://launchpadlibrarian.net/12134194/changelog.diff [2] http://launchpadlibrarian.net/12134253/changelog.diff [3] https://launchpad.net/bugs/193953 signature.asc Description: OpenPGP digital signature -- 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
(``-_-ยดยด) -- 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 signature.asc Description: OpenPGP digital signature -- 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: Accepted: mono-tools 1.2.6-1ubuntu1 (source)
[ CCing -discuss as I'm moderated on -devel ] Martin Pitt wrote: Hi Emilio, Hi Martin, Emilio Pozuelo Monfort [2007-12-23 4:15 -]: mono-tools (1.2.6-1ubuntu1) hardy; urgency=low . * Sync with Debian. * debian/patches/03_mozilla-home.dpatch: - Use firefox instead of xulrunner. Since we have xulrunner-1.9 in main now and want to switch the world to it (and get rid of firefox in favor of firefox-3), can we just drop this and build against xulrunner-1.9? Yeah, but this needs some changes to the build system and to some files. I asked Alexander if he had a patch for this, as he has prepared the migration for some packages, but he didn't have it when I asked him. Alexander, you don't happen to have a patch for this yet, do you? If so, that's fantastic. If not, I could try to look into this, but I may need some guidance (although it might be enough with the wiki and looking at other patches). Cheers, Emilio Martin signature.asc Description: OpenPGP digital signature -- 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: Artwork / packagefreeze exception request
Jeff Schroeder wrote: In the spirit of eye candy and the Consistent and Easy to Use Login Screen and Unlock Screensaver[1] specification, I've made a human gnome-screensaver lock dialog theme. Is it possible to change this now that Hardy is opened? Kenneth, any opinions on it? Cheers, Emilio. Currently, this is what the screensaver unlock dialog looks like: http://www.digitalprognosis.com/opensource/ubuntu/gnome-screensaver-default.png And with the new human theme for users with and without faces: http://www.digitalprognosis.com/opensource/ubuntu/01-human-gnome-screensaver.png http://www.digitalprognosis.com/opensource/ubuntu/02-human-gnome-screensaver.png http://www.digitalprognosis.com/opensource/ubuntu/03-human-gnome-screensaver.png http://www.digitalprognosis.com/opensource/ubuntu/04-human-gnome-screensaver.png You can download it here: http://www.digitalprognosis.com/opensource/ubuntu/gnome-screensaver-human.tar.bz2 This makes the screensaver unlock use the same images as the gdm login albeit scaled down. Doing this increases the overall desktop experience and wow factor of Ubuntu slightly by adding consistency. No strings are changed that require translation, no package is seriously modifed, and nothing risky happens. It is a glade file, a dialog specific gtkrc, and 2 images that need to be added to the gnome-screensaver package. The glade file is just a modified version of the current default. I'm asking for a freeze break for this simply because it is a non-intrusive change that makes Ubuntu look better. Besides my being an idiot and missing the artwork / betafreeze, are there any good reasons to _not_ ship this with gutsy? Perhaps it could be included after the beta freeze? Installation: - Extract the contents of gnome-screensaver-human.tar.bz2 into /usr/share/gnome-screensaver. - Run 'gconftool-2 -s --type=string /apps/gnome-screensaver/lock_dialog_theme human' Reverting back to the default: - Run 'gconftool-2 -s --type=string /apps/gnome-screensaver/lock_dialog_theme default' [1] https://wiki.ubuntu.com/UnifiedLoginUnlock signature.asc Description: OpenPGP digital signature -- 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: Tracker live search in Deskbar applet by default?
Scott James Remnant wrote: On Thu, 2007-09-27 at 18:59 +0200, Emilio Pozuelo Monfort wrote: I've been discussing with Sebastien Bacher whether it's a good idea to enable the Tracker Search Live plugin in the Deskbar applet by default, and we think it's a good idea to discuss it wider here, and see what you think about it. There doesn't seem to be any performance hit to enabling it, since it's just checking the index and not actually indexing to find your searches? That's true, yes. I must admit, I much prefer the Search Live plugin to the Search Tool one; it puts the results exactly where I expect them to be! Yes, it looks more reasonable there. Although the option for open tracker-search-tool is useful too. Should be enabled soon :-) Scott signature.asc Description: OpenPGP digital signature -- 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: Launchpad bug statuses
Christian Robottom Reis wrote: On Tue, Oct 02, 2007 at 11:32:25PM +0200, Emilio Pozuelo Monfort wrote: So this is interesting, because ideally you want some record that the bug has been forwarded and fixed upstream. What I want is the bug to be fixed ;) I don't care that much whether there's a record or not (it may be good to have it, but won't hurt if it isn't there). Well.. - Third, a question: why don't you report the bug upstream anyway, and update its status manually? Too much work? This looks like the second question, but yes, why should I report it in SF if I ping the upstream author, he takes a look at the code, and fixes the issue? It looks useless to me. The software engineer in me does appreciate it when he finds that changes in the code are attached to a bug report which I can look at later to try and figure out rationale, timing and responsibility. I understand you, and see your point. But if forwarding the bug report to the remote bug tracker, and then adding a bug watch takes e.g. 3 minutes, whereas pinging on IRC takes 10 seconds (and it also means a fast response) then I prefer those 10 seconds. But this is not always possible, and not always desirable. However I think if both forwarding the report and pinging on IRC took the same time, I would forward it. But I agree that we need to be practical and I'm still not sure what sort of UI would help you there. Maybe if the bug UI was just faster to use (i.e. full-ajax direct manipulation) this would be less of a problem. You could make this easier, yes. For example, if adding a bug watch meant opening a portlet or elsewhere, and then introducing the #bugnumber or the url from the upstream bug. Instead of having to go to +affectsupstream, and then going back to the bug report. - Fourth, would it help is Launchpad made it really easy for you to post the bug to SourceForge, perhaps opening the bug-filing page with all your details filled in and just waiting for you to submit? I think so. That would be really useful, since that would save a lot of time (not that reporting a bug takes one hour, but when you report a lot, then there's a big difference). This would have a big risk, though, which is that there could be 'spam' in upstream's bug trackers, but this could be avoided by only letting people in the Distribution Bug Contact team to report bugs upstream using that method. Well, my initial thoughts would be that you would need to have an account in the upstream bugtracker to actually forward the bug. I don't think this is a big problem, at least for bug triagers. I personally have an account on most of the big bug trackers (SF, b.g.o, fd.o...) and in those small trackers for packages that I triage. If you could implement this, the new workflow for forwarding a bug to upstream could be: - Clicking on 'Forward to Upstream' - Add some information to the description, or change the summary (if necessary) - Introduce the remote # bug number or url into Launchpad so it adds a bug watch (not sure if this could be automatized). I think I'll surely forward more bugs than I actually do. This is complicated for trackers such as debbugs, but would address this concern for most other bugtrackers. It is somewhat cumbersome, but not too cumbersome for Seb's b.g.o use case or sourceforge.net in general, since you only need one account for the N projects hosted there. signature.asc Description: OpenPGP digital signature -- 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
Tracker live search in Deskbar applet by default?
Hello there! I've been discussing with Sebastien Bacher whether it's a good idea to enable the Tracker Search Live plugin in the Deskbar applet by default, and we think it's a good idea to discuss it wider here, and see what you think about it. Actually, the Tracker Search Tool plugin is enabled by default. What it does is simply create an Actions item which is 'Search for $yoursearch with Tracker Search Tool'. The Tracker Search Live plugin, which is disabled by default at this moment, displays directly the tracker results for your query in the search window. That way you don't have to open Tracker Search Tool in case your search shows what you are looking for (although you can still click on 'Search for with Tracker Search Tool'. So what do you think about this? Thanks for your comments. Emilio P.S.: Tracker 0.6.3 was out a couple of days before beta, but the release team decided to wait after it to upload it, since it was too late for that change. Will be in the repositories tomorrow. signature.asc Description: OpenPGP digital signature -- 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: tracker in gutsy [was: Re: Ubuntu Technical Board meeting, 2007-09-25]
[Moved to -discuss] Martin Pitt wrote: Hi, Matt Zimmerman [2007-09-25 13:10 -0700]: After a wandering discussion about the challenges facing Ubuntu Server, community and Canonical developers and the project in general, Soren's application was approved. Please welcome him as our newest core developer! Congratulations, Soren! Well-earned! Mark Shuttleworth raised Tracker for discussion, which is the subject of an ongoing email exchange between the Board, upstream developers and Ubuntu developers. There remain some bugs affecting Tracker which make it unsuitable for release with Ubuntu 7.10, but the developers involve hope to have them resolved in time to keep it in the release. As a contingency plan, Tracker can be easily disabled by default via gconf if the problems are not corrected in time. That was my plan, too. Upstream is very cooperative and has worked with us closely to have something good for release. He will release 0.6.3 very soon It's already there, although Jamie is working on fixing some memory leaks, and in fixing bug 130935 [1], which is targeted for beta (although it won't make the target, obviously). We should have this just after Beta (on Thursday or Friday), and then ensure it's Ok to have it by default, fixing any possible bugs it may have. now which addresses some of the worst problems like stopping indexing when switching to battery, and much better I/O behaviour. In particular, he fixed all the 'fix committed' bugs on [1], which includes all the critical/high bugs. Very impressive, thanks Jamie! It's not the type of update we would commonly do after beta, but I think it is worth giving a try. Emergency fallback would be to disable it by default if the new indexing format gives troubles. Pretty reasonable. Although I hope it isn't necessary ;) Have a nice day, Emilio Thanks, Martin [1] https://bugs.edge.launchpad.net/ubuntu/+source/tracker/ signature.asc Description: OpenPGP digital signature -- 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: GParted 0.3 packaging
Alex Jones wrote: GParted has had pretty much universal support for moving partitions and file systems since September 2006. Unfortunately, we're still packaging some old version of 0.2. Please can someone look at pulling down a new upstream release and packaging it for Feisty (if not, Gutsy)? It's already in Gutsy: [EMAIL PROTECTED]:~$ apt-cache madison gparted gparted | 0.3.3-2ubuntu1 | http://archive.ubuntu.com gutsy/main Packages gparted | 0.3.3-2ubuntu1 | http://archive.ubuntu.com gutsy/main Sources If you want it in Feisty, you can request a backport here: https://bugs.launchpad.net/feisty-backports/+filebug Cheers I think this is important, as it gives more technical users more flexibility in managing their partitions when preparing an installation with our Live CD, in particular moving an NTFS partition further up the disk to put an Ubuntu installation at the start. Thanks signature.asc Description: OpenPGP digital signature -- 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: Packaging of wxwidgets2.8
Jerone Young wrote: Sweet! IS this fro 2.8 to make it into feisty. This fixes my favorite feature for VLC .. always on top now works under metacity (gnome). It's already there: http://packages.ubuntu.com/feisty/source/wxwidgets2.8 Cheers Emilio On 2/23/07, Barry deFreese [EMAIL PROTECTED] wrote: Daniel Holbach wrote: Hello everybody, Matthias doko Klose asked me if I knew somebody who'd package wxwidgets2.8. It's available from http://wxpython.org/download.php - it's just that the Ubuntu packages from there need to merge packaging changes of the 2.6 package. If you want to work on that, it'd be appreciated - just contact doko or me. Have a nice day, Daniel OK, I stuck a 2.8 package up on REVU if folks want to pick it apart. http://revu.tauware.de/details.py?upid=4480 Thanks! Barry deFreese (aka bddebian) -- ubuntu-devel mailing list [EMAIL PROTECTED] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel signature.asc Description: OpenPGP digital signature -- 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: Error in wiki page DebuggingProgramCrash?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 William Tracy wrote: The debi command is more correct. $ debi bash: debi: command not found This is on KUbuntu/Edgy. It's included in devscripts -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGDFbKPHB1VjBTaKERAlkzAJ0dkiJVNKIlC9DcvSqnuHzArZWEsACcC9p7 jIgM+WmD9dTltPt33PgrOGA= =QzNB -END PGP SIGNATURE- -- 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
