[00:06] is the GTF tool trust worthy enough to create modelines? [00:46] Hello [00:51] kahrytan: hello [00:52] Im still working on my bug [00:52] what is it about? [00:52] bug 223835 [00:52] oops wrong one [00:53] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/220952 [00:54] https://bugs.launchpad.net/ubuntu/+bug/220952 [00:54] I read I should check xorg log. nv driver output allot of tests and possible modelines. [00:57] mmm [00:57] I was just gonna say something about ddcprobe output being useful too [00:59] kahrytan: are you using a 32 bit or a 64 bit kernel? [01:00] 32bit [01:00] could you add the full output of 'ddcprobe' as an attachment to your bug too? [01:00] lol nvidia doesnt spit out any modelines in log. uses autoselect [01:00] bdmurray, I bet nv's report would be useful [01:01] ddcprobe not installed [01:03] bdmurray, hows this http://pastebin.org/32918 [01:04] I think it has the same relevant bits [01:04] lol [01:04] it generated modelines [01:05] what is the name of the package that controls the time settings? i have an issue with dual booting windows xp and hardy.. they're both set to automatic time sync, and my clock is way out when i reboot from windows back into hardy [01:05] im just trying to see if its already been reported [01:06] bdmurray, does it matter i had nvidia turn on at probe? [01:07] i condider it a "bug" that ubuntu isnt automatically updating the time like i told it to.. and there must be some kind of localtime/utc issue (Which i have no idea how to configure) [01:09] bdmurray, the nv gives more information like dot clock [01:10] kahrytan: I don't think it matters. [01:11] wouldnt nv log be better, given it did tests, output more information, and gave modelines for x to use? [01:13] It'd be best to add both, or almost everything you can then. [01:13] I uses gtf to make modelines too [01:14] snadge: You may want to read this: https://help.ubuntu.com/community/UbuntuTime?action=show&redirect=ChangeTimezoneHowto#head-31a2e864837bce9761bc0520026f78970d18afde [01:14] hmm.. why didnt someone tell me to edit /etc/default/rcS and change UTC=yes to no ;) [01:14] i will check that [01:15] snadge: that page tells you to change the UTC setting :-) [01:16] this one is difficult, the general consensus is that its a bug in windows.. it is fixable on windows, but the fix apparently doesn't work properly (100%) ;) [01:24] bdmurray, https://bugs.launchpad.net/ubuntu/+bug/220952 i added both. [01:25] great! [01:25] bdmurray, X needs to detect the monitor better. [01:26] bdmurray, thats why i added displayconfig-gtk. If someone has a problem as well, they can just select their monitor and it'll config xorg correctly . Right now, there is no template for the monitor. [01:28] bdmurray, i found Gentoo wiki very helpful in this bug [01:29] bdmurray, http://gentoo-wiki.com/HOWTO_Widescreen_Resolutions_%28WSXGA%29 [01:32] bdmurray, How am i doing? [01:33] I think the information you've provided will help out the developers [01:34] The more information, faster the fix [01:36] But how accurate does ddcprobe or nv report things? [01:37] As I understand it, ddcprobe gets the values right from the monitor [01:37] However, not all monitors advertise their values right [01:38] I considered emailing viewsonic [01:39] I does report model and serial# right [01:41] ddcprobe did error on part [01:41] timing: 1024x768@87 Hz Interlaced (8514A) [01:41] Monitor doesnt do interlaced. [01:41] its in the specs. [01:46] time for a break from this. [02:01] Can I mark a bug that I cannot reproduce as incomplete until the user responds with more info? [02:04] ffm: if you ask for more triaging info, yes [02:04] and subscribe yourself to the bug === bdmurray changed the topic of #ubuntu-bugs to: Ubuntu BugSquad | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | If you have been triaging bugs for a while, please apply to https://launchpad.net/~ubuntu-bugcontrol/ - http://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad === jordoex_ is now known as jordoex [07:21] bug 172507 [07:22] hmm, ENOBOT :( [07:23] yeah [07:56] thekorn: I'm getting error 104 when trying to use the 5-a-day applet [07:59] secretlondon, hmm, that's an bzr error, can you please give me your /tmp/5-a-day-applet.txt [08:00] thekorn: URLError: [08:00] Committing Bug #217489 ... [08:00] Committing Bug #94009 ... [08:00] ... Finished with ErrCode 104 [08:00] there was a python traceback before [08:00] can you please paste me this traceback [08:02] thekorn: http://paste.ubuntu.com/8846/plain/ [08:02] thank you [08:02] I've not been able to submit a bug to 5-a-day for about a month. I removed the applet and installed the current version 'fresh' as a result of the tag bug I submitted [08:05] :( I was able to reproduce this 'tag' bug [08:06] thekorn: I saw, and that was why I removed my 5-a-day applet and then reinstalled [08:08] ok, your issue is unrelated to the traceback, I've a similar one, launchpad might have some connectivity problems this morning [08:09] it's been like this for a while [08:09] not just today [08:09] the prbelem is we are loosing the information of the bzr-error somewhere so it's not easy to track this donw [08:10] I suspect this might be my internet provider blocking something :( [08:18] james_w, hi, is there a list of all error-codes of 'bzr' available somewhere? [08:37] secretlondon, there might be better debug information for your 104 error when the fix in bug 224568 is released [08:42] thekorn thanks [08:47] the motu have a bug bot called ubottu [08:51] I see, this bot is also in several other #ubuntu-* channels but not here [08:52] nor in -announce === emu is now known as emu1982 [09:26] hi [09:26] anyone here ? [09:27] i just wanted to talk about a bug that's not really severe but probably confusing to newbies [09:28] it has been reported many times in different forms on the launchpad so i'm not sure it's useful to file it anew [09:29] i don't understand why it is not corrected yet since it has been reported at least since 2005 and it doesn't seem really complicated [09:29] nico_: Do you have bug numbers for these? No idea without looking at them first. [09:30] yes, i describe i first in a general way and then i send 3 or 4 urls that seem related to the same bug [09:30] it is related to the keyboard layout configuration [09:30] Okay. [09:31] if one want to change it from the gnome control center, it works once but after rebooting the keyboard comes back to the initial configuration [09:31] hi all. [09:31] although the gnome control center still show the one chosen [09:32] to get the right keyboard, i had to check this file : /etc/X11/xkb/symbols/fr ( i guess other versions exist like /etc/X11/xkb/symbols/ca or /etc/X11/xkb/symbols/en or /etc/X11/xkb/symbols/ru etc.) [09:33] and find there which layout i want (just check the comments and the name after the keyword xkb_symbols) [09:33] and then report the name of the desired keyboard in xorg.conf just next to Option "XkbVariant" in the keyboard section [09:34] then save xorg.conf and reboot and i get the right keyboard layout [09:34] i don't understand why the gnome control center doesn't manage it itself [09:34] so, here some urls : [09:35] that sounds odd that it didn't manage it like it should. [09:35] https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-keyboard/+bug/196277 [09:37] i guess this bug is fixed isn't it? [09:38] well not in hardy [09:38] i mean, i installed hardy and have the problem as well as many others in forums [09:38] looks also a bit like it : https://bugs.launchpad.net/gnome-control-center/+bug/103111 [09:39] https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/46046 (see last comments) [09:40] yeah, i see the comments. i don't think everyone's going to want to change their xorg.config file to fix the problem. but that's just me. [09:41] https://bugs.launchpad.net/gnome-control-center/+bug/173721 === emu1982 is now known as emu [09:42] all of those links report similar problems. [09:42] yes [09:42] nico_: what is your issues exactly? [09:43] check those links he mentions. keyboard layout issues, it seems ubuntu keeps switching back to a default layout after a reboot instead of remembering what was selected as the current layout before the reboot. [09:44] @seb128 : here's the whole description if one want to change it from the gnome control center, it works once but after rebooting the keyboard comes back to the initial configuration [09:44] although the gnome control center still show the one chosen [09:44] to get the right keyboard, i had to check this file : /etc/X11/xkb/symbols/fr ( i guess other versions exist like /etc/X11/xkb/symbols/ca or /etc/X11/xkb/symbols/en or /etc/X11/xkb/symbols/ru etc.) [09:44] and find there which layout i want (just check the comments and the name after the keyword xkb_symbols) [09:44] and then report the name of the desired keyboard in xorg.conf just next to Option "XkbVariant" in the keyboard section [09:44] then save xorg.conf and reboot and i get the right keyboard layout [09:44] i don't understand why the gnome control center doesn't manage it itself [09:46] so i don't think it's a good idea to file a new bug report... [09:46] i hope this can be fixed, especially for newcomers [09:47] weird [09:47] me too. it would be annoying. [09:47] I've done a lot of hardy test installations [09:47] and all got azerty correctly configured as selected in the installer [09:47] yes [09:47] and using the gnome capplet to change the layout works correctly [09:47] ah [09:47] it just doesn't apply to your user [09:47] so not to the login screen [09:48] well the keyboard configuration was the one chosen during the installation [09:48] then i noticed i made a mistake and wanted another keyboard layout (without re installing) [09:48] then the problem showed up [09:49] i didn't try in the login screen [09:49] what problem? [09:49] there is "in the login screen" [09:49] go to system, preferences, keyboard [09:49] layout tab [09:49] add one [09:49] remove the one you had before [09:49] and you have the new layout [09:49] yes : that doesn't work [09:49] no [09:49] it just works once === emu is now known as emu1982 [09:50] when i did that, the next time i rebooted it switched again to the initial keyboard layout [09:50] did you configure several layout? [09:51] or only one? [09:51] only one [09:51] was the right layout still listed in the gui after the reboot? [09:51] yes, the layout tab from gnome-control-center is still right [09:52] gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd? [09:53] gconftool-2 -g /apps/gnome-settings-daemon/plugins/keyboard/active? [10:00] it's the middle of the night here lol. [10:12] my nickname has been changed from nico_ to nico__ ! [10:12] problem looking similar https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/19159 [10:14] nico__: [10:14] gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd? [10:14] gconftool-2 -g /apps/gnome-settings-daemon/plugins/keyboard/active? [10:14] nico__: do you use GNOME? [10:14] yes [10:15] didn't you get my answers for these two commands ? [10:15] no [10:15] so here they are again : [10:15] gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd now gives : layouts = [fr latin9] [10:15] model = [10:15] options = [lv3 lv3:ralt_switch,grp grp:alts_toggle] [10:15] overrideSettings = true [10:15] which is right since i configured it myself so in xorg.conf [10:15] the second command gives : [10:15] Aucune valeur définie pour « /apps/gnome-settings-daemon/plugins/keyboard/active » [10:15] which means no defined value for « /apps/gnome-settings-daemon/plugins/keyboard/active » [10:16] all that is not good [10:16] i also added these things, if that can help : [10:16] the xorg.conf keyboard section was Section "InputDevice" [10:16] Identifier "Generic Keyboard" [10:16] Driver "kbd" [10:16] Option "XkbRules" "xorg" [10:16] Option "XkbModel" "pc105" [10:16] Option "XkbLayout" "fr" [10:16] Option "XkbVariant" "oss" [10:16] Option "XkbOptions" "lv3:ralt_switch" [10:16] EndSection [10:16] and never changed when using the gui [10:17] i changed it to Section "InputDevice" [10:17] Identifier "Generic Keyboard" [10:17] Driver "kbd" [10:17] Option "XkbRules" "xorg" [10:17] Option "XkbModel" "pc105" [10:17] Option "XkbLayout" "fr" [10:17] Option "XkbVariant" "latin9" [10:17] Option "XkbOptions" "lv3:ralt_switch" [10:17] EndSection [10:17] and it works [10:17] i had to find the name of the right XkbVariant in /etc/X11/xkb/symbols/fr [10:17] the result of "gconftool-2 -g /apps/gnome-settings-daemon/plugins/keyboard/active" ( no defined value for « /apps/gnome-settings-daemon/plugins/keyboard/active ») looks weird, like something is not configured [10:17] ups [10:17] they renamed it [10:18] it's /apps/gnome_settings_daemon/plugins/keyboard/active now [10:18] ok, so i try again [10:19] it returns true [10:19] ok, so I've no idea what the issue is [10:20] you get no gnome-settings-daemon error on login? [10:20] no [10:20] well........ === emu1982 is now known as emu [10:20] you might want to log into a non gnome session, run gnome-settings-daemon --debug --no-daemon and read if the keyboard plugin is correctly loaded [10:20] i must add that i run gnome-settings-daemon from e17 and gnome-control-center as well... [10:21] could that be related to e17 ??? [10:21] yes, it could [10:21] e17 could have it's own config and apply it after GNOME [10:21] s/it's/its [10:21] then i try to log in with gnome and i check if the same bug shows up in gnome [10:21] good idea [10:21] i reconnect soon [10:22] change your xorg to a wrong value [10:22] yes [10:22] ok === emu is now known as emu1982 === emu1982 is now known as emu === emu is now known as emu1982 [10:33] well that's done [10:33] you're right [10:33] i made the change in the gnome control center from gnome and it lasted [10:34] i also checked the login screen but its layout remains the wrong one (which has not so much importance) [10:34] seb128 : are you still here ? [10:35] re [10:35] seb128 : are you seb128_ ? [10:35] ok [10:35] yes [10:35] i repost my answers : [10:35] well that's done [10:35] you're right [10:35] i made the change in the gnome control center from gnome and it lasted [10:35] i also checked the login screen but its layout remains the wrong one (which has not so much importance) [10:36] ok, that's the expected behaviour [10:36] as said the GNOME setting is an user one [10:36] so it'll not change the system banner [10:36] thekorn: not really, IIRC 3 is user error and 4 is internal error, does 104 correspond to 4? [10:36] seb128_ : alright, that's why the xorg.conf has still the same value ? [10:37] yes [10:37] ok [10:37] and it still works in e17, that's great [10:37] so i should remember to change my settings in gnome instead from e17 (though it worked well for the printer) [10:37] alright [10:37] thanks ! [10:43] well, there are no e17 ubuntu packages ... [10:44] who knows what quality the ones are you use [10:46] i installed e17 from the repos [10:46] it's not e17 anymore sorry, it's enlightenment [10:50] well when i change the xorg.conf value, it fixes the login screen bug [10:50] as i wanted to use latin9 instead of oss keyboard layout, i guess it's no problem to change this xorg.conf value [10:53] nico_: right, it's no issue [10:53] nico_: the GNOME tool is there to configure a specific layout for your user [10:53] thx :) [10:54] if i chose the right value at install, then xorg.conf would also have it ? [10:55] nico_: why don't you use dpkg-reconfigure xserver-xorg ? [10:55] oh yeah, that's an idea :o) [10:56] nico_: are on 8.04 ? [10:56] are your* [10:56] yes [10:56] you* [10:56] ok [10:56] the new xorg only configure mouse and keyboard with dpkg-reconfigure [10:57] so, no probleme with display :) [10:57] yep :o) [10:58] and its not a bug ^^ [10:59] well i did that and it just changed the XkbVariant value as i wanted to [11:00] looks really like editing the xorg.conf [11:11] @narcan [11:11] i have to register before writing private msgs [11:12] and it doesn't work [11:16] james_w, oh, sorry 104 is related to 5-a-day, I found 'bzr' error codes around 768 some time ago [11:17] thekorn: hi. is there some translation between what you see from $? and the return code seen in python? Or are they the same? [11:19] 5-a-day is running bzr as a subprocess, so I think they should be the same [11:22] thekorn: I'm not sure then, sorry. [11:23] np === nico_ is now known as nico_h === nico_h is now known as nico_h_ === nico_h_ is now known as nico_h [11:55] bug 1 [11:55] Launchpad bug 1 in ubuntu "Microsoft has a majority market share" [Critical,Confirmed] https://launchpad.net/bugs/1 [11:55] persia: ^ [11:55] jussio1: Thanks :) [11:56] :) === _Czessi is now known as Czessi === seb128_ is now known as seb128 [12:56] hi [12:56] who use gedit ? [12:56] have you got gedit who open on all desktop ? [13:08] Hi, over there! My ubuntu-alternate install seems to hang reproducibly when trying to set up a crypted partition... [13:10] Anybody know of similar problems (I was unable to find a similar bug in the launchpad database)? [13:11] erisdiskordia: you're not installing in kvm are you? [13:11] in what? I'm trying to install inside a virtualbox on mac os [13:12] that's ok, the only bug I have heard about like this was specific to kvm, which is similar to virtualbox [13:13] erisdiskordia, are you sure it hangs ? when i did my test install of it it took quite a while to zero out the partition before formatting [13:13] it seems slightly unresponsive doing that [13:13] s/doing/while doing/ [13:14] no after that's finished it tries to start the partition manager and hangs at 47% for ever(?) [13:14] i let it run ca. 4 hours - no result [13:15] cpu usage was zero all the time [13:15] get /var/log/syslog from that instal and file a bug [13:15] how should I do this? It hanged, after all... [13:15] (with the syslog attached indeed) [13:16] you cant switch to tty2 ? [13:16] no [13:17] but I have the whole machine state (hdd, mem, cpu) as files [13:17] if you can tell me where I have to look I can fatch it perhaps [13:17] fetch [13:20] all state+hdd files together are about 150M, I shouldn't attach the whole thing... [13:22] well, the only intresting thing is the syslog file [13:22] which very likely holds the error message [13:22] what you can do is start over and switch to tty4 while the system still responds [13:23] the log is running there so you can propbably see the message while the error happens [13:30] * iulian looks around [13:30] Where is ubotu? [13:31] it's on holiday [13:31] bug #1 [13:31] we have ubottu helping us out at the moment. [13:31] Ohh, I see his brother here. [13:31] iulian: Error: Could not parse data returned by Launchpad: The read operation timed out [13:32] bug #1 [13:32] Hmm, broken? [13:32] james_w: Error: Could not parse data returned by Launchpad: The read operation timed out [13:32] LP is slow [13:32] it was working earlier [13:32] matter of luck i guess [13:32] it even takes ages to open a bug page atm [13:33] Indeed [13:42] I am using Ubuntu 8.04 64-bit version, if i install any 32-bit applications like browsers, datbase clients ...etc. The 32-bit based applications not able to reach /etc/resolv.conf file to communicate to the network. Any one tell me how to resolve this issue ? [13:47] Against which package should you report your bug when there are fewer resolutions detected than your monitor can handle [13:47] The monitor I'm currently using can handle greater than 1024x768 [13:48] but that is the resolution that's used now [13:49] ah, it's already reported [13:54] (ogra, james_w:) switching the console seemed not to work; i'll retry ;; the memory dump contains interesting stuff, tho: 'Cool computer, but...' or 'OMFG!!' ... lol! [14:01] can someone help me with some advice on Bug #155061? [14:01] Launchpad bug 155061 in slocate "slocate typo: "serach_db"" [Low,In progress] https://launchpad.net/bugs/155061 [14:02] it's a simple to fix bug, but I'm not sure what I need to do to test it. The typo is in a test case for if something goes wrong. [14:02] james_42: hi. What would you like to know? [14:02] what do you mean by test it? [14:03] test that my change to the code is working. [14:03] if it's just a typo, in an error message do I really need to test it? [14:03] I think that would be pretty hard to test, I'd just assume that it works. [14:05] ya, that's what I was thinking too [14:05] so you have prepared a patch? [14:05] I've looked at the diff file that I've created, and it shows the spelling correction [14:05] nearly finished everything I think [14:06] great [14:06] it's a bitesized bug, but it's my first :-) [14:09] if the software program doesn't use a patching system, I just upload the diff file to comments for the bug right? === LucidFox_ is now known as LucidFox [14:16] james_42: that would be a start [14:41] is ubotu having a bad day or something? Its not doing anything on -announce... [14:41] Kirrus: yup, it's on holiday [14:41] Kirrus: ubotu has gone [14:41] Kirrus: We're having issues with bots currently due to a bit of a situation [14:42] 'a bit of a suituation' sounds ominous... oh well, I guess back to the old-fassioned way of finding things to triage... thanks :) [14:43] It is :/ [14:44] ubottu has slightly different syntax. [14:44] persia: Error: "has" is not a valid command. [14:44] bug 6 [14:44] Launchpad bug 6 in rosetta ""next 10 entries" at bottom of page" [Medium,Invalid] https://launchpad.net/bugs/6 [14:44] bug #6 [14:45] Err. bug #1 [14:45] Launchpad bug 1 in ubuntu "Microsoft has a majority market share" [Critical,Confirmed] https://launchpad.net/bugs/1 [14:45] Err. Nevermind. I thought it did. No idea why it didn't respond before. === LucidFox_ is now known as LucidFox === neversfelde|mobi is now known as kubuntu-deIRC === kubuntu-deIRC is now known as never|mobi === never|mobi is now known as neversfelde|mobi [16:54] is bug 219613 on the right package, or should it be gdm? [16:54] Launchpad bug 219613 in language-support-translations-ru "GDM timed login displays "Linux" instead of the user name for russian language" [Undecided,New] https://launchpad.net/bugs/219613 [17:01] james_w: translations issues are usually assigned to language-pack-gnome-locale [17:02] james_w: so translators know about those, they can fix on rosetta and often they are in contact with upstream teams too === x-spec-t is now known as Spec === x-spec-t is now known as Spec [17:37] question about headsett and sound! My headsett works perfekt in windows so its noting wrong with it BUT in 7.10 and hardy i cant use the microphone on the headsett but the mic on the screen actually works! I wonder i anyone know what to do ?? === x-spec-t is now known as Spec === never|mobi is now known as neversfelde|mobi === x-spec-t is now known as Spec === x-spec-t is now known as Spec [18:37] Boo [18:40] hi [18:42]