| === wylde_ is now known as wylde | ||
| veger | I could use some help in further processing bug #911260 | 07:38 |
|---|---|---|
| ubot2 | Launchpad bug 911260 in mail-notification "Notify OSD integration instead of popup" [Undecided,Incomplete] https://launchpad.net/bugs/911260 | 07:38 |
| veger | The issue is still present in Precise, so I suppose the next step is to file an upstream report? | 07:38 |
| veger | But I am wondering where to send the upstream report to? | 07:39 |
| veger | the source package comes is merged from Debiam, so the report should go to Debian? | 07:40 |
| veger | I decided to send an upstream report to Debian, we'll see from there :) | 08:26 |
| veger | Could someone set its status to Triaged and the importance to Wishlist? (bug #911260) | 08:27 |
| ubot2 | Launchpad bug 911260 in mail-notification "Notify OSD integration instead of popup" [Undecided,Confirmed] https://launchpad.net/bugs/911260 | 08:27 |
| krnekhelesh | can anyone set this bug report to medium priority https://bugs.launchpad.net/unity/+bug/979699 | 10:23 |
| ubot2 | Launchpad bug 979699 in gnome-settings-daemon "Display on external monitor reverts to mirror display on restart and logout" [Undecided,Confirmed] | 10:23 |
| seb128 | krnekhelesh, that bug seems buggy, in session it should work, login screen and boot are plymouth and lightdm issues and duplicates | 10:29 |
| krnekhelesh | seb128, oh...so you think they are related to plymouth and lightdm | 10:30 |
| seb128 | krnekhelesh, that bug is not very useful, hard to say | 10:30 |
| seb128 | krnekhelesh, boot is plymouth | 10:31 |
| seb128 | the login screen is lightdm, unity-greeter uses gnome-settings-daemon but I think it doesn't use the xrandr plugin | 10:31 |
| seb128 | then the session store configs through gnome-settings-daemon xrandr | 10:31 |
| seb128 | which works | 10:31 |
| seb128 | so it's not broken for everybody for sure | 10:31 |
| krnekhelesh | seb128, ok...but it is an issue...for me in the login screen I get duplicate display rather than an extended display | 10:31 |
| seb128 | not sure if the user means the login screen doesn't follow the in session config | 10:31 |
| seb128 | krnekhelesh, right, that's a known issue for years, nothing is configuring the login screen resolution | 10:32 |
| seb128 | like the in session config is user specific | 10:32 |
| seb128 | the login screen is shared between all users | 10:32 |
| seb128 | so they don't use the same config | 10:32 |
| krnekhelesh | ah ok | 10:32 |
| krnekhelesh | because I thought I had it working before... | 10:32 |
| krnekhelesh | but I guess when I created additional users then the problem kicked in | 10:33 |
| seb128 | well maybe your driver or xorg was defaulting to something else | 10:33 |
| seb128 | or you had autologin or something | 10:33 |
| krnekhelesh | so does that mean that the mockups made for the login screen do not apply for multiuser computers | 10:34 |
| seb128 | krnekhelesh, what mockups? | 10:34 |
| krnekhelesh | the one with the login screen on the primary computer and ubuntu logo on the other | 10:34 |
| krnekhelesh | I'll find the link, 1 min | 10:34 |
| seb128 | I'm not sure that got implemented fully this cycle | 10:34 |
| krnekhelesh | it did not..but the login screen part was | 10:35 |
| krnekhelesh | https://docs.google.com/document/d/1MT5Qrouudu9EftJdbtuz-Z1l26bDUDlcpPD52YsABYM/edit | 10:35 |
| seb128 | krnekhelesh, what is? then it regressed I guess, in any case login screen doesn't run unity so it's not an unity issue in any case | 10:35 |
| krnekhelesh | nvr mind..its not that link | 10:35 |
| seb128 | and I don't think it used gnome-settings-daemon for display config either | 10:36 |
| krnekhelesh | ok.. | 10:36 |
| seb128 | so it would rather be an unity-greeter bug | 10:36 |
| krnekhelesh | yes | 10:36 |
| krnekhelesh | I'll link that package to the bug | 10:36 |
| seb128 | but well your issue seems different from the one described on that bug | 10:36 |
| krnekhelesh | for the user, the configuration is back to "same image on both monitors" ... and I have that as well but only during the login screen and boot process | 10:37 |
| krnekhelesh | I'll ask the user for confirmation | 10:37 |
| seb128 | krnekhelesh, your issue is bug #907128 or similar | 10:37 |
| ubot2 | Launchpad bug 907128 in unity-greeter "Displays on wrong monitor" [Undecided,New] https://launchpad.net/bugs/907128 | 10:37 |
| krnekhelesh | hmm, for him the lightdm starts on the plasma tv only right? but for me it starts on both the displays | 10:39 |
| seb128 | krnekhelesh, ok, yours is bug #959592 then | 10:40 |
| ubot2 | Launchpad bug 959592 in lightdm "Multi monitor mirrored instead of using primary/selected monitor" [Undecided,Confirmed] https://launchpad.net/bugs/959592 | 10:40 |
| seb128 | I told you it was reported :p | 10:40 |
| seb128 | it should took me a bit to find the right number | 10:40 |
| krnekhelesh | awesome...yup this is what i fce | 10:40 |
| krnekhelesh | face* | 10:41 |
| seb128 | krnekhelesh, I can confirm the bug, if you reconnect the external screen it works, so the code is there it's just an init issue | 10:46 |
| krnekhelesh | seb128, yes I just tried it out by switching account and then removing and reattaching the monitor | 10:48 |
| krnekhelesh | you are right | 10:48 |
| seb128 | krnekhelesh, I will triage it | 10:48 |
| krnekhelesh | seb128, thnx | 10:48 |
| === bladernr_afk is now known as bladernr_ | ||
| dupondje | What permissions are needed to set a bug to 'Won't Fix'? | 13:26 |
| seb128 | dupondje, bugsquad membership I guess | 13:28 |
| dupondje | seb128: well i'm bugsquad member, but can't set to 'Wont Fix' | 13:29 |
| roadmr | dupondje: what's the bug # ? | 13:30 |
| dupondje | https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/558913 | 13:30 |
| ubot2 | Launchpad bug 558913 in cryptsetup "Cryptsutup out of date in Lucid" [Undecided,Confirmed] | 13:30 |
| dupondje | Triaged & Won't Fix are grayed out for me | 13:31 |
| dupondje | any idea's ? | 13:41 |
| roadmr | dupondje: hmm I think only bug control members can select those statuses | 13:41 |
| roadmr | dupondje: see here: https://wiki.ubuntu.com/UbuntuBugControl | 13:42 |
| dupondje | I see :) Could I get added? | 13:44 |
| krnekhelesh | dupondje, yup Triaged, Won't Fix and the bug priority are only for ubuntu bug control members | 13:45 |
| === raju is now known as ubucop | ||
| * dupondje hates applications by email :) To much typing work. | 13:47 | |
| roadmr | dupondje: if you fulfill the requirements, you could be added :) in the meanwhile, it's OK to ask for importance and status changes in here, someone from bug control can help you | 13:49 |
| dupondje | I fulfill all your requirements ;) | 13:49 |
| dupondje | https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/558913 => wont fix please :) | 13:50 |
| ubot2 | Launchpad bug 558913 in cryptsetup "Cryptsutup out of date in Lucid" [Undecided,Confirmed] | 13:50 |
| hggdh | dupondje: Although I do not doubt you fulfill the requirements for -control, this is the process in place... you got to apply ;-) | 15:04 |
| === bulldog98_ is now known as bulldog98 | ||
| === bladernr_ is now known as bladernr_afk | ||
| === bladernr_afk is now known as bladernr_ | ||
| === krnekhelesh is now known as nik90 | ||
| EvilResistance | i was reading through the bugs on the ZNC package, and this one seems outrageously old, considering the stable versions in lucid and onwards are newer than the specified versions (hardy's a different story, but still): LP Bug 343494 | 19:46 |
| ubot2 | Launchpad bug 343494 in znc "Security Issue in all ZNC <0.066" [Undecided,Confirmed] https://launchpad.net/bugs/343494 | 19:46 |
| EvilResistance | should this still be listed as "confirmed" given that there's fixes in lucid and later (i.e. newer versions) | 19:47 |
| hggdh | EvilResistance: you could, yes. But the point in the bug is that we need a patch to apply to it | 20:00 |
| hggdh | (it is already known to be real) | 20:01 |
| EvilResistance | hggdh: you mean a patch to apply to hardy? | 20:02 |
| EvilResistance | TBPFH, the ZNC devs extremely *rarely* fix things with patches, but rather just go and fix with next upstream | 20:03 |
| EvilResistance | in which case the fix would be an update | 20:03 |
| EvilResistance | given this from the changelogs for 0.066: How can I protect myself? | 20:03 |
| EvilResistance | Upgrade to ZNC 0.066 or newer or unload webadmin. | 20:03 |
| EvilResistance | and even that there has security holes | 20:04 |
| EvilResistance | in which case i'd probably have to be talking to the MOTUs about updating the packages in hardy (which i hear is a general no-no) | 20:05 |
| hggdh | indeed -- we do not, as rule, update to a newer version of a package | 20:07 |
| EvilResistance | then the bug is therefore not fixable by rule | 20:14 |
| EvilResistance | and will indefinitely remain confirmed, or rather should be marked somehow as "not fixable" | 20:14 |
| hggdh | EvilResistance: no, the bug is -- theoretically -- fixable, by a patch | 20:16 |
| EvilResistance | but only in theory | 20:16 |
| EvilResistance | by your own admission the package won't be updated to a newer version | 20:16 |
| EvilResistance | (by rule) | 20:16 |
| hggdh | no. Someone interested in it could build a patch | 20:16 |
| * EvilResistance wishes that person luck, because god knows they'll need it | 20:16 | |
| === yofel_ is now known as yofel | ||
| === ogra_- is now known as ogra_ | ||
| === Resistance is now known as EvilResistance | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!