/srv/irclogs.ubuntu.com/2013/02/14/#ubuntu-devel.txt

=== salem_ is now known as _salem
=== wedgwood is now known as wedgwood_away
GunnarHjslangasek: still there?00:19
slangasekGunnarHj: yep00:22
GunnarHjslangasek: In sudo they have user_readenv=0, so I  take it that the sudo tasks are invalid on bug 952185.00:28
ubottubug 952185 in lightdm (Ubuntu Precise) "~/.pam_environment not parsed by default" [High,In progress] https://launchpad.net/bugs/95218500:28
slangasekGunnarHj: yep, sounds like they are00:29
slangasekGunnarHj: good catch, sorry I overlooked that00:29
GunnarHjslangasek: Ok, then my thinking was right for once. ;-)00:29
smoserslangasek, ok... new theory.00:48
smosercloud-fconfig actually just writes the shell script.00:48
smosercloud-final would run it00:48
smosercloud-final runs on00:49
smoserstart on (stopped rc RUNLEVEL=[2345] and stopped cloud-config)00:49
slangaseksmoser: well, that doesn't look problematic to me00:49
smoserno?00:50
smoseri think this was reported as https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/110388100:50
ubottuUbuntu bug 1103881 in upstart (Ubuntu) "cloud-final is never executed if upstart is upgraded during initialization of the image " [High,Confirmed]00:50
=== zz_jackyalcine is now known as jackyalcine
slangasekah00:50
smoserwhich i think is a wrong diagnosis, i'm seeing this without upgrade of upstart.00:50
slangasekmm00:50
slangasekwell, jibel seemed convinced it was happening only when upstart was getting upgraded00:51
smoserin our pastebin here http://paste.ubuntu.com/1646707/00:51
smoserwe never see 'rc' stop00:51
slangasekah00:51
slangasekso what all is in /etc/rc2.d/ ?00:52
slangasekthe only thing I know of that would prevent 'rc' from stopping is an init script that's hanging00:52
slangasekand jibel's bug does show rc being stopped (https://launchpadlibrarian.net/129295546/LP1103881.dmesg)00:53
slangasekso I think you have two different bugs with the same symptom00:53
smoserhm... so maybe they're coincidence.00:53
smoserjust 'set -x' on rc00:54
smoserinto /run/log00:54
smoserso i'll see that here  in a minute.00:54
slangasekok00:54
smoserslangasek, i've got to run again. i'm really confused now.01:04
smoserhttp://paste.ubuntu.com/1647304/01:04
slangaseksmoser: well, this shows no rc (or rc-sysinit) job running at all... ?01:05
smoserright.01:05
smosertomorrow01:07
* xnox waves from february 14th =) the international day of loving to debug mysterious presents in boot stacks01:25
slangasekit's a niche holiday01:25
mwhudsonnot really the right place to ask the question but01:37
mwhudsonare there any docs on building custom initramfses?01:37
mwhudsoni want mkfs + friends in one01:38
TheMusoYou need only write a hook for update-initramfs to run to put the files you want in the initramfs.01:38
mwhudsonsounds suspiciously easy01:39
hallynhm, my boot time in raring just got really bad in the last few days.  from about 8 secs to about 30 secs.  bootchart doesn't show disk use or anything...01:39
TheMusomwhudson: Look in /usr/share/initramfs-tools/hooks/ for some good examples.01:39
TheMusomwhudson: Then its just a matter of writing extra hooks to be run in the initramfs.01:39
mwhudsonok01:39
mwhudsondo you have to build the initramfs on the same arch as you're going to run it on?01:40
mwhudsoni guess practically speaking yes01:40
=== jackyalcine is now known as zz_jackyalcine
cjwatsonYeah01:40
cjwatsonSince it copies stuff from the host fs01:40
hallynreally dbus-daemon is the only thing that stops right when gnome stuff finally starts01:41
mwhudsoni suppose you can chroot + qemu-arm-static01:41
mwhudsonbut01:41
cjwatsonIn principle yes01:41
cjwatsonamd64 <-> i386 probably works fine with chroots; not sure if there mightn't be some weird quirk with ARM, but worth trying if it would make life easier01:42
mwhudsonnot sure if it would tbh01:42
mwhudsonjust the tediousness of copying files around01:42
penguin42mwhudson: You can, it does work for simple stuff (or did 18 months or so ago last time I tried it)01:45
=== micahg_ is now known as micahg
* xnox does qemu-arm-static a lot. For most things it's quicker than panda, but nexus7 beats it, as compared to my i501:47
=== zz_jackyalcine is now known as jackyalcine
=== jackyalcine is now known as zz_jackyalcine
=== zz_jackyalcine is now known as jackyalcine
=== jackyalcine is now known as zz_jackyalcine
=== zz_jackyalcine is now known as jackyalcine
=== jackyalcine is now known as zz_jackyalcine
=== emma_ is now known as em
=== emma_ is now known as em
=== em is now known as emma
pittiGood morning05:36
YokoZar*files bug against 6 packages, uploads debdiffs for all, makes sponsorship queue sad*06:03
YokoZarIs it correct for apt-get-install foo to bail out if recommends are uninstallable without the --no-install-recommends flag, or should apt be trying to get as many as it can?06:06
slangasekYokoZar: unsatisfiable recommends should not cause apt-get to bail out, though they will cause warnings to be output06:09
YokoZarslangasek: Then this is also an apt bug :D https://bugs.launchpad.net/ubuntu/+source/winetricks/+bug/112371006:10
ubottuUbuntu bug 1123710 in winetricks (Ubuntu) "wine1.4:i386 not installable on raring amd64" [Low,Triaged]06:10
slangasekYokoZar: I'm reasonably certain that the problem there is not that the recommends are uninstallable, but that the recommends are available, apt follows them, and as a result renders one of the *depends* uninstallable06:12
slangasekso... yes, apt could be smarter about skipping the recommends in that case, but this is a complicated problem06:13
YokoZarslangasek: so apt is considering switching a recommended (arch all but not M-A: foreign) package to it's "i386" version, then trying to get i386 versions of the arch:all's package depends, and then hitting a conflict and giving up rather than just ignoring the recommend06:15
slangasekhitting a conflict because it's managed to break one of the dependencies in the process and is too far down the rabbit hole to unwind06:16
YokoZarslangasek: I think that's right...and I think correct for apt in this case would be to ignore the recommended package rather than count the installed arch:all version as conflicting with itself.06:16
slangasekwell, it wouldn't try to use i386 packages to satisfy the dependencies of an Arch: all package, no06:17
YokoZarI meant transitive i386 deps06:17
YokoZareg when an arch: all package had arch specific deps06:17
slangasekstill no06:17
slangasekan Arch: all package will have its deps satisfied by packages of the native arch06:17
YokoZaronly if it's marked M-A foreign, yes?06:18
YokoZar(in the case of installing a non-native package that depends on the arch:all package)06:18
slangasekno06:18
slangasekan Arch: all package is treated as equivalent to a package of the native arch, in every way06:19
YokoZarErr then I'm confused because all the conflicts in question in the linked bug are recommends of arch:all packages06:19
YokoZarindeed, already installed arch:all packages06:19
slangasekwell, I can't reproduce that error output on a raring system, so06:19
slangasekI get a completely different set of conflicts06:19
YokoZarapt-get install wine1.4 first06:19
slangasekah right, I have wine1.5 installed06:20
YokoZarthen remove it (but not the stuff it pulls in) and apt-get install wine1.4:i38606:20
slangasekYokoZar: still can't reproduce this in a clean chroot (and I'm not clobbering the wine1.5 install on my desktop for testing right now)06:31
YokoZarslangasek: The fact that you want to protect your wine1.5 install makes me kinda happy :D06:37
slangasekI'd be happier if the software in question didn't need it ;)06:38
YokoZarslangasek: I'll see if I can nail down an exact repro step on a new VM06:39
dholbachgood morning07:53
Dedunugood morning08:21
Adri2000I've got a bug waiting for archive admin action since last december (#1086468). did I do something wrong? :)08:47
seb128bug #108646808:47
ubottubug 1086468 in obm (Ubuntu) "Please remove obm source and binaries from raring" [Wishlist,Confirmed] https://launchpad.net/bugs/108646808:47
seb128Adri2000, seems not, it's just that removal are not always done regularly I think08:48
Adri2000as long as it's processed before raring is released, it's ok for me :)08:50
seb128it will, no worry08:50
didrocksdoing right now :)08:51
didrocksAdri2000: done08:53
=== zz_jackyalcine is now known as jackyalcine
Adri2000didrocks: thanks08:55
didrocksyw08:55
=== jackyalcine is now known as zz_jackyalcine
pittiseb128: I'm not a big fan of a comment field for whoopsie reports because we are never going to actually review them all09:02
pittiseb128: and it would create the impression that this is a kind of bug report09:03
pittiseb128: I'd much rather see the "collect extra information" or "request filing a bug report the next time" flag09:03
seb128pitti, we could have both ;-)09:03
seb128not denying we need the "request info"09:03
seb128but as said going through an hundred description can be enough to see a pattern09:04
=== zz_jackyalcine is now known as jackyalcine
seb128like "I was changing user when it happened"09:04
seb1285 of those in a long stack can be enough to give an useful clue09:04
pittiseb128: for those I'd personally prefer a bug report09:05
pittiseb128: but anyway, I'm not strongly vetoing this, I'm just not a fan of it09:06
seb128pitti, @bug report, I though the idea was to stop reports to launchpad, so we need to get the infos we need linked to the whoopsie reports09:07
pittiseb128: right, but add a flag "the next person to encounter that please file a bug report", and it waits until someone actually does09:07
pittithere will always be cases where we need a proper dialog with reporters09:08
seb128pitti, right, I just feel like if we start automatically abusing that feature to ask "what were you doing" on most bugs then it's a sign that something is not right in the system09:10
seb128and that maybe the info should be asked upfront09:10
seb128oh well, let's see how it works in practice09:10
=== Quintasan_ is now known as Quintasan
=== henrix_ is now known as henrix
seb128bdrung, so, after sponsoring libreoffice for Sweetshark, do you feel more comfortable for the ppu? should he run again, or is there anything you recommend him to work on/change to be accepted?09:33
seb128bdrung, the details you found/fixed in your review seems mostly small and old packaging glitches, mostly cosmetic or coming from Debian, not mistakes from Bjoern09:34
=== Zic is now known as Guest11517
=== Guest11517 is now known as Zic
davmor2hey guys I have done a fresh install of Raring on my Lenovo Y580, good news bluetooth now works out of the box huzzah, bad news the screen is black because it is dimmed right down, I have to wait for the drums and then I can up the brightness, is there any info I can get on it for you11:41
=== emma is now known as em
=== _salem is now known as salem_
=== dholbach_ is now known as dholbach
=== jighrgoir is now known as ahasenack
xnoxmicahg: announcement? =)13:42
=== shuduo is now known as shuduo_afk
mdeslaurcyphermox: FYI, I'm going to nag you to get dnsmasq 2.66 into raring as soon as it comes out14:20
mdeslaurcyphermox: 2.65 breaks local resolution with libvirt14:20
=== wedgwood_away is now known as wedgwood
cyphermoxmdeslaur: ok14:36
smoserjodh, ping wrt https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/112438414:58
ubottuUbuntu bug 1124384 in cloud-init (Ubuntu) "reload-configuration can confuse upstart" [High,Confirmed]14:58
=== rsalveti_ is now known as rsalveti
=== Ursinha_ is now known as Ursinha
jodhsmoser: were you running upstart in debug mode at the time?15:18
smoserhave have dmesg output with --verbose15:18
smoseri can easily get you --debug15:18
jodhsmoser: yes please15:18
=== jtechidna is now known as JontheEchidna
=== shuduo_afk is now known as shuduo|iphone
smoserslangasek, i'd appreciate your thoughts/input on bug https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/112322015:54
ubottuUbuntu bug 1123220 in cloud-initramfs-tools (Ubuntu) "cloud-image VM causes kernel panic if image is resized" [Low,Triaged]15:54
=== doko__ is now known as doko
SpamapSare there known bugs in raring causing X to repeat keypresses a lot? like just normal typing but suddenlllllllllllly l repeates a bunch?16:15
smoseri've not seen that.16:16
SpamapSI hesitate to report bugs from my old macbook pro.. because it has been dist-upgraded early in each cycle since it was installed with 10.10 alphasomething16:16
SpamapSbut its getting rather frustrating :-P16:16
dobeyi've never seen that either16:17
infinity@pilot in16:17
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: infinity, smoser
dobeyonly on my phone, which isn't ubuntu16:17
jdstrandhallyn: hey, fyi, I just pushed libivt ubuntu5 for an apparmor denial16:18
jdstrandhallyn: libvirt*16:19
smoser@pilot out16:20
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: infinity
hallynjdstrand: ok.  possibly related to the nova bug zul was mentioning?16:20
jdstrandI doubt it: access to @{PROC}/sys/vm/overcommit_memory r16:20
jdstrandseemed like a harmless denial16:20
jdstrand(but noisy)16:21
hallynoh, ok16:21
apwslangasek, can you remind me when and who switches us to vt during boot16:23
apwslangasek, in the non vt-handoff case16:24
=== henrix is now known as henrix_
=== henrix_ is now known as henrix
user12423is ubuntu 12.04.2 released yet?16:38
cjwatsonuser12423: Nearly but not quite16:39
cjwatsonSorting out the tail end of testing16:39
user12423cjwatson: how much time will be take? Will it be released today?16:40
cjwatsonLet's just say that I'm doing the release, I'm in the UK, and I want to be able to go to the pub with a clear conscience this evening16:40
mdeslaurhehe16:40
user12423cjwatson: I have read that ubuntu 12.04.2 comes with kernel 3.5. Will it work with proprietary ati drivers for radeon 4000 series as they are not compatible with quantal?16:42
cjwatsonI'm afraid I don't know; you'll have to ask X folks, perhaps #ubuntu-x16:42
user12423cjwatson: ok thanks16:42
infinityuser12423: Installing with 12.04.1 media and upgrading will have you on a 3.2 kernel by default, if you have a proprietary blob that hates 3.516:48
user12423infinity: amd recently updated their legacy drivers to version 13.1, don't they work too in 3.5?16:49
infinityuser12423: I have no idea, they may well work.  I was just saying "if they don't.."16:49
user12423infinity: ok16:51
seb128@pilot in17:08
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: infinity, seb128
hallynslangasek: is the ovmf package intended to have a readme?17:34
* hallyn wiating for src to d/l over slow link17:35
hallynok, i guess it's just my iso that's the problem - waiting for an even longer release iso d/l :)17:43
quadrisprohi everybody18:02
=== tkamppeter_ is now known as tkamppeter
quadrisproI see dogtail is currently blacklisted, could anyone remove it from the sync-blacklist? Upstream has started again to develop and support dogtail, I took it in Debian18:06
quadrisprothe latest release is available in experimental18:07
mitya57_quadrispro: https://bugs.launchpad.net/ubuntu/+source/dogtail/+bug/460210/comments/818:08
ubottuUbuntu bug 460210 in dogtail (Ubuntu) "Sync dogtail 0.8.1-1 (universe) from Debian experimental (main) and remove it from the blacklist" [Wishlist,Triaged]18:08
quadrispromitya57_, cool! thanks, I'll look into it18:08
quadrispromitya57_, uploading the patch to experimental in few minutes18:13
mitya57_quadrispro: great, please also leave a comment on that bug18:14
didrocksbarry: it seems you didn't merge oneconf 0.3.3 to lp:oneconf?18:21
barrydidrocks: in a meeting...18:21
=== deryck is now known as deryck[lunch]
mitya57_quadrispro: did you really want to remove "def _getEncoding(self):" line?18:32
mitya57_nevermind, I've got confused by diff output :)18:33
quadrisproeh yes :) np18:34
quadrisprosee you around18:34
* mitya57_ wishes good night to everybody18:47
seb128stgraber, hey, can you set https://code.launchpad.net/~baltix/ubuntu/precise/ubuntu-defaults-builder/remove-quotes-from-firefox-bookmarks-titles/+merge/137107 as "work in progress"?19:00
stgraberseb128: done19:00
seb128stgraber, thanks19:00
=== jackyalcine is now known as zz_jackyalcine
slangaseksmoser: bug #1123220> hmm, that seems to me that your a) option is the best (kernel not attaching /dev/console to something that doesn't work)19:10
ubottubug 1123220 in cloud-initramfs-tools (Ubuntu) "cloud-image VM causes kernel panic if image is resized" [Low,Triaged] https://launchpad.net/bugs/112322019:10
slangasekapw: what do you mean by "to vt"?19:10
timrcwookey, Hi, I've been trying to figure out multistrap.. I noticed in raring version, 2.1.6ubuntu3, still contains /usr/share/multistrap/ubuntu/crosschroot-maverick.conf -- would you like me to file a bug on this?19:10
slangasekhallyn: I didn't put any readme in the ovmf package, no19:11
smoserslangasek, but kernel is really dumb19:16
smoserand that assignment happens really early19:17
smoserback some time ago i had smb investigate a bit and he seemed to think that was non-trivial19:17
smosereven in the event that the kernel was smarter, having safety code in upstart and initramfs seems like it wouldn't hurt.19:18
slangaseksmoser: well, in this case you say it's crashing in the initramfs, right?  we might reasonably be able to make upstart itself more robust against a broken /dev/console... but not every command that might write to stdout in the initramfs.19:18
smosersh -e 'echo hi; echo by' should not exit failure.  thats just not friendly to anyone.19:18
smoserslangasek, my suggestion was that in the initramfs (early) we do the code i posted.19:19
slangaseksmoser: yes, but afaics that would merely be advisory?19:19
smoserbasically redirecting to somewhere in /run or /dev/null if we can't find something useful.19:19
smoserhuh?19:19
slangasekoh, you're proposing actually redirecting, ok19:20
smoseroh. yes, clearly if some other script in the initramfs opened /dev/console explicitly, then i can't stop that.19:20
smoserbut stdout shouldn't be broken.19:20
slangasekwell, init will reopen the console19:20
slangasekI don't know if it fails in this case19:20
smoserright.19:20
smoserso upstart would need the same thing.19:20
smoseropen succeeds19:20
smoserwrites fail19:20
slangasekI really think this needs to be fixed in the kernel19:21
slangasektrivial or not19:21
slangasek/dev/console should not be broken when you write to it19:21
smoserslangasek, it seems like maybe my suggested work aroudn wouldn't work.  see https://bugs.launchpad.net/maas/+bug/1061977/comments/4 . i'm not certain  that is correct, but i seem to remember that some writes to /dev/console worked fine.19:25
ubottuUbuntu bug 1061977 in MAAS "Machine fails to commission when console=ttyS0 is present on kernel opts" [Critical,Fix released]19:25
smoseras if there was a buffer that got filled up and it didn't fail until kernel tried to flush that19:26
slangaseksmoser: yeah, I was just going to say, if this is related to the other bugs I've seen before in this area, there's probably kernel buffering making a mess of it besides19:26
smoserfwiw, we have 'console=ttyS0' (and want to keep that) because cloud providers (ec2 and openstack at least) give you access to data written to the serial device19:28
smoserso you can view that log.  if we have *no* console= parms, then it goes to a vga device, which is completely useless.19:28
* slangasek nods19:30
hallynslangasek: ok - i just wasn't sure if there was something i could/should do to work around the 'secure boot not enabled' msg.19:30
slangasekhallyn: you can nag me to fix that output from shim :)19:30
hallynnag, i can do that :)19:31
=== yofel_ is now known as yofel
=== deryck[lunch] is now known as deryck
=== fisted_ is now known as fisted
seb128@pilot out21:56
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: infinity
ogra_geez21:56
ogra_nighflight21:56
=== henrix is now known as henrix_
=== salem_ is now known as _salem
zykes-7win 3822:54
=== zz_jackyalcine is now known as jackyalcine
=== fisted_ is now known as fisted
=== kentb is now known as kentb-out
=== jackyalcine is now known as zz_jackyalcine
=== zz_jackyalcine is now known as jackyalcine
m4n1shLaney, cjwatson : is the feature freeze applicable to a main package which has a revamped UI but hardly any new features. I hope so, but just cross checking23:34
m4n1shAFAIK you both are in release team23:34
RAOFThe UI would most certainly be considered a feature. :)23:37
m4n1shRAOF: please tell me you are joking23:38
m4n1shor maybe my sarcasm detector is broken23:39
xnoxm4n1sh: https://wiki.ubuntu.com/FeatureFreeze23:39
RAOFI'm not sure how you'd significantly rework the UI *without* requiring a FFe.23:39
xnoxm4n1sh: also note https://wiki.ubuntu.com/FreezeExceptionProcess#UserInterfaceFreeze_Exceptions23:39
RAOFOr, to put it another way, a revamped UI is *definitely* a feature.23:39
* xnox once revampted a non-essential ubiquity screen - only to crash by default the installer due to i18n error23:40
=== jackyalcine is now known as zz_jackyalcine
xnoxm4n1sh: the point is that it's potentially disruptive and can introduce bugs.23:41
xnoxwhen one least expects them.23:41
m4n1shyeah, introducing bug is surely the biggest problem23:41
m4n1shxnox: Thanks. So that means I am really short of time23:41
xnoxm4n1sh: what package is it?23:41
m4n1shxnox: activity-log-manager23:42
m4n1shThe new design by matthew paul thomas23:42
m4n1shit has been present since long and implemented too, but I am fighting with the code (some startup issues) and build system23:42
xnoxm4n1sh: right so User Interface Freeze is on the 21st. Just work through it and polish it, then request FFe and everything will be good.23:43
xnoxm4n1sh: you have 5 weeks \o/23:43
RAOFYou might also want to ask for a *preemptive* FFe; the release team like to know what's coming up.23:44
m4n1shxnox: yeah. Just hopeful it doesnt break anything new.23:44
m4n1shRAOF: Yes. that would be better23:44
=== zz_jackyalcine is now known as jackyalcine
m4n1shxnox: this is the mockup https://lh4.googleusercontent.com/aYbxFHevnMXUmWkVF73FXF1IGj8AaxMRWCZKJb71V3vsKpWWEVmlZ7S9U-QKV3UuquFSbeU5PxnFoVXxMSlwxzfQCDmh38wKJF9ztV7MW_v_kcvO31U23:47
m4n1shJust FYI23:47
xnoxm4n1sh: the joined up dropdown + and - buttons with toolbar inline style in gtk has a bug where it will not look joined up, just so you know23:48
lifelesscjwatson: can grub2 read kernel + initramfs from within a raid6 mdadm array ?23:48
* xnox has some glade work with a similar pattern from mpt for ubiquity23:48
m4n1shxnox: in raring?23:49
xnoxm4n1sh: it did in quantal, didn't check raring recently.23:49
xnoxm4n1sh: yeap still broken - open "Videos" (totem) and look at the buttons just below the playlist23:50
=== jackyalcine is now known as zz_jackyalcine
m4n1shxnox: I can see this http://i.imgur.com/vUJkhpT.png23:51
xnoxm4n1sh: the most right "v" button should be rounded on the right23:52
xnoxe.g. (+ | - | v | ^ | v ) not (+ | - | v | ^ | v ]23:52
m4n1shxnox: oh yeah. It slipped my eyes, I thought you were talking about the buttons being spaced apart23:52
m4n1shyeah, that is a bug23:52
xnoxbut it's a theming issue.23:53
* xnox filed it against light-themes but still not fixed. maybe i'll have to write the patch =(23:53
xnoxm4n1sh: i could also trigger it to appear as ( | )[ | | ] which is even more ugly =/23:53
=== wedgwood is now known as wedgwood_away
m4n1shyeah, or every button be squared23:54
m4n1shatleast that would have consistency23:54
=== wedgwood_away is now known as wedgwood
=== wedgwood is now known as wedgwood_away

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!