[Bug 70535] Re: nautilus crashes when copying a 4G file on a vfat volume
Ok, I have just read a lot about file size limitations on FAT32 being 4GB - before I post a dup bug while copying a 6GB file to an SMB share (the underlaying FS is ext3 AFAIK) should SMBFS have a problem with files >2GB?? ** Attachment added: "_usr_bin_nautilus.1000.crash" http://librarian.launchpad.net/7733750/_usr_bin_nautilus.1000.crash -- nautilus crashes when copying a 4G file on a vfat volume https://bugs.launchpad.net/bugs/70535 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87947] Re: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
Thanks for testing! The handoff patches are based on libxcb git commit 7a74ba3d0212f9bfe021d6da9070f71cbc53f85b and libX11 git commit 64325f38bab082a8e0e9ce779a8e582de5c8588e. It'll probably apply against newer versions of libX11, but there's been a lot of work in libxcb since we started trying to make this new handoff approach go, so I'm not surprised the patches don't apply. -- xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/87947 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 86103] Re: azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
On 10/23/07, Luke Hoersten <[EMAIL PROTECTED]> wrote: > Googling the error shows that this is a widespread problem. Sun claims it's > already fixed: > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373 > Perhaps the package just needs to be updated or patched? Sun reports the Java bug is fixed in JDK7 beta 22: http://download.java.net/jdk7/changes/jdk7-b22.html However, the release notes for JDK5 and JDK6 do not mention fixes for this bug, as far as I can tell. The fix was straightforward, since correct code was already being used in Solaris builds. But the Sun engineers were concerned about making sure it passed all of their test suite, which is why it took a while. I don't know if we'll see a similar fix from the JDK5 and JDK6 teams, but I sure hope so. -- azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/86103 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 86103] Re: azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
On 10/27/07, Luke Hoersten <[EMAIL PROTECTED]> wrote: > I don't think it's just the JDK. Many people trying to use the JRE are > having the same problem ... Yes, this is a generic Java issue. The JRE is a subset of the JDK that contains almost all the same code. The distinction is too troublesome for normal discussion. > Does anyone know of a workaround or patch for this problem? Sure. You can turn off Xinerama support in your X server, or as Josh Triplett documented in June, you can effectively disable Xinerama support in Java: https://bugs.freedesktop.org/show_bug.cgi?id=9336#c15 Upstream libxcb also now has a variant of the Novell sloppy lock patch, so that you can set an environment variable to disable the asserts when you run broken applications, like Java before JDK7 beta 22. Furthermore, experimental packages of JDK7 are available for Ubuntu Gutsy and are expected to work with Debian as well. http://lists.debian.org/debian-java/2007/08/msg00028.html > Here's a list of some other bug reports: All the bug reports you listed are already fixed, both upstream and in Debian, Gentoo, and I assume in Ubuntu and elsewhere. None of them are relevant to the Java issue. Why do you bring them up? -- azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/86103 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 86103] Re: azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
On 10/27/07, James Stansell <[EMAIL PROTECTED]> wrote: > Ubuntu Gutsy repositories have the icedtea packages based on JDK7 beta 21. > The Hardy archives have the beta 22 packages. Fascinating, and good for them! I didn't know Ubuntu had icedtea integrated in any sense yet. For the record, though, the repository I referred to has icedtea beta 22 built for Gutsy (on amd64). -- azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/86103 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 86103] Re: azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
On 10/16/07, Dirk R. Gently <[EMAIL PROTECTED]> wrote: > A library is the issue? NWN worked fine for me until I added the > "Undrentide" expansion pack. Seems related to the > /nwn/en/miles/libmss.so.6.5.2 file. I don't have NWN so I can't reproduce your issue. It's unrelated to the Java bug (which Sun has acknowledged and they intend to release a fix), so would you open a new bug report and include at least the output of `ldd /nwn/en/miles/libmss.so.6.5.2`, and preferably a backtrace from gdb? -- azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/86103 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32415] Bluetooth Mouse and Keyboard pairing broken in Dapper/Edgy/Feisty/ and now Hardy
I'm using the Logitech diNovo Media Desktop Laser, and Hardy/8.04 64 bit. I seem to have the issue that requires unplug, and plug of the bluetooth dongle. All the mouse buttons (except the tilt wheel) work after some tinkering, but I still can't get the bluetooth to connect at boot. Let me know if I can help by providing any info. (I'm new to Linux [this month!]) But the whole newbie thing, still, has given me less fits than Vista Ultimate 64. -- Apple Bluetooth Mouse and Keyboard pairing broken in Dapper/Edgy/Feisty https://bugs.launchpad.net/bugs/32415 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 86103] Re: azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
On 11/12/07, Kow <[EMAIL PROTECTED]> wrote: > If I reapply the "allow sloppy locks" workaround patch to libxcb the > problem is gone. By "the problem", you mean the stack trace you just reported? That's very strange. I can't find anything related to Xlib or XCB near the top of the stack traces you provided, though the memory map confirms that you are using XCB. A variant of the "allow sloppy locks" patch has been committed upstream in XCB and is in the recent 1.1 release, so hopefully it will make it into Ubuntu in the near future. I dunno, maybe they're waiting for me to roll a new Debian package, which I haven't had time to do yet. :-/ -- azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/86103 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 87390] Re: c->xlib.lock
On 12/18/07, Che Guevara <[EMAIL PROTECTED]> wrote: > Setting back to confirmed as this bug is back for hardy If you can confirm this bug, then you have an obligation to provide a lot more information. Many quite different problems were reported in this Launchpad bug, and many things have changed since they were originally reported. I still consider this particular report resolved, until proven otherwise. 0) Are all your packages fully up to date? 1) What did you test? 2) How did it break? 3) Provide a backtrace from the assertion failing. (libxcb1.1 now automatically generates one for you, on glibc systems like Linux.) You may need to install debug packages to get a complete backtrace. 4) What version do you have installed of any libraries in the backtrace? (I don't have an Ubuntu install handy, so don't just tell me "the newest ones"--I don't know if that's current from upstream.) 5) Does your test work when LIBXCB_ALLOW_SLOPPY_LOCK is set? In other words, *please* read the history of this bug report and answer the questions already given. :-) -- c->xlib.lock https://bugs.launchpad.net/bugs/87390 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl
Josh and I just announced a set of changes to XCB and Xlib/XCB which, among other things, should address all the outstanding assertion failures that we know of. Could anyone experiencing this bug please build XCB and Xlib with the patches found at http://lists.freedesktop.org/archives/xcb/2008-March/003347.html and retest? -- hardy, locking assertion failure, xorg/libsdl https://bugs.launchpad.net/bugs/185311 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 87947] Re: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
Josh and I just proposed a set of changes to XCB and Xlib/XCB which, among other things, should address all the outstanding assertion failures and synchronization problems that we know of. Could anyone experiencing this bug please build XCB and Xlib with the patches found at http://lists.freedesktop.org/archives/xcb/2008-March/003347.html and retest? -- xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/87947 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 86103] Re: azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
Josh and I just proposed a set of changes to XCB and Xlib/XCB which, among other things, should address all the outstanding assertion failures and synchronization problems that we know of. Could anyone experiencing this bug please build XCB and Xlib with the patches found at http://lists.freedesktop.org/archives/xcb/2008-March/003347.html and retest? -- azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/86103 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 88815] Re: Sluggish rendering since xorg 7.2 update
The x11perf results are a known issue, but not obviously significant. (How many apps do you have that use the X NoOperation request?) Despite our belief that the "slow" requests have almost no impact on real applications, we are working on improvements in this area. However, I believe the bug you actually experienced with metacity is identical to https://bugs.freedesktop.org/show_bug.cgi?id=10644, which Josh Triplett and I believe is fixed in libX11 git. Can you confirm that current libX11 from upstream git fixes metacity's performance for you? Assuming it does, could the libX11 maintainer for Ubuntu please stop building libX11 without XCB? -- Sluggish rendering since xorg 7.2 update https://bugs.launchpad.net/bugs/88815 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86103] Re: azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
The Neverwinter Nights issue is unrelated to the bug originally reported here. The bug likely lies in a library that NWN is using, rather than in the game itself, and so is likely fixable. A backtrace would help in tracking down the cause of that failure. Regarding the Sun Java bug, according to Josh Triplett: > I worked with jcristau and christoph4 via IRC on #debian-x, and we managed to > track down the problem with broken locking in Sun Java 1.5 and 1.6. It only > occurs if Java finds the Xinerama extension, at which point it does something > broken with locking and triggers the assertion. If Java never finds the > Xinerama extension, it doesn't trigger the assertion for broken locking. > > The following workarounds address this problem: > > For sun-java5-bin: > sed -i 's/XINERAMA/FAKEEXTN/g' > +/usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/lib/i386/xawt/libmawt.so > > For sun-java6-bin: > sed -i 's/XINERAMA/FAKEEXTN/g' > +/usr/lib/jvm/java-6-sun-1.6.0.00/jre/lib/i386/xawt/libmawt.so > > The same fix (applied to the appropriate file) might work for other > proprietary JDKs. -- azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/86103 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86103] Re: azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
The Neverwinter Nights issue is unrelated to the bug originally reported here. The bug likely lies in a library that NWN is using, rather than in the game itself, and so is likely fixable. A backtrace would help in tracking down the cause of that failure. Regarding the Sun Java bug, according to Josh Triplett: > I worked with jcristau and christoph4 via IRC on #debian-x, and we managed to > track down the problem with broken locking in Sun Java 1.5 and 1.6. It only > occurs if Java finds the Xinerama extension, at which point it does something > broken with locking and triggers the assertion. If Java never finds the > Xinerama extension, it doesn't trigger the assertion for broken locking. > > The following workarounds address this problem: > > For sun-java5-bin: > sed -i 's/XINERAMA/FAKEEXTN/g' > +/usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/lib/i386/xawt/libmawt.so > > For sun-java6-bin: > sed -i 's/XINERAMA/FAKEEXTN/g' > +/usr/lib/jvm/java-6-sun-1.6.0.00/jre/lib/i386/xawt/libmawt.so > > The same fix (applied to the appropriate file) might work for other > proprietary JDKs. -- azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/86103 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91077] Re: Closing glxgears window causes xcb_xlib_lock assertion and sound interruption
We believe this bug is fixed in current upstream libX11 git. -- Closing glxgears window causes xcb_xlib_lock assertion and sound interruption https://bugs.launchpad.net/bugs/91077 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90072] Re: [feisty5] kcmshell crashes on closing following administrator mode
We believe this bug is fixed in current upstream libX11 git. -- [feisty5] kcmshell crashes on closing following administrator mode https://bugs.launchpad.net/bugs/90072 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 89211] Re: Monitor & Display (in System Settings) is always crashing
We believe this bug is fixed in current upstream libX11 git. -- Monitor & Display (in System Settings) is always crashing https://bugs.launchpad.net/bugs/89211 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kde-systemsettings in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 96703] Re: Kubuntu System Settings crashes on exit
We believe this bug is fixed in current upstream libX11 git. -- Kubuntu System Settings crashes on exit https://bugs.launchpad.net/bugs/96703 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95266] Re: Updated libxcb1 crashes the system.
Can you supply a backtrace for these crashes? -- Updated libxcb1 crashes the system. https://bugs.launchpad.net/bugs/95266 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87390] Re: c->xlib.lock
We believe that current libX11 from upstream git fixes the problems when GL-using apps exit on systems with the proprietary nVidia driver. To the people who reported other bugs here: please ensure your X libraries are up-to-date, and if you can still reproduce the problem please supply a backtrace. -- c->xlib.lock https://bugs.launchpad.net/bugs/87390 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99667] Re: [apport] beryl crashed with SIGSEGV
The stack trace looks completely corrupt. I find it very unlikely that the crash actually occurred in xcb_poll_for_event. ** Summary changed: - [apport] beryl crashed with SIGSEGV in xcb_poll_for_event() + [apport] beryl crashed with SIGSEGV -- [apport] beryl crashed with SIGSEGV https://bugs.launchpad.net/bugs/99667 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99560] Re: vmware does not run on feisty because of assertion failure in libxcb
Can you supply a backtrace for this problem? -- vmware does not run on feisty because of assertion failure in libxcb https://bugs.launchpad.net/bugs/99560 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99385] Re: vmware reporting libxcb not found after upgrade
Since the libraries exist and yet aren't being found by the dynamic linker, it seems pretty clear that this is not an XCB bug. Sounds like an Ubuntu packaging bug, perhaps. -- vmware reporting libxcb not found after upgrade https://bugs.launchpad.net/bugs/99385 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99385] Re: vmware reporting libxcb not found after upgrade
On further thought, it sounds like Ubuntu needs to supply a 32-bit version of libxcb. -- vmware reporting libxcb not found after upgrade https://bugs.launchpad.net/bugs/99385 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88906] Re: synergyc crashes when opening a new gnome-terminal tab
Can you supply a backtrace for this problem? -- synergyc crashes when opening a new gnome-terminal tab https://bugs.launchpad.net/bugs/88906 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97604] Re: [apport] kicker crashed with SIGSEGV
The mention of _xcb_unlock_io looks very much like stack corruption. I doubt that the segfault actually occurred in XCB. ** Summary changed: - [apport] kicker crashed with SIGSEGV in _xcb_unlock_io() + [apport] kicker crashed with SIGSEGV -- [apport] kicker crashed with SIGSEGV https://bugs.launchpad.net/bugs/97604 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96901] Re: [apport] gnome-panel crashed with SIGSEGV
Given that the crash occurred in malloc, this sounds like arena corruption rather than an XCB bug. -- [apport] gnome-panel crashed with SIGSEGV https://bugs.launchpad.net/bugs/96901 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87947] Re: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
Per the debian-devel-announce message, please make sure your X libraries are up to date. If you can still reproduce the problem, can you supply a backtrace? -- xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/87947 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90072] Re: [feisty5] kcmshell crashes on closing following administrator mode
Josh Triplett and I are doing the upstream release wrangling right now. I expect we'll release libX11 1.1.2 tomorrow. -- [feisty5] kcmshell crashes on closing following administrator mode https://bugs.launchpad.net/bugs/90072 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87351] Re: Xorg uses 100% CPU
This doesn't sound like an XCB-related bug, especially since Ubuntu currently isn't using XCB, so I've marked it no longer a duplicate of #88815. ** This bug is no longer a duplicate of bug 88815 Sluggish rendering since xorg 7.2 update -- Xorg uses 100% CPU https://bugs.launchpad.net/bugs/87351 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87947] Re: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
I believe this bug is now fixed in upstream libX11 git. http://gitweb.freedesktop.org/?p=xorg/lib/libX11.git;a=commitdiff;h=c2f88cdf5cd9c94b77e5bfdac572b5ac06ab4aa8 ** Changed in: libx11 (Debian) Sourcepackagename: libxcb => libx11 Bugwatch: Debian Bug tracker #401571 => Debian Bug tracker #427296 Status: Unconfirmed => Unknown ** Changed in: libx11 (Ubuntu) Sourcepackagename: fcitx => libx11 Status: Unconfirmed => Confirmed -- xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/87947 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232476] Re: Xlib can deadlock when using mutlithreaded
I think the original poster's problem should have been solved with the socket-handoff rework in newer libX11/libxcb, such as the versions Norbert most recently reported success with from Jaunty. It isn't obvious to me that Karol's bug or Norbert's locking assertion failure were the same bug as the original post though. Of course the locking assertion failures are no longer detected in socket-handoff versions either, so that problem has disappeared as well. -- Xlib can deadlock when using mutlithreaded https://bugs.launchpad.net/bugs/232476 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 1823055] [NEW] krb5-user fails to install on 18.04 AMD64
Public bug reported: When installing the package krb5-user(1.16-2build1) it fails due to dependency on libkrb5-3. Apt-Get is expecting 1.16-2build1 but only 1.16-ubuntu0.1 is available for the libkrb5-3 package ** Affects: krb5 (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/1823055 Title: krb5-user fails to install on 18.04 AMD64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1823055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823055] Re: krb5-user fails to install on 18.04 AMD64
current universe repo for 18.04.2 was missing causing the conflict. ** Changed in: krb5 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823055 Title: krb5-user fails to install on 18.04 AMD64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1823055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823055] Re: krb5-user fails to install on 18.04 AMD64
I was missing the universe repo. I actually just resolved it and came here to say make sure the Universe repo is enabled. It appears to be a known issue with the Ubuntu 18.04.1 installer not enabling this repo by default -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823055 Title: krb5-user fails to install on 18.04 AMD64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1823055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1823055] Re: krb5-user fails to install on 18.04 AMD64
This was an in-house template virtual machine with a base 18.04 server installer. I'm not 100% if it was from 18.04 or 18.04.1. I have since corrected the issue and generated a new template so we won't have to worry about it in the future :) On Wed, Apr 3, 2019 at 2:25 PM Andreas Hasenack wrote: > Correct, thanks for letting us known. This but in the 18.04 installer is > nowadays fixed. If you got it with the latest installer > (http://cdimage.ubuntu.com/releases/18.04.2/release/) then it's a > regression. Can you please verify which iso image you used? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1823055 > > Title: > krb5-user fails to install on 18.04 AMD64 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1823055/+subscriptions > -- Jamey Steinmann 407.697.0197 jameysteinm...@gmail.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823055 Title: krb5-user fails to install on 18.04 AMD64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1823055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
