[11:03] <utkarsh> hello, i have a problem with Ubuntu 10.04 - my swap memory gets full after 5-6hours of computer usage
[11:03] <utkarsh> should i report a bug? if yes, then what dump should i provide?
[11:04] <ddecator> utkarsh: you may wish to check in #ubuntu+1 to see if anyone else has encountered that
[11:04] <utkarsh> okay, thanks :)
[13:55] <xteejx> bug 237738....the wallpaper-tray package is no longer active, should this be set wont fix?
[13:55] <ubot4`> Launchpad bug 237738 in wallpaper-tray (Ubuntu) "wallpaper-tray crashes (often) when adding new (large) folders (heat: 14)" [Undecided,Incomplete] https://launchpad.net/bugs/237738
[13:58] <tobi122> hi guys, i found a problem with my notebook and the kernel module r8169 (for ethernet card) and i fixed the problem, but i dont know if i had to write it to lunchpad, can anyone help me?!
[13:58] <xteejx> What did you do to fix it? Did you write a patch?
[13:59] <tobi122> no only get a newer driver from realtek and blacklist the old module
[13:59] <tobi122> but it fix a problem with the ethernet card.... befor the wakeonlan was always enabled and couldnt be disabled...
[14:00] <xteejx> Check if it's reported on LP, if not file a bug report explaining what the problem was, what you expected, and how step-by-step how you fixed it.
[14:01] <tobi122> okay, i will try
[14:01] <tobi122> one last question: in which topic in lp it comes
[14:02] <tobi122> for kernel bugs?
[14:02] <tobi122> or which package is right for this
[14:04] <kklimonda> xteejx: the fact that package isn't developed anymore doesn't mean we can close bugs as long as it's supported
[14:04] <kklimonda> (following you up from #-motu ;) )
[14:05] <yofel> even if the package is in universe? I thought we only supported main packages? (I seriously have no idea what to do here either)
[14:05] <kklimonda> yofel: hmm.. package is still in karmic
[14:05] <xteejx> that's what I thought
[14:06] <yofel> kklimonda: yes, but the bugfix would if anything get into lucid, were the package was dropped
[14:06] <yofel> *where
[14:06] <kklimonda> yofel: I think we could do SRU anyway *if* anyone cared to fix it
[14:06] <xteejx> it's unlikely, it hasn't been actively developed since july 2007
[14:06] <kklimonda> sure it is, the bug will rot there for another 12 months
[14:08] <xteejx> this is what I mean...what's the point? (with all due repsect)
[14:08] <kklimonda> xteejx: if the bug is still reproducible it doesn't disappear when we sweep it under the rug
[14:09] <kklimonda> xteejx: sure, if you can't contact the original reporter and no one else can reproduce it you can close it. but not because it's no longer maintained upstream
[14:10] <xteejx> !info wallpaper-tray karmic
[14:10] <ubot4`> xteejx: wallpaper-tray (source: wallpaper-tray): wallpaper changing utility for GNOME. In component universe, is optional. Version 0.5.5-0ubuntu3 (karmic), package size 97 kB, installed size 388 kB
[14:11] <kklimonda> we could close all bugs from packages in universe that are dead upstream - the chance of anyone fixing them is slim to none
[14:11] <xteejx> I suppose you're right kklimonda :) I was really unsure about this bug and thought it would be a Won't Fix since it isn't developed upstreamed anymore, but if someone wanted to fix it in Ubuntu I suppose they could
[14:12] <xteejx> That would probably take a good hit out of the numbers, but I suppose it's unrealistic
[14:46] <TheNewAndy> hi, I'm running lucid, and I have a reproducible crash bug in nautilus
[14:46] <TheNewAndy> but apport has stopped showing up when I crash it
[14:47] <TheNewAndy> apport showed up the first time, but I closed it while I worked out the simplest
[14:47] <TheNewAndy> way to reproduce the bug
[14:48] <TheNewAndy> Does it keep a list of crashes to avoid reporting that I can clear?
[14:49] <yofel> TheNewAndy: you you have a crash file in /var/crash/ ?
[14:49] <yofel> *do you
[14:49] <TheNewAndy> yes
[14:50] <yofel> then apport already knows of the crash, just run 'ubuntu-bug <crashfile>' to report it
[14:51] <TheNewAndy> excellent, thanks
[17:02] <Damascene> hello, is there a bug about wireless connection always connect to what ever network it see?
[17:09] <xteejx> Damascene: I don't understand
[17:10] <xteejx> If you mean it is auto connecting, this is not a bug - you can remove it in the Edit Connections option in the right click menu
[17:10] <Damascene> xteejx, when ever I login it connects to what ever wireless network is there
[17:10] <Damascene> there is about 20 network there
[17:10] <xteejx> How can it connect without a wireless key?
[17:10] <Damascene> I didn't set auto connect to any of it
[17:11] <Damascene> will it tries every one
[17:11] <Damascene> and if it find one without key it will calm down
[17:11] <Damascene> it collect them from every place I go to
[17:11] <Damascene> collects
[17:11] <xteejx> How did you find out it does this?
[17:11] <Damascene> by looking to the screen
[17:12] <xteejx> are you sure they're not just probe requests?
[17:12] <Damascene> what do you mean? "probe requests"
[17:12] <Damascene> I see the network icon searching and trying to connect
[17:12] <Damascene> until I click disconnect wireless
[17:13] <Damascene> by the way that in lucid
[17:13] <xteejx> That's normal, it's trying to search for a previously entered wireless access point
[17:13] <xteejx> All OS's do it
[17:13] <Damascene> but I wonder if there is open bug about it or not
[17:13] <Damascene> xteejx, may I ask if you are in the bug squad?
[17:14] <xteejx> No, I'm Bug Control and Bug Squad
[17:14] <Damascene> will what happens to me isn't normal
[17:14] <xteejx> Can you explain exactly what happens, what you see, etc
[17:14] <Damascene> ok
[17:15] <Damascene> first I login, I've wire connection. the network manger connect to the wire. show that it's trying to connect to the wireless but because it doesn't have the key it doesn't connect
[17:15] <Damascene> if it has it it will connect
[17:15] <Damascene> if there is no key it will connect
[17:16] <xteejx> Ok, and where do you see the problem, i.e. what part is the problem?
[17:16] <Damascene> if there is some available network it should say so. not connect automatic
[17:17] <Damascene> automaticly
[17:17] <xteejx> you mean open networks? (of course it can't connect to WEP/WPA/WPA2 without keys)
[17:17] <Damascene> what ever the word is
[17:17] <Damascene> ok do you find  a bug in what I said
[17:18] <xteejx> let me just clarify...everything is fine apart from the fact that the wifi tries to connect to open networks automatically?
[17:18] <persia> Damascene: I've had that behaviour on many of my machines since jaunty.
[17:18] <persia> It may be a bug, but it's not a regression, and it's not just you.
[17:19] <Damascene> xteejx, and it tries to connect to the protected ones too. and show you the screen to enter the key
[17:19] <xteejx> It may even be expected behaviour on the part of GNOME?
[17:19] <Damascene> persia, have it been reported before?
[17:19] <xteejx> Damascene: Ok, I understand...that it shouldn't do
[17:20] <xteejx> Unless they were connected to before, or you manually tried before, they'd be in "Edit Connections"....check that first just in case
[17:20] <Damascene> why you people who are in bug squad doens't have wiki page so some one could look in before he tries to ask stupid questions
[17:21] <xteejx> because it may not be a bug
[17:21] <Damascene> xteejx, what if there were connected to before? as every one have motorola modem here
[17:21] <xteejx> If they were connected to before from your machine, it would remember that you tried and would continue to try to connect asking for key etc
[17:22] <Damascene> no it shouldn't till I select auto connect
[17:22] <Damascene> as two of bug squad team doesn't know an open bug about that and after me doing some searches
[17:23] <Damascene> I've to open a bug, sorry
[17:23] <xteejx> every other OS does the same...even windows - it's so that people don't have to keep re-clicking to go onto their own router, i.e. at home you wouldnt expect to have to click it every time, you'd want it to reconnect itself
[17:24] <Damascene> xteejx, ubuntu isn't like every other os
[17:24] <xteejx> Also, Launchpad is searchable, you could have done this
[17:24] <Damascene> and I don't think windows was doing that
[17:24] <Damascene> xeros, I did. but titles aren't very clear alwayes
[17:24] <Damascene> always
[17:24] <xteejx> I've searched for you anyway so no worries. It doesn't appear to be a known problem
[17:26] <persia> FOund it: http://xkcd.com/416/
[17:26] <Damascene> what was that?
[17:27] <persia> It's a prior description of the issue: n-m is too agressive at trying to connect to strange networks.
[17:27] <Damascene> yeah :)
[17:28] <persia> But it's been that way since Intrepid or Jaunty or something.  I believe it's intentional.
[17:28] <xteejx> Yeah, I too think it's expected behaviour, not a bug. You can still file for a change at Ubuntu brainstorm though
[17:29] <persia> I'll disagree with that.  It's *always* a bug when someone's computer does something annoying.
[17:29] <Damascene> xteejx, I'm going to file a bug. any way you can close it :)
[17:29] <persia> But I think it's a wishlist item, and I think the solution is to have a way to turn it off (or have the way to turn it off be better documented).
[17:29] <persia> And I think it's best resolved upsteam.
[17:29] <xteejx> No problem, let us know the bug number, we can set it as Wishlist
[17:29] <xteejx> Yeah ^
[17:30] <persia> I'm happy to press the "Me Too" button on that one: I often don't want my laptop to go hunting networks (e.g. when I turn it on in the train station and expect to pass through *many* networks in the next hour).
[17:38] <Damascene> persia, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/560802
[17:38] <ubot4`> Launchpad bug 560802 in network-manager (Ubuntu) "network manger auto connect to every wireless network it sees (affects: 1)" [Undecided,New]
[17:39] <persia> Damascene: Actually, I only get the popup window to enter keys for networks I've already used.
[17:40] <persia> So my experience may be a little bit different.
[17:40] <Damascene> did you try with another network with the same name?
[17:40] <Damascene> yofel,
[17:40] <yofel> ?
[17:41] <Damascene> sorry I thought you are someone else :)
[17:41] <Damascene> his name is yaron
[17:41] <yofel> ah, np
[17:42] <Damascene> persia, if you entered a key for network but you didn't connect successfully will it try to connect it in the next time you login?
[17:43] <persia> Yes.
[17:43] <persia> Well, if that network is present.
[17:43] <persia> I can make it not do that by deleting stuff in edit connections.
[17:44] <persia> But I can't make it not search for lots of networks and otherwise generate radio traffic on startup.
[17:45] <xteejx> persia: Aren't probe requests normal in all OS's to see if the remembered networks are there?
[17:45] <persia> xteejx: Yes.  Doesn't mean I want them :)
[17:45] <xteejx> Of course :)
[17:45] <Damascene> should I report it upstream?
[17:45] <persia> To me, a better behaviour would be to run in receive-only mode and sniff available ESSIDs from ambient traffic, without sending any data unless requested by the user.
[17:45] <xteejx> Upstream would be the best place for it tbh
[17:46] <persia> But that's hard, and means an extra step for users who just want to connect to some network already.
[17:46] <xteejx> persia: That would definitely be better, especially with laptops too it would save power, albeit not much, but still
[17:46] <persia> (and who have no call to enter areas with active radio scanning which draws information security folk)
[17:47] <xteejx> yeah, laptops in airplanes, etc
[17:47] <persia> OOh.  A plane is a good example :)
[17:47] <xteejx> ;)
[17:49] <Damascene> so should I report it upstream?
[17:49] <persia> It's more likely to have a chance of being fixed upstream, certainly.
[17:51] <Damascene> ok thanks
[17:51] <Damascene> and it's gnome?
[17:51] <Damascene> or redhat?
[18:01] <Jpowers123> hello
[18:02] <persia> Damascene: http://www.gnome.org/projects/NetworkManager/
[18:02] <Jpowers123> I have a question about a bug in ubuntu 10.04 beta 2 involving the use of 3g modems
[18:04] <Jpowers123> some modems mount as cd-rom drives instead of modems and thus ubuntu won't use them even though the drivers are in the kernel, the solution is to install a package called usb_modeswitch and alter a few udev rules to prevent conflicts
[18:04] <Jpowers123> however I can't find any conframation this will be fixed for final release
[18:05] <persia> There's been several discussions about that: I'm not sure there is consensus as to the final solution.
[18:05] <persia> Given the point in the release schedule, and the trivial workaround for those devices that aren't quirked, I don't expect a general solution to be made for release.
[18:06] <Jpowers123> well jolicloud has it fixed, so it is possible
[18:06] <persia> That said, please file a bug about your *specific* device: it may be that your device can be quirked.
[18:06] <persia> The solution you describe doesn't begin to address the issue.  Consider a USB connection to a phone: is that a modem connection?  A storage connection?  An input connection?  A sound device? etc.
[18:07] <persia> It is a workaround that happens to work for a variety of combination storage/modem devices.
[18:07] <Jpowers123> I already know how to fix my specific device, my concern is for normal computer users that ubuntu is aimed at won't be able to fix it
[18:08] <persia> I understand.  That's why I asked you to file a bug about your specific device.
[18:08] <Jpowers123> okay
[18:08] <persia> There exists no general solution at the current time.
[18:08] <persia> But it is possible to quirk some devices.  If your device is of the class read-only-storage+modem then it deserves to be quirked for all users of your device.
[18:08] <Jpowers123> then you may want to talk to jolicloud devlopers that do have this problem fixed
[18:09] <persia> Really, it's not fixed :)
[18:09] <persia> I promise.
[18:09] <persia> It's just more quirks for more classes of cheap storage+modem solutions.
[18:09] <persia> Except that jolicloud uses usbmodeswitch to handle the quirks.
[18:10] <persia> So the issue is less visible, except to users who might want to actually use the storage on the device (if read/write-storage+modem), or for more complex devices (e.g. phones).
[18:10] <Jpowers123> well then may I ask weather or not a good portion of 3g dongels work an the problem only effects obscure hardwrae
[18:11] <persia> I know that there's been significant effort to add hints for most of the read-only-storage+modem devices.
[18:11] <persia> But I'm not sure if all of these devices have been reported, which is why I suggest filing a bug for your device: I suspect that one isn't being handled.
[18:11] <persia> I'm not sure your device falls into that simple case, but if it does, it ought be quirked.
[18:11] <Jpowers123> okay, then I will file my bug report
[18:11] <persia> (pending a real solution)
[18:12] <persia> Thanks!
[18:12] <Jpowers123> bye, thanks for the info
[18:13] <Tiibiidii> hum... guys, i'm not really into triaging, but i sometimes report some bugs... so i've always preferred to avoid doing things like changing the status of a bug
[18:13] <Tiibiidii> so... originally i thought that to do something like that i would've to join the bugsquad or something
[18:14] <Tiibiidii> but i see that's not required (ok, if i contribute for a while it's good practice to join)
[18:14] <Tiibiidii> the point is: to me seems quite strange...
[18:14] <persia> No, it's not required, although it's encouraged.
[18:15] <persia> How so?
[18:15] <Tiibiidii> i mean: i can't modify the importance of a bug
[18:15] <Tiibiidii> why it is that i can modify the status, though?
[18:15] <persia> For that you need to be in bug control.
[18:15] <Tiibiidii> to me the "status" of a bug doesn't really seems less important than the "importance"
[18:16] <persia> Well, there's lots of use cases for status modifications.  For example, you might have reported a bug, and someone marked it incomplete, and you provided the requested information, and want to reset it to New.
[18:16] <crimsun> furthermore, at this stage, the importance of a bug is used in burn-down charts for release management
[18:16] <Tiibiidii> ah ok... so that's would be a legit use of modifying status?
[18:16] <persia> Or you might have reported a bug, and a developer uploaded a change that fixed it, and you want to mark it fix released, even though nobody happened to get to look at your bug yet, and fixed it unintentionally, or from a different report.
[18:16] <Tiibiidii> mhn
[18:17] <persia> RIght, there's a few of them.
[18:17] <Tiibiidii> ok
[18:17] <Tiibiidii> thanks
[18:17] <Tiibiidii> another question
[18:17] <Tiibiidii> often
[18:17] <Tiibiidii> no, actually recently, i started to
[18:17] <Tiibiidii> use the "affects me" functionality
[18:18] <Tiibiidii> (that way i don't have to pollute the comments area, etc.etc.)
[18:19] <Tiibiidii> the problem is that i don't get notified of changes of status in the bugs... nor the bugs i selected as affecting me are being listed among the related bugs
[18:19] <persia> After setting also affects me, use the subscribe feature on the right side.
[18:19] <Tiibiidii> i'm wondering if i'm the only one to feel this lacking feature
[18:20] <Tiibiidii> yeah, but by subscribing you'll receive all comments on the bug
[18:20] <Tiibiidii> sometimes it's useful
[18:20] <persia> I consider it a feature that I don't get auto-subscribed to all the bugs I mark "also affects me".
[18:20] <Tiibiidii> yesyes
[18:20] <Tiibiidii> i mean...
[18:20] <persia> Sometimes I want to note that I'm also hit by something to increase the affected users count, but don't actually want to read all the discussion about it.
[18:20] <Tiibiidii> i don't want to be subscribed... only notified if it gets fixed... or closed or whatever
[18:21] <persia> I don't think there's any means of handling that.
[18:21] <Tiibiidii> yeah, that's the point...
[18:21] <Tiibiidii> do you think it should be requested? maybe as a wishlist bug?
[18:21] <persia> You might file a bug against launchpad to have an +affectedbugs URL added for users that shows the list of open bugs that affect the user.
[18:22] <persia> That's different than notification when stuff gets closed, but does provide some similar idea.
[18:22] <Tiibiidii> do you think it might be useful? (i don't really want to report it if the only one benefitting from it would be me)
[18:22] <persia> And I suspect it's easier to implement than some special notification that only happens for bugs that get marked invalid/won'tfix/fixreleased.
[18:23] <persia> Report it anyway.  I wouldn't use it, but I imagine others would :)
[18:23] <Tiibiidii> lol ok
[18:23] <persia> https://launchpad.net/malone/+filebug
[18:23] <Tiibiidii> one last question:
[18:23] <Tiibiidii> i have about a dozen bugs i wanted to report in my TODO list :)
[18:24] <Tiibiidii> unfortunately i wanted to report these before the freezes of lucid... in hope they would've been fixed in time
[18:24] <Tiibiidii> but now is late...
[18:24] <Tiibiidii> do you suggest waiting for lucid, check if these are still valid and only then reporting these?
[18:25] <persia> Actually, yes.
[18:25] <persia> Alternately, try lucid beta2, and see if they still affect that.
[18:25] <persia> Because if you report bugs against karmic now, unless they are critical bugs, someone will probably ask you to check them in lucid (or even maverick) anyway.
[18:26] <Tiibiidii> ok
[18:26] <Tiibiidii> unfortunately i think i won't be able to do it
[18:26] <Tiibiidii> (some of these happens only on this pc)
[18:26] <Tiibiidii> (and before doing the upgrade i want to get up and running my home server to manage backups)
[18:27] <Tiibiidii> (but unfortunately i had problems with lvm on it)
[18:27] <Tiibiidii> (yeah: i'm a mess)
[18:27] <persia> You might try with testdrive: http://blog.dustinkirkland.com/2009/11/introducing-testdrive.html
[18:27] <Tiibiidii> don't have the disk space XD
[18:27] <Damascene> how to report bug upstream. once I saw a template but I can't find the link to it
[18:27] <persia> Ah.  That makes it tricky.
 Ah.  That makes it tricky. <-- nevermind, i'll get over it... however thanks for the tips
[18:28] <persia> Damascene: https://wiki.ubuntu.com/Bugs/Upstream
[18:29] <persia> Tiibiidii: Good luck, and thanks for reporting bugs.  We have a lot, but we need as many as possible to help make sure Ubuntu is best :)
[18:37] <nigelspow> hi, has anyone heard of issues with gnome-wm not starting since upgrading to lucid beta 2 ?
[18:40] <crimsun> nigelspow: can you reproduce it with a new user?
[18:40] <crimsun> there are several session races appearing now
[18:40] <crimsun> (I'm covering the audio-related ones)
[18:41] <nigelspow> I haven't tried adding a new user actually. I can give that a go now.
[18:43] <nigelspow> A new user seems just fine.
[18:44] <crimsun> right, so that seems to be the recurring "stale gconf settings do bad things on new session" symptom
[18:45] <nigelspow> it sounds like this has come up before.
[18:48] <crimsun> it's long-standing. I've been able to reproduce it since 5.04
[18:48] <crimsun> also, it's pretty tricky to migrate gconf settings during a package's maintainer scripts run
[18:49] <crimsun> system-wide defaults can, of course, be changed, but merging those into a user's existing are pretty crufty
[18:50] <nigelspow> Fair enough. If I just remove the .gnome directory for that user then I assume it'll just get re-created with the current system defaults
[19:11] <alb> Hi! I've just upgraded to Lucid and I'm hitting an xorg bug using the Intel driver (X closes after a couple of minutes, and goes back gdm). I searched launchpad and it doesn't seem to be reported, but since it's not out yet, I wasn't sure whether to file it or not
[19:12] <alb> (surprisingly it may have something to do with the terminal and/or vim, as every time it crashed it was when I was using vim, and now it's been up for some time and I've avoided the terminal)
[19:13] <persia> alb: Please do file it: it's bugs filed against the release-in-progress that are the best means of ensuring that the release is high quality.
[19:14] <alb> persia: ok, will do, thanks a lot
[19:14] <persia> alb: Thanks for helping improve Ubuntu
[19:14] <alb> persia: well, I should be thanking you for that =)
[19:15] <persia> Nah.  X works fine for me, with the Intel driver.  I'd have never noticed that issue.
[19:33] <etali> Could somebody check bug 495524 please (I think it should be set to wishlist / medium)
[19:33] <ubot4`> Launchpad bug 495524 in gwibber "Retweeting ignores posting permissions (affects: 1) (heat: 408)" [Undecided,New] https://launchpad.net/bugs/495524
[19:36] <alb> persia: well, thanks for being nice anyway. It's been reported (bug 560899). I'll go do more testing now, but if anyone has any suggestion, you can send it to albertito (which is running on another machine). Thanks again!
[19:36] <ubot4`> Launchpad bug 560899 in xserver-xorg-video-intel (Ubuntu) "After upgrading to Lucid, xorg exits after a couple of minutes (affects: 1)" [Undecided,New] https://launchpad.net/bugs/560899
[19:36] <persia> alb: Subscribe to the bug to get updates on it.  Also, press the "Also affects me" if it also affects you.
[19:37] <albertito> persia: thanks, both things were done automatically by launchpad
[19:38]  * persia is confused by "affects: 1" and looks harder
[19:39] <persia> Ah.  I misinterpreted "it has been reported" as meaning previously, by someone else.  Apologies for the confusion :)
[19:39] <albertito> persia: yeah, I wasn't clear enough with that, sorry =)
[20:35] <bullgard> What does mean "tags: added: freeze" in https://bugs.launchpad.net/bugs/552418?
[20:35] <ubot4`> Launchpad bug 552418 in xserver-xorg-video-intel (Ubuntu) "[915GM] Chatzilla Firefox plugin freezes repeatedly display image, keyboard unfunctional except for magic SysRq keys (affects: 1) (heat: 8)" [Undecided,Confirmed]
[20:36] <micahg> bullgard: that a tag in launchpad was added to the bug
[20:37] <bullgard> micahg: And what does the added tag "freeze" mean?
[20:38] <micahg> bullgard: probably a way for the X team to track freezes
[20:39] <bullgard> Ah! Thank you.
[20:43] <anoteng> Could a bug controller please set status on bug #554627 to triaged, I'm in doubt about importance but I'm suggesting high: "Makes a default Ubuntu installation generally unusable for some users"
[20:43] <ubot4`> Launchpad bug 554627 in linux (Ubuntu) "boot freeze on "Starting up ..." with generic kernel (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/554627
[20:53] <cjohnston> what package should Bug #560937  be?
[20:53] <ubot4`> Launchpad bug 560937 in ubuntu "After update, panel displays user name twice (affects: 1)" [Undecided,New] https://launchpad.net/bugs/560937
[21:11] <anoteng> cjohnston: probably indicator-applet
[21:12] <cjohnston> ty
[21:13] <anoteng> you're a bug-controller?
[21:26] <cjohnston> yes
[21:38] <alvin> There are probably a lot of questions like this here these days, but I'm going to do it anyway. Can someone eveluate the importance of bug 557909? Right now, systems with lvm have troublesome boot experiences.
[21:38] <ubot4`> Launchpad bug 557909 in devmapper (Ubuntu) "lucid hangs on boot because of device ownership (affects: 5) (heat: 34)" [Undecided,Confirmed] https://launchpad.net/bugs/557909
[23:54] <sweb> hail
[23:54] <sweb> some time my screen saver not work
[23:55] <sweb> i dont know why
[23:59] <persia> How do you mean "not work"?