[01:38] So I know it's nitpicky and trivial, but it says May 23th as opposed to May 23rd in the release schedule [01:38] https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule [01:41] litropy, someone's spellcheck is messed up :) [01:44] nice pick up. 4 more months!! [01:48] litropy: fixed [01:57] Hah, thx. I'll be sure to update my resume: "Ubuntu Contributor" === Logan_ is now known as Guest48721 === Guest128 is now known as Logan_ === viv`d is now known as vivid === Logan_ is now known as Guest15447 === Logan__ is now known as Logan_ === Jikai is now known as Jikan === Ian___ is now known as Ian_Corne === SwedMike is now known as SwedeMike [07:49] Hi [07:49] Do you know what is happening with kde-workspace-*. Upgrades are currently impossible because of missing dependencies. [08:33] SorenHolm: that's bits an pieces required for the in-progress kde sc 4.10.80 release already being in the archive. Try not to dist-upgrade kde for the next few days [08:38] yofel: thanks - I was just wondering it is was an accidential change. :) [11:16] Hey all === mydogsnameisrudy is now known as monkeyjuice === Nakkel_ is now known as nakkel [13:45] Hi, I use Ubuntu 13.10, today I made an upgrade after something like 3 weeks (or mabye more) of no-upgrade period. After reboot I noticed that my network interface names are no longer renamed according to /etc/udev/rules.d/70-persistent-net.rules. Anybody knows what can be the problem here? [13:47] Orion78, network interface names ? How have they changed ? [13:50] BluesKaj: I have two hardware network cards, one build into motherboard 1GBit (which I do not use) and one PCI realtek 8139, before an upgrade 8139 was eth0 and builtin was eth1, now it is the opposite. [13:51] BluesKaj: /etc/udev/rules.d/70-persistent-net.rules has entries to make 8139 -> eth0 and buildin -> eth1, but those entries are not applied. [13:51] Orion78, is there 'network pci card as default' setting in the bios [13:51] ? [13:51] I do not know. [13:53] Orion78, do you use network manager ? [13:53] BluesKaj: but, renaming network cards worked before an upgrade, I could name cards as I pleaded, it does not work now and it bothers me. [13:53] BluesKaj: no, I do not have it even installed. [13:55] ok what about your /etc/network/interfaces ethernet settings , you might want to check the settings there [13:56] BluesKaj: standard stuff there, static interface configuration for eth0 [13:56] so what about the onboard ethernet ? [13:57] BluesKaj: I do not use it cause it sucks. [13:57] yes, but is it listed ? [13:58] BluesKaj: in /etc/network/interfaces? no [13:58] BluesKaj: wait, in /etc/network/interfaces are only listed lo and eth0 [13:59] BluesKaj: It happens that after boot eth0 is onboard card. [13:59] no static , ok then change it to eth1 [13:59] BluesKaj: in /etc/udev/rules.d/70-persistent-net.rules I have both cards with names I want them to have. [14:00] BluesKaj: why? [14:01] Will it help me to rename my network cards as I plead? [14:01] well , if the rules aren't persistent then why not? [14:01] BluesKaj: what do you mean rules aren't persistent? [14:02] the assigned names aren't working [14:02] BluesKaj: /etc/udev/rules.d/70-persistent-net.rules is not updated, it is an old file with correct entries. [14:02] Oh, I got it, you are proposing a workaround. [14:03] Thank you, but no. [14:03] I want to know why renaming stopped working and make it work again. === om26er is now known as om26er|opt === om26er|opt is now known as om26er-otp [14:05] well , then someone else will have to answer that ..I have no idea .unless that rule file is no longer valid [14:10] why not just go with the default settings and use eth1 in the interfaces file [14:11] or whatever the pci nic is assigned [14:11] BluesKaj: I moved /etc/udev/rules.d/70-persistent-net.rules and regenerated it with # echo add > /sys/class/net/eth0/uevent, it appears that the entry format has changed. [14:12] BluesKaj: I edited /etc/udev/rules.d/70-persistent-net.rules to make names as I wanted and I will reboot now, I will report back after reboot. [14:17] BluesKaj: It didn't work :) [14:20] well, dunno why you insist on using a rule that doesn't seem to be applicable ..13.10 is a dev release after all , not everything is expected to work as it should . [14:23] BluesKaj: If I am not be able to fix it today I will eventualy be forced to switch to eth1 temporarily. I just do not like to give in to technical problems. [14:24] Orion78, I mean the pci nic assigned ethernet , ethX , or whatever that numberX is [14:25] i do not mean, use the onboard [14:25] BluesKaj: I got it the first time :) [14:27] one has to be sure :) [14:29] BluesKaj: Thank you. === Ian____ is now known as Ian_Corne [14:38] BluesKaj: We have a couple machines here that we want eth0 to be the onboard then eth1 through eth 6 to be the pci NIC cards. But if you have all the adapters in and set up, the first PCI one usually is eth0, then it goes through all those and the onboard becomes eth6 in the end. So we have to tinker with the 70-persistent-net.rules file for that. The onboard in this case is like the cascade/uplink port of a router and needs to be gigabit and not fast [14:38] ethernet, etc. [14:39] ok, but is there a nic setting the bios for pcis? [14:40] or is the 70-persistent-net.rule required , genii ? [14:41] BluesKaj: No bios settings. So the only way is custom udev rule like that. [14:42] ok genii , good to know , thanks === om26er-otp is now known as om26er [16:39] wow, running pidgin, firefox and my 13.10 system is using 1.1 GB memory === ryanakca_ is now known as ryanakca === LordOfTime is now known as LordOfTime|EC2 [18:47] and now chrome chrashes on start up? :S [19:16] FernandoMiguel: chrome or chromium? i don't have any problems with chromium default home page [19:16] chrome. dev! [19:16] reported it as https://code.google.com/p/chromium/issues/detail?id=251848 and someone deleted it [19:16] great, just great [19:16] memory usage is quite high on 13.10 [19:17] tell me about it [19:17] oh no, it was deleted [19:17] yeah, I know! feeling kinda bumped! [19:17] no issue no bug!! [19:18] can't believe using 25% of memory on a 4 GB machine using pidgin, chromium, firefox. [19:19] johnjohn101: I've got OOM with just chrome and firefox (and java CrashPlan) [19:19] on 8GBs of RAM [19:19] i guess lightweight linux a thing of the past. [19:20] eheh [19:21] I have a chromebook... 1.5GB RAM... not enough to run ChromeOS for a poweruser [19:23] got it up with $ google-chrome --no-experiments [19:27] what are you running on it? [19:29] johnjohn101: ? [19:31] your chromebook, didn't understand what you posted [19:34] johnjohn101: it's samsung arm chromebook, running stock chromeOS beta branch [19:38] and it barely runs on that hardware? [19:38] yeah === Gasseus is now known as Rallias === yofel_ is now known as yofel === terryh is now known as terryh-afk [20:59] darn [20:59] unity-panel-service is totally broken [20:59] it used to use all CPU [20:59] but now won't even restart [21:00] I've not had unity work for me since I updated [21:00] and it complains it's not supported in my HW [21:00] now that chrome finally supports WebGL on my HD3000 [21:00] unity stops.... [21:02] nautilus also crashing when dropbox is running [21:02] I think my issue is with fglrx [21:02] it's going to be one of those cycles ..... [21:05] FernandoMiguel: still very early in the cycle, right? [21:05] no idea [21:06] I always start on day One [21:06] i've had to reload once and i just use mimimal until beta comes out [21:07] i think alpha 1 stage is 8 days away [21:08] I asked this under #ubuntu-app-devel, but no one is there. Is there a way to emit a PropertiesChanged signal using Q_PROPERTIES? I'm trying to implement this: http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-properties, as per http://www.mentby.com/Group/dbus/propertieschanged-signal-take-2.html. [21:08] This is with the Qt5 DBus interface. [21:19] FernandoMiguel: are you running on hardware or in a VM? [21:19] hw [21:19] always hw [21:20] intel,nvdia,or amd? [21:20] for years [21:20] on this, intel HD3000 [21:20] is that sandy bridge? [21:21] something like that [21:21] I never know their names [21:21] [ 0.072344] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, Intel PMU driver. [21:22] [ 0.072327] smpboot: CPU0: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz (fam: 06, model: 2a, stepping: 07) [21:25] ut oh, got the partial upgrade thing... i guess i'm going to wait a few days [21:29] I got the same partial upgrade complaint, but you can usually fix it yourself with Synaptic. [21:30] Usually update-manager just does a partial update because you have an old package that's conflicting with new packages that need to be installed to complete the update. [21:34] i hope i dont have to reload [21:34] i guess this is the alpha level with all the packages.. it's a lot [21:35] alpha 1 [21:38] ok survived the reboot, whew [21:55] alias distupgrade='sudo apt-get update && sudo apt-get upgrade -y && sudo apt-get dist-upgrade' [21:55] that's what I run at least once a day [22:00] That's interesting. [22:05] i just hit software updater once in the morning and once in the afternoon [22:13] there's a button? :O [22:24] so far, i don't see much of a difference between 13.04 and 13.10. [22:25] scopes and kernel [22:26] rarely is [22:26] johnjohn101: your first +1? [22:27] first this early. [22:27] I've been on +1 since 2007 [22:27] i usually start at alpha 2 + two weeks [22:27] was on beta with 2006.10 [22:28] I think I've been on +1 since day one starting in 2008... not sure [22:29] do you open bugs? [22:30] i just use basically 3 apps. pidgin, firefox, chromium [22:30] not as many as I used to [22:30] will test libreoffice when it changes [22:30] johnjohn101: I use those yeah, a several more [22:35] linux/ubuntu is pretty mature. just seems more incremental now. [22:52] ha, can't change background [23:01] nity nite [23:16] having trouble running software center [23:16] here is my error log http://pastebay.net/1241735 [23:16] not error log just the spit from terminal === bazhang_ is now known as bazhang [23:17] clickclack, What about a update from the cli, can you pastebin the text. [23:17] Looks like you might be having this problem: https://bugs.launchpad.net/ubuntu/+source/dbus-python/+bug/1068680 [23:17] Launchpad bug 1068680 in dbus-python (Ubuntu) "Software center does not start [dbus.proxies - ERROR - Introspect error]" [Undecided,Confirmed] [23:17] You have python-dbus installed? [23:17] have not installed it manually [23:17] If it's a python/dbus problem, then you also might not be able to use Ubuntu One. [23:18] It's strange that you have the problem and I don't. [23:18] one sec and il try installing dbus, [23:18] Okay. [23:19] is the package name just dbus-python? [23:21] both dbus and python-dbus are newest versions [23:21] Ahh, sorry. That's what I have too. [23:22] Can you run the software center from the Guest Session? [23:23] If you can run it from the guest session, then you'll know that it's an issue with your local config. [23:24] trying that now [23:25] nope wont work in guest [23:25] and ubuntu one is not working either [23:31] found something that says to try installing sip and qt4 however it throws me this [23:32] The following packages have unmet dependencies: python-qt4 : Depends: sip-api-9.2 E: Unable to correct problems, you have held broken packages. justyn@justyn-ubuntu:~$ sudo apt-get install sip-api-9.2 Reading package lists... Done Building dependency tree Reading state information... Done Package sip-api-9.2 is a virtual package provided by: python-sip 4.14.7-1 [Not candidate version] E: Package 'sip-api-9.2' has no i [23:33] that needs python-qt4 rebuilt against new sip. Should be done within a day [23:35] fixed [23:35] just install sip,