Haven't seen this problem for a while and just tested on 14.04: Seems it
has been fixed somewhere in the last two years.
So I guess this bug report could be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Since some time ago I loose all of my 3 pinned tabs every morning while
my ~20 "normal" tabs never have disappeared.
Btw: My workaround at the moment is the add-on "session buddy". It auto
saves my tab session in the evening and I manually restore them every
morning.
--
You received this bug no
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 13.10
Release:13.10
$ uname -a
Linux mhassert 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
$gcc -dumpversion
4.8
$ ld -v
GNU ld (GNU Binutils for Ubuntu) 2.23.52.20130913
$ LC
gcc-4.8 4.8.1-10ubuntu9 in saucy-proposed fixes the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246802
Title:
STL std::nth_element bug (fixed upstream)
To manage notifications abou
Dmitrijs:
I don't see how this bug is related to any of the points mentioned in that
security notice.
On a closer look at the openSuse bug report comment #2 just mentions those
security fixes without directly claiming that they fix the bug itself. In
Comment #3 the bug was declared fixed, perhap
This bug or a similar is still present in 13.10 (and has been in 12.10
and 13.04):
I believe this is essentially the same as a bug report over at Novell:
https://bugzilla.novell.com/show_bug.cgi?id=819524
Seems strlen is being called on NULL pointers. As the bug report at
Novell has been fixed ve
** Description changed:
+ EDIT: adapted description according to SRU Bug Template
+
+ [IMPACT]
+
+ * impact on users:
+ Profiling an application with callgrind produces false results: The
application silently changes behavior because of false strstr() results in
certain cases.
+
+ * justifi
Hi Julian,
nice to see the patch made it into upcoming quatal/12.10.
Any chance to get it also into precise/12.04? After all it's a LTS
release and lot's of machines (especially development machines) won't
make the switch to 12.10 and so would be stuck with the bug for years.
--
You received th
Yes, compiling myself was of course the quick solution. I patched and
built the valgrind package from Ubuntu locally and it works like a
charm. Thanks again! Saves me lots of trouble.
There's no particular reason to care about other Ubuntu users. It's not
really an security issue or anything like
Hi Josef and Julian. Thanks for fixing the bug so fast!
As far as I understand the patches are for now only in cvs head? I'd really
love to get this fixed in the debian/ubuntu package as fast as possible. Do you
plan on releasing a patched version of valgrind-3.7.0 in the near future? Or
should
I built a patched version of the current valgrind package using
fix-VEX-PCMPxSTRx.patch
Attached is the output of debdiff.
I'v been using this patched version for a day now and it works fine for me.
** Patch added: "Output of debdiff including my previous patch"
https://bugs.launchpad.net/ubu
The attached patch is taken from the fix of the upstream bug report. I modified
it slightly to fit version 3.7.0 in the debian/ubuntu package:
- removed the second part as that function does not yet exist in 3.7.0
- Corrected line numbers of chunks to avoid warning when patch is applied.
** Patch
Setting to confirmed because it is confirmed and fixed upstream
** Changed in: valgrind (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027977
Title:
strstr(
Also created an upstream bug report:
https://bugs.kde.org/show_bug.cgi?id=303963
** Bug watch added: KDE Bug Tracking System #303963
https://bugs.kde.org/show_bug.cgi?id=303963
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Attachment added: "minimal test case"
https://bugs.launchpad.net/bugs/1027977/+attachment/3232950/+files/strstrtest.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027977
Title:
strstr() fun
Public bug reported:
$valgrind --version
valgrind-3.7.0
When an application that uses the strstr() function from the C standard library
is profiled with valgrind --tool=callgrind, the strstr() function produces
false results (at least) under the following conditions:
* the string s1 to search i
Just checked sudo's behavior regarding the login count. It consistently
uses the user "root" before and after the given command:
[BEGIN OF LOG]
[sudo] password for USER:
pam_mount(pam_mount.c:364): pam_mount 2.10: entering auth stage
pam_mount(pam_mount.c:553): pam_mount 2.10: entering session st
Hi, I'm affected too and would like to provide some additional
information:
I suspect this bug is not caused by _how often_ pam_mount is called but rather
a mixup of the user it is run under.
When running sudoedit, before the editor component is started, pam_mount always
tries to mount the parti
18 matches
Mail list logo
