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
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
> 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
(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:
(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
(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
(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
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
(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.
(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
(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
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
(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
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
(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
(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.
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
(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
(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
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
(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
(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
(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
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
(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
(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
(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?
(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
(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
(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
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.
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:
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
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
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
> 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
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:
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"
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
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
** 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
** 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
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
> 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
*** 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
*** 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
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'
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.
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.
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
** 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
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.
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]
** 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
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
** 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
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.
--
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
** 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.
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.
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.
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
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,
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:
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.
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
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.
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
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
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
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.
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.
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
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
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
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.
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.
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
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)
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
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
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
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1280030
Title:
php-json
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
*** 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
*** 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
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
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
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
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,
$ 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
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!
-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
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
--
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:
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,
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:
** 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
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.
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 '\'.
** 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
1 - 100 of 157 matches
Mail list logo
