[01:51] good morning [02:44] can some one tell me what their file says /sys/devices/system/cpu/cpu0/cpufreq/related_cpus ? [02:46] Phruis: sysop@x1804mini:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/related_cpus >> 0 1 . [02:46] Phruis: I don't think any answer is going to help you. You might try rephrasing the question. [02:47] Bashing-om: thanks [02:48] For some reason my cpu is only listing itself [02:48] if you have 32 cores it should have that [02:48] yes? [02:49] each core only has itself listed as related_cpus [02:50] perhaps this is the difference between cores and threads [02:51] even then it should have 16 right? [02:51] you haven't shared which processor you have [02:51] threadripper 1950x [02:52] right, so 16 core, 32 thread... you'd see them all under /proc/cpuinfo [02:52] you should probably spend more time using it than worrying what values some paths report [02:53] im trying to fix a bug in some kernel software that relies on that file [02:54] would be nice if it was accurate but if we are using another file to get this information i will use that [02:56] riiiiight [03:00] i found an old unrelated bug https://bugzilla.kernel.org/show_bug.cgi?id=58761 [03:00] bugzilla.kernel.org bug 58761 in cpufreq "related_cpus truncated with acpi-cpufreq driver on kernel 3.9.3" [Normal,Closed: code_fix] [03:00] this happens often? [03:03] unless i dont have something setup properly [05:58] Good morning [06:47] good morning === tds3 is now known as tds [12:34] Lynoure: there are several things that speedup the solving of bugs actually [12:34] Hello, are there any public statistics somewhere on how quickly a bug report gets it's first response? [12:34] Lynoure: and you as member of the ubuntu community can also help influence this [12:34] lotuspsychje: I don't mean solving, that can take time [12:34] Just the first response [12:35] I cannot triage nor confirm my own bugs. Sometimes I have gone out of my way to have someone else verify them, only to still get no dev response for a year [12:35] Lynoure: wich bug are we talking about exactly? [12:36] I am hoping this has changed... that's why I am asking about if there are stats [12:36] like i say, we have a little pre-bug team in the announce channel these days [12:36] that help the devs filtering bugs as much as possible [12:36] lotuspsychje: that all was 5+ years ago. Like I wrote elsewhere, I have a brand new laptop, and consider coming back to ubuntu... but I know that would still drive me nuts [12:38] Lynoure: there are bugs on every Os, there's no magic red button for certain bugs neither, some special cases can still indeed haunt you across several ubuntu releases [12:39] but as i said, it also depends a lot on several influences [12:40] Can you tell me some of them? Back then it felt like no one even read them, which made me want to cry over all the time I spent on the reporting & steps to replicate [12:42] Lynoure: to confirm your bug more easy, find more users affected in the community [12:42] Lynoure: to keep your bug alive, keep testing things yourself inside your bugs comments [12:43] I know, I would sometimes do it, still get no response for months. But back then things might have been very different. That's why I am asking if there is some detailed stats on this? [12:44] Lynoure: i dont think we can generalize stats from bugs, dont you think every case is unique? [12:45] Yes, and so is every human, yet they make stats of people too :) [12:47] Lynoure: the best you can do, is share your bug ID and give it some love [12:47] I take that to mean "such stats don't exist" and move on. Thank you for your time. [12:47] thats not what i meant no [12:49] Oh? [12:51] Lynoure: https://wiki.ubuntu.com/Bugs/Stats [12:51] Lynoure: ill be pretty curious what you will conclude, let me know ok [12:59] lotuspsychje: haven't found it yet. Basically it's first response time (from devs/staff, not the main community) for confirmed and unconfirmed bugs that interests me. [13:00] I guess it could be the time it takes from the bug on average or median to move from New to Assigned or Confirmed to Assigned [13:01] Lynoure: bugs confirmed als has several influences [13:01] Lynoure: like it gets auto confirmed when the second user affects the bug [13:01] Yes, that's why median is probably the most informative number [13:03] Lynoure: there's also auto confirming bots out there [13:03] i know the kernel team uses those [13:07] I understand Ubuntu has so many users and probably so many bug reports that are not valid... I don't think I have it in me not to spend a day trying to figure out the problem before filing a bug, so that means I need to file it somewhere where that pays off. [13:09] Lynoure: if a bug is valid, file it, why spend time on your own while the community could also help? [13:11] I think it's called due diligence =) [13:13] When I was young, I was told it is important to report a bug well and that means to me ruling out a lot of other things that could affect the situation. How would one really know otherwise it's a valide bug? [13:16] Anyway, thanks for the efforts, pity those stats couldn't be found. Stay healthy, all [19:07] !!!!!!!!!!! [19:07] Hello! [19:07] the demon is here! [19:09] time to watch the Exorcist one more time [19:16] somebody call constantine [19:16] has someone tried Virtual Box 6.1.6? [19:17] it says that a program had an issue and asks to send a report [19:17] in 18.04 [19:21] from PPA? [19:21] marcoagpinto, what kernel version? Was the kernel or Vbox updated since reboot? [19:21] yeah no doubt the classic module fail [19:22] daftykins: I simple leave the desktop on for some time and it opens a window saying a problem had a problem and asks if I want to send a report [19:22] :) [19:22] simply* [19:23] I updated VirtualBox today or yesterday, I can't remember [19:23] a problem=a program* [19:23] marcoagpinto, make sure to use the virtualbox-dkms package, it breaks less [19:23] Though takes longer to update [19:24] I went to a nap while I was downloading some videos and when I returned to the computer, it seems something happened... the key "U" got like jammed [19:24] it was UUUUUUUUUUU writing all over [19:25] it was very hard to close all applications and reboot Windows 10 [19:25] spilled cola in it again? [19:25] ;) [19:25] no, it was strange [19:25] :) [19:25] it happened in Ubuntu, but then all over Windows [19:25] :) [19:26] something happenefd [19:26] :) [19:26] hardware level issue then by the sounds [19:26] what?! why?! when?1 [19:27] my brand new Lenovo [19:27] :) [19:29] daftykins: what do you mean with hardware issue? [19:29] :) [19:30] marcoagpinto, If it's just one key, it's probably fixable. Ask ##hardware? [19:31] i do not recommend that channel at all [19:31] lordcirth: everytime I clicked in a text gadget it would get all Us [19:31] UUUUUUUUUUUUUUUUUU [19:31] endless UUUUUs [19:31] daftykins, why not? [19:31] then, after I managed to reboot Windows, it worked well [19:32] they're a bunch of elitists who spread disinformation [19:32] Example of disinformation? [19:32] are you serious? [19:32] ohhhhhhhhhh.... I am an elitist too :((((((((((( [19:32] Buaaaaaaaaaaaaaaaaaaa [19:33] they give bad advice, simple as that [19:34] Nietzche superman [19:34] :) [19:36] daftykins, I was hoping for an example? [19:46] i don't log so i can't help you there [19:58] "I ain't no fortunate son" [19:58] :p [19:59] ahhhh.... daftykins... I have just reduced the bright of the screen [19:59] :) [20:00] for a week that I have terrible headaches... maybe 16 hours at the computer per day [20:05] UWN: issue627 Hot of the terminals: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue627 :D [20:06] what? [20:20] :-) [20:20] oerheks: Dear beloved brother! [20:20] >:) [20:20] amen [20:21] merry meet [20:22] I have reviewed 3 chapters of my thesis!!!!!! [20:22] <:) [20:22] >:) [20:22] hundreds of pages! [20:22] but my Unity course is going very slowly :( [20:23] I can only watch 30 minutes of videos per day [20:23] it will take me over a month to see them all [20:23] and for two or three days that I haven't watched any videos of the course