[Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
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 Title: [regression] compiz crashes after Mesa upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 566075] Re: no way to specify the password
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. It seems that persisting an account's password should be decoupled from the future possibility of any provider needing it. I.e. the password is a property of the account, not the provider's implementation (SIP stack's behaviour) at some arbitrary point in the future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/566075 Title: no way to specify the password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linphone/+bug/566075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250746] [NEW] package fglrx-pxpress 0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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 DuplicateSignature: package:fglrx-pxpress:0.4:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-11-01 (11 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: fglrx-pxpress Title: package fglrx-pxpress 0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fglrx-pxpress (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250746 Title: package fglrx-pxpress 0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-pxpress/+bug/1250746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999899] Re: system monitor 3.4.1 shows incorrect numbers for more than 3.0 GiB/s
** 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. https://bugs.launchpad.net/bugs/999899 Title: system monitor 3.4.1 shows incorrect numbers for more than 3.0 GiB/s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/999899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999899] [NEW] system monitor 3.4.1 shows incorrect numbers for more than 3.0 GiB/s
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: system monitor 3.4.1 shows incorrect numbers for more than 3.0 GiB/s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/999899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342164] Re: ".svn/entries" files truncated if system crashes while "svn up" on ext4 filesytem: working copy inoperable
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 in svn though. -- ".svn/entries" files truncated if system crashes while "svn up" on ext4 filesytem: working copy inoperable https://bugs.launchpad.net/bugs/342164 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 330824] Re: Soft lockups (freezes) when deleting files from ext4 partitions on 2.6.28
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 Duo, and when doing these same operations, I got about the same number "freezes", only now they recovered faultlessly (so far...) after second or two. After an upgrade to 2.6.30-020630-generic #020630 from the Ubuntu Kernel-ppa mainline, (to solve unrelated HP laptop sound issues), I have not experienced any more "freezes" temporary, or otherwise. c. 2009/7/16 Jared Heath > It happened very frequently on my Dual Core i86 based system (never got > more than 5 single rm commands off without a hang before I went to the > higher kernel) so it certanly can happen on multi-core systems often. > > Your theory on race conditions is interesting though--it certainly > exhibits the behavior of a race that goes infinite and does not get > caught. > > -- Soft lockups (freezes) when deleting files from ext4 partitions on 2.6.28 https://bugs.launchpad.net/bugs/330824 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342164] Re: ".svn/entries" files truncated if system crash while "svn up" on ext4 filesytem: working copy inoperable
** 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 filesytem: working copy inoperable -- ".svn/entries" files truncated if system crashes while "svn up" on ext4 filesytem: working copy inoperable https://bugs.launchpad.net/bugs/342164 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342142] Re: Replaced files truncated on upgrade on EXT4 filesystem, potentially leaving system inoperable
@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 upgrade on EXT4 filesystem, potentially leaving system inoperable https://bugs.launchpad.net/bugs/342142 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342164] [NEW] ".svn/entries" files truncated if system crashes while "svn up" on ext4 filesytem: working copy inoperable
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 "./svn/entires" files are truncated. That is, they exist, but are zero length. I assume this bug is caused by precisely this reason: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/317781 for which Theodore Ts'o suggests what application programmers should be doing when *overwriting* important files here: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/317781/comments/54 How to reproduce: 1) Working copy checked out on an ext4 file system with default settings. 2) $ svn up 3) Pull the power out of your machine (assuming a normal Desktop) before the previous command exits. This is obviously too extreme, but the *kernel* needs to be crashed uncleanly. 4) Restart 5) $ svn up svn: Working copy '.' locked svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) 6) $ svn cleanup svn: Can't read file 'foo/bar/aaa/.svn/entries': End of file found Find shows 39 zero length entries files in my working copy (of 52000 files): $ find -size 0c | grep ".svn/entries" | wc -l 39 $ find | wc -l 52363 There are many other zero length files, so other SVN metadata files may be affected. What I expect to happen: If and upgrade is interrupted, then I expect that, running "svn cleanup && svn update" in the WC should finish doing what I originally started. More info: $ apt-cache policy subversion subversion: Installed: 1.5.4dfsg1-1ubuntu2 Candidate: 1.5.4dfsg1-1ubuntu2 Version table: *** 1.5.4dfsg1-1ubuntu2 0 500 http://za.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: subversion 1.5.4dfsg1-1ubuntu2 ProcEnviron: PATH=(custom, user) LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: subversion Uname: Linux 2.6.28-9-generic i686 ** Affects: subversion (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- ".svn/entries" files truncated if system crashes while "svn up" on ext4 filesytem: working copy inoperable https://bugs.launchpad.net/bugs/342164 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342142] Re: Replaced files truncated on upgrade on EXT4 filesystem, potentially leaving system inoperable
** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 317781] Re: Ext4 data loss
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 files being upgraded (e.g. libpng12.so.0.27.0). -- Ext4 data loss https://bugs.launchpad.net/bugs/317781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
