Related Categories:
Computers
Debian
Fedora
Gentoo
Linux
Mandriva
nix
RedHat
Slackware
SUSE
Ubuntu
|
|
|
|
Marco Ceppi: Bugs are not questions
It’s been a long standing policy that bugs are off-topic for Ask Ubuntu and for good reason, we have Launchpad which is the best place for bugs in Ubuntu to end up. Before I dive too deeply into the history of this issue and what we’re doing to fix this, if you have a bug please see here on how to report it! Despite having formed the “No bugs on Ask Ubuntu” policy over a year and a half ago we’ve ended up being too lax in how we identified and handled bugs. As a result the site is swimming with “Questions” that have no answer and likely never will because they are bugs.
To combat this we’ve mobilized the community to weed out, flag, and close these buggy questions which means a lot of questions will end up closed as off-topic. This isn’t a bad thing – in fact it’s quite a good thing. With each question getting a sign post saying “This is a bug, report your bug to Launchpad” any future users who stumble on to these questions from search engines will now know where to look, instead of finding disappointment in an answer-less ”question”. We need more help! If you happen to come across a question on Ask Ubuntu that’s a duplicate of an existing bug report, or clearly should be submitted as a bug report, click the “flag” button at the bottom of the post and let us know! The sooner we prune and notify users these are actually bugs the quicker we can get them logged against the appropriate Launchpad project/package. The result will be a more fluid experience for new users and future users (since all these bugs will be fixed!). If you have questions about whether a question is a bug you can join the Ask Ubuntu chat or ask on the Ask Ubuntu Meta site. Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Aurélien Gâteau: PyQt+WebKit experiments part 2: debugging
(This is part 2 of the PyQt+WebKit experiments series) In Part 1 I described how to embed WebKit in a PyQt application and how to expose PyQt objects in WebKit and manipulate them with JavaScript. Even if you are a great JavaScript master, you can’t avoid the occasional typo while writing JavaScript code in your application. This can be quite frustrating with QtWebKit because it likes to stay quiet: it won’t tell you about any error. Let’s have a look at an example. First here is loader.py, a simple Python script which loads a block of HTML:
import sys
from PyQt4.QtCore import *
from PyQt4.QtGui import *
from PyQt4.QtWebKit import *
class Window(QWidget):
def __init__(self):
super(Window, self).__init__()
self.view = QWebView(self)
layout = QVBoxLayout(self)
layout.setMargin(0)
layout.addWidget(self.view)
def main():
app = QApplication(sys.argv)
window = Window()
html = open(sys.argv[1]).read()
window.show()
window.view.setHtml(html)
app.exec_()
if __name__ == "__main__":
main()
And here is “broken.html”, our broken HTML code:
<html>
<head>
<script>
function brokenFunction(arg1, arg2) {
var result;
result = arg1 * 2;
result += arg2;
resul /= 4;
return result;
}
</script>
</head>
<body>
Complex computation:
<script>
document.write(brokenFunction(2, 3));
</script>
</body>
</html>
Notice the missing ‘t’ in “resul /= 4″? The last-resort, grandpa-debugged-js-this-way, debugging tool is still there: the mighty alert() function. Just stuff your code with calls to alert() and be happy… Anyone ever wrote code like that?
<html>
<head>
<script>
function brokenFunction(arg1, arg2) {
var result;
result = arg1 * 2;
alert("1");
result += arg2;
alert("2");
resul /= 4;
alert("3");
return result;
}
</script>
</head>
<body>
Complex computation:
<script>
document.write(brokenFunction(2, 3));
</script>
</body>
</html>
Easy enough, no? With the great alert() function we can quickly pinpoint the bug in our brokenFunction() is between alert(“2″) and alert(“3″). Can we do better?alert()-style debugging gets old very fast. Clicking that “OK” button is a pain. Fortunately, there is a way to get more useful feedback from our PyQt application. The job of the QWebView class is to show the content of a QWebPage instance. By default QWebView creates its own instance of QWebPage, but it is possible to replace this instance with our own QWebPage. The QWebPage class has a few virtual methods. Among them, the javaScriptConsoleMessage() method is the one we are looking for: it is called every time console.log() is called from JavaScript. Here is an implementation of WebPage which uses Python logging module to get JavaScript console messages out:
import logging
from PyQt4.QtWebKit import *
class WebPage(QWebPage):
"""
Makes it possible to use a Python logger to print javascript console messages
"""
def __init__(self, logger=None, parent=None):
super(WebPage, self).__init__(parent)
if not logger:
logger = logging
self.logger = logger
def javaScriptConsoleMessage(self, msg, lineNumber, sourceID):
self.logger.warning("JsConsole(%s:%d): %s" % (sourceID, lineNumber, msg))
And here is “loader-log.py”, a loader which uses this class:
import os
import sys
from PyQt4.QtCore import *
from PyQt4.QtGui import *
from PyQt4.QtWebKit import *
from webpage import WebPage
class Window(QWidget):
def __init__(self):
super(Window, self).__init__()
self.view = QWebView(self)
self.view.setPage(WebPage())
layout = QVBoxLayout(self)
layout.setMargin(0)
layout.addWidget(self.view)
def main():
app = QApplication(sys.argv)
window = Window()
html = open(sys.argv[1]).read()
window.show()
window.view.setHtml(html)
app.exec_()
if __name__ == "__main__":
main()
If we load “broken.html” with “loader-log.py” we get the following on stderr: That should make it easier to find and fix our bug, even if we don’t get very useful file names or line numbers. javaScriptConsoleMessage() receives all console messages. This means our logger will also print out calls to console.log(). Here is “console-log.html”:
<html>
<head>
<script>
function chattyFunction(arg1, arg2) {
var result;
result = arg1 * 2;
console.log("result" + result);
result += arg2;
console.log("result" + result);
result /= 4;
console.log("result" + result);
return result;
}
</script>
</head>
<body>
Complex computation:
<script>
document.write(chattyFunction(2, 3));
</script>
</body>
</html>
When loaded with “loader-log.py”, we get this output: Not good enough?Getting the output of console.log() is nice, but modern browsers have much more efficient tools: if you open “broken.html” with Rekonq and look at the output in the Web Inspector Console, you can not only see console output, but you can also easily inspect your HTML tree and many other things.
Like us, Rekonq uses QtWebKit, so is there a way to get a similar tool? It is actually possible. Rekonq uses a class named QWebInspector. All that is necessary to get a nice inspector tool for our application is to:
Here is “loader-webinspector.py”, a new HTML loader which can show a web inspector when one presses F12:
import os
import sys
from PyQt4.QtCore import *
from PyQt4.QtGui import *
from PyQt4.QtWebKit import *
from webpage import WebPage
class Window(QWidget):
def __init__(self):
super(Window, self).__init__()
self.view = QWebView(self)
self.setupInspector()
self.splitter = QSplitter(self)
self.splitter.setOrientation(Qt.Vertical)
layout = QVBoxLayout(self)
layout.setMargin(0)
layout.addWidget(self.splitter)
self.splitter.addWidget(self.view)
self.splitter.addWidget(self.webInspector)
def setupInspector(self):
page = self.view.page()
page.settings().setAttribute(QWebSettings.DeveloperExtrasEnabled, True)
self.webInspector = QWebInspector(self)
self.webInspector.setPage(page)
shortcut = QShortcut(self)
shortcut.setKey(Qt.Key_F12)
shortcut.activated.connect(self.toggleInspector)
self.webInspector.setVisible(False)
def toggleInspector(self):
self.webInspector.setVisible(not self.webInspector.isVisible())
def main():
app = QApplication(sys.argv)
window = Window()
html = open(sys.argv[1]).read()
window.show()
window.view.setHtml(html)
app.exec_()
if __name__ == "__main__":
main()
The four steps I described are done in the “setupInspector()” method. And here is “console-webinspector.html”:
<html>
<head>
<script>
function chattyFunction(arg1, arg2) {
var result;
result = arg1 * 2;
console.log("result: %d", result);
result += arg2;
console.warn("result: %d", result);
result /= 4;
console.error("result: %d", result);
return result;
}
</script>
</head>
<body>
Complex computation:
<script>
document.write(chattyFunction(2, 3));
</script>
</body>
</html>
It is similar to “console-log.html” but takes advantage of two new features which do not work with the previous approach:
Loading “console-webinspector.html” with “loader-webinspector.py” and pressing F12 we get this:
Closing wordsThese two approaches should help you track down the nastiest bugs in your embedded JavaScript code. The Web Inspector approach is probably the most powerful one, but the Python logging approach can also be useful when tracking down bugs where it is more practical to have one single log output for both the PyQt and the JavaScript sides.
        Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Martin Albisetti: Support open source games, donate to 0 A.D.
0 A.D. is an awesome cross-platform game that is fun, has stunning graphics and is completely open source. They are looking for a round of donations to pay for some more development work, and as of this moment they're $634 USD short. I've just sent $50 their way. Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Jim Kielman: Ubuntu Forums Ubuntu +1 update for February 3/2012
It’s that time again. Alpha 2 was released yesterday, here is one members experience: http://ubuntuforums.org/showthread.php?t=1919854 There have also been several threads on kernel panics with the 3.2 version: http://ubuntuforums.org/showthread.php?t=1913073 http://ubuntuforums.org/showthread.php?t=1896087 http://ubuntuforums.org/showthread.php?t=1910857 My own problem was solved by removing an SD card from the card reader, but that really is only a work around. The problem looks to be solved with the next kernel release. The classroom session effenberg0x0 and I put on at UDW went well, but we found we had to much information for the length of the session. We are in discussion about doing some sessions using the Community Learning Project. Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Didier Roche: Unity 5.2 is now released!
Phew! It's been a crazy ride to release Unity 5.2 once ubuntu precise released its alpha 2, but we finally get there! Thanks a lot for all the community participation, we actually got 27 testers answering to Nick's call for testing. Those were high quality contributions and enabled us to get closer to the unity release. So, what's new since 5.0? Well, a lot! Test resultsHere are some feedback after 5 hours that I took to collect and analyze the test results from all the (numerous) comments that were on the test results:
A story of boot timeFinally and probably the most important feedback from the whole list, peope started to feel that "it was longer to start/boot". Jumping on this fact, we made some bootcharts on our machines to get real and precise values and you know what... the comments were right! The multimonitor support made the boot time badly regressing. Consequently, we decided to delay the release until today to get that fixed rather than pushing a version with this performance impact on intel cards. We finally got the fix, push it to trunk and now, this is all old story! The importance of testing defaultsSome testers remarked that in the system settings test, we never told to add gnome control center to the launcher. However, in the introduction text, we clearly expressed that we expect testers having the default settings (you have the guest session for it, use it, love it!) and the system settings is by default pinned in the launcher. To sum upUnity 5.2 is now building in the official repositories and should soon be available to all precise users. Thanks again to everyone participating in this project and see you soon for... 5.4 (or maybe a little bit before for an incoming compiz release that I heard of) ! Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Jorge Castro: Taking a different tack when it comes to growth.
One of the "good problems" I think we have is there's always things to do. As Charlie Kravetz points out, this can be a bad thing too. I wanted to post this on Planet to get a better feel for what other people think.
So for certain things I think we're doing too much, which is why we've streamlined some of the IRC workshops to be shorter. However as I thought of a more detailed answer to Charlie's concern I came up with the answer (I think). I don't think we have too many events, in fact, as we grow the number of events will grow, and our community will need to scale to match that. I am starting to realize that it's not a bad thing that people can't find the time to participate in everything. The real problem isn't that Charlie doesn't scale, it's that someone needs to have his back. So perhaps when events do clash we should look at which teams have what coverage in what events. For example, Charlie clearly needs to do ISO testing, but at the same time Xubuntu should have coverage in developer week because it's really one of the best places to find new contributors that can .... help Charlie do ISO testing. Catch 22. So maybe from a team level instead of an individual level we should be focusing on finding people who can jump in when a team is overtaxed for a week. For example, in hindsight maybe we could have done a better job helping Charlie find someone to cover developer week for Xubuntu. A forum thread, a planet post, a tweet, a mention on our Facebook page? These are all things we could do to help the creaking an overburdened person might face. It's a bummer that one person can't scale, but at the same time having different people focusing on different individual things will probably be healthier in the long run. Discuss! Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Jim Campbell: Configure gedit for documentation
I’ve been maintaining the gedit documentation since the run-up to the gedit 3.0 release, and doing so has helped me to get to know some of the ins-and-outs of the program. What can I say, it’s one of the perks of writing documentation – you get to know the software that you’re documenting. With that, though, I thought I’d pass along some of the basic configurations that help me to write documentation more quickly, and in a more consistently-formatted way. Here’s a quick run-down of some settings that you may find helpful: View Preferences – Edit > Preferences > View:
Editor Preferences: Edit > Preferences > Editor
With regards to plugins, I recommend enabling the dashboard plugin (which will be available as part of gedit 3.4, included in Ubuntu 12.04, Fedora 17, OpenSUSE 12.2, etc.), and the gedit snippets plugin. In the near future I’ll be writing up a post about using gedit snippets. One other neat feature that I often use with gedit is the keyboard shortcut for moving a line up or down within the text. If you position your mouse cursor on any point in a line, and then press Alt + Up Arrow, it will move the entirety of that line up within the text. Pressing Alt + Down Arrow will move that line down within the text. Simple enough! (The complete list of gedit shortcut keys is available in the user help, by the way. Just open up gedit and press F1.) Do you have any suggestions or tips for using gedit to write documentation? If so, I’d appreciate you sharing them with me in the comments. Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Brandon Perry: What browsers support @import in their CSS?
I prefer the following CSS: <html> But not all browsers support @import. I wanted to see exactly which ones didn't so I used browsershots.org with a simple test. Here are the results: http://browsershots.org/http://volatileminds.net/import_test.html Black means it supports it. White means it doesn't.  Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Ubuntu Classroom: Developer Week: Summary Day 3
It’s sad news, yes – Ubuntu Developer Week for the 12.04 cycle is over. It’s been three fantastic days full of action-packed sessions. If you couldn’t attend, check out the logs of the sessions, all of them are posted on the UDW page.
Here’s what happened on day 3, yesterday:
What a fantastic day. Thanks a lot to all the speakers who made this Ubuntu Developer Week possible. Thanks a lot to everyone who attended as well. It was great to see a lot of interaction, questions and interest. Until next time!         Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
The Fridge: Precise Pangolin Alpha 2 Released!
Welcome to Precise Pangolin Alpha 2, which will in time become Ubuntu 12.04. Pre-releases of Precise Pangolin are *not* encouraged for anyone needing a stable system or anyone who is not comfortable running into occasional, even frequent breakage. They are, however, recommended for Ubuntu developers and those who want to help in testing, reporting, and fixing bugs. Alpha 2 is the second in a series of milestone images that will be released throughout the Precise development cycle. This is the first Ubuntu milestone release to include images for the armhf architecture, for the ARM CPUs using the hard-float ABI. New packages showing up for the first time include:
You can download Alpha 2 images here: http://cdimage.ubuntu.com/releases/precise/alpha-2/ (Ubuntu, Ubuntu Server) Additional images are also available at: http://cloud-images.ubuntu.com/releases/precise/alpha-2/ (Ubuntu Cloud Server) Alpha 2 includes a number of software updates that are ready for wider testing. This is quite an early set of images, so you should expect some bugs. For a more detailed description of the changes in the Alpha 2 release and the known bugs (which can save you the effort of reporting a duplicate bug, or help you find proven workarounds), please see: http://www.ubuntu.com/testing/ If you’re interested in following the changes as we further develop 12.04, we suggest that you subscribe initially to the ubuntu-devel-announce list. This is a low-traffic list (a few posts a week) carrying announcements of approved specifications, policy changes, alpha releases, and other interesting events. http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce Originally sent to the ubuntu-release mailing list by Kate Stewart on Thu Feb 2 20:27:28 UTC 2012 Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Tony Whitmore: Ubuntu Podcast, Season 5
We’re going out for the Planning Curry for season five of the Ubuntu Podcast this week. Over the years, it has become a tradition for all the presenters to go out for a curry before the start of the season. It’s a time to catch up in person, as we haven’t seen much of each other since the end of the last season. But it’s also a chance to discuss any changes we want to make to the show and throw ideas for new segments around. So, if there’s anything you’d like to see in the new season, whether it’s an idea for a segment or a change to something we already do, please let us know. You can leave a comment on this blog post or get in touch using any of the methods on the show website. Thanks!
Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Lubuntu Blog: DEFT Linux 7
Another Linux distro updated now with Lubuntu in its core: DEFT Linux 7. This is a great recovery and forensic distro with lots of tools to aid for repairing partitions, damaged clusters, recover lost data, make network tests and configurations, etc. I can't write the whole list of apps included in this release, not enough space :) Mmm, thatartwork sounds familiar to me... :D Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Ubuntu Classroom: Developer Week: Summary Day 2, Outlook Day 3
Day 2 of Ubuntu Developer Week is over and it was awesome! Logs up are up at the UDW page, so go and check them out if you couldn’t make it yesterday.
What a lot of excellent content. What a huge amount of great people and great questions. The good thing is, there’s more. Here’s what our last day has for you:
Have a great time!         Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Khairul Aizat Kamarudzzaman: Ubuntu-my Collaboration with Federal of Malaysian Consumers Association (FOMCA)
 Last month i get a call and email from FOMCA representative asking community to support their national program Access to Knowledge- National Campaign on A2K Policies , Campaign to promote Open Source Software to consumers . We (Ubuntu-my) are more than happy to corporate and collaborate with FOMCA to do our best to make the policy & campaign success. I will bring this topic to our 1st Ubuntu-my Meetup for 2012 Overall objective: Increase the uptake of free, legal software for Malaysian consumers Activities: Impact expected: Here i share the full post by FOMCA and draft brochure for the awareness program. 
I also hope that Ubuntu Community Globally & FOSS Community will give us support to make this happen ! \0/ May Ubuntu will r0cking all over Malaysia … Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Ubuntu Kernel Team: [Precise] linux kernel 3.2.0-13.22 uploaded (ABI Bump)
We have uploaded a new Precise linux kernel. Please note the ABI bump. The most notable changes are as follows: * Fixes for radeon issues on MacBook Pro 8,2 The full changelog can be seen at: https://launchpad.net/ubuntu/+source/linux/3.2.0-13.22 Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Ubuntu Cloud Portal: juju can help your development team speed up iteration
In this blog post the Launchpad team uses juju to deploy oops-tool, a Django-based tool that aggregates bug reports for the Launchpad project. We typically talk about services that people commonly deploy, such as Mediawiki or WordPress. However there is another use case for juju that is just as powerful, as a tool to help iterate on whatever you’re working on faster. oops-tool is not a general tool that most people will want to use; it’s very specialized. However the Launchpad team have encapsulated their service in a charm. Any person can now deploy oops-tool in 4 commands. Now have a think about a project you and your team might be working on and the complexities of that service and how wonderful it would be if any person on any team could deploy any service in your project’s code base with that kind of ease. You’re codifying the management of your service so that as you work on a feature branch you can deploy, test, and then iterate. juju strives to deploy your service in the same way that people strive to have their software build in one set of processes, but it’s more than just that. Deploy-and-forget is nice, but being able to manage a service over its lifetime is what people need in the cloud and you can do that with a juju charm. Launchpad has a myriad of services it provides, we’ll keep you in touch on how that team is using juju to simplify their processes. Got more questions about juju and how we can help you manage in the cloud? Feel free to Contact Us and ask questions! Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Stéphane Graber: Ever wanted an armhf container on your x86 machine? It's now possible with LXC in Ubuntu Precise
It took a while to get some apt resolver bugs fixed, a few packages marked for multi-arch and some changes in the Ubuntu LXC template, but since yesterday, you can now run (using up to date Precise):
And enjoy an armhf system running on your good old x86 machine. Now, obviously it’s pretty far from what you’d get on real ARM hardware. Also, because of limitations in qemu-user-static, a few packages from the “host” architecture are installed in the container. These are mostly anything that requires the use of ptrace (upstart) or the use of netlink (mountall, iproute and isc-dhcp-client). This feature should be used as an improvement on top of a regular armhf chroot using qemu-user-static and not as a replacement for actual ARM hardware (obviously), but it’s cool to have around and nice to show what LXC can do. I confirmed it to work for armhf and armel, powerpc should also work, though it didn’t succeed to debootstrap when I tried it earlier today. Enjoy! Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Aaron Toponce: DISCLAIMER
DISCLAIMER: By sending me email, you agree to the following:
Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Alexander Sack: Developer Platform & Ubuntu sessions at Linaro Connect Q1.12
Ubuntu our LEB and the overall Developer Experience on ARM are hot topics again for Linaro Platform Team this Connect (http://connect.linaro.org). Be sure that you have checked and subscribed to your preferred sessions by the Developer Platform Team. Even if you cannot attend the event in person, there is no reason to not participate remotely. To make this even more convenient and interactive, Linaro will experiment with google hangouts this time. Be sure to check this out! Here a convenience list of sessions by the DevPlatform Team announced by Ricardo Salveti a few days ago on linaro-dev: Ubuntu LEB and LAVA: Current status and future planning for proper image testing and validation https://blueprints.launchpad.net/linaro-ubuntu/+spec/linaro-platforms-q112-lava-and-ubuntu-leb-testing-validation Improvements and future discussions for LTs and the Ubuntu LEB https://blueprints.launchpad.net/linaro-ubuntu/+spec/linaro-platforms-q112-lt-platform-discussions Packaged Kernel CI: Current Status and Next Steps https://blueprints.launchpad.net/linaro-ubuntu/+spec/linaro-platforms-q112-packaged-kernel-ci-next-steps Sysroots: Automation, Maintenance and Future Work https://blueprints.launchpad.net/linaro-ubuntu/+spec/linaro-platforms-q112-sysroots-automation-maintenance U-Boot-Linaro Future Planning https://blueprints.launchpad.net/linaro-ubuntu/+spec/linaro-platforms-q112-u-boot-linaro-future-future-planning Developer Platform: Future Planning https://blueprints.launchpad.net/linaro-ubuntu/+spec/linaro-platforms-q112-dev-plat-future-planning Cross Build with Multi-Arch: Current state and future planning https://blueprints.launchpad.net/linaro-ubuntu/+spec/linaro-platforms-q112-cross-multi-arch-support Exciting stuff! The original post to the mailing list can also be found in the archives: Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
|
|
Launchpad News: How to do Juju – Charming oops-tools
Recently the Launchpad Red Squad and Product Team started working on a new cloud project. As part of that project we’ll be using Juju, a tool that helps you easily deploy services on the cloud. As an opportunity to learn more about how Juju works, I wrote a charm to deploy oops-tools, an open source Django application that helps visualize and aggregate error reports from Launchpad, on Amazon’s EC2 and Canonical’s private Openstack cloud. You might be asking, what’s a charm? Charms are basically instructions on how to deploy services, that can be shared and re-used. Assuming you already have a bootstrapped juju environment, deploying oops-tools using this charm is as easy as: That’s it! With just a few commands, I have an instance of oops-tools up and running in a few minutes. Under the hood, the oops-tools charm:
There’s still work to do, like add support for RabbitMQ (oops-tools uses rabbit to provide real-time error reports), but this initial iteration proved useful to learn about Juju and how to write a charm. As it is, it can be used by developers who want to hack on oops-tools and can be easily changed to deploy oops-tools in a production environment. If you’d like to give it a try, you can get the charm here: https://code.launchpad.net/~charmers/charms/oneiric/oops-tools/trunk Enjoy!
Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu |
More precisely, we got multimonitor support with screen edge detection, "push to reveal" launcher behavior to avoid false positive when hitting the back button of firefox, per workspace alt-tab switcher, new home dash, automaximize only on netbooks and a lot of small details that matter.
We strongly recommend people using the guest session to ensure all settings and environment are correct for the tests!
