Please revert my above status change (which was done in error).
** Changed in: mesa (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735594
IIRC, some SIP providers "successfully" register all attempts as a
security/DOS protection technique (obviously, later, when an
[unauthorised] call is attempted, it fails.).
Perhaps, because there is never a SIP password authentication challenge,
this is why Linphone never prompts for a password.
Public bug reported:
13.10
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: fglrx-pxpress 0.4
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Wed Nov 13 09:36:25 2013
Public bug reported:
See screenshot attachment.
** Affects: gnome-system-monitor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/999899
Title:
** Attachment added: Look at the network History Y axis ticks
https://bugs.launchpad.net/bugs/999899/+attachment/3148167/+files/systemMonitor.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am no longer affected by this issue, due to the ext4 patch (in kernel
v2.6.30 and subsequent) which handles file replacement sub-optimally,
but more like ext3.
According to Theodore Ts'o post here:
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/317781/comments/54
it is still an bug
Apologies, this is a qualitative post --- but now that people are talking
about different processors, I'll contribute some fluffy info.
That said, I experienced many freezes per day on my Core Solo laptop when
doing dangerous operations (svn update, rsync, rm, etc.). Then I swapped
to a Core 2
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/23817282/Dependencies.txt
** Visibility changed to: Public
--
Replaced files truncated on upgrade on EXT4 filesystem, potentially leaving
system inoperable
https://bugs.launchpad.net/bugs/342142
You received this bug
@Chris
I am sure you are right. I was [mistakenly] thinking that Denial of
Service was a security issue (e.g. it would be easy for a user to crash
the system when a scheduled aptitude full-upgrade was happening,
potentially leaving the entire system inoperable).
--
Replaced files truncated on
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/23818138/Dependencies.txt
** Summary changed:
- .svn/entries files truncated if system crash while svn up on ext4
filesytem: working copy inoperable
+ .svn/entries files truncated if system crashes while svn up on ext4
Public bug reported:
Binary package hint: subversion
I am using the ext4 filesystem, and Jaunty Desktop Alpha.
If the system freezes (I assume due to independent reasons) while doing
an svn update, then various branches of the working copy are left
inoperable after restart because many of the
I can confirm that Subversion (on update) and aptitude update (or the
underlying dpkg?) can also be left in an inconsistent/broken state when
this occurs. Subversion ends up with many truncated .entries files
leaving the working copy unusable. Aptitude/dpkg ends up with truncated
versions of the
12 matches
Mail list logo
