@Sebastien Sorry for the late reply.
I recall that the workaround consisted in adding a random delay to the
apt-daily task, so that it would not happen *right* at startup.
How exactly this was done, unfortunately, I did write it down :-/ but I
think it was adding or creating the file ./system/apt
Same problem with 20.04.
I believe this is related to this issue:
https://bbs.archlinux.org/viewtopic.php?id=255817 .
FTR, as `apt-daily.service` is running on startup, this was also
increasing my boot-time significantly (although I found a workaround for
this particular problem). Just to emphasi
FTR, I tried as Daniel described, and it didn't work.
My configuration is slightly different, though:
* using Ubuntu 19.04
* my current firmware is 1.1.3
When I click on the update with AC plugged in, I get a "Software is up to date"
message,*
with no indication to reboot.
When I reboot, I see
I have had the same problem since I got my XPS 7390, and I have the same
problem. I just found this report and will try Daniel's fix ASAP
(actually, my laptop has been charging all night, so I hope it will
work). However, just before I do, here is the output of the two commands
required by Sebastie
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 14.04 LTS
Release:14.04
$ apt-cache policy evince
evince:
Installed: 3.10.3-0ubuntu10
Candidate: 3.10.3-0ubuntu10
Version table:
*** 3.10.3-0ubuntu10 0
500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Pa
The problem seems to have disappeared for me,
probably following some update...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1168293
Title:
"No Certificate" dialog n
Actually, I realize that the dialog underneath the warning dialog (entitled
"Wii-Fi Network Authentication Required") is still active;
I can check the "Show password" box, click on "Connect" again (no effect) or on
"Cancel", which closes both dialogs alltogether.
(I attach a screenshot to make t
Public bug reported:
I'm using ubuntu 13.04 (raring ringtail) beta.
I try to connect to a secure wi-fi network (eduroam).
I enter my login and password, but no certificate -- I'm instructed by my
university to ignore the warning (I know this is bad, but...).
Said warning appears (dialog entitled
yes; here are the installed versions of all the dependencies:
account-plugin-sip 3.6.4-0ubuntu3
--\ empathy 3.6.4-0ubuntu3
--\ libc6 2.17-0ubuntu4
--\ libglib2.0-0 2.36.0-1ubuntu1
--\ mcp-account-manager-uoa 3.6.4-0ubuntu3
--\ telepathy-rakia 0.7.4-1
--\ unity-asset-p
Public bug reported:
I installed account-plugin-sip, and tried to create a new SIP account.
First, the dialog is empty, but for Cancel and Done buttons; no configuration
field.
Then, whether I click on Cancel or Done, credentials-preferences stops with a
segmentation fault.
NB: I'm using gnome-
After further investigation, the problem disappears when I kill
seahorse-daemon, but comes back when I relaunch it... :-/
Not sure if this is related, but when I run seahorse-daemon, I get the
following (warning?) message:
pa@nua:~$ killall -q seahorse-daemon; seahorse-daemon -d
** (seahorse-dae
Same problem here with 13.04 .
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/1154049
Title:
Crashes with GLib-GIO-CRITICAL. UnknownMethod: Method "DescribeAll"
To manage notific
I have a very similar use case.
Rather than a preference to disable auto-reload, I would like a
preference to disable focus-stealing when the document change. I would
even be happy if this was only accessible via gconf-editor.
For the record, I can't imagine any scenario where this focus-stealing
Martin, I did as you asked with my iPhone, and it worked. I attach the
output of both commands.
However, the bug seems to have been fixed with the update to f-spot
0.5.0.3-0ubuntu1.
** Attachment added: "iphone.txt"
http://launchpadlibrarian.net/18765371/iphone.txt
--
F-Spot - Error connecti
I still have the bug under Intrepid with two cameras (FUJIFILM FinePix F30 and
iPhone).
How come the bug is marked as "Fix released", while many people seem to
experience it?
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received
15 matches
Mail list logo