[01:23] <huayra> hello.. I'm running karmic and my gdm login dissapeared after todays update
[01:23] <huayra> has that happened to others?
[01:24] <huayra> I mean the X server works as I can type username/password and login and gnome loads... The only problem being that I cannot see ANY of this
[01:24] <huayra> I was trying to fill a bug but links is giving me a hard time in launchpad
[01:24] <huayra> that's why I installed irssi
[01:24] <huayra> hope you guys can help me to either solve this or at least post a bug
[01:26] <huayra> I tried using different kernel version at boot (It has actually worked under HArdy in another computer)
[01:27] <huayra> I have a intel card so no big deal regarding that
[01:29] <huayra> anyway.. There's something broke with the system... LEt's see if tomorrow update fixes it. If you are able to help me report this or have suggestions: huayra _at_ ubuntu _d0t_ com
[01:29] <huayra> nite
[01:32] <ArkoldThos> how do I upgrade my kubuntu to Karmic? i mean, alt+f2 + update-manager etc doesn't wrok
[01:43] <kklimonda> update-manager -d
[01:43] <kklimonda> hmm.. it doesn't work either..
[01:55] <arand> Current dist-upgrade wants to remove mktemp, nice...
[02:46] <DanaG> grr, damn notify-osd... completely IGNORES my notify-send setting for timeout.
[02:51] <DanaG> oh, and what's with the "omg I'm at max volume and you pressed volume up!" blinking?
[02:55] <DanaG> https://bugs.launchpad.net/notify-osd/+bug/337861
[02:59] <DanaG> interesting: https://bugs.launchpad.net/notify-osd/+bug/361958
[03:02] <DanaG> https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/344772
[03:02] <DanaG> er, /me stops pasting now.  =þ
[03:03] <r00tw4rrior> Daviey
[03:04] <r00tw4rrior> hello?
[03:04] <Pici> Hi
[03:05] <r00tw4rrior> I have a question
[03:05] <Pici> Ask away
[03:05] <r00tw4rrior> I am running Ubuntu 9.04 on a Sony Vaio and my mouse is malfunctioning, my left click doesnt work
[03:06] <r00tw4rrior> nore does the click on the pad work
[03:06] <Pici> r00tw4rrior: This channel is only for the development version: 9.10 (Karmic Koala) support and discussion, not 9.04.  Try #ubuntu instead.
[03:07] <r00tw4rrior> oh, thanks
[04:13] <cwillu> DanaG, I don't want your app deciding how long notifications stay up on my desktop :p
[04:14] <DanaG> I do.
[04:14] <DanaG> It sucks having my "ambient light sensor on" notification stay up for a full second.
[04:14] <cwillu> I know you do, that's why I'm glad notify-osd doesn't let you :p
[04:14] <DanaG> Or wait, it's more like 2 seconds.
[04:14] <DanaG> Way too long.
[04:14] <DanaG> Oh, and try using service-discovery-applet with notifications for all services.
[04:15] <DanaG> Behavior upon connecting to new network:  old system: spams a bunch of notifications all at once, that then disappear 1 second later.
[04:15] <DanaG> New system: queues them, and blocks everything else for, oh, probably like half an hour.
[04:16] <DanaG> Might be a good idea to add this bit of code: respect timeouts IF the client ALSO sends a new notification.
[04:16] <cwillu> honestly, that sounds like broken behaviour from the applet more than anything
[04:16] <DanaG> But that hardcoded delay is bad.
[04:16] <DanaG> Oh, and the "omg i'm at maximum volume! blink!blink!blink!" behavior sucks.
[04:17] <cwillu> I'll give you that one :p
[04:17] <DanaG> Try playing music, holding volume up for a bit, and then try to turn it down.  You can't.
[04:17] <DanaG> Same with the sluggishness -- the "show old value"
[04:17] <DanaG> It's because the volume change waits for the notification itself.  That strikes me as odd.
[04:18] <DanaG> Oh yeah, is a bubble staying up for 1.5 seconds, a bug?
[04:18] <DanaG> Or, a more sane example: try skipping 3 tracks in quodlibet.  Normally you get the three bubbles popping up in rapid succession, and then soon disappearing.  Now, you get the inability to tell which track you're on, because it lags.  =þ
[04:19] <DanaG> Test case for volume change: hold the key so it repeats when already at the end; it'll sit there devouring the CPU and blocking all other changes.
[04:19] <DanaG> Oh hey, perhaps you could make just the "already at max" notification be interruptible.
[04:19] <cwillu> notify-osd was supposed to have some way of amending notifications, wonder why nobody is using it
[04:20] <cwillu> that would solve all the issues that you've mentioned as far as I can see
[04:20] <DanaG> The old way of stacking and then disappearing was tolerable enough, I guess.
[04:20] <cwillu> aside from the blocking (which is an app problem) and the flashy-flashy (which is a developer-iq problem :p)
[04:20] <DanaG> try this: 	notify-send -t 750 "Ambient Light Sensor" "ON" -i gnome-brightness-applet
[04:21] <cwillu> problem exists between compiler and chair
[04:21] <DanaG> The blocking is "synchronous" notifications -- a "feature"
[04:22] <DanaG> The service-discovery-applet case is more of a torture test, if anything.  =þ
[04:22] <DanaG> Kind of like when you detonate 1000 explosive barrels at once in HL2, or something.
[04:25] <DanaG> Oh, and capping notifications would be good: if something starts spamming, don't give it the full 0.5 seconds -- or perhaps forcibly "append" as well.
[04:39] <DanaG> What's the default timeout supposed to be?  Frankly, the "don't let users customize things" smells too much like Apple, to me.
[04:47] <cwillu> I'm not talking about the users not customizing, I'm talking about the app writers not having say over these sorts of general services' settings
[04:47] <cwillu> not saying it's perfect, by any means though
[04:56] <DanaG> Good point, there.
[07:51] <mib_nl84j7> Trying to dist-upgrade, apt warns me that it wants to remove mktemp...Is this a known bug ?
[07:56] <joetheodd> mib_nl84j7, not sure but i think mktemp is no longer necessary with an upgrade to GNU coreutils, which includes the same functionality.
[07:57] <mib_nl84j7> So is it safe to dist-upgrade  ?
[07:57] <joetheodd> I believe so, but it might be wise to wait.
[07:58] <mib_nl84j7> Okay thanks :)
[07:59] <joetheodd> mib_nl84j7, https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/383768
[09:47] <Machtin> hm.. why does dist-upgrade want to remove mktemp?
[10:19] <cdE|Woozy> apparently mktemp is now provided by coreutils
[10:21] <LordKow> yes, wait for the update (7.4-2)
[10:23] <LordKow> heh doh
[10:23] <LordKow> the same bug we're talking about has brought package building to a stand-still
[10:23] <LordKow> none of the buildds are working until 7.4-2 gets in
[10:24] <cdE|Woozy> :)
[10:56] <Machtin> LordKow: i should wait for some update then?
[10:58] <Machtin> i btw. love To continue, type the phrase "I am aware that this is a very bad idea":"
[10:58] <Machtin> +"
[11:31] <mrwes> https://bugs.launchpad.net/ubuntu/+source/hal/+bug/381106
[11:32] <mrwes> when do bugs get triaged?
[11:41] <mrwes> sigh....
[11:49] <maxb> when someone triages them
[13:14] <korn_> karmic cannot be updated because mktemp would be removed. will this problem be fixed later on. or do I have to reinstall? (is only running in a VM)
[13:15] <aemyr> force it do update..there is no problem
[13:19] <korn_> update-manager reported an error. I will try apt-get dist-ugrade
[13:19] <korn_> *upgrade
[13:23] <korn_> http://pastebin.com/d2f89a37c
[13:32] <robin0800> Is it safe to remove mktemp?
[13:36] <c_korn> there is already a bug report about it: https://bugs.launchpad.net/bugs/383768
[13:44] <robin0800> c_korn from the bug report it appears the answer is yes as core utilities contain a replacement for it
[14:38] <mib_cix7727t> any one can help //pls
[14:53] <macvr> hi all, when is the karmic final release date? is it going to collide with win7?
[14:55] <Jeruvy> !release
[14:58] <macvr> ^well that didnt answer my question! but found out its 29th , is it wise to release i week after win7?
[14:59] <macvr> 1week^
[15:05] <scizzo-> macvr: why wouldn't it be?
[15:05] <Jeruvy> macvr: ubuntu releases are very consistant.  The link from ubottu is quite clear for your question.  If you read the link, it tells you the answer.
[15:06] <macvr> probably it might take the attention off from the release :(
[15:07] <macvr> Jeruvy: i was looking for https://wiki.ubuntu.com/KarmicReleaseSchedule , but only found this link after i asked here
[15:08] <scizzo-> ??? still don't get what would be the problem
[15:11] <gnomefreak> Ubuntu releases dont care much about win releases. we release every 6 months win releases every 3-5 years
[15:12] <gnomefreak> so to collide would not be important ;)
[15:12] <Pici> !schedule
[15:13] <macvr> scizzo-: was just wondering if it was a good decision? just that it might take the sheen of the release... just my thoughts!
[15:13] <gnomefreak> vista was released 2-3 years after it was sceduled to we release 6moths regaurdless
[15:14] <scizzo-> macvr: listen to gnomefreak and Pici they know...
[15:15] <macvr> scizzo-: i know the fixed release cycles , but was just wondering ... nevermind...
[16:18] <ikonia> !uptime
[16:18] <ikonia> !give ikonia a test
[17:40] <maxb> Hrm. It seems gnome-power-manager is no longer aware that I have a battery, and thinks I'm always on AC power
[17:45] <alteroo> Hello having some issues with Akregator installing
[17:45] <alteroo>  It's conflicting with kde-icons-oxygen
[18:04] <alteroo> /var/cache/apt/archives/libkdepim4_4%3a4.2.85-0ubuntu1~jaunty1~ppa5_i386.deb
[18:04] <alteroo> E: Sub-process /usr/bin/dpkg returned an error code (1)
[18:10] <alteroo> trying to overwrite `/usr/share/icons/oxygen/16x16/status/meeting-organizer.png', which is also in package kde-icons-oxygen
[19:00] <alteroo> Anyone can assist with a conflict?
[19:22] <alteroo> Anyone can assist with a conflict?
[19:25] <jussi01> alteroo: Im not sure of the recommended way, but if you read man apt-get itll tell you ;)
[19:26] <alteroo> :-) I did that ran through the gamut of apt-get -f install, apt-get -f dist-upgrade, dpkg -i --force-overwrite
[19:26] <alteroo> None of them seem particualrly capable of solving this
[19:27] <jussi01> usually Ive sorted it with --force-all then apt-get install -f
[19:27] <jussi01> but that is only me.
[19:27] <alteroo> Ah let me try that
[19:35] <alteroo> jussi01: I'm not finding a --force-all option
[19:36] <jussi01> in dpkg ?
[19:36] <alteroo> Yah
[19:36] <alteroo> Unless I'm reading the man wrong
[19:36] <jussi01> dpkg -i --force-all iirc
[19:37] <alteroo> \o/
[19:38] <alteroo> it was saying something about an option conflict before
[19:38] <alteroo> not sure
[19:38] <alteroo> jussi01: you deserve muffins
[19:39] <jussi01> yw
[19:40] <alteroo> :-D thanks a lot
[19:40] <alteroo> Hooray Akregator goodness
[19:49] <maxb> Using --force-all is usually a mistake
[19:51] <alteroo> maxb: What is the non mistaken way?
[19:52] <maxb> At a very minimum, figure out exactly what you're forcing and use the more specific option, but better still, fix the underlying problem instead
[19:52] <alteroo> underlying problem is they both install the same PNG file it looks like
[19:53] <alteroo> maxb: It's a single file a shared Meeting-online.png
[19:59] <dtchen> missing conflicts / replaces combination
[19:59] <dtchen> haven't read scrollback, however
[20:04] <alteroo> dtchen: Hmm?
[20:14] <dtchen> alteroo: when multiple packages own the same file, at least one needs some combination of Conflicts/Replaces (though each individually is valid - really depends on the specific instance)
[20:16] <c_korn> is XServer 1.7 going to be in karmic?
[20:16] <alteroo> dtchen: Right so just a packaging sanfu
[23:31] <c_korn> is XServer 1.7 going to be in karmic?
[23:47] <hggdh> well, xserver.xorg is at 1:7.4~5ubuntu1 right now
[23:58] <c_korn> the xserver is only on version 1.6: http://packages.ubuntu.com/karmic/xserver-xorg-core
[23:58] <c_korn> 1.7 is not released, yet
[23:58] <c_korn> is it going to be in karmic?