I had a version of this bug.
- starting from 18.04 LTS, with all package updates
- software-updater didn't offer 20.04 (surprised me this many months
after 20.04 was released)
- followed https://ubuntu.com/blog/how-to-upgrade-from-ubuntu-18-04-lts-
to-20-04-lts-today
- all went well until proce
Oops:
The problem has gone away. I'm not sure why. Things that I did:
- updated thunderbird (that didn't fix the problem by itself -- I did
that before posting #2)
- did a software update on the server (Fedora 32). But that doesn't
explain the problem since the problem arose WITHOUT a softwar
I had a problem much like this.
- in 2020 January.
- Ubuntu 18.04
- broke when I updated Thunderbird from 1:52.7.0+build1-0ubuntu1
- fixed when I rolled it back and pinned it.
With recent updates, even 1:52.7.0+build1-0ubuntu1 failed in a way that
seems the same.
I then updated to the latest
I'm getting this too. /var/log/syslog gets this:
Feb 17 11:17:01 redback console-kit-daemon[3481]: GLib-CRITICAL: Source
ID 373 was not found when attempting to remove it
>From reading this launchpad entry, I infer that it is a bug in each
application that generates this. So perhaps my message
Just happened to me again. After an upgrade to
Linux version 3.2.0-58-generic (buildd@allspice) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #88-Ubuntu SMP Tue Dec 3 17:37:58 UTC 2013
$ sudo dkms status
[sudo] password for hugh:
nvidia-304, 304.88, 3.2.0-53-generic, x86_64: installed
nv
I have experienced this problem on my Ubuntu 12.04.3 LTS system.
Here's an extract from dmesg output:
[ 30.521761] NVRM: API mismatch: the client has the version 304.108, but
[ 30.521763] NVRM: this kernel module has the version 304.88. Please
[ 30.521764] NVRM: make sure that this kernel
For some unknown reason, this problem showed up on my system recently
(XFCE / Ubuntu 12.04.2 LTS system with all updates).
Deleting ~/.config/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml and
logging in again didn't fix it for me. (See #7)
That file contains so I don't
know what theme is bein
Addendum to #10: guvcview works fine.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gstreamer0.10 in Ubuntu.
https://bugs.launchpad.net/bugs/963920
Title:
Cheese doesn't start, hangs with 100% CPU
Status in “gstreamer0.10” package i
I updated for 10.04 LTS AMD64 => 12.04 LTS AMD64 in the last few days.
Cheese went from working to failing in the way described above:
At launch, it took 100% CPU and did not even show a window.
This was true with and without my HP USB webcam plugged in.
I wanted to give a useful traceback but the
See also https://bugzilla.mozilla.org/show_bug.cgi?id=633763 "Cookie
confirmation dialogs should be tab-modal"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/833952
Title:
cookie dial
I'm getting a particularly frustrating variant of this problem with
firefox 17.0 on 64-bit Fedora 17 Gnome.
I get a stack of these cookie confirmation dialog boxes and I wish to
click "allow for Session" on each of them. The top of the stack won't
take a click! If I drag the FF window, some of t
Romano: +1
12.04 is LTS: supported of some more years.
Furthermore, Mythbuntu only supports LTS, and the proprietary driver is
necessary for home theatre applications.
So: this needs to be fixed for 12.04
--
You received this bug notification because you are a member of Desktop
Packages, which
@ Martin Pitt #23
Is your proposed fix to nvidia-common supposed to fix jockey's handling
of installing proprietary AMD drivers (fglrx)? That seems rather
counter-intuitive.
I have a fresh AMD64 installation of Oneiric, plus all updates (but no
-proposed). Jockey fails with the message "sorry i
13 matches
Mail list logo
