[Bug 1283218] Re: fail to start
This affects me. I happen to notice this do symlink to the ehcache that red5-server depends on so not sure why it's not picking it up -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283218 Title: fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/red5/+bug/1283218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123483] Re: package red5-server 1.0~svn4279-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This is related to #1283218 on Utopic and probably Trusty too -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123483 Title: package red5-server 1.0~svn4279-1 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/red5/+bug/1123483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 856481] Re: gnome-shell is not installable after last upgrade
Yes, this happened to me as well, I installed from a beta1 DVD and told it to automatically download updates. Given gnome-shell isn't there by default, it seems I'm forced to Unity for a few days (i.e. I didn't have the option about partial upgrade that you normally get form update- manager -d). Anyway, would be good to know when this resolves :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/856481 Title: gnome-shell is not installable after last upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/856481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806548] Re: [xorg-edgers] Desktop gets messed
Yes, the issue with this is: xserver-xorg-video-intel 2:2.15.0+git20110706.0be47f45 If you are using an Intel graphics chipset (I have a Thinkpad with a similar setup and had similar issues). The best way to work round this for now is to download and install: https://launchpad.net/~xorg-edgers/+archive/ppa/+build/2589725/+files /xserver-xorg-video- intel_2.15.0%2Bgit20110624.471115a9-0ubuntu0sarvatt_amd64.deb (From page https://launchpad.net/~xorg- edgers/+archive/ppa/+build/2589725) This should get round things for the short term. I also noticed when I installed any later versions of this package that were built between now and 471115a9 that my X display would randomly go black and refuse to switch modes (i.e. switching to a TTY by pressing Ctrl + Alt + F2, etc wouldn't switch the display, but otherwise did allow me to switch to TTY to gracefully reboot by three finger salute). Likewise SAK (Sys Req + Alt Gr + K wouldn't reset X) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806548 Title: [xorg-edgers] Desktop gets messed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/806548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 529011] [NEW] Ruby 1.9.1 leaks memory in Lucid on AMD64
Public bug reported: Binary package hint: ruby1.9.1 I reported this, originally at #514322 I've put in another report as this affects Lucid as well as Karmic. This bug only seems to affect AMD64 platforms. The latest SVN trunk of Ruby 1.9 has been fixed for the last few weeks since it was marked as fixed at http://redmine.ruby- lang.org/issues/show/1392 A simple test case for this is under AMD64: ./ruby -e 'loop { Class.new.__send__ :include, Module.new }' ./ruby -e 'loop { Module.new.extend Module.new }' Running the above will leak memory. This is easy to see through any process listing application, such as top, or GNOME task manager. This will happen until the system runs out of memory, or the offending Ruby process is killed. Given that most people using Ruby 1.9.x will be Rails developers using Rails in development (debug) mode who wish to migrate their code base from 1.8.x so it's compatible with 1.9.x, I would guess that it is in the interest in the Ruby Rails community to utilize the latest 1.9.x branch were possible. Also, given that in the Ruby community that Ruby 1.9 is known to be a moving target, developers will want to test against the latest version (compared to 1.8.x which is supposed to fairly static and thus considered stable). Will it be asking too much to do this, (as I'm guessing the packages are pulled upstream from Debian, I'm guessing this will need to be passed on to Debian maintainers?) ** Affects: ruby1.9.1 (Ubuntu) Importance: Undecided Status: New -- Ruby 1.9.1 leaks memory in Lucid on AMD64 https://bugs.launchpad.net/bugs/529011 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 514322] [NEW] Ruby 1.9.1 leaks memory when using Module.include
Public bug reported: Binary package hint: ruby1.9.1 I've discovered, along with a handful of others that Ruby 1.9.1 leaks memory when using Module.include This is major issue for those using Ruby in an persistent environment (i.e. Rails processes which are typically daemonised) as the host machine will probably run out of memory. A simple test-case is: ruby -e 'loop { Module.new.extend Module.new }' I've nudged the Ruby developers upstream about this over here: http://redmine.ruby-lang.org/issues/show/1392 There is now a patch (pending as I speak) which is going to be committed to the 1.9.2 trunk. Given that it looks like lucid is still working from 1.9.1, and there will be Karmic users utilizing Ruby 1.9.1 it would be highly desirable if this can be back-ported to Lucid and Karmic. ** Affects: ruby1.9.1 (Ubuntu) Importance: Undecided Status: New ** Tags: extend include leak memory ruby1.9 ** Tags added: extend include leak memory ruby1.9 -- Ruby 1.9.1 leaks memory when using Module.include https://bugs.launchpad.net/bugs/514322 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 479489] Re: disable Super+MiddleClick by default
Agreed, this totally annoys the hell out of me. I do this by accident regularly on my laptop when intending to do Alt + Middle mouse and drag to resize, because the the keyboard layout / spacing is physically a little different from a typical keyboard. -- disable Super+MiddleClick by default https://bugs.launchpad.net/bugs/479489 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 450048] Re: xorg memory use
Why has this been marked as invalid. I have found the ATI driver seems to either be leaking, or eating far too much RAM on my 4Gb system (to the point where it swaps a lot under load). Installing the ATI driver via envyng-core resolved my memory issues. Clearly the default binary blob shipped seems to have some issues still. -- xorg memory use https://bugs.launchpad.net/bugs/450048 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 428619] Re: pulseaudio crackle/distortion with cs46xx on latest update
I can confirm that I also have this. My active sound card is the onboard sound on my Asus M2N32 WS Pro motherboard. It's using a AD1988B (Analog Devices) chip, and it's driving spare! -- pulseaudio crackle/distortion with cs46xx on latest update https://bugs.launchpad.net/bugs/428619 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 363412] Re: Xinerama does not work on jaunty RC with fglrx driver
FYI, it appears Bug #364497 is a copy of this too. -- Xinerama does not work on jaunty RC with fglrx driver https://bugs.launchpad.net/bugs/363412 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 363412] Re: Xinerama does not work on jaunty RC with fglrx driver
Any news on this? I know it's not something totally in your control because down to ATI/AMD to sort out their blob's. Would be nice to be able to use Jaunty -- Xinerama does not work on jaunty RC with fglrx driver https://bugs.launchpad.net/bugs/363412 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 363412] Re: Xinerama does not work on jaunty RC with fglrx driver
** Attachment added: lspci -vvnn http://launchpadlibrarian.net/26000842/pci.txt -- Xinerama does not work on jaunty RC with fglrx driver https://bugs.launchpad.net/bugs/363412 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 363412] Re: Xinerama does not work on jaunty RC with fglrx driver
** Attachment added: X Org log http://launchpadlibrarian.net/26000848/Xorg.0.log -- Xinerama does not work on jaunty RC with fglrx driver https://bugs.launchpad.net/bugs/363412 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 363412] Re: Xinerama does not work on jaunty RC with fglrx driver
** Attachment added: Old X Org log http://launchpadlibrarian.net/26000854/Xorg.0.log.old -- Xinerama does not work on jaunty RC with fglrx driver https://bugs.launchpad.net/bugs/363412 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 363412] [NEW] Xinerama does not work on jaunty RC with fglrx driver
Public bug reported: Binary package hint: xorg-driver-fglrx I'm using an ATI HD 2600 pro and find that enabling Xinerama causes X to produce a garbled display (basically looks like the the memory from boot screen at top but garbled / wrong colours, so I assume it's set the screen resolution but hasn't cleared the frame buffer). It appears the screen resolution is set on both screens, but X seems to hang shortly after. I notice the hard-disk goes for a second or so, but then then my machine completely freezes. Obviously I'm expecting both screens to work as a large desktop and the system not to crash in the process (excuse the sarcasm, it did ask me in the guidelines to state what i expect to happen =p) Ctrl Alt Backspace / AltGr SysReq / 3 finger salute doesn't seem to be acknowledged, so I get the impression this is a kernel freeze. This is damn annoying for me (as I really need 2 screens). I understand it's not totally something that is under the control of Ubuntu Developers directly, but I assume you communicate with ATI and have prodding authority when it comes to making them patch up their stinking code blob. Both my screens are the same (DVI digital) at 1600x1200. I've using a fresh install of the release candidate (as I released it's only since the beta fglrx got updated for xserver 1.6), with all updates installed. I can get independent dual screens to work (i.e. work as independent X displays, however compiz doesn't fully work here) and for both displays to mirror a screen with full acceleration (compiz is fine here). Intrepid and Gutsy seemed fine under this setup, so I really would like this to work in jaunty as well if you can squeeze this in between now and the final release. I'm not too sure what else you want from me, would a lspci -vvv be of any help? This is similar to bug #40544, however I've opened a new report as this affects Jaunty, not Dapper, and so I assume the causes / reasons for the bug are very different. Thanks for your time. Jase. ** Affects: linux-restricted-modules-2.6.24 (Ubuntu) Importance: Undecided Status: New -- Xinerama does not work on jaunty RC with fglrx driver https://bugs.launchpad.net/bugs/363412 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 287811] Re: Emptying Trash Fails with 'Error while expunging folder'
Hi, I think what I suggested at https://answers.launchpad.net/ubuntu/+source/evolution/+question/50690 should fix things. Evolution changed it's mail format recently, so the searching for ev-summary files doesn't do anything, which is why that fix doesn't work in Ibex. instead remove the index / cmeta / index.data files -- Emptying Trash Fails with 'Error while expunging folder' https://bugs.launchpad.net/bugs/287811 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