This happened to me just now on a fresh installation of 20.04. Exactly
as reported - first attempt at calibration with a Spyder 3 fails, on the
second attempt gnome-control-center crashes hard.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This should definitely be fixed in ssh-copy-id - making these
assumptions is just bad.
However, I found a workaround that is convenient for me at least and
that I think could be a stopgap for others too, until such time as ssh-
copy-id is fixed. I wrote it up here:
This should definitely be fixed in ssh-copy-id - making these
assumptions is just bad.
However, I found a workaround that is convenient for me at least and
that I think could be a stopgap for others too, until such time as ssh-
copy-id is fixed. I wrote it up here:
This still occurs randomly in 14.04. Seems to be happening no less (and
no more) often than in 13.10.
I'd still like to know whether there's a way to see which process is
actually changing the settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Good to see that it's still being looked at.
I'm trying the dconf watch / thing now, but I see two problems with
it: The output of dconf is not timestamped nor does it show what process
caused the dconf change. Is there any way to obtain that information?
--
You received this bug notification
This bug is definitely not fixed. It still happens randomly on all of my
13.10 installations (all of them upgraded from 13.04, if that helps).
It's also only customized shortcuts that involve the Windows key
(super), at least those are the only ones that I notice. I can see no
pattern as to when
Is there a way to log what application sets gsettings and when? That
could help find the culprit.
Also, why is there anything that sets these shortcuts *at all*? That
should be a user setting and not something an application does on its
own.
--
You received this bug notification because you are
I am still seeing this in fully updated 13.04 installations. I can't
trigger it, it seems to happen at random, but feels like it's after
every other login. All window management and virtual desktop shortcuts
are reset to the unity/gnome defaults.
It happens both with Unity sessions as well as
I can confirm this bug.
Trying size 9 with Ubuntu Mono Regular the problem is minimized but not
entirely gone. Other fonts and other sizes are basically unusable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Nothing much to add, except that I can confirm this bug. I'd love to see
the new libmusicbrainz packaged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005075
Title:
Libmusicbrainz fails to parse
This is hardly a wishlist item, I think. This problem affects core
bluetooth functionality and thus should be set much higher.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/837196
Title:
Cannot
Also, in that upstream bug the gnome dev seems to think a Bluetooth name
must always be the same as the system's hostname.
(https://bugzilla.gnome.org/show_bug.cgi?id=658154, No, and we're not
interested in supporting that.)
Ignoring for a moment the condescending attitude that is infesting Gnome
I can confirm this happening on a Dell Latitude E6500 with the following wifi:
0c:00.0 Network controller: Intel Corporation WiFi Link 5100
I'm seeing the same messages, and am getting extreme latency spikes
(8000ms within the local network) as well as packet loss 60%.
The proposed workaround
I am also getting this on Intrepid with a GeForce 7900 GT/GTO, exactly
as described and shown in the screenshots.
Interesting side note, not sure whether this is related to this or
warrants a separate bug: I tried the 96 drivers offered by the
restricted drivers managers. The titlebar problem was
I'm seeing the same behavior with the following setup. Processor speed
remains fixed at 1000MHz, and cpufreq-info says current policy:
frequency should be within 1000 MHz and 1000 MHz. even though 2000MHz
are possible and I'm using the performance governor. Other governors
give me the same result.
15 matches
Mail list logo
