[00:00] <RAOF> Hello, x86-64 assembly reference.  Do you have 400 pages worth of instruction definitions?  You do?  Guess it's lucky there's code already written!
[00:05] <bryceh_> dang sun, get out of my eyes and off my monitors
[00:20] <bryceh_> RAOF, did you see bug 732809?
[00:20] <ubot4`> Launchpad bug 732809 in mesa (Debian) (and 1 other project) "mesa update to 7.10.1-0ubuntu1 breaks ipython matplotlib (dup-of: 259219)" [Unknown,New] https://launchpad.net/bugs/732809
[00:20] <ubot4`> Launchpad bug 259219 in software-center (Ubuntu Natty) (and 3 other projects) "Broken TLS support in libGL.so (affects: 121) (dups: 28) (heat: 300)" [High,Triaged] https://launchpad.net/bugs/259219
[00:21] <bryceh_> ah that's just the TLS bug, nevermind :-)
[00:24] <RAOF> bryceh_: I did indeed ;)
[00:24] <RAOF> And, barring assembly, I've got it done locally.
[00:34] <bryceh_> pity no feedback yet on bug 702090.  did I go overboard with the paint-by-numbers directions and scare everyone off?
[00:35] <ubot4`> Launchpad bug 702090 in xserver-xorg-video-intel (Ubuntu Natty) (and 6 other projects) "i965gm GPU lockup if vesafb is left loaded (EIR: 0x00000010 PGTBL_ER: 0x00000100) - *ERROR* EIR stuck: 0x00000010, masking (affects: 72) (dups: 57) (heat: 520)" [High,Incomplete] https://launchpad.net/bugs/702090
[00:40] <bryceh_> apw, from my limited testing the vesafb kernel doesn't appear to *cause* issues near as I can tell.  If you wanted to just roll it out, we get enough automatic gpu error reports I think it would become pretty clear within a couple days whether it has eliminated the issue.  We should notice a flattening of the curve and no further bug reports filed with these codes.
[01:32] <RAOF> I WIN! (At causing glxinfo to segfault)
[01:42] <RAOF> And if you don't clobber registers mesa assumes aren't clobbered, glxinfo doesn't segfault either!
[02:16] <RAOF> Ahem.  And if you actually preserve the other registers, glxgears works, too.
[02:26] <bdrung> hi, my new sandbybridge system has frequent gpu lockups (bug #733006). is there something that i can do (test)?
[02:26] <ubot4`> Launchpad bug 733006 in xserver-xorg-video-intel (Ubuntu) "[sandybridge] GPU lockup 1a28f5a9 () (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/733006
[02:43] <RAOF> bdrung: Is that before or after mesa 7.10.1?  There were lots of sandybridge fxxups in that.
[02:44] <bryceh_> looks like it - version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu1
[02:45] <bryceh_> bdrung, unfortunately your gpu dump has a 00's for the error codes
[02:45] <bryceh_> [   49.302005] [drm:init_ring_common] *ERROR* render ring initialization failed ctl 00000000 head 00000000 tail 00000000 start 00000000
[02:45] <bryceh_> "render ring initialization", haven't heard of that one before
[02:46] <bryceh_> bdrung, so here are the things I'd suggest testing, in no particular order:
[02:46] <bryceh_> * boot an older kernel if you still have one installed.  That can help identify if it's a drm regression
[02:47] <bryceh_> * downgrade mesa.  Like raof says it has some changes for sandybridge.  Conceivably those changes could carry bugs too
[02:47] <bryceh_> bdrung, the above two are especially useful if this is a regression from it used to work right in the past
[02:48] <RAOF> * upgrade mesa; I think xorg-edgers is usable at the moment, and upstream's always more interested in bugs not fixed in the bleeding-edge.
[02:48] <bryceh_> * try the intel-drm-next kernel - http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/ - which will either identify if there might be a fix upstream, or else demonstrate it's an upstream bug
[02:51] <bryceh_> ok I am told I have a tired demanding pregnant wife needing some attention, so gtg
[02:52] <bryceh_> bdrung, hopefully the above helps.  Also keep filing apport bugs, sometimes it'll catch error codes when you're getting a string of 0's.
[02:53] <bryceh_> bdrung, there are a couple other people with similar error=0x00000 types of bugs for various chips, it's possible they're related.  I hesistate to send them upstream without more specifics but if we get enough reported will do so
[02:53] <bryceh_> l8r
[05:04] <Sarvatt> bdrung: try booting with with drm_kms_helper.poll=0 additionally please :)
[05:20] <Sarvatt> hmm, I guess updating lucid/maverick in xorg-edgers wont be that big a deal in the end, I just didn't want to backport the libdrm-nouveau1a rename since I'd have to rebuild crap like plymouth in there when the one built against 2.4.17 nouveau abi works fine but its just plymouth
[06:02] <RAOF> Bah.  When are those darned new Sony notebooks coming out?
[06:07] <bryceh_> check it --> http://www.bryceharrington.org/cgi-bin/upstreamer.cgi?bug=728823
[06:08] <bryceh_> attachment forwarding is partly in there to but it's sloooowwww so left it disabled for now
[06:11] <RAOF> Funky!
[06:14] <RAOF> Doh!
[06:14] <RAOF> Stupid IA32 assembler.
[07:17] <bryceh_> apw, https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/733096
[07:17] <ubot4`> Launchpad bug 733096 in xserver-xorg-video-intel (Ubuntu) "[q45] GPU lockup 32b1ab02 (EIR: 0x00000010 ESR: 0x00000010 PGTBL_ER: 0x00000002 IPEHR: 0x01000000) (affects: 1) (heat: 6)" [Undecided,New]
[09:12] <ricotz> RAOF, hi
[09:14] <ricotz> RAOF, did you see issues like these yet? nvidia-blob: http://enyo.zakx.de/~angelos/docky.png -- intel: http://img713.imageshack.us/i/docky.png/
[09:51] <bdrung> good morning. i will try all your suggestions and report back.
[10:38] <bdrung> bryceh_: the drm-intel-next kernel crashes with an ops while booting
[10:44] <bryceh_> bdrung, the drm-next branch might be a bit more stable
[10:53] <bdrung> bryceh_: that crashes too (general protection fault)
[10:59] <bryceh_> bdrung, the fact that it's crashing is probably interesting and may be relevant on your original issue.  hope you're taking notes
[10:59] <bdrung> bryceh_: nope, but screenshots ;)
[11:00] <bdrung> now i am trying xorg-edgers
[11:02] <bryceh_> have I mentioned today how much I hate the intel video driver's bugginess?
[11:02] <bdrung> no and i have to agree
[11:03] <bdrung> i had to start Windows to verify that the hardware is ok and that it's only a software problem
[11:04] <bdrung> bryceh_: xorg-edgers brought no improvement
[11:05] <bdrung> still gpu lockups
[11:05] <bdrung> right after login
[11:05]  * bryceh_ nods
[11:05] <bryceh_> well, xorg-edgers won't make a difference if it's a kernel drm issue, which is what it's starting to sound like
[11:06] <bryceh_> I'm curious about the oops and the gpf
[11:06] <bryceh_> if those are unrelated that would be seriously unfortunate
[11:06] <bryceh_> more likely though, they are different reactions to the same or similar fundamental issue
[11:06] <bdrung> bryceh_: are they stored somewhere on the disk? will apport report them?
[11:07] <bryceh_> you could look in /var/crash - if that's empty apport won't report them
[11:07] <bryceh_> I *think* that apport might neglect to report them since they're not stock kernels, but I'm not sure
[11:08] <bryceh_> you can look in /var/log/kern.log* to see if those files show the errors
[11:08] <bryceh_> if not, I'd suggest rebooting to those kernels and capture dmesg
[11:08] <bdrung> how should i capture dmesg if they crash on booting?
[11:10] <bdrung> and the second question is: what workaround can i use to avoid those crashed to have a chance to run apport?
[11:10] <jcristau> netconsole
[11:11] <bdrung> what command do i need to report these problems?
[11:12] <bryceh_> bdrung, a photo to capture the dmesg output showing the OOPS or fault would be a starting point
[11:12] <bryceh_> sometimes you can ssh in and grab it
[11:13] <bryceh_> if you can't ssh in, that would suggest a deeper kernel issue
[11:13] <bryceh_> like, ssh with an ethernet cable, if wireless hasn't kicked in yet
[11:14] <bdrung> wow, launching the drm-next kernel in recovery mode works. i have a console and can run dmesg
[11:14] <bryceh_> for workarounds, if you snag the file from /var/crash/ that corresponds to the crash and copy it to another machine, there are ways to file it from the other machine
[11:15] <bdrung> here's the dmesg output of drm-intel-next: http://paste.ubuntu.com/578782/
[11:16] <bryceh_> [   11.620556] Process plymouthd (pid: 346, threadinfo ffff88041edfa000, task ffff88041b2ec440)\
[11:17] <bdrung> so plymouthd died?
[11:17] <bryceh_> looks like it
[11:17] <bryceh_> could try booting with splash disabled, see if that makes the crash go away
[11:18] <bryceh_> or uninstall plymouth (if that still works)
[11:18] <bdrung> how is the splash disabling parameter called?
[11:19] <bryceh_> I think you just delete 'splash' from the kernel cmdline
[11:19] <bryceh_> linux	/boot/vmlinuz-2.6.38-4-generic root=UUID=2b238928-f3f1-4074-b551-2cceff54c6a4 ro   quiet splash vt.handoff=7
[11:20] <bdrung> i copied all crash files from /var/crash to this machine.
[11:20] <bryceh_> so you'd just go into grub (hold down left shift during boot), trim out 'splash', and boot
[11:20] <bryceh_>        apport-cli [ --save file ] symptom | pid | package | program path | .apport/.crash file
[11:21] <bryceh_> APPORT_IGNORE_OBSOLETE_PACKAGES=true apport-cli <foo.crash>
[11:21] <bryceh_> ^ that should be the magic to get the report to file from your other machine
[11:24] <bdrung> apport-cli complains that the crash doesn't belong to an not installed package
[11:28] <bryceh_> hrm, yeah I should have added I'd never gotten that magic to work right myself
[11:29] <bryceh_> fwiw, the .crash file is largely text... you can upload it to one of your bug reports for reference.  I think I should be able to extract the errors from the file myself.
[11:29] <bryceh_> I don't like doing that in general, but for you...  ;-)
[11:31] <bdrung> removing plymouth let the drm-intel-next kernel boot and it's currently running without locking up
[11:31] <bdrung> so i can report the bug on the main machin
[11:31] <bdrung> e
[11:33] <bryceh_> sweet
[11:33] <bryceh_> bdrung, ok, so sounding like a kernel/plymouth type of bug.
[11:33] <bdrung> but i can't report the crashes because apport complained that the package are not ubuntu packages
[11:35] <bryceh_> yeah, like I mentioned earlier
[11:36] <bryceh_> just attach the .crash files to the bug report, and I'll sort it from there
[11:37] <bdrung> bryceh_: i could pastebin them
[11:38] <bryceh_> it's getting a bit late for me, I'd prefer if you attached them to one of your bug reports, and I'll look at it tomorrow
[11:38] <bryceh_> (3:30am... need to hit the sack soon)
[11:38] <bdrung> bryceh_: should i file it against the kernel package or intel?
[11:41] <bryceh_> kernel
[11:41] <bryceh_> make sure to tag it 'natty'
[11:42] <bryceh_> actually, if you know how, I'd suggest filing it against both 'linux' and 'plymouth'
[11:42] <bdrung> k, will do that
[15:32] <bdrung> bryceh_: bug #733321 reported and crash logs attached
[15:32] <ubot4`> Launchpad bug 733321 in plymouth (Ubuntu) (and 1 other project) "[sandybridge] GPU lockups and other crashes (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/733321
[16:45] <Sarvatt> bdrung: go figure you have the screwed up board mentioned here too http://www.phoronix.com/scan.php?page=article&item=intel_sandy_speed&num=1 :(
[16:52] <bdrung> Sarvatt: can you give me the pointer to the phoronix command that triggers the issue?
[16:52] <bdrung> Sarvatt: i have the same board (with an b3 stepping)
[16:53] <Sarvatt> just booting was screwed up for them, i'm trying to find any discussion on what the actual problems were
[16:55] <bdrung> Sarvatt: my system runs fine with the drm-intel-next kernel (after only one plymouth related boot crash -> bug #733321)
[16:55] <ubot4`> Launchpad bug 733321 in plymouth (Ubuntu) (and 1 other project) "[sandybridge] GPU lockups and other crashes (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/733321
[16:56] <bdmurray> bryceh_: I'm still seeing bug 726807
[16:56] <Sarvatt> bdrung: even without drm_kms_helper.poll=0 ?
[16:56] <ubot4`> Launchpad bug 726807 in xserver-xorg-video-ati (Ubuntu) "drawing of drop down boxes produces artifacts temporarily (affects: 1) (heat: 479)" [High,Triaged] https://launchpad.net/bugs/726807
[16:56] <bdrung> Sarvatt: not tested yet
[16:59] <Sarvatt> it looks like 2.6.38-rc8 should work if drm-intel-next works
[19:40] <ricotz> Sarvatt, hi
[19:41] <ricotz> Sarvatt, did you hear about some cairo breakages (with transformation matrizes) lately?
[19:46] <Sarvatt> ricotz: afraid not, whats up?
[19:47] <ricotz> Sarvatt, http://enyo.zakx.de/~angelos/docky.png
[19:47] <evilvish> Sarvatt: hey, i recall you mentioned to use for the x freeze: $ echo 0x001ee62d | eu-addr2line -e /usr/lib/debug/lib/libdrm_radeon.so.1.0.0
[19:47] <evilvish>  and echo 0x001ee5da ; echo 0x001d35da ; echo 0x001d362d
[19:48] <evilvish> Sarvatt: should that be before the freeze or after?
[19:48]  * evilvish forgot.. :s
[19:48] <ricotz> Sarvatt, this happens for people on archlinux and gentoo lately, which seems to be cairos fault or the mono 2.10 bindings
[19:48] <evilvish> i got this without those echo lines » http://launchpadlibrarian.net/66142834/gdb-Xorg-2.6.35-6.7-generic.txt and after echo » http://launchpadlibrarian.net/66142892/gdb-Xorg-2.6.35-6.7-generic-echo.txt
[19:48] <ricotz> Sarvatt, but i suspected cairo, mesa or xserver
[21:19] <Sarvatt> real fix for jcastro's pageflip problem - http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commit;h=fdc315a19a2c33da29dd87d4ca88f4e4407bd42d
[21:21] <bryceh_> Sarvatt, what was jcastro's bug #?
[21:22] <bryceh_> hm, bug 715330 maybe?
[21:22] <ubot4`> Launchpad bug 715330 in xserver-xorg-video-ati (Ubuntu) (and 2 other projects) "Freeze after login with KMS enabled on Radeon HD6310 (affects: 2) (heat: 124)" [High,Confirmed] https://launchpad.net/bugs/715330
[21:22] <bryceh_> yep
[21:23] <Sarvatt> yep, beat me to it (was digging through mail)
[21:23] <Sarvatt> also he's working on a fix for the AGP pageflip problem https://bugs.freedesktop.org/show_bug.cgi?id=35183 \o/
[21:23] <ubot4`> Freedesktop bug 35183 in DRM/Radeon "system freezes with 2.6.38-rc kernel and kms pageflip enabled" [Normal,New]
[21:25] <bryceh_> Sarvatt, ok flagged it for JFo
[21:25] <Sarvatt> awwh he changed it from Not-reported-usefully-by: Michael Larabel @ phoronix to Article-written-by: Michael Larabel @ phoronix
[21:26] <bryceh_> hehe
[21:26] <bryceh_> Sarvatt, feel free to close the -ati task if you think there's nothing more needed to be done on our end (unless you think it's worth leaving open just for tracking it)
[21:49] <cnd> bryceh_, heads up: I have asked for a FFe for XInput 2.1 support in xinput (the utility) (bug 733536)
[21:49] <ubot4`> Launchpad bug 733536 in xinput (Ubuntu) "Add XInput 2.1 support to xinput utility (affects: 1) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/733536
[21:50] <cnd> I'm outta here now though :)
[21:50] <cnd> see you later
[21:53] <bryceh_> cnd, ok thanks for the notice
[22:09] <Sarvatt> ricotz: please dont tell me it's https://bugs.launchpad.net/bugs/259219 too :)
[22:09] <ubot4`> Launchpad bug 259219 in software-center (Ubuntu Natty) (and 3 other projects) "Broken TLS support in libGL.so (affects: 202) (dups: 66) (heat: 688)" [High,Triaged]
[22:15] <Sarvatt> ricotz: so whats needed to reproduce that docky problem?
[22:21] <ricotz> Sarvatt, unlikely that bug :P -- you would need mono 2.10, so not reproduceable on ubuntu/debian that easy
[22:22] <ricotz> looks like it is a mono/docky problem perhaps a change in the cairo bindings, pretty weird though


[01:03] <CrypticByte> does anyone know if kubuntu has the ability to have a global menu.  I know kde does since version 4.10 but i'm courious to know if the global menu has gtk2/3 support in kubuntu
[01:41] <CrypticByte> does anyone know if kubuntu has the ability to have a global menu.  I know kde does since version 4.10 but i'm courious to know if the global menu has gtk2/3 support in kubuntu
[07:28] <SamwiseGamgee> If I boot up a live CD, Kubuntu 14.04, can I install anything without affecting the hard drive?
[07:29] <SamwiseGamgee> I mean if I go to "Try and Decide" using the live CD
[07:45] <Pibble> SamwiseGamgee: The live cd is self contained. So Im pretty sure you cant install anything beyond what packages are included
[07:45] <SamwiseGamgee> yeah, I guess someone gave me some bad advice
[07:45] <Pibble> You can however make a live USB stick and you should be able to add any packages you need when creating it
[07:46] <SamwiseGamgee> oh, yeah, I think holstein told me to use a live CD to experiment with shutter, to see if I like it
[07:47] <SamwiseGamgee> but the Windows guys told me I can't install anything when using a Live CD, so I don't know why he told me that
[07:47] <Pibble> You should be able to "install" the package onto the ram drive, if you have enough space available that is.
[07:48] <Pibble> Try an apt-get for whatever you are needing and see if it goes through
[07:48] <SamwiseGamgee> ok
[07:50] <SamwiseGamgee> is there a way to protect your hard drive when installing stuff with a live CD, because I have never used a Live CD for that stuff before
[07:51] <Pibble> Nothing you do in the live cd will interact with your HDD
[07:51] <Pibble> Its isolated
[07:51] <Pibble> unless that is, you mount your HDD and allow the OS to access it.
[07:52] <SamwiseGamgee> Don't some Live CDs automatically mount your drives so you can access them?
[07:52] <Pibble> Its possible, but it wont install anything to the HDD. The OS is running on a RAM drive
[07:53] <SamwiseGamgee> Ok, then I will check the memory available on my RAM drive and see how many megabytes the Shutter app uses, and compare them before I try anything with the Live CD
[07:54] <SamwiseGamgee> sorry, RAM memory
[07:54] <Pibble> Aye
[07:54] <Pibble> You should be able to do it if it will allow it, but youll lose anything you do when you power down the compuer
[07:54] <Pibble> computer*
[07:55] <Graf_Westerholt> SamwiseGamgee, RAM stands for "ramdom access memory".
[07:55] <SamwiseGamgee> I got 1.41 GiB of RAM
[07:57] <SamwiseGamgee> Shutter uses around 45 MB when installed
[07:57] <SamwiseGamgee> Does that mean I have room to install it with the live Kubuntu CD?
[07:58] <Pibble> Like I said, try it, if it lets you do it, youre golden, if not... well yeah.
[07:58] <SamwiseGamgee> yeah, sounds like I got nothing to lose if I try it
[07:58] <Pibble> yep yep
[07:58] <SamwiseGamgee> thanks Pibble
[07:59] <Pibble> Sure thing, I hope you enjoy Kubuntu, its a great OS.
[07:59] <SamwiseGamgee> yeah, I like it more than xubuntu, which is what I'm using now
[07:59] <Pibble> KDE is nice. :3
[08:00] <SamwiseGamgee> but Kubuntu is too heavy for this PC, it runs slower than xubuntu
[08:00] <Pibble> KDE is rather loaded. Its more of a modern GUI than XFCE for sure.
[08:01] <Pibble> Its comperable to windows 2k vs windows 7
[08:02] <SamwiseGamgee> I really miss Kubuntu
[08:03] <SamwiseGamgee> also, the Kubuntu operators seem more friendly than the xubuntu operators
[08:03] <Pibble> Eh, there are bad examples in any distro/gui/shell/OS.
[08:04] <SamwiseGamgee> Not in my experience, I love the Kubuntu operators
[08:04] <Pibble> Just remember, open source means open to everyone, be it a rude, bad mannered person, or a helpful, kind person.
[08:05] <SamwiseGamgee> Pibble, nice to meet a kind person, thanks
[08:25] <lordievader> Good morning.
[11:40] <Naphatul> why can't i remove nepomuk, isn't baloo suposed to do it
[11:40] <Naphatul> *it's job now?
[11:42] <yofel> which kubuntu release?
[11:42] <Naphatul> 14.04
[11:43] <yofel> the runtime files *should* be optional, they just have to be there for the initial migration to baloo
[11:44] <yofel> what exactly are you trying to remove?
[11:44] <Naphatul> libnepomuk4
[11:45] <Naphatul> everything that matches nepomuk in dpkg -l actually
[11:45] <yofel> ah, that will only work in 4.14. 4.13 still has nepomuk support built into some applications, which doesn't really do anything as nepomuk isn't running
[11:47] <Naphatul> hmm well i'm running the same 4.13 on arch and it doesn't need nepomuk, guess it's a ubuntu thing
[11:47] <yofel> nepomuk-core-runtime has the bulk of runtime files and should be removable
[11:48] <Naphatul> is 4.14 going to be in 14.04? if so when?
[11:49] <yofel> 4.13.97 is in ppa:kubuntu-ppa/backports now, 4.14.0 will be released in a few days (upgrading to that will automatically remove libnepomuk4 btw.)
[11:49] <Naphatul> great
[12:44] <MartyB4> Hi. Since the upgrade from 12.04 to 14.04 I've got the problem that logging out of KDE doesn not work. Instead the shutdown dialog is shown and after the timeout the computer goes into sleep mode. Can anyone help me?
[12:47] <rostam> HI I am using ubuntu 14.04.  accroding to dpkg --list | grep linux-image  I have two linux image installed on my system:  linux-image-3.13.0-24  and linux-image-3.13.0-32.  Currently my system has booted to later one, 3.13.0-32, How could I boot to older release, 3.13.0-24? thanks
[12:48] <soee__> rostam: when grub is loade dyou should be able to choose other version i think
[12:49] <rostam> soee__, I have struggled with this I have used GRUB_DEFAULT="... " or set-default-.  still is not working will you please expand more  on your help...
[12:51] <swook> j #tmux
[12:51] <swook> oops
[12:51] <swook> sorry
[12:57] <soee__> rostam: i remember that after reboot GRUOB loads there is a list with some entries, first is problably Kubutnu
[12:57] <soee__> there should be also one that allows to to show list of older kernels and boot using one of them
[13:39] <georgelappies> hi guys, it seems that the vsync setting does not stick, I have to change my renderer to opengl 2.0 and then back to 3.1 before the tearing goes away when moving windows around after a reboot
[13:52] <soee> georgelappies: there are huge issues with is sadly :/
[14:17] <georgelappies> soee: isn't there a script one can run to emulate changing the renderer to opengl2.0 and back to opengl3.1 right after a boot?
[14:18] <georgelappies> it is sad, because it definitly does work correctly after retogling the renderer, just wished that it would stick or get correctly applied on a boot up :)
[14:22] <soee> no idea georgelappies
[14:22] <soee> lordievader: ^ any thoughts ?
[14:22] <lordievader> georgelappies: What card/driver?
[14:24] <georgelappies> hi lordievader, nvidia GeForce GTX 650 (GPU 0) using proprietary 331.38 from the repos
[14:25] <georgelappies> but the tearing is present in the opensource drivers as well
[14:26] <georgelappies> best way to test it is to drag a window around on the screen and look at the right side edge of the window against the wallpaper
[14:28] <georgelappies> going to see if kdenlive can record it, will report back
[14:29] <lordievader> I'm thinking a crappy driver, apart from that I have no idea.
[14:46] <georgelappies> here is a clip showing it, the first half of the clip shows it working as it should, the second half shows it how it is after a reboot: https://dl.dropboxusercontent.com/u/12004103/KDE_Tearing_Clip/tearing.mpg
[14:51] <zmitya> hi gents
[14:53] <zmitya> at work I have multiple monitors. I do have a panel at the very right side of the screen where my taskbar sits, this is an auto-hidden panel... Since I upgraded to 14.04 I have to click on the right screen if I want to get my panel in case when an app has the focus on the left screen..
[14:53] <zmitya> is it a bug ot a feature ?
[15:35] <pmted> Where do I change the graphics driver to Nvidia? When you first install Kubuntu it notifies you that you can use legacy drivers, but I chose not to and now I changed my mind.
[15:39] <Walex2> pmted: there is a specific page on the Ubuntu Wiki on how to install the prepackaged nVidia binary drivers
[15:40] <Walex2> pmted: the first step is to install the right packages, because there are a few variants.
[15:41] <Walex2> zmitya: with "auto-hidden" that seems like a feature
[15:41] <pmted> Walex2: Ah, bingo. Thanks!
[15:41] <Walex2> !nvidia
[15:42] <Walex2> plus many others...
[15:47] <Naphatul> will systemd be default in 14.10?
[16:02] <linux_> hi who can fix this
[16:02] <linux_> (cheese:3130): cheese-WARNING **: Device '/dev/video0' is busy: gstv4l2object.c(2524): gst_v4l2_object_set_format (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin17/GstV4l2Src:video_source:
[16:02] <linux_> Call to S_FMT failed for YU12 @ 1280x720: Device or resource busy
[16:03] <lordievader> !crosspost | linux_
[16:04] <linux_> ok but i did not know that
[16:04] <linux_> hehh
[16:04] <linux_> Im using kubuntu so
[16:08] <BluesKaj> howdy folks
[16:14] <linux_> hey
[16:14] <linux_> anyone live
[16:14] <RaSTuS> Hi BluesKaj, hi everyone
[16:15] <linux_> who want bear
[16:15] <BluesKaj> hi RaSTuS
[16:16] <linux_> can someone help i use motion first 4 days and it worked after update now is broken
[16:16] <linux_> and also cheese dont work
[16:16] <linux_> it says hi who can fix this (cheese:3130): cheese-WARNING **: Device '/dev/video0' is busy: gstv4l2object.c(2524): gst_v4l2_object_set_format (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin17/GstV4l2Src:video_source:
[16:16] <linux_> Call to S_FMT failed for YU12 @ 1280x720: Device or resource busy
[16:17] <lordievader> !patience | linux_
[16:19] <linux_> ok lordievader do you know is there any channel where I can give ideas on inprowment of look and feel of kubuntu
[16:21] <lordievader> linux_: Actually I have no idea.
[16:21] <lordievader> linux_: Mailing list perhaps?
[16:22] <linux_> ok
[16:23] <BluesKaj> linux_, look and feel is a personal thing. What someone else likes may not be to your taste. Check system settings> application settings and workspace appearance
[16:25] <lordievader> ^ that is very true. Linux is quite customizable.
[16:58] <linux_> yea but that is for newbee
[16:59] <linux_> so there are loots of places where plugin can be loaded or it can displaz other options of folder
[16:59] <linux_> of appp
[16:59] <linux_> and other things
[18:59] <femtac> Hi, I want to try out out KDE 5. Can I safely install the neon/kf5 ppa repository wihout affecting the stable 14.04?
[19:00] <femtac> How does it work after I install it? Do I switch to KDE 5 during login?
[19:06] <kubuntuplasma5> allo?
[19:12] <bprompt> allo
[19:19] <soee> femtac: yes, when using neon you can choose if you want to login into plasma5 or 4
[19:35] <smaudet> hmm, could anyone recommend to me where to look to perform an *offline* grub installation? i.e. to an external drive intended to boot in another computer
[19:35] <smaudet> problem with grub-mkconfig is that it runs for the current system
[19:37] <bprompt> hmm
[19:38] <bprompt> smaudet:      IIRC when having it to boot from an external device.. you can just include grub in the external partition specifically  with grub-install
[19:40] <smaudet> bprompt: not sure if you understood the question, grub when it boots should be an internal system, but I'm trying to build a drive from a different system, so the grub install is external.
[19:40] <smaudet> I'm pretty sure my grub config is all screwed up on the computer I'm on at the moment as I've been telling it to look at the external drive.
[19:40] <smaudet> But that's fine, I'll just reconfigure when I'm done building the external (before I reboot)
[19:41] <smaudet> conversely you can't pass in e.g. grub-mkconfig /dev/sdX and have it dump a config file for just that hard drive
[19:43] <smaudet> also, to keep things simple, everything is mbr, I have no need to mess with gpt at the moment, other than for future proofing the drive (if it is transfered at some point to a computer whose bios supports gpt)
[19:48] <smaudet> I *think* the issue is three fold - the mbr I've already tested was overwritten successfully on both test drive instances, but it's pointing at a drive on this computer setup, not the one it needs when booting from another computer
[19:49] <smaudet> So the second issue is that I'm not sure where to stick the imaginary /boot partition for the drive, and the third issue being that I don't know how to overwrite what grub-install points to when it writes its mbr record
[19:52]  * smaudet netsplit yay
[19:52] <bprompt> hehe
[19:53] <smaudet> hmm...reading the manual it looks like the recommendation is to manually write the grub.cfg file...
[19:53] <smaudet> X_X
[21:50] <smaudet> does anyone in here have a working windows xp multiboot by any chance (using grub)?
[23:34] <skinux> I've been having problems with chmod having no affect on .bin files, with or without using sudo.
[23:50] <cyclick> Why is the 32bit version recommended over the 64bit version? (ie: what are the most popular problems?)
[23:51] <cyclick> s/problems\?/problems with the 64bit version\?/


[01:38] <Prf_Jakob> Hey
[01:38] <Prf_Jakob> bryce, Sarvatt, RAOF: Two questions.
[01:39] <Prf_Jakob> Is feb 16th the date where you wont take any fixes from Mesa? Or just the date where you wont accept any new "feature" packages?
[01:39] <Prf_Jakob> Secondly when will all this new mesa stuff hit the daily ISO images?
[02:21] <tjaalton> Prf_Jakob: means that bugfix releases are still fine after that date
[02:22] <tjaalton> Prf_Jakob: so for instance 8.0.x is still acceptable
[02:23] <Prf_Jakob> tjaalton: ta
[02:23] <tjaalton> ..until the archive is frozen
[02:24] <tjaalton> since we'll get 8.0-rc before that, it shouldn't be an issue to get further fixes to it
[02:24] <Prf_Jakob> Ok good
[02:24] <Prf_Jakob> I'm planning on doing the rc tomorrow/today.
[02:24] <tjaalton> great
[02:26] <tjaalton> kibi from debian has done some work on the mesa master packaging
[02:42] <Prf_Jakob> when is the last date for 8.0.x pickup?
[03:35] <tjaalton> Prf_Jakob: april 12th
[03:35] <tjaalton> final final freeze :)
[03:36] <Sarvatt> yep!
[03:36] <tjaalton> so bugfix releases are generally good until that
[03:36] <Sarvatt> as long as we have something from 8.x in before feb 16th\ we can update up until the release
[03:37] <tjaalton> right
[03:37] <tjaalton> with some amount of paperwork
[03:39] <Prf_Jakob> ok
[03:39] <Prf_Jakob> We are planning on doing the 8.0 on feb 2.
[03:40] <tjaalton> like a walk in the park then :)
[11:02] <RAOF> Sarvatt: Yo dude, where you at?  I've got a laptop to palm off to a Lexingtonite and your huey :)
[11:02] <apw> RAOF, bryceh, http://people.canonical.com/~apw/edid-precise/
[11:02] <bryceh> apw, excellent
[11:03] <RAOF> Let's see if the queen boots that one! :)
[11:11] <bryceh> apw, seems to be disliking my bcmwl
[11:14] <bryceh> wish me luck
[11:27] <tjaalton> so, is the necessary fix for unity included in the 5.0 upload or not?
[11:27] <tjaalton> to use with the frankenserver
[11:27] <RAOF> I believe so, yes.
[11:28] <tjaalton> ooh, will dist-upgrade then
[11:28] <RAOF> You still need a fixed geis, but that's building.
[11:28] <tjaalton> right
[11:28] <tjaalton> noticed the upload
[11:28] <tjaalton> "Start in 37 minutes", and i386 built it already, meh
[11:34] <Sarvatt> tjaalton: yeah i'm using 5.0 now
[11:35] <ricotz> hi, finally ;)
[11:36] <tjaalton> Sarvatt: oh cool
[11:41] <cnd> RAOF, on second thought, I'd rather just use ppa:ubuntu-x-swat/x-staging
[11:41] <cnd> I've got a bunch of random stuff in dx-touch/unstable
[11:42] <cnd> and I'd rather leave it as-is with some daily build recipes set up
[11:42] <cnd> although x-staging doesn't build armel and powerpc, I think people on those archs can handle held back packages
[11:42] <cnd> what do you think?
[13:34] <tjaalton> dist-upgrade it is..
[14:07] <RAOF> cnd: https://launchpad.net/~canonical-x/+archive/x-staging is available for your delectation.
[14:33] <tjaalton> oh look, compiz spinning on cpu again :)
[14:34] <tjaalton> unity from the unity-team ppa, utouch-geis 2.2.2
[14:36] <bryceh> RAOF, https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/814895
[14:36] <ubot4> Launchpad bug 814895 in xserver-xorg-video-intel (Ubuntu) "[snb-m-gt2] Booting with external monitor fails with *ERROR* Couldn't find PLL settings for mode! (affects: 4) (heat: 22)" [High,Confirmed]
[14:38] <tjaalton> Sarvatt: which versions did you have again?
[14:49] <tjaalton> ok, so I _don't_ have the new utouch-geis update
[14:50] <tjaalton> wonder why it's taking so long to get published..
[15:02] <tjaalton> ok, got it updated, works again
[15:05] <tjaalton> and on that bombshell, it's time to call it a week
[19:55] <FernandoMiguel> evening
[22:55] <Hanmac> hay i tryed to make fglrx to an multiarch package (to avoid lib32) but i have problems to get glx working ... someone there that probably could help me?


[12:45] <RikMills> sgmoore: FYI: digikam, tellico and meta-kde merged. krusader syncd
[12:45] <RikMills> git pushed as well
[12:48] <sgmoore> thanks
[12:49] <sgmoore> I am helping with kf6 on the debian side and looking into post release bugs.
[12:51] <sgmoore> RikMills: can you help me understand how minimal installation works? apparently sound notifications are not working and I am wondering if somehow it didn't get the switch to pipewire.
[12:52] <RikMills> sgmoore: on noble? I am not sure myself with calamares
[12:56] <sgmoore> correct. okay, I will investigate further. arraybolt3 maybe you know?
[13:01] <RikMills> or tsimonq2
[13:06] <RikMills> to be honest I didn't realise it had one
[13:07] <BluesKaj> Hi all
[13:36] <sgmoore> hi
[14:53] <tsimonq2> RikMills, sgmoore: Minimal installation is super simple, actually
[14:53] <tsimonq2> https://git.lubuntu.me/Lubuntu/calamares-settings-ubuntu/src/branch/ubuntu/oracular/kubuntu/modules/pkgselect_context.conf#L6
[14:55] <sgmoore> hmm, that doesn't look like it would break notification sounds..
[14:59] <RikMills> sgmoore: unless once they are removed, something needed is removable by the later apt autoremove?
[15:00] <RikMills> I would hope not as that would mean we have insufficent deps on something else
[15:00] <sgmoore> exactly
[15:00] <sgmoore> requires further investigation.
[15:00] <sgmoore> valorie: I am looking into kwalletmanager too
[15:01] <RikMills> might be worth running that minimal remove command in a vm full install or iso, to see what then becomes autoremovable
[15:12] <RikMills> sgmoore: looks like qml-module-org-kde-notifications would be one thing that is removed?
[15:16] <RikMills> oh maybe not
[15:18] <RikMills> or maybe yes, lol
[15:20] <RikMills> only neochat seems to depend on that so maybe not at fault
[15:21] <RikMills> but a shed load of other stuff is also autoremoved
[15:22] <RikMills> oh, and you said sound notifications
[18:28] <tomreyn> Hi! There's an issue with 24.04 Torrent downloads geeting blocked in current Firefox due to HTTP (not HTTPS) URLs.
[18:28] <tomreyn> There's a Firefox feature (?) introduced in v125.0.1  ( https://www.mozilla.org/en-US/firefox/125.0.1/releasenotes/ ) which blocks http:// downloads with a warning message of "File Not Downloaded: Potential Security Risk" https://www.askvg.com/fix-file-not-downloaded-potential-security-risk-error-message-in-firefox/
[18:29] <tomreyn> changing https://kubuntu.org/alternative-downloads/ to point to (not httP but) httpS://cdimage.ubuntu.com/kubuntu/releases/noble/release/kubuntu-24.04-desktop-amd64.iso.torrent overcomes it
[18:38] <valorie> sgmoore: thank you! for now, Thomas' solution (hitting escape repeatedly until the warning goes away) works
[18:38] <valorie> but I'd rather have kwallet *actually* work
[18:39] <valorie> and also: congratulations on your new GSoC student!
[18:39] <sgmoore> valorie: I can't reproduce it. Can you send me screenshots please
[18:39] <sgmoore> thank you
[18:39] <valorie> I hope comms are working out for you two
[18:39] <valorie> ok, next restart I will send a screenie
[18:39] <sgmoore> yeah we have actually been in communication for quite awhile. Good kid
[18:40] <sgmoore> thanks!
[18:40] <valorie> excellent!
[18:40] <valorie> it doesn't happen (kwallet) on the upgraded box
[18:40] <valorie> just this new install
[18:40] <sgmoore> I tested on a new install
[18:41] <sgmoore> or did I. haha let me verify
[18:41] <valorie> 'twas confusing because it has Just Worked for well over a decade
[18:42] <sgmoore> yep same here. let me spin up a vm fast, I think the other lappy is an older install and not release ISO
[19:05] <sgmoore> doesn't happen in new vm.
[22:45] <valorie> sgmoore: on that old pam-kwallet bug BR, that does not seem to be the issue now
[22:46] <valorie> 100 /var/lib/dpkg/status
[22:46] <valorie> libpam-kwallet-common:
[22:46] <valorie>   Installed: 4:5.27.11-0ubuntu2
[22:46] <valorie>   Candidate: 4:5.27.11-0ubuntu2
[22:46] <valorie> from apt-cache policy pam-kwallet*