| hggdh | iceroot, bkerensa: the alternate uses debian-installer | 01:22 |
|---|---|---|
| hggdh | (late, but ah well) | 01:22 |
| === bladernr_ is now known as bladernr_afk | ||
| iceroot | hggdh: thank you, it was not to late :) | 06:30 |
| === bladernr_afk is now known as bladernr_ | ||
| penguin42 | does anyone know if there is a master bug for support of 1366x768 displays? (Or know if it ever works?) | 13:14 |
| roadmr | penguin42: what problem do you see? I've never had problems with that resolution | 13:15 |
| penguin42 | roadmr: I've had problems on 2 entirely diverse machines; one is a modern Intel graphics card with VGA to a 1366x768 TV, the other is an ancient Geforce (2?) card to a 1366x768 monitor, again by VGA | 13:45 |
| penguin42 | roadmr: There is a known problem with EDID on VGA at that res, so you say you never had a problem - was it on VGA? | 13:45 |
| roadmr | penguin42: ah so that's the thing :) no, I mostly test it on laptop internal panels | 13:46 |
| penguin42 | roadmr: The problem is 1366 isn't divisible by 8 and apparently that breaks EDID | 13:46 |
| roadmr | penguin42: oh I see | 13:46 |
| penguin42 | roadmr: see: http://mjg59.dreamwidth.org/8705.html | 13:46 |
| penguin42 | roadmr: I can see lots of bugs where they've been closed/expired/merged with other 'wrong resolution' bugs - but I think it's the geenral 1366x768 problem | 13:47 |
| roadmr | interesting | 13:52 |
| penguin42 | submits it as bug 975175 | 14:08 |
| ubot2 | Launchpad bug 975175 in xorg "1366x768 over VGA generic problems" [Undecided,New] https://launchpad.net/bugs/975175 | 14:08 |
| penguin42 | admits it's a little odd report, but I think it's right | 14:12 |
| === Nafallo_ is now known as Nafallo | ||
| krnekhelesh | is there anyone part of ubuntu bug control here? | 17:37 |
| krnekhelesh | I need someone to mark a bug as won't fix ... after a small discussion | 17:38 |
| greg-g | krnekhelesh: best method is to say what you are thinking and people will respond when/if they have time | 17:41 |
| krnekhelesh | oh ok | 17:42 |
| krnekhelesh | basically if you look at this bug report https://bugs.launchpad.net/indicator-session/+bug/973181 | 17:42 |
| ubot2 | Launchpad bug 973181 in indicator-session "System commands presence confuse the definition of App" [Medium,Fix committed] | 17:42 |
| krnekhelesh | it removes the systems commands like shutdown, restart from the dash | 17:43 |
| krnekhelesh | but there is another bug report https://bugs.launchpad.net/unity/+bug/958467 | 17:43 |
| ubot2 | Launchpad bug 958467 in unity "Add "suspend" entry to the dash, in addition to "Restart" and "Shut Down"." [Wishlist,Incomplete] | 17:43 |
| krnekhelesh | which is asking for suspend to be added to the dash | 17:43 |
| krnekhelesh | these 2 bug reports are conflicting each other | 17:43 |
| krnekhelesh | I propose that "Add suspend entry" bug report be marked as won't fix since it has been decided to remove shutdown, restart entries from the dash | 17:44 |
| greg-g | I would let the Unity people deal with that one, as with any interface design decisions, there will be disagreements, and they might have their own policy on how to handle such situations | 17:44 |
| greg-g | krnekhelesh: I would ask in #ubuntu-unity | 17:45 |
| krnekhelesh | greg-g, are you going to ask or you recommend that I ask? | 17:47 |
| penguin42 | what's the definition of 'core application' for the bug importance guidance? If it's in main is it core? | 17:48 |
| greg-g | krnekhelesh: you should ask, sorry I was unclear with that. | 17:52 |
| krnekhelesh | greg-g : i have asked john lea, waiting for his input..thnx | 17:54 |
| greg-g | aweomse, np | 17:57 |
| micahg | penguin42: http://people.canonical.com/~stgraber/package_sets/precise/core | 19:08 |
| penguin42 | micahg: Ah thank you - any chance of linking to that or a stable URL for that from https://wiki.ubuntu.com/Bugs/Importance | 19:10 |
| penguin42 | (actually it would be better if lp showed you a package was core when you looked at it's bug) | 19:11 |
| dlentz | This bug might need looked at (preferably, someone should at least set the importance so it doesn't show up in the critical list): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/863504 | 23:09 |
| ubot2 | Launchpad bug 863504 in ubuntu "Steelseries Xai mouse causing slow resume from suspend" [Undecided,Fix released] | 23:09 |
| penguin42 | dlentz: Now it shows as fix released - is it? | 23:18 |
| penguin42 | dlentz: Hmm just read it through - bit of a mess; so it's saying that it seems to break windows boot as well, but at least on windows it doesn't seem to break their suspend | 23:32 |
| dlentz | and then the last person says they're not experiencing it? | 23:32 |
| dlentz | the Improtance=Unknown is what causes it to show up on the critical list though | 23:33 |
| penguin42 | hmm what a mess - I wonder if it depends on USB controller/hub/power/phase of the moon | 23:33 |
| * dlentz consults his lunar calendar | 23:33 | |
| penguin42 | dlentz: But what should be the importance, I mean looking at the list 'A problem with an essential hardware component (disk controller, built-in networking, video card, keyboard, mouse)' would flag for high, but then again it's only a delay not a crash/hang/unusable device, and it only affects resuming | 23:34 |
| dlentz | even 'high' would be better than unknown/critical | 23:36 |
| penguin42 | dlentz: Why do you say critical next to unknown ? | 23:36 |
| dlentz | if you go to https://bugs.launchpad.net/ubuntu , then this bug shows up at the top of list when sorted by importance (even higher than the critical bugs) | 23:38 |
| dlentz | i personally see it as low importance because there's an easy workaround (wait 20 secs) | 23:38 |
| penguin42 | oh, hmm - why does that happen - I mean there have to be loads of unknown status bugs | 23:39 |
| dlentz | unknown != undecided | 23:39 |
| penguin42 | dlentz: We could cut it in the middle and put it at medium | 23:39 |
| penguin42 | oh yes, sorry hadn't noticed that | 23:39 |
| dlentz | you could even set it to undecided | 23:39 |
| penguin42 | how does it get to Unknown then? | 23:39 |
| penguin42 | I'll set it to Medium | 23:40 |
| dlentz | a triager set it that way | 23:40 |
| dlentz | thanks for time/attn | 23:41 |
| penguin42 | dlentz: Hey, it just made me curious | 23:41 |
| penguin42 | dlentz: It seems nuts that a trigger would set something to a state that nothing else would | 23:44 |
| dlentz | you mean 'triager'? | 23:47 |
| penguin42 | dlentz: But how did they set it - I can't pick unknown off there | 23:48 |
| penguin42 | is it becuase it's wired to the debian bug and it's waiting to get input from that? | 23:49 |
| dlentz | i'm not the most experienced bug squad member, a good question for someone higher-up though | 23:50 |
| penguin42 | me neither - I don't quite understand that mechanics | 23:51 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!