[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev
Affects me too. We are having to (re-)package our own version of nodejs-dev with depend on libssl-dev instead of libssl1.0-dev in order to use nodejs without uninstalling hundreds of other debian package on an 18.04 system. Surprised this is still open over a year after reporting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794589 Title: libssl1.0-dev conflicts libssl-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1794589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
Folks, this bugzilla entry, with the amount of different issues reported and the amount of FUD all collected in one place, is prohibitively hard for a debugger to handle. So, I'd suggest if you still would like your issue looked at, to open a separate bug. And please refrain from commenting on a bug with your own issue - it is much easier to open a separate one first and then when it turns out that it is a known issue, to merge the two bugzilla entries than to keep them apart in a single report. Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
> Sep 10 21:13:56 BelliashPC kernel: Workqueue: 0x0 (events) > Sep 10 21:13:56 BelliashPC kernel: RIP: 0010:worker_thread+0xfc/0x3b0 > Sep 10 21:13:56 BelliashPC kernel: Code: 0f 84 8e 02 00 00 48 8b 4c 24 18 49 > 39 4f 38 0f 85 a9 02 00 00 83 e0 fb 41 89 47 60 ff 4a 34 49 8b 17 49 8b 47 > 08 48 89 42 08 <48> 89 10 4d 89 3f 4d 89 7f 08 48 8b 45 20 4c 8d 6d 20 49 39 > c5 74 > Sep 10 21:13:56 BelliashPC kernel: RSP: 0018:aec608acfec0 EFLAGS: > 00010002 > Sep 10 21:13:56 BelliashPC kernel: RAX: 000d RBX: > 8d78aecdfa80 RCX: 8d789fa1b400 > Sep 10 21:13:56 BelliashPC kernel: RDX: 8d78a4112780 RSI: > 8d78a91e56c0 RDI: 8d78aecdfa80 > Sep 10 21:13:56 BelliashPC kernel: RBP: 8d78aecdfa80 R08: > 8d78aece0180 R09: 1800 > Sep 10 21:13:56 BelliashPC kernel: R10: R11: > R12: 8d78a4112b68 > Sep 10 21:13:56 BelliashPC kernel: R13: 8d78aecdfaa0 R14: > 8d78a4112b40 R15: 8d78a4112b40 > Sep 10 21:13:56 BelliashPC kernel: FS: () > GS:8d78aecc() knlGS: > Sep 10 21:13:56 BelliashPC kernel: CS: 0010 DS: ES: CR0: > 80050033 > Sep 10 21:13:56 BelliashPC kernel: CR2: 00b0 CR3: > 00069063a000 CR4: 00340ee0 > Sep 10 21:13:56 BelliashPC kernel: Call Trace: > Sep 10 21:13:56 BelliashPC kernel: kthread+0xf8/0x130 > Sep 10 21:13:56 BelliashPC kernel: ? set_worker_desc+0xb0/0xb0 > Sep 10 21:13:56 BelliashPC kernel: ? kthread_park+0x80/0x80 > Sep 10 21:13:56 BelliashPC kernel: ret_from_fork+0x22/0x40 > Sep 10 21:13:56 BelliashPC kernel: Modules linked in: nvidia_drm(PO) > nvidia_modeset(PO) nvidia(PO) vboxpci(O) vboxnetadp(O) vboxnetflt(O) > vboxdrv(O) You have proprietary crap loaded. Try reproducing it with the latest upstream kernel and *without* that nvidia* and vbox* gunk. If you can, please open a separate bug and add me to CC. Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Philip Rosvall from comment #593) > Since 5.0.10, and this commit ...: > > (https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.0.10) > "commit 205c53cbe553c9e5a9fe93f63e398da7e59124b6 > Author: Thomas Gleixner > Date: Sun Apr 14 19:51:06 2019 +0200 > > x86/speculation: Prevent deadlock on ssb_state::lock If that commit really fixes the "issue" on your machine then you shouldn't have been experiencing any softlockups etc, i.e., what this bugzilla is about, but rather a software deadlock. Which would mean that your machine is not necessarily affected by the entering into a C-state with MWAIT and not waking up after, issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to JerryD from comment #578) > $ sudo rdmsr -a 0xc0011020 > 68000 > > This is on: > > cpu family: 23 > model : 17 > model name: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx > stepping : 0 > microcode : 0x8101007 You're showing me the MSR output for erratum 1033 but your CPU is not affected. > Has your patch been applied to kernel yet? No it hasn't - I'm still waiting for someone to test it and confirm that it fixes the issue on their boxes. And by issue I don't mean erratum 1033 - that is a red herring anyway - but the lockups people are reporting on some broken BIOSes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Lars Viklund from comment #570) > rdmsr yields 68010, which has bit 4 set. Looks like your BIOS applies the fix. Now, does the patch in comment #526 fix your freezes? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Dennis Schridde from comment #573) > 2068100 If this is correct: http://www.cpu-world.com/CPUs/Zen/AMD-Ryzen%205%202400G.html then you should have in /proc/cpuninfo something like this: cpu family: 23 model: 17 stepping: 0 and if so, not affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
There's a patch in comment #526 for people to test before we include it so that there's at least *some* fix in the kernel, going forward... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to alfie from comment #566) > But I really want C6/P6 and ignoring the BIOS seems to get me there... Why do you think the patch I pointed to won't give you C6? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Tolga Cakir from comment #568) > @Borislav has the fix for erratum 1033 "A Lock Operation May Cause the > System to Hang" been applied so far? The suggested workaround was "Program > MSRC001_1020[4] to 1b", but I couldn't find anything about it in master > branch. According to the document, 1033 only affects B1. Such a "fix" does not exist. Possibly because it is unlikely this is causing it and BIOS might be applying the fix already. People with B1s (model 1, stepping 1) could test though by doing as root: # modprobe msr # rdmsr -a 0xc0011020 and looking at bit 4 in the result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Klaus Mueller from comment #530) > Hmm, if rev. 1 doesn't support MWAIT - why can it be a problem anyway > at the same time which must be fixed by disabling the usage of MWAIT? > I seem to miss something? That's a good question but, frankly, I don't have a very exact answer to it right now. In order to understand what's *really* going on in the cstate detection code one would need to instrument at least acpi_processor_get_power_info_cst() and acpi_processor_ffh_cstate_probe() to figure out what exactly does the kernel parse from those CST objects and what it uses to try to enter idle. And do all that instrumentation on an affected system. My current suspicion is is that it tries to enter idle with misconfigured states and under certain conditions, it misses the wakeup, leading to the stall. This is all a conjecture anyway. Now my patch simply falls back to the good old idle entry on AMD where we simply do HLT and we won't even attempt to enter idle the ACPI way. Makes sense? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
Ok, here's a test patch ontop of 4.20-stable. It should practically make idle=halt the default on revisions before B2. You check which revision you have by doing $ grep stepping /proc/cpuinfo The number must be < 2. For the folks with B2 machines we need to keep debugging. Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Klaus Mueller from comment #528)
> What's the downside of generally disabling mwait?
So in your case, you can't do MWAIT to enter C1 anyway because your
revision doesn't support it. This is why you're seeing those firmware
messages.
> I'm using a Ryzen 7 1700X and don't have any problem ("fixed" it w/
> 200 MHz of CPU Overclocking). The only thing I see, is, that the ACPI
> firmware bug messages disappear. That's all.
That's an "interesting" way to fix it but if it works ... :)
The intention of the fix is to make idle=halt the default for obvious
reasons.
HTH.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
Created attachment 280961 Don't do mwait on B1 and earlier -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Philip Rosvall from comment #522) > I have only used the workaround since kernel 4.20.4, so I just booted the > kernel now without and with the parameter. As can be seen in line 704 in the > log without "idle=halt", we see the error "[Firmware Bug]: ACPI MWAIT > C-state 0x0 not supported by HW (0x0)". This error does not occur when > "idle=halt" is set. Yeah, this is starting to look more and more like a BIOS issue on certain mobos. Since your machine is issuing that ACPI MWAIT error, can you apply the debugging patch from comment #512, build a kernel, boot into it without "idle=halt" and upload dmesg again? Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Philip Rosvall from comment #518) > I can confirm that "idle=halt" makes both my Ryzen desktop and Ryzen > notebook more stable than anything else I've tried. I have not experienced > freezes for some days now. Can you upload dmesg from the working and non-working kernels pls? Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
Created attachment 280825 acpi-dump-cstates.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to T X from comment #509) > I haven't built a kernel in about decade, but if you provide step-by-step > instructions for how to do so, I'll attempt to build the patched kernel and > then post the dmesg. Ok, here we go: 1. Clone stable kernel from here if you haven't done so yet: $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git 2. checkout 4.20 branch $ git checkout -b 4.20-stable origin/linux-4.20.y 3. apply the attached patch $ patch -p1 -i acpi-dump-cstates.diff 4. copy your 4.20 config $ cp /boot/config-4.20 .config 5. do $ make oldconfig 6. build $ make -j16 7. install kernel, needs root # make modules_install install # reboot Then, select this new kernel in grub, boot it and upload full dmesg. Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to T X from comment #502) > Jan 25 09:38:33 kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored > Jan 25 09:38:33 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported > by HW (0x0) Yah, even with the new BIOS that's still there. Doesn't look like it has been fixed. If I send you a debugging patch, would you be able to apply it, build a kernel, boot into it and get me dmesg from the box? Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
Can people confirm that idle=halt fixes the issue, like Aaron says in comment #506? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Maxim Bakulin from comment #503) > I tried and it didn't help. After freezes started happening at Xubuntu > 18.04LTS with stock 4.15, I compiled latest 4.20.3 kernel and added > CONFIG_RCU_NOCB_CPU=y, as it was suggested here, but freezes didn't stop. > There's my dmesg at comment 492 with latest kernel. Lemme get this straight: opensuse 4.20.0 kernel doesn't freeze the box but 4.20.3 stable kernel does?! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Maxim Bakulin from comment #500) > I found out that openSUSE Tumbleweed with stock 4.20.0 kernel doesn't appear > to freeze. I tried copying suse's kernel and /lib/modules to Xubuntu > 18.04LTS, but it didn't seem to help, xubuntu still freezes. Maybe, > xubuntu's firmware packages are old? But I could've done something wrong > with the transplant procedure :) Yeah, I wouldn't do that. What's stopping you from building a kernel on your machine and installing it? The web is full of tutorials like this one: https://www.linux.com/learn/how-build-latest-linux-kernel-debian-linus- git-repo for example, which is for debian-based systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to T X from comment #498) > Jan 24 17:59:39 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported > by HW (0x0) So this looks like a broken BIOS. > Jan 24 17:21:00 kernel: Hardware name: To Be Filled By O.E.M. To Be > Filled By O.E.M./AB350 Gaming-ITX/ac, BIOS P4.60 04/19/2018 Looking at Asrock's website, there's newer BIOS for your board, AFAICT, so can you update it and rerun the same test? Or what you were doing to cause the splat. Also, please upload full dmesg after you've updated the BIOS. Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
Folks, just a quick thing: please check whether you have the latest BIOS and if not, do upgrade it and check if it makes any difference. Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Trevor Cordes from comment #485) > Also, we were able to get a stack trace / panic output that was on > the frozen screen in a phone capture jpg. If anyone wants that, I can > attach it. Please do. > We did the "idle: typical" bios tweak What is that? > and the idle=nomwait tweak and the system has been 100% stable for the > 2 days since. Ok, it would be good to test those settings separately: 1. once with the "idle: typical" BIOS thing 2. idle=nomwait and say which fixes the issue for ya. Or both? Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Trevor Cordes from comment #488) > Sorry the pic is so horrible in attachment 280661 [details], but at least > you can see most of the stack traces. I have a wider pic of it I can use to > transcribe the missing right-hand-side bits if needed. Thanks, that's good enough. Btw, is there any particular reason why you're running a 32-bit kernel? If not, I'd consider switching to a 64-bit kernel which is a lot more and widely tested. > By "idle: typical" bios tweak I meant the < idle">> tweak everyone else has done. I need to figure out what's behind that setting. What kind of BIOS do you have? dmesg | grep DMI: should have it. > As for which fix (1 or 2) really fixed it, I'll get back to you in about a > month because this box is now in production and we can't afford downtime > until our next scheduled period. I have a feeling just the bios tweak is > required (from all I've read in dozens of forums), but I did both for good > measure. Ok, whenever you can. Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Aaron Muir Hamilton from comment #480) > So my box was mostly idle for the last day or so, and had locked up while > the monitor was asleep, so I had to reset it. Let me make sure I understand it correctly: you had "idle=nomwait" on the kernel command line and it became unresponsive? If so, it would be really helpful if you could connect that box over serial to another one and collect logs in realtime with the hope of maybe catching something relevant. The other thing I could suggest is to disable SMT: I know of another threadripper machine where disabling SMT helped with the lockups. (Not saying this is the final solution but it would be a good data point to know). Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Aaron Muir Hamilton from comment #483) > That is maybe an option, for now I disabled C6 from my board firmware (in > ASRock's case, by selecting "Typical current idle" [sometimes called "Common > current idle" I think, on some Ryzen boards] in Advanced > AMD CBS > Zen > Common Options > Power Supply Idle Control); and I'll see if that does the > trick. Yes, that's also worth a try. Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Aaron Muir Hamilton from comment #476) > For the time being, I've now added idle=nomwait to my kernel params, as it > seems at least one of these issues is related to MWAIT (according to AMD's > errata). Ok, that's good. Please give your box hell to check whether that really is fixing the issue. Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
(In reply to Aaron Muir Hamilton from comment #474) > I just experienced this issue with a Threadripper 2950X on kernel 4.20.3 Anything in dmesg? Please upload full dmesg, /proc/cpuinfo and kernel .config. Anything particular you did to reproduce it? Any correlation between what the box does and occurrence of the lockup? Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
Sorry but this bugzilla entry is humongous with 110 people on CC and all reporting some different aspects of what they're seeing and what they're trying and and... In order to debug this properly, I'd like for someone to test the latest upstream kernel 4.20 and try to reproduce the issue there. Then to explain how exactly one has reproduced it. Once that happens we'll take it from there with further questions. Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646914] Re: Ubuntu 16.04 package version contains improper API
Fix works. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646914 Title: Ubuntu 16.04 package version contains improper API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaml-cpp/+bug/1646914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788181] [NEW] cantor does not detect the maxima backend
Public bug reported: Installing cantor-backend-maxima is a no-op. Maxima is not a session you can start and, unlike Sage, Maxima does not appear in the Cantor configuration screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cantor-backend-maxima 4:17.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-31.33-generic 4.15.18 Uname: Linux 4.15.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 21 15:44:47 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (371 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: cantor UpgradeStatus: Upgraded to bionic on 2018-03-18 (155 days ago) ** Affects: cantor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788181 Title: cantor does not detect the maxima backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cantor/+bug/1788181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646914] Re: Ubuntu 16.04 package version contains improper API
It would be great if the Ubuntu maintainers could allows the 16.10 packages for libyaml-cpp to get pushed out with 16.04. These libraries are unusable in 16.04 but work fine to installed the 16.10 versions. The issues are that CI builds using Docker images require extra steps to get these packages in them that keep all my CI stuff forked from my community that doesn't necessarily care about libyaml-cpp. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646914 Title: Ubuntu 16.04 package version contains improper API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaml-cpp/+bug/1646914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal
I would like to ask you to reconsider the decision to make ubuntu- minimal depend on ubuntu-advantage-tools. You can skip this paragraph if you're in a hurry. First, thank you for holding this discussion in the open. I totally understand the marketing reasons for this: I depend on Canonical's distribution, and want Canonical to offer their paying customers a fantastic out-of-the-box experience so that they can continue to offer their services to the general public, too. That said, the ubuntu-advantage-tools package is not in fact strictly necessary to allow the machine to boot, detect hardware, connect to a network, install packages or perform basic diagnostics. With ubuntu- minimal 1.400, this is now essentially a mandatory piece of software that will, at best, emit an error message. Would changing the relationship from Depends to Recommends meet your requirements (automatic setup on every Ubuntu machine) while allowing manual removal of the package? Actually, one could argue that the ubuntu-minimal package on non-LTS releses should Conflict, not Depend, on ubuntu-advantage-tools. This ought to cause for the automatic removal of the package when dist- upgrading to a non-LTS release. That would give the package scripts a chance to warn the system administrator that they are about to give up on the benefits of their paid subscription. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686183 Title: Ship ubuntu-advantage in ubuntu-minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal
> With ubuntu-minimal version 1.400 on artful, this is now essentially a mandatory piece of software that will, at best, emit an error message. I accidentally missed a couple of critical words from that sentence. Apologies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686183 Title: Ship ubuntu-advantage in ubuntu-minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714908] Re: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 00007f54021c9836 sp 00007fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000]
Workaround: apt install xubuntu-desktop (choose lightdm over gdm) ** Description changed: Attempting to use multiple monitors from the graphical interface results in nothing happening: (gnome-control-center:8910): display-cc-panel-WARNING **: Error applying configuration: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig Attempting to set up the same from xrandr causes segmentation faults in libmutter: $ sudo dmesg --console-on $ xrandr --output eDP-1 --off --output DP-1-2 --mode 1920x1080 --rotate left --pos 2160x0 --output DP-1-1 --pos 0x0 --mode 1920x1080 --rotate left --output DP-1-3 --pos 1080x0 --mode 1920x1080 --rotate left --verbose --scale 1x1 screen 0: 3240x1920 858x508 mm 95.92dpi crtc 0:1920x1080 60.00 +1080+0 "DP-1-3" crtc 1:1920x1080 60.00 +2160+0 "DP-1-2" crtc 2:1920x1080 60.00 +0+0 "DP-1-1" - sraffa@sraffa-Latitude-E7270:~⟫ [Sep 4 11:07] gnome-shell[3603]: segfault at 8 ip 7f79e651bda0 sp 7ffd48c3d1b8 error 4 in libmutter-1.so.0.0.0[7f79e64c2000+13f000] + [Sep 4 11:07] gnome-shell[3603]: segfault at 8 ip 7f79e651bda0 sp 7ffd48c3d1b8 error 4 in libmutter-1.so.0.0.0[7f79e64c2000+13f000] It should be noted that all monitors are working as expected during boot (e.g. while typing my HDD unlock password) + + Regrettably the segfault information changes every time and apport + doesn't seem able to capture reports for it. + + xfce sessions from lightdm start regularly and can use external monitors + regularly. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libmutter-1-0 3.25.91+20170902~ce515c5-1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 11:02:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714908 Title: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 7f54021c9836 sp 7fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714908] Re: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 00007f54021c9836 sp 00007fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000]
Of course, the Ubuntu repos removed the previous version of the relevant packages so I can't roll back the package upgrade to see if that helps anything. ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+attachment/4944025/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714908 Title: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 7f54021c9836 sp 7fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714908] Re: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 00007f54021c9836 sp 00007fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000]
Re-attaching redacted journal messages. My username wasn't fully scrubbed out. ** Attachment added: "JournalMessages.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+attachment/4944030/+files/JournalMessages.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714908 Title: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 7f54021c9836 sp 7fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714908] [NEW] Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 00007f54021c9836 sp 00007fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000]
Public bug reported: Attempting to use multiple monitors from the graphical interface results in nothing happening: (gnome-control-center:8910): display-cc-panel-WARNING **: Error applying configuration: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig Attempting to set up the same from xrandr causes segmentation faults in libmutter: $ sudo dmesg --console-on $ xrandr --output eDP-1 --off --output DP-1-2 --mode 1920x1080 --rotate left --pos 2160x0 --output DP-1-1 --pos 0x0 --mode 1920x1080 --rotate left --output DP-1-3 --pos 1080x0 --mode 1920x1080 --rotate left --verbose --scale 1x1 screen 0: 3240x1920 858x508 mm 95.92dpi crtc 0:1920x1080 60.00 +1080+0 "DP-1-3" crtc 1:1920x1080 60.00 +2160+0 "DP-1-2" crtc 2:1920x1080 60.00 +0+0 "DP-1-1" sraffa@sraffa-Latitude-E7270:~⟫ [Sep 4 11:07] gnome-shell[3603]: segfault at 8 ip 7f79e651bda0 sp 7ffd48c3d1b8 error 4 in libmutter-1.so.0.0.0[7f79e64c2000+13f000] It should be noted that all monitors are working as expected during boot (e.g. while typing my HDD unlock password) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libmutter-1-0 3.25.91+20170902~ce515c5-1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 11:02:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Description changed: Attempting to use multiple monitors from the graphical interface results in nothing happening: (gnome-control-center:8910): display-cc-panel-WARNING **: Error applying configuration: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig Attempting to set up the same from xrandr causes segmentation faults in libmutter: $ sudo dmesg --console-on $ xrandr --output eDP-1 --off --output DP-1-2 --mode 1920x1080 --rotate left --pos 2160x0 --output DP-1-1 --pos 0x0 --mode 1920x1080 --rotate left --output DP-1-3 --pos 1080x0 --mode 1920x1080 --rotate left --verbose --scale 1x1 screen 0: 3240x1920 858x508 mm 95.92dpi crtc 0:1920x1080 60.00 +1080+0 "DP-1-3" crtc 1:1920x1080 60.00 +2160+0 "DP-1-2" crtc 2:1920x1080 60.00 +0+0 "DP-1-1" sraffa@sraffa-Latitude-E7270:~⟫ [Sep 4 11:07] gnome-shell[3603]: segfault at 8 ip 7f79e651bda0 sp 7ffd48c3d1b8 error 4 in libmutter-1.so.0.0.0[7f79e64c2000+13f000] + It should be noted that all monitors are working as expected during boot + (e.g. while typing my HDD unlock password) + ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libmutter-1-0 3.25.91+20170902~ce515c5-1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 11:02:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714908 Title: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 7f54021c9836 sp 7fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712548] Re: Gnome 3 lock screen does not respect org.gnome.desktop.lockdown disable-user-switching
** Description changed: - The "log in as other user" option on the lock screen has been known to - cause Gnome 3 to stop responding on my hardware. - - I am open to assuming that this is a problem with my hardware, but - disabling org.gnome.desktop.lockdown disable-user-switching should - remove this option from the lock screen. It does not. - - This means anyone in the physical vicinity of my laptop may cause loss - of work with a single click. This is almost a security vulnerability. + Disabling org.gnome.desktop.lockdown disable-user-switching should + remove the "log in as other option" link from the lock screen. It does + not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 13:35:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Disabling org.gnome.desktop.lockdown disable-user-switching should - remove the "log in as other option" link from the lock screen. It does + remove the "log in as other user" link from the lock screen. It does not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 13:35:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712548 Title: Gnome 3 lock screen does not respect org.gnome.desktop.lockdown disable-user-switching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1712548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712548] Re: Gnome 3 lock screen does not respect org.gnome.desktop.lockdown disable-user-switching
** Description changed: - The "log in as other user" option on the lock screen occasionally causes - Gnome 3 to stop responding. (The only time it hasn't was right after I - filed this bug, naturally.) + The "log in as other user" option on the lock screen has been known to + cause Gnome 3 to stop responding on my hardware. I am open to assuming that this is a problem with my hardware, but disabling org.gnome.desktop.lockdown disable-user-switching should remove this option from the lock screen. It does not. - This means anyone in the physical vicinity of my laptop can cause loss + This means anyone in the physical vicinity of my laptop may cause loss of work with a single click. This is almost a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 13:35:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712548 Title: Gnome 3 lock screen does not respect org.gnome.desktop.lockdown disable-user-switching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1712548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712548] [NEW] Gnome 3 lock screen does not respect org.gnome.desktop.lockdown disable-user-switching
Public bug reported: The "log in as other user" option on the lock screen has been known to cause Gnome 3 to stop responding on my hardware. I am open to assuming that this is a problem with my hardware, but disabling org.gnome.desktop.lockdown disable-user-switching should remove this option from the lock screen. It does not. This means anyone in the physical vicinity of my laptop may cause loss of work with a single click. This is almost a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 13:35:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Description changed: - The "log in as other user" option on the lock screen causes Gnome 3 to - stop responding. + The "log in as other user" option on the lock screen occasionally causes + Gnome 3 to stop responding. (The only time it hasn't was right after I + filed this bug, naturally.) I am open to assuming that this is a problem with my hardware, but disabling org.gnome.desktop.lockdown disable-user-switching should remove this option from the lock screen. It does not. This means anyone in the physical vicinity of my laptop can cause loss of work with a single click. This is almost a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 13:35:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712548 Title: Gnome 3 lock screen does not respect org.gnome.desktop.lockdown disable-user-switching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1712548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
> I just tried and my Dell XPS 13 9343 does not boot (hangs with a blank screen > right after kernel selection in grub) with generic variants from: > > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3 I can replicate this. Dell Latitude E7250. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687572] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
*** This bug is a duplicate of bug 1680904 *** https://bugs.launchpad.net/bugs/1680904 ** This bug is no longer a duplicate of bug 1677673 System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 ** This bug has been marked a duplicate of bug 1680904 zesty unable to handle kernel NULL pointer dereference -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687572 Title: BUG: unable to handle kernel NULL pointer dereference at 0018 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-edge/+bug/1687572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250
*** This bug is a duplicate of bug 1680904 *** https://bugs.launchpad.net/bugs/1680904 bleh, whatever gets this bug fixed. ** This bug has been marked a duplicate of bug 1680904 zesty unable to handle kernel NULL pointer dereference -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1646914] Re: Ubuntu 16.04 package version contains improper API
BtW this is fixed in 16.10 but the fixes were never ported to 16.04. My
company's fix in the meantime us just been to install the 16.10 deb files
using dpkg. Works great.
On Wed, May 17, 2017 at 5:30 PM Launchpad Bug Tracker <
1646...@bugs.launchpad.net> wrote:
> Status changed to 'Confirmed' because the bug affects multiple users.
>
> ** Changed in: yaml-cpp (Ubuntu)
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1646914
>
> Title:
> Ubuntu 16.04 package version contains improper API
>
> Status in yaml-cpp package in Ubuntu:
> Confirmed
>
> Bug description:
> A call to equals was broken by an API change, and one of the calls in
> the header was never updated.
>
> /usr/include/yaml-cpp/node/detail/impl.h:136:15: error: ‘equals’ was not
> declared in this scope
>if (equals(*it->first, key, pMemory)) {
>
>
> This is fixed in the 0.5.3 source.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/yaml-cpp/+bug/1646914/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646914
Title:
Ubuntu 16.04 package version contains improper API
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaml-cpp/+bug/1646914/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250
With that comment do you mean to say you're positive that 4.12 will have a fix, or do you mean to say you're positive that 4.11 will NOT have a fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250
My VERY shitty workaround has been to add the yakkety repositories back to my machine with apt edit-sources, then install and use the 4.8.x kernel from there. :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679927] [NEW] can't install ubuntu 16.04
Public bug reported: can't boot ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Wed Apr 5 12:04:30 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679927 Title: can't install ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1679927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250
** Summary changed: - System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl + System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl
Yes, the bug is indeed the same as that one. dd19674bacba227ae5d3ce680cbc5668198894dc doesn't seem like it's made it to the main kernel repository yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl
Unfortunately I was still able to reproduce. Here's the current trace, this time without arbitrary line cutoffs. While this report, too, has chrome as the "comm" I've also seen compiz being the "culprit." IP: gen8_ppgtt_alloc_page_directories.isra.40+0x115/0x250 [i915] PGD 0 Oops: 0002 [#1] SMP Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter rfcomm cmac bnep binfmt_misc cmdlinepart intel_spi_platform intel_spi spi_nor mtd dell_wmi sparse_keymap arc4 intel_rapl x86_pkg_temp_thermal dell_laptop intel_powerclamp coretemp iwlmvm dell_smm_hwmon kvm_intel kvm mac80211 irqbypass intel_cstate uvcvideo intel_rapl_perf videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 btrtl videobuf2_core btbcm btintel dell_led joydev videodev iwlwifi dell_smbios dcdbas media bluetooth snd_hda_codec_hdmi serio_raw snd_hda_codec_realtek snd_hda_codec_generic cfg80211 input_leds snd_soc_rt5640 snd_soc_rl6231 snd_hda_intel mei_me snd_soc_ssm4567 snd_hda_codec shpchp mei lpc_ich snd_hda_core snd_soc_core snd_hwdep snd_compress ac97_bus snd_pcm_dmaengine snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi int3403_thermal snd_seq snd_seq_device snd_timer elan_i2c snd acpi_als dw_dmac soundcore kfifo_buf dw_dmac_core industrialio snd_soc_sst_acpi i2c_designware_platform snd_soc_sst_match int3402_thermal 8250_dw i2c_designware_core spi_pxa2xx_platform mac_hid processor_thermal_device dell_rbtn int3400_thermal intel_soc_dts_iosf int340x_thermal_zone acpi_thermal_rel int3406_thermal acpi_pad parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt hid_generic usbhid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd i2c_algo_bit glue_helper drm_kms_helper cryptd ahci psmouse syscopyarea libahci sysfillrect sysimgblt fb_sys_fops sdhci_pci e1000e drm ptp pps_core wmi video sdhci_acpi sdhci i2c_hid hid CPU: 1 PID: 3403 Comm: chrome Not tainted 4.11.0-041100rc5-generic #201704022131 Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015 task: 969e1cf0 task.stack: be03435b8000 RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.40+0x115/0x250 [i915] RSP: 0018:be03435bb8c0 EFLAGS: 00010246 RAX: 969cf4346f80 RBX: 0003 RCX: 0003 RDX: RSI: 969e1b5f3000 RDI: 969e8ac8 RBP: be03435bb918 R08: R09: R10: R11: 0001 R12: 969c89f3c000 R13: 969d2a61e090 R14: fffef000 R15: 8000 FS: 7ff2cab90b00() GS:969e9e48() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0018 CR3: 00019c1c6000 CR4: 003406e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: gen8_alloc_va_range_3lvl+0xd1/0x920 [i915] ? __alloc_pages_nodemask+0xdf/0x240 ? alloc_pages_vma+0xab/0x250 ? add_hole+0xd8/0x100 [drm] gen8_alloc_va_range+0x25b/0x410 [i915] i915_vma_bind+0x81/0x170 [i915] __i915_vma_do_pin+0x30b/0x3b0 [i915] i915_gem_execbuffer_reserve_vma.isra.30+0x14d/0x1b0 [i915] i915_gem_execbuffer_reserve.isra.31+0x3a7/0x3d0 [i915] i915_gem_do_execbuffer.isra.37+0x4af/0x15b0 [i915] ? find_get_entry+0x20/0x100 ? shmem_getpage_gfp+0x104/0xc70 i915_gem_execbuffer2+0xa1/0x1e0 [i915] drm_ioctl+0x218/0x4b0 [drm] ? i915_gem_execbuffer+0x310/0x310 [i915] do_vfs_ioctl+0xa3/0x600 ? __secure_computing+0x3f/0xe0 ? syscall_trace_enter+0xcd/0x2e0 SyS_ioctl+0x79/0x90 do_syscall_64+0x5b/0xc0 entry_SYSCALL64_slow_path+0x25/0x25 RIP: 0033:0x7ff2c3f23907 RSP: 002b:7ffc4169eec8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 09f2220b3000 RCX: 7ff2c3f23907 RDX: 7ffc4169ef10 RSI: c0406469 RDI: 000e RBP: 7ffc4169ef10 R08: R09: R10: 0038 R11: 0246 R12: c0406469 R13: 000e R14: R15: Code: e6 48 8b 90 28 03 00 00 48 8b b8 e0 02 00 00 48 8b 52 08 48 83 ca 03 e8 9a d1 ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 08 0f 1f 44 00 00 e9 53 ff ff ff 65 8b 05 RIP: gen8_ppgtt_alloc_page_directories.isra.40+0x115/0x250 [i915] RSP: be03435bb8c0 CR2: 0018 ---[ end trace d5d6c6116f3943bc ]--- ** Tags added: bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags removed: bug-exists-upstream ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a memb
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl
** Attachment added: "WikiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+attachment/4850653/+files/WikiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677673] [NEW] System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl
Public bug reported: I just upgraded to 17.04. It appears that now leaving the system locked for long enough now makes it unable to respond to any input but SysRq. This apepars to be the only relevant bit in `journalctl --boot -1`: BUG: unable to handle kernel NULL pointer dereference at 0018 IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] PGD 0 Oops: 0002 [#1] SMP Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100 CPU: 3 PID: 3826 Comm: chrome Tainted: G OE 4.10.0-14-generic #16-Ubuntu Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015 task: 99ddb372da00 task.stack: b0ec037dc000 RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 0018:b0ec037df880 EFLAGS: 00010246 RAX: 99dd0367b880 RBX: 0003 RCX: 0003 RDX: RSI: 99ddb737e000 RDI: 99de4ad9 RBP: b0ec037df8d8 R08: R09: R10: R11: 0001 R12: 99ddc994a000 R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000 FS: 7fd3a0fa7b00() GS:99de5e58() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0018 CR3: 000174607000 CR4: 003406e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] ? __alloc_pages_nodemask+0xff/0x260 gen8_alloc_va_range+0x23d/0x470 [i915] i915_vma_bind+0x7e/0x170 [i915] __i915_vma_do_pin+0x2a5/0x450 [i915] i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915] i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915] i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915] ? radix_tree_lookup_slot+0x22/0x50 ? shmem_getpage_gfp+0xf9/0xc10 i915_gem_execbuffer2+0xa1/0x1e0 [i915] drm_ioctl+0x21b/0x4c0 [drm] ? i915_gem_execbuffer+0x310/0x310 [i915] ? __seccomp_filter+0x67/0x250 do_vfs_ioctl+0xa3/0x610 ? __secure_computing+0x3f/0xd0 ? syscall_trace_enter+0xcd/0x2e0 SyS_ioctl+0x79/0x90 do_syscall_64+0x5b/0xc0 entry_SYSCALL64_slow_path+0x25/0x25 RIP: 0033:0x7fd39a33a907 RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907 RDX: 76323860 RSI: c0406469 RDI: 000e RBP: 76323860 R08: R09: R10: 0038 R11: 0246 R12: c0406469 R13: 000e R14: R15: Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 08 0f 1f 44 00 RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: b0ec037df880 CR2: 0018 ---[ end trace 2a4103476767c23b ]--- I walked to my computer 12 minutes later, finding it soft-locked as described above. I realize that this appears somewhat far removed from the real cause of the problem, so please let me know what other data I can provide to facilitate the debugging process. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sraffa 2780 F pulseaudio /dev/snd/controlC0: sraffa 2780 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Mar 30 17:44:00 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640 InstallationDate: Installed on 2015-11-02 (514 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E7250 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-29 (0 days ago) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0V8RX3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl
** Attachment added: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+attachment/4850655/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl
Scrubbed PII from attachments. ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+attachment/4850652/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl
** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+attachment/4850654/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677344] Re: Managed extension is only removed on package purge
Chrome eventually realized that the extension was no longer mandated and proceeded to remove it from my browser. Annoyingly, this was a matter of time rather than browser restarts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677344 Title: Managed extension is only removed on package purge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrome-gnome-shell/+bug/1677344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677344] Re: Managed extension is only removed on package purge
I should point out that an apt-get purge was not sufficient to uninstall this extension or to make it uninstallable. The extension is still in my browser and marked as managed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677344 Title: Managed extension is only removed on package purge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrome-gnome-shell/+bug/1677344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677344] [NEW] Managed extension is only removed on package purge
Public bug reported: These files: /etc/chromium/policies/managed/chrome-gnome-shell.json /etc/opt/chrome/policies/managed/chrome-gnome-shell.json ...are not removed by apt-get remove. Only apt-get purge will remove these files. This is incorrect: as long as those files remain on the system, so does part of the software installed by the package: namely, the part that is forcefully installed through Chrome itself. See also: - http://askubuntu.com/questions/897486/cant-uninstall-gnome-shell-integration-extension-after-uninstalling-gnome/897498 - https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome/Installation#Troubleshooting ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: chrome-gnome-shell (not installed) ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 29 20:20:39 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-02 (513 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: chrome-gnome-shell UpgradeStatus: Upgraded to zesty on 2017-03-29 (0 days ago) ** Affects: chrome-gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677344 Title: Managed extension is only removed on package purge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrome-gnome-shell/+bug/1677344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646914] Re: Ubuntu 16.04 package version contains improper API
I have. The package maintainer seems to be a (former) grad student that is completely unresponsive. Since he/Debian doesn't seem to care, I was hoping Canonical would since their LTS OS has a noncompiling header. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646914 Title: Ubuntu 16.04 package version contains improper API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaml-cpp/+bug/1646914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646914] Re: Ubuntu 16.04 package version contains improper API
Bump. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646914 Title: Ubuntu 16.04 package version contains improper API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaml-cpp/+bug/1646914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646914] Re: Ubuntu 16.04 package version contains improper API
Is there a way to allow Azamat Hackimov's packages to become the new Ubuntu standard over the ones in Debian Sid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646914 Title: Ubuntu 16.04 package version contains improper API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaml-cpp/+bug/1646914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646914] Re: Ubuntu 16.04 package version contains improper API
This PPA uses 0.5.3 instead of 0.5.2 (which has been out for over a year) and works fine. https://launchpad.net/~winterheart/+archive/ubuntu/openxcom -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646914 Title: Ubuntu 16.04 package version contains improper API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaml-cpp/+bug/1646914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646914] Re: Ubuntu 16.04 package version contains improper API
0.5.2 does not compile in Ubuntu 16.04. Please consider promoting 0.5.3 to LTs. https://github.com/jbeder/yaml-cpp/pull/303#issuecomment-264642971 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646914 Title: Ubuntu 16.04 package version contains improper API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaml-cpp/+bug/1646914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646914] Re: Ubuntu 16.04 package version contains improper API
I should have said that the headers for 0.5.2 cannot be included in any program being compiled as the API is broken is the head of 0.5.2. Unsure why this wasn't caught by the package maintainers before but it's causing serious issues wit people using yank-cop. (The entire ROS community) trying to upgrade to 16.04 from 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646914 Title: Ubuntu 16.04 package version contains improper API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaml-cpp/+bug/1646914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646914] [NEW] Ubuntu 16.04 package version contains improper API
Public bug reported:
A call to equals was broken by an API change, and one of the calls in
the header was never updated.
/usr/include/yaml-cpp/node/detail/impl.h:136:15: error: ‘equals’ was not
declared in this scope
if (equals(*it->first, key, pMemory)) {
This is fixed in the 0.5.3 source.
** Affects: yaml-cpp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646914
Title:
Ubuntu 16.04 package version contains improper API
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaml-cpp/+bug/1646914/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635179] [NEW] aptitude hangs after updating the package list
Public bug reported: This is pretty much the same bug as https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=838560, except no -u flag is necessary. Reproduction: 1. Open aptitude 2. Attempt to update the package list with 'u' 3. One of the requests 404s 4. Aptitude hangs at "loading cache", no progress bar is shown on screen Removing the offending entries from the sources list means Aptitude no longer hangs. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: aptitude 0.8.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 20 11:14:25 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-02 (352 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: aptitude UpgradeStatus: Upgraded to yakkety on 2016-09-30 (19 days ago) ** Affects: aptitude (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635179 Title: aptitude hangs after updating the package list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1635179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581834] Re: In the new version, gscan2pdf can only scan one page from ADF
Ouch. That did it. Yes, that was very silly of me! How can I not notice? It works just fine when I selected "All" instead of "#". Sorry for the trouble! Great software and thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581834 Title: In the new version, gscan2pdf can only scan one page from ADF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1581834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581834] Re: In the new version, gscan2pdf can only scan one page from ADF
Attached is the log file for diagnosis ** Attachment added: "Log File" https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1581834/+attachment/4662935/+files/gscan2pdf.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581834 Title: In the new version, gscan2pdf can only scan one page from ADF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1581834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581834] [NEW] In the new version, gscan2pdf can only scan one page from ADF
Public bug reported: Hi there, I've been using gscan2pdf for over a year now. Ever since the new version sometime in December or so (couldn't remember exactly) it won't scan past the first page. It will scan the first page and then it will spit the rest of the pages. I first thought it was a hardware issue, then I used Simple Scan, Adobe Acrobat Pro on Mac OS X, and the scanner's own built-in "Scan to USB" and they are all okay and can scan multiple pages. Then I thought maybe it was a libsane issue, but if it is, then why does Simple Scan 3.20 work? Scanner model: Brother MFC-J650DW. OS: Ubuntu 14.04 and Ubuntu 16.04 (confirmed both) gscan2pdf version: 1.39 and 1.40 (I even tried the manual download) I tried adjusting the blank threshold to 0.0 from 0.003 and it doesn't make any difference. It's a great program, not sure what happens with the new version. It was working fine all these time. ** Affects: gscan2pdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581834 Title: In the new version, gscan2pdf can only scan one page from ADF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1581834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540553] Re: task Xorg:1042 blocked for more than 120 seconds in schedule+0x37/0x80
I tried today from a live Ubuntu 16.04 environment for a shorter amount of time, this time with the right bitness and Chrome version 50. I still cannot reproduce the issue. I noticed that this issue is most easily reproduced when I try and launch Chrome as soon as possible after booting up. This is difficult to reproduce on a live environment as I have to first download and install the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540553 Title: task Xorg:1042 blocked for more than 120 seconds in schedule+0x37/0x80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1540553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540553] Re: task Xorg:1042 blocked for more than 120 seconds in schedule+0x37/0x80
I am currently running a 16.04 live environment, and I'm slowly trying to reproduce my usual working environment. However I must note that the live environment is 32-bit, so the test may be inconclusive. So far I have been unable to reproduce the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540553 Title: task Xorg:1042 blocked for more than 120 seconds in schedule+0x37/0x80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1540553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540553] Re: task Xorg:1042 blocked for more than 120 seconds in schedule+0x37/0x80
Thank you for your patience. sudo dmidecode -s bios-version: A09 sudo dmidecode -s bios-release-date: 11/18/2015 ** Changed in: xorg (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540553 Title: task Xorg:1042 blocked for more than 120 seconds in schedule+0x37/0x80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1540553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540553] Re: task Xorg:1042 blocked for more than 120 seconds in schedule+0x37/0x80
Sorry for the long response time. I proceeded to upgrade my laptop to version A09, rebooted, launched Chrome, and X froze immediately as described above. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540553 Title: task Xorg:1042 blocked for more than 120 seconds in schedule+0x37/0x80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1540553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540553] [NEW] task Xorg:1042 blocked for more than 120 seconds in schedule+0x37/0x80
Public bug reported: Since system updates on or after Thursday 28th, I have been experiencing complete system freezes when attempting to do tasks such as opening a menu or a window. Compiz manages to draw a shadow around the new window, then everything freezes: * You can SSH into the machine normally * Audio and network work fine * You can move the mouse cursor around * SysRq-REISUB works Everything else doesn't: * Clicking * Typing * Ctrl-Alt-Fn * Ctrl-Alt-Backspace (after having enabled it) * Killing Xorg * Occasionally, killing lightdm/compiz/etc. This has happened both with Unity and Cinnamon, so compiz and friends are not to blame. Xorg.org complains it is the victim: (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. [...] (EE) [mi] EQ overflow continuing. 1000 events have been dropped. (EE) [mi] No further overflow reports will be reported until the clog is cleared. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55b72ecb868e] (EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x55b72eb74152] (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f2a73a45000+0x60a7) [0x7f2a73a4b0a7] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f2a73a45000+0x687d) [0x7f2a73a4b87d] (EE) 4: /usr/bin/X (0x55b72eb04000+0x96ac8) [0x55b72eb9aac8] (EE) 5: /usr/bin/X (0x55b72eb04000+0xbfc92) [0x55b72ebc3c92] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f2ae000+0x352f0) [0x7f2a777b32f0] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f2a7787b0b7] (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f2a78b62a08] (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm_intel.so.1 (0x7f2a71f55000+0x6736) [0x7f2a71f5b736] (EE) 10: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so (0x7f2a72176000+0x4173f1) [0x7f2a7258d3f1] (EE) 11: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so (0x7f2a72176000+0x417763) [0x7f2a7258d763] (EE) 12: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so (0x7f2a72176000+0x148597) [0x7f2a722be597] (EE) 13: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so (0x7f2a72176000+0x148803) [0x7f2a722be803] (EE) 14: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so (0x7f2a72176000+0x148c38) [0x7f2a722bec38] (EE) 15: /usr/lib/xorg/modules/libglamoregl.so (0x7f2a7347d000+0x20d20) [0x7f2a7349dd20] (EE) 16: /usr/lib/xorg/modules/libglamoregl.so (0x7f2a7347d000+0x20ed2) [0x7f2a7349ded2] (EE) 17: /usr/lib/xorg/modules/libglamoregl.so (0x7f2a7347d000+0x1181d) [0x7f2a7348e81d] (EE) 18: /usr/lib/xorg/modules/libglamoregl.so (0x7f2a7347d000+0x1191a) [0x7f2a7348e91a] (EE) 19: /usr/bin/X (0x55b72eb04000+0x13fbb3) [0x55b72ec43bb3] (EE) 20: /usr/bin/X (0x55b72eb04000+0x54ce3) [0x55b72eb58ce3] (EE) 21: /usr/bin/X (0x55b72eb04000+0x5818f) [0x55b72eb5c18f] (EE) 22: /usr/bin/X (0x55b72eb04000+0x5c34b) [0x55b72eb6034b] (EE) 23: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f2a7779ea40] (EE) 24: /usr/bin/X (_start+0x29) [0x55b72eb4a6c9] All the kernel knows is XOrg isn't responding. Not even kill -9 will make it budge. [ 7316.307467] INFO: task Xorg:1042 blocked for more than 120 seconds. [ 7316.307481] Not tainted 4.2.0-27-generic #32-Ubuntu [ 7316.307484] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 7316.307488] XorgD 88021e516640 0 1042 1 0x0046 [ 7316.307497] 88020ef07698 0046 880214a73700 880211c46e00 [ 7316.307504] 88020ef07728 88020ef08000 88021e516640 7fff [ 7316.307509] 88020fad1f28 88020ef076b8 817edc37 [ 7316.307515] Call Trace: [ 7316.307530] [] schedule+0x37/0x80 [ 7316.307538] [] schedule_timeout+0x189/0x250 [ 7316.307592] [] ? gen6_read32+0xd9/0x180 [i915] [ 7316.307601] [] ? read_tsc+0x9/0x10 [ 7316.307613] [] io_schedule_timeout+0xa4/0x110 [ 7316.307647] [] __i915_wait_request+0x404/0x540 [i915] [ 7316.307653] [] ? wake_atomic_t_function+0x60/0x60 [ 7316.307661] [] ? __ww_mutex_lock_slowpath+0x74/0x1d0 [ 7316.307696] [] i915_wait_request+0x73/0xe0 [i915] [ 7316.307724] [] i915_gem_object_wait_rendering+0x6d/0xc0 [i915] [ 7316.307731] [] ? mutex_lock+0x16/0x40 [ 7316.307775] [] intel_crtc_wait_for_pending_flips+0x12a/0x230 [i915] [ 7316.307817] [] ? drm_atomic_get_plane_state+0x32/0xe0 [drm] [ 7316.307859] [] intel_crtc_disable_planes+0x32/0x100 [i915] [ 7316.307901] [] __intel_set_mode+0x942/0xb60 [i915] [ 7316.307935] [] ? drm_atomic_set_fb_for_plane+0x20/0x90 [drm] [ 7316.307976] [] intel_crtc_set_config+0x2b6/0x580 [i915] [ 7316.308008] [] ? drm_modeset_lock_all_crtcs+0x90/0xa0 [drm] [ 7316.308037] [] drm_mode_set_config_internal+0x66/0x100 [drm] [ 7316.308061] [] drm_framebuffer_remove+0xfa/0x140 [drm] [ 7316.308087] [] drm_fb_release+0x9d/0xd0 [drm] [ 7316.308103] [] drm_release+0x424/0x500 [drm] [ 7316.308110] [] __fput+0xe4/0x220 [ 7316.308116] [] ___
[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE
And still an issue as of Nov 17, 2015 Connecting to security.ubuntu.com (2001:67c:1562::17) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412943 Title: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1412943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1347834] [NEW] UnboundLocalError: local variable 'e' referenced before assignment in doUpdate, line 924
Public bug reported: Here's the message I got: File "/tmp/user/0/ubuntu-release-upgrader-y0kam4fv/DistUpgrade/DistUpgradeController.py", line 1822, in run return self.fullUpgrade() File "/tmp/user/0/ubuntu-release-upgrader-y0kam4fv/DistUpgrade/DistUpgradeController.py", line 1724, in fullUpgrade if not self.doUpdate(): File "/tmp/user/0/ubuntu-release-upgrader-y0kam4fv/DistUpgrade/DistUpgradeController.py", line 924, in doUpdate if not e: UnboundLocalError: local variable 'e' referenced before assignment === Command detached from window (Wed Jul 23 19:26:09 2014) === === Command terminated with exit status 1 (Wed Jul 23 19:26:19 2014) === The problem persists also if I upgrade ubuntu-release-upgrader-core to the Utopic version of the software. This was easy to try as do-release- upgrade failed to restore my sources.list file to its previous state as it crashed and burned. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Jul 23 19:28:51 2014 InstallationDate: Installed on 2014-05-09 (74 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2014-07-23 (0 days ago) VarLogDistupgradeAptlog: Log time: 2014-07-23 19:24:30.630772 Log time: 2014-07-23 19:24:50.648009 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347834 Title: UnboundLocalError: local variable 'e' referenced before assignment in doUpdate, line 924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1347834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1291365] Re: gnome screensaver locks again shortly after unlocking
As a result of this bug (the screensaver is not meant to trigger as the user is trying to actively use the system), it might happen that the screensaver fails to acquire focus properly as it fades in. As a result you can type in characters, but the keystrokes are sent in underneath windows... such as an IRC client. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1291365 Title: gnome screensaver locks again shortly after unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1291365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280030] Re: php-json should be package dependency of php-common
This is hardly a problem with the Ubuntu installer. ** Package changed: ubiquity (Ubuntu) => php5 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280030 Title: php-json should be package dependency of php-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1280030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292620] Re: Session unlocking after screen blank results in screen blanking and a locked sessions
*** This bug is a duplicate of bug 1291365 *** https://bugs.launchpad.net/bugs/1291365 ** This bug has been marked a duplicate of bug 1291365 gnome screensaver locks again shortly after unlocking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292620 Title: Session unlocking after screen blank results in screen blanking and a locked sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292965] Re: Unlocking screensaver needs two redundant steps
*** This bug is a duplicate of bug 1291365 *** https://bugs.launchpad.net/bugs/1291365 ** This bug is no longer a duplicate of bug 1292620 Session unlocking after screen blank results in screen blanking and a locked sessions ** This bug has been marked a duplicate of bug 1291365 gnome screensaver locks again shortly after unlocking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292965 Title: Unlocking screensaver needs two redundant steps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292620] [NEW] Session unlocking after screen blank results in screen blanking and a locked sessions
Public bug reported: What happens: 1. I lock my session 2. Time passes; screen goes blank 3. I type in my password 4. I get my session back for 2 seconds 5. Screen blanks (given enough seconds, the monitor says "no HDMI input") 6. I move the mouse, the screen comes back 7. I get another password prompt (same as the one in step 3) 8. I unlock the session correctly 9. I resume work. What should happen instead are steps 1-3,8-9. Questions from https://wiki.ubuntu.com/DebuggingScreenLocking that are still relevant: What desktop environment does this problem occur in? Unity 3D Do you use visual effects? Unity 3D's defaults. Is this a laptop or a desktop machine? Laptop How many monitors do you use? 2, of which only 1 is active. If it is a laptop, do you use an external screen? Yes. Only the external screen is ON. The lid is closed at all times. Do you have the hamster-applet application installed? No. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 17:30:13 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2012-03-15 (728 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-01-22 (50 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "gconftool-2 --dump /apps/gnome-screensaver /apps/gnome-power-manager /desktop/gnome/session /desktop/gnome/lockdown > screen-locking-debug.xml" https://bugs.launchpad.net/bugs/1292620/+attachment/4024173/+files/screen-locking-debug.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292620 Title: Session unlocking after screen blank results in screen blanking and a locked sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286397] [NEW] Window background is black
Public bug reported: The window is black. The font thumbnails are also black. The "all fonts" view is less than helpful. Luckily the single font page itself is dark- grey on black, so that's not invisible. :) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-font-viewer 3.8.0-1build1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 1 01:05:11 2014 InstallationDate: Installed on 2012-03-15 (715 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: gnome-font-viewer UpgradeStatus: Upgraded to trusty on 2014-01-22 (37 days ago) ** Affects: gnome-font-viewer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "Screenshot of the defect." https://bugs.launchpad.net/bugs/1286397/+attachment/4001579/+files/um.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286397 Title: Window background is black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1286397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 656855] Re: Desktop icons and the mouse may reside in areas that are covered by no monitor.
Thanks for the poke. Unfortunately, I won't be able to try and repro on Trusty until mid February. :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/656855 Title: Desktop icons and the mouse may reside in areas that are covered by no monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/656855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166765] Re: unity showing only blank desktop, no dash nor decorations
> -310 being temporarily broken in this case - presumably you fell back to nouveau and then this didn't work for some reason, which is possibly a separate bug that should be filed if someone can verify that is the case Actually -310 works fine; I can tell which drivers are loaded because Ctrl-Alt-F1 and TF2 work differently based on whichever driver is active. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166765 Title: unity showing only blank desktop, no dash nor decorations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1166765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166765] Re: unity showing only blank desktop, no dash nor decorations
> gsettings reset org.compiz.core:/org/compiz/profiles/unity/plugins/core/ active-plugins Yep, this did the trick. Turns out that "compiz (core) - Error: Plugin 'opengl' not loaded." means "opengl was not loaded and you need to fix this" and not "opengl was not loaded because of an error." Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166765 Title: unity showing only blank desktop, no dash nor decorations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1166765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166765] Re: unity showing only blank desktop, no dash nor decorations
$ gsettings get org.compiz.core:/org/compiz/profiles/unity/plugins/core/ active-plugins ['core', 'ccp', 'composite', 'compiztoolbox', 'decor', 'snap', 'gnomecompat', 'regex', 'resize', 'place', 'grid', 'imgpng', 'vpswitch', 'move', 'mousepoll', 'workarounds', 'session'] $ grep -i error ~/.xsession-errors compiz (core) - Error: Plugin 'opengl' not loaded. compiz (core) - Error: Plugin 'opengl' not loaded. Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory [2406:2532:0413/191714:ERROR:object_proxy.cc(624)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.chromium.Mtpd': no such name [2406:2532:0413/191714:ERROR:object_proxy.cc(624)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.chromium.Mtpd': no such name [2406:2406:0413/191716:ERROR:content_settings_pref_provider.cc(492)] Invalid pattern strings: ,* [2406:2406:0413/191716:ERROR:content_settings_pref_provider.cc(396)] Invalid pattern strings: ,* [2406:2406:0413/191719:ERROR:object_proxy.cc(529)] Failed to call method: org.chromium.Mtpd.EnumerateStorages: object_path= /org/chromium/Mtpd: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.Mtpd was not provided by any .service files [2406:2406:0413/191754:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility() [2406:2406:0413/191757:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility() ** (nautilus:2437): WARNING **: Error calling current_status: Method "current_status" with signature "" on interface "com.ubuntuone.SyncDaemon.Status" doesn't exist ** Attachment added: ".xsession-errors" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1166765/+attachment/3643238/+files/.xsession-errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166765 Title: unity showing only blank desktop, no dash nor decorations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1166765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166765] Re: unity showing only blank desktop, no dash nor decorations
When you do either, the net result is window decorations vanish and windows stop accepting input properly. This makes it hard to post the output for bonus points, but basically the opengl plugin seems to fail to load. The only way to recover window decorations that I've found is ctrl- alt-f1, login, sudo killall lightdm; sudo lightdm &; login again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166765 Title: unity showing only blank desktop, no dash nor decorations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1166765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168151] [NEW] The Unity interface does not appear
Public bug reported: Ever since my upgrade from 12.10 to 13.04, Unity has failed to work properly. I get no side bar with the list of applications. I get no top bar with the menu bars; the menu bars are now actually embedded in each window. I got no window decorations until I upgraded some packages (some of them being compiz and unity) and installed xfce; either one of those granted me window decorations. If I run compiz --replace or unity, however, I lose window decorations or the ability to move and resize windows. I get the same problem with both the nvidia-313 drivers or the nouveau + mesa drivers, so I'm filing this against unity. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.10-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 ApportVersion: 2.9.2-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Thu Apr 11 22:50:47 2013 InstallationDate: Installed on 2012-03-15 (392 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-04-08 (2 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168151 Title: The Unity interface does not appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1168151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057748] Re: Package needs to Replace libcurl4-dev
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057748 Title: Package needs to Replace libcurl4-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1057748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057748] [NEW] Package needs to Replace libcurl4-dev
Public bug reported: My build system is now broekn because I haveone package (ros) that depends on libcurl4-openssl-dev and one package (openscenegraph) that depends on libcurl4-dev. While libcurl4-gnutls-dev and libcurl4-nss-dev both have a Replace libcurl4-dev to provide the virtual package, libcurl4-openssl-dev does not. Furthermore libcurl4-openssl-dev cannot be installed with either of the other two packages, so they conflict but do not have the same Replace packages. This problem has been seen by MANY people that use ROS and there are no good answers. IT seems to me that the easiest answer is to properly have this package declare it's replacements and conflicts. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libcurl4-openssl-dev 7.22.0-3ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Thu Sep 27 15:29:06 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: curl UpgradeStatus: Upgraded to precise on 2012-05-04 (146 days ago) ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057748 Title: Package needs to Replace libcurl4-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1057748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 887847] Re: system load indicator auto start does not work
Also in Precise 12.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/887847 Title: system load indicator auto start does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-multiload/+bug/887847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969260] Re: apport-gtk crashed with ValueError in _apt_pkg(): package does not exist
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969260 Title: apport-gtk crashed with ValueError in _apt_pkg(): package does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/969260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839021] Re: Alt plus whatever key above Tab is supposed to let me do application switch. This doesn't work on the Italian keyboard layout.
Yup, the issue is fixed. ** Changed in: unity (Ubuntu) Status: Incomplete => Fix Released ** Changed in: unity Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839021 Title: Alt plus whatever key above Tab is supposed to let me do application switch. This doesn't work on the Italian keyboard layout. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/839021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839021] Re: Alt plus whatever key above Tab is supposed to let me do application switch. This doesn't work on the Italian keyboard layout.
** Attachment added: "Keyboard%20layout.png" https://bugs.launchpad.net/bugs/839021/+attachment/2340702/+files/Keyboard%2520layout.png ** Description changed: In http://www.youtube.com/watch?v=XHFNnygpvcM, Jorge Castro explains that task management in Unity uses two keys, Tab to switch between - applications and the key above it to switch between windows of t he same + applications and the key above it to switch between windows of the same application. On the italian keyboard, this key would be '\'. However, pressing Alt-\ makes nothing happen. I can, however, regularly use the arrow keys once the task switcher is open. This suggests it's merely a keyboard problem. I attach a picture of my keyboard layout for your convenience. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.10.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] Date: Thu Sep 1 21:18:03 2011 InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2011-08-23 (9 days ago) ** Description changed: In http://www.youtube.com/watch?v=XHFNnygpvcM, Jorge Castro explains that task management in Unity uses two keys, Tab to switch between applications and the key above it to switch between windows of the same application. On the italian keyboard, this key would be '\'. However, pressing Alt-\ makes nothing happen. I can, however, regularly use the arrow keys once - the task switcher is open. This suggests it's merely a keyboard problem. + the task switcher is open. This suggests it's merely a keyboard binding + problem. I attach a picture of my keyboard layout for your convenience. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.10.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] Date: Thu Sep 1 21:18:03 2011 InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2011-08-23 (9 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839021 Title: Alt plus whatever key above Tab is supposed to let me do application switch. This doesn't work on the Italian keyboard layout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/839021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839021] [NEW] Alt plus whatever key above Tab is supposed to let me do application switch. This doesn't work on the Italian keyboard layout.
Public bug reported: In http://www.youtube.com/watch?v=XHFNnygpvcM, Jorge Castro explains that task management in Unity uses two keys, Tab to switch between applications and the key above it to switch between windows of the same application. On the italian keyboard, this key would be '\'. However, pressing Alt-\ makes nothing happen. I can, however, regularly use the arrow keys once the task switcher is open. This suggests it's merely a keyboard binding problem. I attach a picture of my keyboard layout for your convenience. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.10.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] Date: Thu Sep 1 21:18:03 2011 InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2011-08-23 (9 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839021 Title: Alt plus whatever key above Tab is supposed to let me do application switch. This doesn't work on the Italian keyboard layout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/839021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 833343] Re: openstv crashed with UnicodeDecodeError in decode(): 'utf8' codec can't decode byte 0xe0 in position 25: invalid continuation byte
** Description changed: While attempting to run the attached ballot file, this exception is raised at certain display widths. For example, no problem is apparent with a display width of 100 chars, while the crash happens at a display - width of 80 characters. Changing the name of the canddiate "Mana ಠдಠ" to + width of 80 characters. Changing the name of the candidate "Mana ಠдಠ" to "Mana" worked around the issue. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: openstv 1.6.1-1 ProcVersionSignature: Ubuntu 3.0.0-9.13-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Wed Aug 24 22:17:23 2011 ExecutablePath: /usr/bin/openstv InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/openstv ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 PythonArgs: ['/usr/bin/openstv'] SourcePackage: openstv Title: openstv crashed with UnicodeDecodeError in decode(): 'utf8' codec can't decode byte 0xe0 in position 25: invalid continuation byte UpgradeStatus: Upgraded to oneiric on 2011-08-23 (1 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/833343 Title: openstv crashed with UnicodeDecodeError in decode(): 'utf8' codec can't decode byte 0xe0 in position 25: invalid continuation byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openstv/+bug/833343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
