, as the Cloud Archive repository only has the latest versions,
and it's unclear how to roll back from this update.
Thank you for your time!
Best regards,
Zakhar
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman
I am experiencing the exact same syndromes plus "Settings" does not seem
to be recording correctly the VNC password, it keeps taking another
value after reboot... strange, I'll have to reproduce it.
I am eagerly waiting for the fix to make its way to the official repos!
It is a pity Canonical is
Dear Mauricio, thanks for the tip.
I had to do the following to make it work:
After:
bzr add debian/source/format
I added:
bzr add debian/compat
The compat file hold only one line with: 10, as in: echo "10" >compat
Without this, it fails to compile, but with this line added, all seems
Strike it, there is no binary package with those commands (unlike with
bzr wrapped) and I am not sure the "source" package is even correct...
I'm lost!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Possible workaround?
It seems that after "manually" providing the compat file in debian
directory in the buildarea, if I run the "naked" debuild commands:
dpkg-buildpackage -us -uc -ui
then
dpkg-buildpackage -us -uc -ui -S
Instead of what is documented:
bzr builddeb -- -us -uc
and
bzr
Dear all, not sure if this bug fix is just about dh_make or the full
process to make a package for Launchpad that is documented on the Ubuntu
documentation.
The former now works, the latter still fails further down the process.
Here is what now works:
$ bzr dh-make 1fichierfs 1.9.2~Focal
It was probably the 'mirror replication delay', now it is correctly
installed after an "apt update" and repeating the above command "apt
install brz-debian/focal-proposed" that previously failed.
I'll test and report within 24h.
--
You received this bug notification because you are a member of
Same no luck:
$ LANG=C sudo apt install brz-debian/focal-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Release 'focal-proposed' for 'brz-debian' was not found
Could it be because I am using the closest apt mirror, which is in my
case:
Hi, thanks for the upgrade.
Am I doing something wrong?
I followed the steps on testing "proposed" from the page you kindly linked.
- Ticked "focal-proposed"
- Pined priorities to 400 for "proposed" (to avoid getting all the "proposed"!)
- ran:
$ LANG=C sudo apt update
Hit:1
Indeed mrsam!
My current workaround is to use 16.04 that I still have, and bazaar and
how it is used in the Ubuntu documentation is still working there.
The limitation of doing so is that some libraries I need on my projects
have since changed, and it does not "build" with 16.04. This is not an
Hello Andrei, and thanks for your concern.
Unfortunately not, I didn't find any third party tutorial. This is an
"official" one, not "community", since it is hosted on ubuntu.com, and
tells us about ppa, which are a nice feature of Ubuntu.
I don't want to do a trial of intent here, but maybe
Hello, this report has stayed "undecided" / "unassigned" for 3 weeks
now.
It makes the Ubuntu ppa documentation irrelevant:
https://packaging.ubuntu.com/html/packaging-new-software.html
Was it the right place to post it or should I post it somewhere else,
for instance "bzr developers"?
--
You
Public bug reported:
Hello,
No need to repeat here that the documentation to properly build a
package is of appalling quality. That has been widely commented and is
probably a major hurdle why people don't "package".
Sorry, so that being said, I am using the little documentation there is
on
Thanks for the heads up Rafael.
Does this mean the fix is going to be in a new version, hence we won't
have it for 20.04 due to the "freeze" policy of Ubuntu, but it could be
in 20.10 or any subsequent version.
[I have my "workaround" anyway, and it works fine for my own use cases]
--
You
Note: the patch (if #101 is the "right" solution) applies to the package
"grub-common" that contains /etc/grub.d/10_linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia]
So to make #101 permanent, you have to "patch" line 335 of
/etc/grub.d/10_Linux
from:
set vt_handoff=vt.handoff=7
to:
set vt_handoff=vt.handoff=1
Not sure though the same "patch" is also to be applied in other files like
10_linuxzfs, etc...
Patch attached:
$
Hello, I can confirm that this bug still exists in 20.04.
I am using NVidia 340.108 because this is a 12 years old laptop with a
completely obsolete GeForce GT230M.
Workaround #34 (removing quiet splash) worked but slows down the boot
process due to the speed of writing on the console.
Thanks a lot Rafael.
Unlike bug #1877617, I don't have a fix to propose for the regression on
LP: #1755858, sorry!
Disabling services is a workaround for me... but definitely not a fix!
My initial "enhancement" report was a little bit more specific, and not
sure it will be fixed.
iscsi
(Please disconsider the previous post, the "targets database" was
corrupted)
---
Steps to reproduce:
---
- With VirutalBox running on top of Ubuntu Destktop 20.04, create a new Virtual
machine
- Install Ubuntu Desktop 20.04 on the new guest (minimal install is
** Attachment added: "iscsid.conf"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5385541/+files/iscsid.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882986
As explained by Christian on #4, I did further tests:
- Disables only open-iscsi
- To be sure, I moved out of the way what was in /etc/iscsi/nodes which is now
empty
- To be sure, did the same with /etc/iscsi/send-targets
- To be extra sure, even removed those directory
And when I boot my
I did some more investigations anyway, and discovered:
"It is not a bug, it is a feature"!
__
Steps to reproduce:
==
- In Virutalbox, start a new test machine
- Install a fresh 20.04 (minimal install is enough, and I did it in my 20GB RAM
disk, it's faster!)
-
(the previous one, as its name said, was isci ENABLED, sorry for the
confusion but you would have corrected with the name!)
** Attachment added: "VM Clean 20.04 startup with iscsi DISABLED"
Dear Rafael,
I would leave it as it is.
It is not yet clear for me why this is delaying the whole startup, but I
agree with you, it is probably not worth investigating more time since
the "workaround" is fine and simple.
What is clear is that iscsi needs "network-online", as per the directive
I am not sure this helps, because apparently "critical-chain" starts
only AFTER graphical.target... and we wanted to know why
graphical.target itself is delayed.
Also you asked a very relevant question:
"How could iscsi services know whether the user actually needs the
mounts or not?"
My
And the 4 files as expected with self-explanatory names.
** Attachment added: "systemd-analyze-dump.txt"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5384175/+files/systemd-analyze-dump.txt
--
You received this bug notification because you are a member of
** Attachment added: "systemctl-status-iscsi-3-services.txt"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5384182/+files/systemctl-status-iscsi-3-services.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "systemd-analyze-critical-chain.txt"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5384180/+files/systemd-analyze-critical-chain.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "systemd-analyze-blame.txt"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5384181/+files/systemd-analyze-blame.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And the graph WITH iscsi.
(EDIT from previous post, some words are missing)
In 16.04 the command
$ sudo iscsiadm -m node -l
was returning to the shell prompt.
In 20.04, the same command does NOT return to the shell prompt, but the
mount seems to work anyway.
** Attachment added: "Startup
Many thanks for the explanations Christian!
Here are some more clarification on my setup.
Indeed, I have done a "discover" for my NAS, and I have a node configured.
The other element is that the NAS is generally off, which means if open-iscsci
would try to communicate with the NAS at startup,
You're welcome.
Indeed, at first I though it was Virtualbox that has no .service (just a
SystemV classic init) but changing that had no effect, and disabling
iscsi gave me back my 10 seconds !
systemd-analyze:
summary: without iscsi
Startup finished in 17.404s (firmware) + 3.367s (loader) +
And the other dump (iscsi ENABLED)
** Attachment added: "systemd-analyze dump (with iscsi services ENABLED)"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5383003/+files/iscsi.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
This is not a bug, but rather an "optimisation" request.
(Probably set this as "enhancement request" + Low)
Apparently, the package is assuming the user will need some iscsi mounts
for his session, and is putting dependencies in the systemd
services/targets which effects
Clean 20.04, I confirm the bug.
There is a very simple way to reproduce the bug, **without even booting
an O.S.**
- Set your machine to boot in EFI mode
- From the Grub (2.04) Menu, enter command mode (by pressing the key 'c')
- Set the root to where you have your iso files:
For instance:
Confirmed also on a clean 20.04, kernel 5.4.0-31-generic
The time difference between gzip and lz4 is not noticeable by the user:
LZ4:
Startup finished in 14.815s (firmware) + 3.483s (loader) + 1.879s (kernel) +
23.176s (userspace) = 43.354s
graphical.target reached after 23.164s in userspace
Sorry, I have stopped using Nautilus when Gnome decided it should be a
tablet tool instead of a PC program, and withdraw all interesting
functions from it (like F3 to open a double pane).
I am now using Nemo, which might still have the bug since it forked
Nautilus before its emasculation, but I
Public bug reported:
In to the bug reported here:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1664067
indicator-datetime was apparently aware of the locale depending of the
options chosen.
Now it does not at all apply the locale, whatever the option chosen.
Environment:
Fresh install of 18.04.1 + Unity
I had the bug, but I can confirm than workaround at post #11 (2 seconds
delay before starting compiz) has fixed it.
Thanks Park Ju Hyung!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry... my "bug" was PEBCAK!
It has nothing to do with entropy. I copied the system from an old HDD
to a SDD, and in the process didn't change the resume UID that sits in:
/etc/initramfs-tools/conf.d/resume
It was still pointing to a partition UID on the old disk. Hence when the
old disk was
** Attachment added: "Boot with SSD + spinning rust HDD plugged to USB2"
https://bugs.launchpad.net/ubuntu/+bug/1779827/+attachment/5160961/+files/dmesg3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Boot with SSD only + touching trackpad/keyboard"
https://bugs.launchpad.net/ubuntu/+bug/1779827/+attachment/5160960/+files/dmesg2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am also attaching the full 3 dmesg if some other differences I could
not spot seem significant for you.
** Attachment added: "Boot with SSD only"
https://bugs.launchpad.net/ubuntu/+bug/1779827/+attachment/5160959/+files/dmesg1
--
You received this bug notification because you are a member
Sorry, but the bug also happens with 4.15.0-23
I upgraded a PC with a SSD replacing a HDD. So this laptop now only has
a SSD which obviously has no spinning part to produce entropy to seed
the random generator.
Here is what happens:
-1) not touching anything, there is a "30 seconds gap" (visible
Here is an ugly 3 steps workaround:
-1) Edit the org.gnome.Vino schema to restore the missing "enabled"
parameter (copying from 16.04)
sudo nano /usr/share/glib-2.0/schemas/org.gnome.Vino.gschema.xml
Add this key:
Enable remote access to the desktop
If true, allows
*** This bug is a duplicate of bug 1741027 ***
https://bugs.launchpad.net/bugs/1741027
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1775423/+attachment/5149412/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification
*** This bug is a duplicate of bug 1741027 ***
https://bugs.launchpad.net/bugs/1741027
More information (crash report) here:
https://errors.ubuntu.com/oops/a5173a48-699f-11e8-9b32-fa163ed44aae
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1741027 ***
https://bugs.launchpad.net/bugs/1741027
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1775423/+attachment/5149413/+files/ProcEnviron.txt
** This bug has been marked a duplicate of bug 1741027
*** This bug is a duplicate of bug 1741027 ***
https://bugs.launchpad.net/bugs/1741027
apport information
** Tags added: apport-collected
** Description changed:
Fresh install 18.04 + ubuntu-unity-desktop
unity-control-center crashes when trying to setup "Desktop Sharing"
Public bug reported:
Fresh install 18.04 + ubuntu-unity-desktop
unity-control-center crashes when trying to setup "Desktop Sharing"
Message (when launched from a terminal)
(unity-control-center:10876): GLib-GIO-ERROR **: 17:49:24.747: Settings
schema 'org.gnome.Vino' does not contain a key
Dear Christopher,
as I posted "upstream"
(https://bugs.freedesktop.org/show_bug.cgi?id=93782), both
- Latest ubuntu drm-tip kernel (as of June 3rd)
- applying the patch suggested C#12 of the upstream post (on the source I
already had of 4.17 rc3 drm-tip)
were NOT successful fixing the bug.
If
Hi Christopher,
1) Ok
2) I have tried kernel 4.17.0-994-generic, downloading it from the provided
link, same result!
For the exact measure of the "damage", a dmesg with the workaround displays
messages from 0.00 to 60.0 sec. With the "bug" it goes up to 266 seconds, which
means 3 minutes and
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148265/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148266/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148270/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148267/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
About the "bug description", you wrote:
"Booting into a installed environment takes a few more seconds than normal."
It is not "a few more seconds"... but rather "a few more minutes"!
Each timeout is about 10 seconds according to dmesg, and there are about
a dozen or more. So it takes at least 2
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148264/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148268/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148272/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Title:
apport-collect done!
Do you need any other info before I start over with a clean install
(including workaround)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Title:
TV-out timeouts in
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148271/+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/1774845
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148269/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148273/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
apport information
** Tags added: apport-collected
** Description changed:
Booting into a installed environment takes a few more seconds than
normal.
WORKAROUND: Use kernel parameter:
video=SVIDEO-1:d
+ ---
+ ApportVersion: 2.20.9-0ubuntu7.1
+ Architecture: amd64
+
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148263/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148262/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Title:
Public bug reported:
This is the automated ubuntu-bug linux
as requested per ticket
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682921
>From the original bug where I posted (1731784) and the ticket I opened
upstream, this has been identified by Intel engineers as a regression in
the
Done with ticket:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1774845
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682921
Title:
sluggish system, kernel errors on Inspiron 1525
Just a short comment, I did the bug report without the workaround, hence
the linux boot command line is "standard" as a fresh install, without
the parameter "video=SVIDEO-1:d" that workarounds the bug.
I imagine it is more significant that way!
Should you need a report with the workaround
Ok, I originally posted on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731784
1731784 has been marked as duplicate as this one after I did an
"upstream" report (https://bugs.freedesktop.org/show_bug.cgi?id=106422)
and Intel engineers investigated to attach it to a "TV-Out" issue with
Hi, I will provide the confirmation (or not!) that this is a complete
workaround, along with the same confirmation on the "upstream" ticket I
opened for that bug: https://bugs.freedesktop.org/show_bug.cgi?id=106422
Same as Kevin, the hardware is not mine, and I have to wait to have
direct access
A workaround was offered "upstream" in Comment #11:
https://bugs.freedesktop.org/show_bug.cgi?id=106422#c11
I tested it successfully so far on my hardware (Inspiron 1525).
1. add "video=SVIDEO-1:d" to your kernel boot options
I still have to confirm the workaround has no other important side
Hello, since the ticket I reported for that bug on freedesktop.org has
now been moved to "high" importance by an Intel person, might I suggest
that this is also moved to "high" accordingly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have posted a full dmesg with the 'drm-tip' kernel compiled
especially.
Please see "upstream" (link above) for details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731784
Title:
system slow
More information.
I have narrowed it down:
16.04.1 - kernel 4.4.0-31-generic
==> Works OK with messages ("encoder detached but still enabled on pipe A.")
No visible slowdown apart for 3 or 4 stack traces in the log.
16.04.2 - kernel 4.8.0-36-generic
==> Shows the "time outs" bug
So there must
As requested above, I filed the bug at freedektop.
Here is the reference:
https://bugs.freedesktop.org/show_bug.cgi?id=106422
** Bug watch added: freedesktop.org Bugzilla #106422
https://bugs.freedesktop.org/show_bug.cgi?id=106422
--
You received this bug notification because you are a
Hi there, I am having this issue too on the same hardware.
This laptop is currently running 14.04 32 bits.
With 14.04 32 bits, there is a message in the log, but it has no effect
but spitting messages in the log!
With 18.04 64bits live, there is the "flip_done timed out" issue. Each one
seems
Public bug reported:
package grub-efi-amd64-signed 1.66.17+2.02~beta2-36ubuntu3.17 failed to
install/upgrade.
After an update crash this package was half installed and now it is
impossible to EFI-boot, I'm back in Legacy with no grub on my /dev/sda
(booting from an old Legacy install on
NOTE: can someone move the status to "Won't Fix" please, it is not
available to "regular users"!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499473
Title:
dash printf builtin does not honor \xNN
Well, I made some more research: I think this can be closed as
WON'T FIX
This seem to be a feature (not a bug) to comply exactly to POSIX,
**nothing more**.
Here is the related POSIX documentation:
http://www.unix.com/man-page/POSIX/1posix/printf/
It specifies octal escaping, and it also
Public bug reported:
VERSION AND CONTEXT
===
$ uname -a; lsb_release -a; dash --version; dpkg -s dash
Linux alain-Desktop 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14 21:42:59 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Thanks Christian for the heavy lifting on the mailinglist and bzr.
I didn't understand, on the FAQ, about yielding permissions to Canonical. Is
that about proposing patches on Launchpad itself, or does it also apply for
projects hosted on launchpad.
Anyway, to whomever, Canonical or upstream
[EDIT] Obviously I meant fancy mountpoints having spaces or \n, do *NOT*
break aa-status!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310598
Title:
AppArmor python tools fail to parse mounts
Ok, so *I fixed it!*
Sorry guys, the 'patch' process is a bit complicated here, so I'll just
give a diff to what I have done, and explain why:
$ diff aa-status aa-status_orig
137,140c137,140
for p in open(/proc/mounts,rb).readlines():
if p.split()[2].decode() == securityfs and \
After some months where it didn't seem to crash -or at least apport
didn't report anything-, now this is crashing again with the same stack
trace about reading my UTF-8/non-ascii mounts.
I'm sending new apports automatic crash reports.
Although, Christian, I would find it normal that it crashes
*** This bug is a duplicate of bug 1014229 ***
https://bugs.launchpad.net/bugs/1014229
After coordination with upstream, it is in fact a translation bug.
The French translation is misleading and tends to make you believe that
there will really be an update. As matter of fact the feature is
MMlosh points out the privacy issue that occurs with the current
configuration being ON by default without the user having explicitly
opted-in.
This is a fact (not an opinion!).
Although the request to get the XML is super clean (checked with wireshark) it
still leaks the user's IP to bunkus.org
The same bug exists on Nemo (should there be different bug report?)
It is less troublesome when you don't set Nemo as handling also your desktop,
because closing Nemo correctly frees the memory.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1
Thank you.
I'll coordinate with upstream as this is probably the best way to do
clean things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353694
Title:
Auto-Update process makes no sense!
To
You are very right Seth.
There could also be a cleaner method to get mounts via some system
calls instead of relying on a reading (pseudo) file. I say they could
because I never needed that in any of my programs, so didn't investigate
the topic.
If the only/easier way is to read a file
And on second thoughts, this bug was posted for Lucid (10.04).
Lucid is using version 7.4 of coreutils:
$ apt-cache show coreutils
Package: coreutils
Essential: yes
Priority: required
Section: utils
Installed-Size: 12988
Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
Hello, I don't know about this new status... I reported this bug at the
time of Lucid, now in Precise, we have version 8.13 of coreutils as apt-
get shows
$ apt-cache show coreutils
Package: coreutils
Essential: yes
Priority: required
Section: utils
Installed-Size: 5496
Maintainer: Ubuntu
YOU WOULD HAVE GUESSED...
---
Obviously we notice this buggy behaviour when we use directly Goto Location
and enter the address: dav://127.0.0.1/webdav
When using the dialog box under File Connect to server..., this does not
happen as there is only one
Public bug reported:
ENVIRONMENT:
-
Precise 64
Nautilus 3.4.2
$ uname -a nautilus --version
Linux zakhar-desktop 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
GNOME nautilus 3.4.2
WEBDAV:
I set up a local Apache
REFINED WORKAROUND:
--
Of course, if like in the case above, it is YOUR server, for YOUR local use,
there is a better way.
Whatever the password length, you bump the keep-alive time-out to an insane
value (600 secs!) so that you have a large amount of time to type
I reopened 'upstream'.
There is indeed no 'bug', as when you mark the pointer volatile, the
warning disappears.
But there is for sure either 'bad detection', or a detection of '*bar'
that can indeed be un-initialized but is reported as 'bar' being un-
initialized.
Thus it is not a 'bug' per se,
My bad, you can mark this bug as Solved/Invalid.
The lines 3 to 9 should read:
/*03*/ extern int
/*04*/ foo( p )
/*05*/ int * volatile p;
/*06*/ {
/*07*/ volatile int foobar,barfoo;
/*08*/ volatile int flag=0;
/*09*/ int * volatile bar;
As I was reporting, the pointer was not volatile, it's
Public bug reported:
Versions of Ubuntu and gcc:
-
(Precise amd64, out-of-the-box gcc)
$ LANG=ENG uname -a echo gcc -v
Linux zakhar-desktop 3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
Using built-in specs
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 12.04 LTS
Release:12.04
$ uname -a
Linux user-Notebook-PC 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
$ LANG=EN dpkg-query --list '*curl*' | grep ii
ii curl
1 - 100 of 159 matches
Mail list logo
