[Bug 40701] Re: creating a folder to computer not permitted but folder listed anyway
gnome-vfs has been deprecated and superseded by gio/gvfs since GNOME 2.22, hence mass-closing many of the gnome-vfs requests/bug reports. This means that gnome-vfs is NOT actively maintained anymore, however patches are still welcome. If your reported issue is still valid for gio/gvfs, please feel free to file a bug report against glib/gio or gvfs. @Bugzilla mail recipients: query for gnome-vfs-mass-close to get rid of these notification emails all together. ** Changed in: gnome-vfs (Ubuntu) Status: Triaged => Invalid ** Changed in: gnome-vfs (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/40701 Title: creating a folder to computer not permitted but folder listed anyway To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/40701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1201709] Re: Couldn't change keyring password
*** This bug is a duplicate of bug 1072510 *** https://bugs.launchpad.net/bugs/1072510 ** This bug has been marked a duplicate of bug 1072510 Couldn't change keyring password -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1201709 Title: Couldn't change keyring password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1201709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188391] Re: vmware tools dont compile with hardy
Hi Vincent, I actually have a somewhat kludgy script that rebuilds these modules from sources on every reboot using module-assistant. There's probably a better way to do this, but my way seems to work just fine. Also the version of tools I'm getting with this repository seems to work much better than the version of tools that shipped with the latest patch of ESX... at the very least this version compiles and has proper 64-bit guest support. :) -- vmware tools dont compile with hardy https://bugs.launchpad.net/bugs/188391 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 188391] Re: vmware tools dont compile with hardy
FYI, VMware does provide packages and even apt repositories with precompiled versions of both kernel modules and VMware Tools for Ubuntu 8.04 and 8.04.1 for ESX version 3.5: http://www.vmware.com/download/packages.html -- vmware tools dont compile with hardy https://bugs.launchpad.net/bugs/188391 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 188391] Re: vmware tools dont compile with hardy
I am in the same position, but quite frankly I am giving up on this. I'm just somewhat annoyed that Canonical decided to kill off the open-vm- tools package that I know to be working just fine, at least with VMware ESX 3.0.x. fadyek: The fix I posted does have ESX-esque naming conventions for the modules. The fact of the matter is, I have a feeling that if you try open-vm-tools (maybe get it off packages.debian.org, because ubuntu killed their for some reason, even though they used to have it... no vlue as to why!), I have a feeling it will work. Since you're using VirtualBox, I'm not sure if you still want to try this for the purposes of experimentation... :) -- vmware tools dont compile with hardy https://bugs.launchpad.net/bugs/188391 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 236066] Re: Resume from STR:Network dhcp timeouts
Clicked accidentally, my apologies. Please disregard. ** Changed in: linux (Ubuntu) Status: New => Invalid -- Resume from STR:Network dhcp timeouts https://bugs.launchpad.net/bugs/236066 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 188391] Re: vmware tools dont compile with hardy
Fadyek, I'm glad you got a solution. Your experience brings me to another point: is VMware going to release a proper VMware Tools package for Hardy or not? Debian users at least get the option of using open-vm- tools, which Ubuntu has removed from its package repositories (I am assuming this is in preparation for the official VMware package and not some political/contractual restriction; I would be deeply troubled if the latter was the case). I don't mean to nag, but it's been exactly one month since the original announcement of VMware's intentions to provide official packages (https://bugs.launchpad.net/ubuntu/+source/vmware- server/+bug/188391/comments/6). Any updates on that front? Thanks! -- vmware tools dont compile with hardy https://bugs.launchpad.net/bugs/188391 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 188391] Re: vmware tools dont compile with hardy
Fadyek, please check my previous post on this bug, it contains an attachment which has the tarballs you seek, with the exception of vmppuser.tar. Hope this helps! :) Also try replacing the tarballs from my package to the one you're trying to compile, unless you're sure it's vmppuser.tar specifically that fails to build. -- vmware tools dont compile with hardy https://bugs.launchpad.net/bugs/188391 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 188391] Re: vmware tools dont compile with hardy
Seeing how there are no updates on this bug, I feel compelled to share the following workaround. Here's what one needs to do to get VMware ESX 3.0.2's latest tools to compile properly on Hardy JeOS: 1. Start VMware Tools Install. Mount /media/cdrom (or whatever you call your CD-ROM drive) and grab the tools tarball from it. At the time of writing, the latest tarball name was VMwareTools-3.0.2-69376.tar.gz. 2. Copy the above mentioned tarball to root's home directory. Untar it the usual way (tar xvfz VMwareTools-3.0.2-69376.tar.gz). 3. Download the open-vm-tools source package from http://sourceforge.net/project/showfiles.php?group_id=204462 (I used the 2008.04.14 release; although there's a newer one now, I haven't tested it yet). Again, in my case the open-vm-tools tarball was named open-vm-tools-2008.04.14-87182.tar.gz. 4. Untar the open-vm-tools tarball the usual way as well with tar xvfz open-vm-tools-2008.04.14-87182.tar.gz. 5. For each subdirectory in open-vm-tools-2008.04.14-87182/modules/linux/, rename it to *-only and then create an uncompressed tarball named after the directory... in other words, vmmemctl directory gets renamed to vmmemctl-only and then packaged into vmmemctl.tar. When you untar the resulting tar archive, it should create the -only directory (i.e. it shoud be included in the tarball). 6. Replace the tarballs in vmware-tools-distrib/lib/modules/source with the tarballs you just created. 7. Run VMware tools install as usual. Things should compile OK. I realize these steps are a tad painful, so I'll try including a tarball that contains all the tarballs from the open-vm-tools package premade already. All you need to do is copy them over to vmware-tools- distrib/lib/modules/source and run the installer. Note that these are the April 14th version, which is not necessarily the latest release of open-vm-tools. I hope this helps someone... it certainly is an alternative to Hanno's solution, in case your site absolutely requires the use of the pre- bundled VMware tools package. ** Attachment added: "open-vm-tools 2008.04.14 kernel module tarballs" http://launchpadlibrarian.net/14238795/vmware-tools-tarballs.tar.bz2 -- vmware tools dont compile with hardy https://bugs.launchpad.net/bugs/188391 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 188391] Re: vmware tools dont compile with hardy
Whatever happened to open-vm-tools? http://open-vm- tools.sourceforge.net/ Am I right to assume that this is an official VMware project on SourceForge? I find that if I replace the source tarballs inside the VMware ESX 3.0.2 tools installer things compile just fine... I also saw references to that package in Hardy's repository before, however it seems to be gone now (or has it ever existed)? What's going on here? -- vmware tools dont compile with hardy https://bugs.launchpad.net/bugs/188391 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 188391] Re: vmware tools dont compile with hardy
Confirmed here with latest release of vmware tools for VMware ESX 3.0.2. It would be nice if Ubuntu would either bundle compatible precompiled modules with the ESX tools tarball, or even better, include these modules and tools in the repository. ESX, unlike VMware Server, absolutely relies on the vmmemctl driver as well as the VMware tools. It becomes especially important when it comes to memory management and VMotion (only available on ESX). As such, this bug is a major showstopper, because it prevents Ubuntu adoption on VMware ESX (read many, many enterprise clients). While I realize this is a VMware bug, as Hanno said, Canonical should work definitely collaborate on this with VMware Inc. -- vmware tools dont compile with hardy https://bugs.launchpad.net/bugs/188391 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 120512] Re: cloop don't work with 7.04 (amd64)
I'm speculating here, but I think cloop (given its age) won't be included in Hardy, since it won't compile on kernels > 2.6.23. Therefore, if this bug isn't fixed in Feisty, I don't think there's any point in keeping it open. -- cloop don't work with 7.04 (amd64) https://bugs.launchpad.net/bugs/120512 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 160541] Re: Gutsy server kernel takes too long to initialize on VMWare ESX 3.0.2 as guest
Since this isn't going to be fixed in Gutsy, then this bug should be marked as Invalid. The new Hardy server images aren't stable under ESX, probably because they are XEN-aware? Anyway, the problem with regular vanilla hardy server ISOs appears to be much more severe than just slow kernel initialization. I don't have time at the moment to gather enough info for a proper bug report, and as such I will submit a new bug report sometime in the future. I am therefore marking this bug as invalid, since this specific issue does not apply to Hardy at all. Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- Gutsy server kernel takes too long to initialize on VMWare ESX 3.0.2 as guest https://bugs.launchpad.net/bugs/160541 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 49600] Re: Unable to specify which wep key# to store key in
*** This bug is a duplicate of bug 42860 *** https://bugs.launchpad.net/bugs/42860 This bug is a duplicate of bug #42860. Also the upstream bug I reported also happened to be a duplicate (visit http://bugzilla.gnome.org/show_bug.cgi?id=382491 for more info). ** This bug has been marked a duplicate of bug 42860 No support for key indexes -- Unable to specify which wep key# to store key in https://bugs.launchpad.net/bugs/49600 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 125919] Re: [Hardy, Gutsy] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa)
Looks like they're still working on the ath5k driver, however, since it's been included in the master kernel git tree it means that it's passed whatever standards drivers typically need to be included in the kernel. And that's a good thing. :) Theoretically it should be possible to test drive the driver right now by using the following steps: 1. svn co http://svn.madwifi.org/ath5k/trunk ./ath5k-source 2. cd ath5k-source 3. make 4. sudo make install 5. sudo modprobe ath5k More info is available in the README file and at http://linuxwireless.org/en/users/Drivers/ath5k. You can also browse the source code in SVN at http://madwifi.org/browser/ath5k/trunk. -- [Hardy, Gutsy] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125919 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 125919] Re: [Hardy, Gutsy] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa)
Thanks for clearing that up! I'll be waiting to test things re: this bug when they become available. -- [Hardy, Gutsy] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125919 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 125919] Re: [Hardy, Gutsy] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa)
I'm attempting to set the status on the linux-source-2.6.24 to "Confirmed", since we have a confirmation here (reported by Scott), however, every time I try it I get an error saying that this bug was already reported in linux-source, with the package name changed from "linux-source-2.6.24" to just "linux-source". I can reproduce this on both launchpad.net and edge.launchpad.net (the beta site). Is this normal behaviour, or should this be reported as a Launchpad bug? Either way, this bug also affects the Hardy 2.6.24 kernel, since it never inherited the new version of the madwifi source which supports the wireless adapter present in the MBP Santa Rosa. Given the evidence submitted by Scott, I believe that the status for the linux- source-2.6.24 package should be set to "Confirmed" and the bug assigned to "Ubuntu Kernel Team". -- [Hardy, Gutsy] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125919 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 125919]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects ubuntu/linux-source-2.6.24 assignee ubuntu-kernel-team status confirmed -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFHnZOOGVBZzhf+o/cRAvbBAJ4i4OesrN+ALPoZCczFS61R9CbcHgCfSY/Z /hVOvUR8BTxaD/f6DRShGTQ= =mLgH -END PGP SIGNATURE- -- [Gutsy] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125919 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 144242] Re: DVD+R disc does not mount
Further discussion in bug 44233 seems to suggest that this may be due to the fact that your DVD was burned in multisession mode. Can you burn 2 test discs, one in multisession and one as a single session using Nero (Windows) or K3B (Linux) and test this? Thanks! -- DVD+R disc does not mount https://bugs.launchpad.net/bugs/144242 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 179791] Re: Built-in card reader not working with tifm driver on LG W1 series laptop
** Changed in: linux-source-2.6.22 (Ubuntu) Assignee: (unassigned) => Rouben Tchakhmakhtchian (rouben) -- Built-in card reader not working with tifm driver on LG W1 series laptop https://bugs.launchpad.net/bugs/179791 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 179791] Re: Built-in card reader not working with tifm driver on LG W1 series laptop
This is a kernel issue, therefore I am adding the package association linux-source-2.6.22. The following information is pending, as such I am marking this bug "incomplete" until I receive this information from the bug reporter as per https://wiki.ubuntu.com/KernelTeamBugPolicies uname -a > uname-a.log cat /proc/version_signature > version.log dmesg > dmesg.log sudo lspci -vvnn > lspci-vvnn.log ** Changed in: linux-source-2.6.22 (Ubuntu) Sourcepackagename: None => linux-source-2.6.22 Status: New => Incomplete -- Built-in card reader not working with tifm driver on LG W1 series laptop https://bugs.launchpad.net/bugs/179791 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 146341] Re: Buttons not appearing in Apple HD trailers website
I use the i810 driver, and I'm not seeing this issue. Can someone confirm? -- Buttons not appearing in Apple HD trailers website https://bugs.launchpad.net/bugs/146341 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 150132] Re: Compiz breaks gedit workspace grouping behavoir
This has been fixed by the Gnome developers. It would be nice to merge these changes. Either that or we'll just have to wait for the next release! :) -- Compiz breaks gedit workspace grouping behavoir https://bugs.launchpad.net/bugs/150132 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 128787] Re: applesmc not loaded at startup [gutsy]
Confirmed, when I comment out applesmc from /etc/modules, it is *not* loaded on startup as expected. As such, I needed to load it manually and restart the pommed service to get things like the keyboard backlight working again. ** Changed in: linux-source-2.6.22 (Ubuntu) Status: New => Confirmed -- applesmc not loaded at startup [gutsy] https://bugs.launchpad.net/bugs/128787 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 160541] Re: Gutsy server kernel takes too long to initialize on VMWare ESX 3.0.2 as guest
** Attachment added: "VMWare configuration file" http://launchpadlibrarian.net/10293151/Ubuntu%20Gutsy%20Test%20Box.vmx -- Gutsy server kernel takes too long to initialize on VMWare ESX 3.0.2 as guest https://bugs.launchpad.net/bugs/160541 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 160541] Re: Gutsy server kernel takes too long to initialize on VMWare ESX 3.0.2 as guest
The following log files are attached from the Ubuntu Gutsy guest OS running under VMWare ESX Server 3.0.2: * uname -a > uname-a.log * cat /proc/version_signature > version.log * dmesg > dmesg.log * sudo lspci -vvnn > lspci-vvnn.log All these files are in the attached tarball. ** Attachment added: "Gutsy server kernel bug report logs" http://launchpadlibrarian.net/10293116/logs.tar.bz2 -- Gutsy server kernel takes too long to initialize on VMWare ESX 3.0.2 as guest https://bugs.launchpad.net/bugs/160541 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 160541] Gutsy server kernel takes too long to initialize on VMWare ESX 3.0.2 as guest
Public bug reported: Binary package hint: linux-source-2.6.22 Ubuntu Gutsy server takes too long to boot up as a guest on VMWare ESX 3.0.2 server with all the latest patches on both host and guest machines. It takes over 81 seconds for the kernel to initialize, as shown by this sniplet of dmesg log: --- SNIP --- [0.00] Kernel command line: root=UUID=00b0896d-91ca-48fc-acc6-bfdd1c7a8333 ro quiet splash [0.00] Initializing CPU#0 [0.00] PID hash table entries: 4096 (order: 12, 32768 bytes) [ 81.594771] time.c: Detected 1994.569 MHz processor. [ 81.613771] Console: colour VGA+ 80x25 [ 81.613817] Checking aperture... --- SNIP --- The full logs as requested by the kernel team bug policies page will be attached to this bug. ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New -- Gutsy server kernel takes too long to initialize on VMWare ESX 3.0.2 as guest https://bugs.launchpad.net/bugs/160541 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 160508] Re: Windows should slide to other workspace
Window sliding and workspaces are implemented via the window manager, no? So shouldn't this technically be an emerald bug? -- Windows should slide to other workspace https://bugs.launchpad.net/bugs/160508 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 119248] Re: feisty-updates not enabled by default
I am attaching the requested /var/log/installer/syslog file off a fresh amd64 Feisty server install. I'm not sure, maybe just the regular desktop install is affected? However, my /var/log/installer/syslog file shows that the feisty-updates repositories were consulted during the install. Furthermore, as seen below, all my apt list files have the feisty-updates repositories enabled out of the box: === [EMAIL PROTECTED]:~$ grep -v ^\# /etc/apt/sources.list | grep updates deb http://ca.archive.ubuntu.com/ubuntu/ feisty-updates main restricted deb-src http://ca.archive.ubuntu.com/ubuntu/ feisty-updates main restricted === What I'm trying to say is that I am *unable* to reproduce this issue on a fresh install of Feisty server amd64 edition. ** Attachment added: "/var/log/installer/syslog off an amd64 Feisty server install" http://launchpadlibrarian.net/10247319/syslog -- feisty-updates not enabled by default https://bugs.launchpad.net/bugs/119248 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 158382] Re: fglrx >= 8.42 now support AIGLX
I think this is more about upgrading the fglrx module in Gutsy... unfortunately, I think this isn't possible with the current policies, not even with a backport request. I think the best thing to do is to nominate this bug for Hardy (i.e. request that Hardy ship with this version of fglrx along with the necessary X.org configuration changes). I may be wrong on this one, though. -- fglrx >= 8.42 now support AIGLX https://bugs.launchpad.net/bugs/158382 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 158382] Re: fglrx >= 8.42 now support AIGLX
That would really depend on whether or not this version of the fglrx driver is updated... I believe the version in Gutsy at the moment is still 8.37? -- fglrx >= 8.42 now support AIGLX https://bugs.launchpad.net/bugs/158382 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 125919] Re: [Gutsy RC] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa)
Update: ndiswrapper works fairly well with the latest Bootcamp Windows XP driver. I will have to do further tests to see if the slowness I experienced was due to a half-stunned access point or whether it was signal strength/distance/interference related. -- [Gutsy RC] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125919 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 145539] Re: [UNMETDEPS] iscsitarget has unmet dependencies; build from source fails
This seems to have been fixed in Hardy, the package has been upgraded to 0.4.15-4 from 0.4.15-2 according to this page: https://edge.launchpad.net/ubuntu/+source/iscsitarget -- [UNMETDEPS] iscsitarget has unmet dependencies; build from source fails https://bugs.launchpad.net/bugs/145539 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 145539] Re: [UNMETDEPS] iscsitarget has unmet dependencies; build from source fails
According to the iscsitarget project devel mailing list, one needs to build the SVN trunk of the source in order to build this kernel module successfully: http://sourceforge.net/mailarchive/forum.php?thread_name=46F96917.4080108%40forrie.com&forum_name =iscsitarget-devel Therefore, it appears that upstream the developers of the iscsitarget project are aware of this issue and that it will be resolved in the next stable release. ** Description changed: Binary package hint: iscsitarget Installing iscsitarget results with the following error: === iscsitarget: Depends: iscsitarget-module but it is not installable E: Broken packages === This is due to the fact that the binary package iscsitarget-module is not available in the Ubuntu repositiries at the moment. Building iscsitarget-source to produce an iscsitarget-module package fails as follows (originally reported by Todd Deshane in bug #137107 ): === sudo apt-get install iscsitarget-source - sudo module assistant + sudo module-assistant *prepare* *select* --> Select iscsitarget - *install* *build* +--> Build will fail; review build logs. === The original buildlog from bug #137107 as provided by Todd Deshane can be seen here: http://launchpadlibrarian.net/9102605/iscsitarget- source.buildlog.2.6.22-10-generic.1188844553 -- [UNMETDEPS] iscsitarget has unmet dependencies; build from source fails https://bugs.launchpad.net/bugs/145539 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 145539] Re: [UNMETDEPS] iscsitarget has unmet dependencies; build from source fails
The above behaviours have been confirmed on Ubuntu Gutsy 7.10 with all the latest updates at the time of this post. -- [UNMETDEPS] iscsitarget has unmet dependencies; build from source fails https://bugs.launchpad.net/bugs/145539 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 145539] Re: [UNMETDEPS] iscsitarget has unmet dependencies; build from source fails
** Changed in: iscsitarget (Ubuntu) Status: New => Confirmed -- [UNMETDEPS] iscsitarget has unmet dependencies; build from source fails https://bugs.launchpad.net/bugs/145539 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 145539] Re: [UNMETDEPS] iscsitarget has unmet dependencies; build from source fails
** Summary changed: - [UNMETDEPS] iscsitarget has unmet dependencies + [UNMETDEPS] iscsitarget has unmet dependencies; build from source fails ** Description changed: Binary package hint: iscsitarget - A run of - . - LC_ALL=C apt-cache -i unmet | grep ^Package | cut -d' ' -f2 | grep - -v dbgsym | sort -u | xargs apt-cache showsrc | grep ^Directory | - sed 's/Package\:\ //g' | grep verse | cut -d'/' -f4 - indicates that the source package iscsitarget has binary packages that are not - installable (on AMD64) at the moment. - . - Please have a look and make sure it's installable again. + Installing iscsitarget results with the following error: + + === + iscsitarget: Depends: iscsitarget-module but it is not installable + E: Broken packages + === + + This is due to the fact that the binary package iscsitarget-module is + not available in the Ubuntu repositiries at the moment. + + Building iscsitarget-source to produce an iscsitarget-module package fails as follows (originally reported by Todd Deshane + in bug #137107 ): + + === + sudo apt-get install iscsitarget-source + sudo module assistant + *prepare* + *select* +--> Select iscsitarget + *install* + *build* + === + + The original buildlog from bug #137107 as provided by Todd Deshane can + be seen here: http://launchpadlibrarian.net/9102605/iscsitarget- + source.buildlog.2.6.22-10-generic.1188844553 -- [UNMETDEPS] iscsitarget has unmet dependencies; build from source fails https://bugs.launchpad.net/bugs/145539 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 137107] Re: [gusty] iscsitarget-source build fails
*** This bug is a duplicate of bug 145539 *** https://bugs.launchpad.net/bugs/145539 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #145539, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. -- [gusty] iscsitarget-source build fails https://bugs.launchpad.net/bugs/137107 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 137096] Re: [gusty] iscsitarget broken package, depends iscsitarget-module
*** This bug is a duplicate of bug 145539 *** https://bugs.launchpad.net/bugs/145539 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #145539, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug is no longer a duplicate of bug 137320 iscsitarget install fails ** This bug has been marked a duplicate of bug 145539 [UNMETDEPS] iscsitarget has unmet dependencies -- [gusty] iscsitarget broken package, depends iscsitarget-module https://bugs.launchpad.net/bugs/137096 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 137320] Re: iscsitarget install fails
*** This bug is a duplicate of bug 145539 *** https://bugs.launchpad.net/bugs/145539 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #145539, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 145539 [UNMETDEPS] iscsitarget has unmet dependencies -- iscsitarget install fails https://bugs.launchpad.net/bugs/137320 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 150663] Re: iscsitarget locks up and kernel BUG reported in syslog
For the time being, please use the package open-iscsi. According to its project website http://sourceforge.net/projects/iscsitarget/ it is currently in beta and therefore may be unstable. -- iscsitarget locks up and kernel BUG reported in syslog https://bugs.launchpad.net/bugs/150663 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 137107] Re: [gusty] iscsitarget-source build fails
*** This bug is a duplicate of bug 145539 *** https://bugs.launchpad.net/bugs/145539 ** This bug is no longer a duplicate of bug 137320 iscsitarget install fails ** This bug has been marked a duplicate of bug 145539 [UNMETDEPS] iscsitarget has unmet dependencies -- [gusty] iscsitarget-source build fails https://bugs.launchpad.net/bugs/137107 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 149073] Re: warzone on gusty with compiz
Is there a way for you to play this game without fullscreen mode for the time being? -- warzone on gusty with compiz https://bugs.launchpad.net/bugs/149073 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 140519] Re: when i put it on cube i can't move to a difrent workplace
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems. http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: compiz (Ubuntu) Status: New => Incomplete -- when i put it on cube i can't move to a difrent workplace https://bugs.launchpad.net/bugs/140519 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 137134] Re: Windows that touch opposite edges of the screen can't be resized
I can't reproduce this issue with latest Compiz + Emerald on Gutsy. -- Windows that touch opposite edges of the screen can't be resized https://bugs.launchpad.net/bugs/137134 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 155666] Re: "Desktop Cube" is geometrically inaccurate
Thank you for your observation. While you are technically absolutely correct (obviously so when Compiz runs in single-"cube" dual-monitor mode, where it's quite obvious that it's a right prism spanning multiple monitors and not a cube), however, the change you are requesting isn't really a bug with Compiz per se, certainly not from a programming perspective. This is more of a nomenclature/terminology/documentation issue which should be forwarded upstream to the Compiz development community, in my opinion. Note that sometimes inaccurate nomenclature is used for marketing/promotional purposes, where a well-known term such as "cube" is used in lieu of a lesser-known (possibly) term such as "right prism". Either way, I don't think that a bug tracker is the best place for discussing this sort of nomenclature issue. Have you tried raising this issue on the compiz forum? Perhaps the "Project feedback" section? http://forum.compiz-fusion.org/forumdisplay.php?f=103 Thank you very much for reporting this issue and please note that my opinion is not "set in stone" by any means. If you feel strongly about having this issue raised on launchpad, please feel free to respond. ** Changed in: compiz (Ubuntu) Status: New => Invalid -- "Desktop Cube" is geometrically inaccurate https://bugs.launchpad.net/bugs/155666 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 125919] Re: [Gutsy RC] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa)
I got the latest Apple Bootcamp Windows driver to work with ndiswrapper on Gutsy, although very slowly (seems to saturate the bus or something, even video slows down). SVN releases of madwifi drivers didn't work for me at all, in particular probably because my wireless network is ad-hoc. Although that is supported by the madwifi drivers, it just doesn't work for me. -- [Gutsy RC] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125919 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 153045] Re: Ubuntu 7.10: Mathematica and Matlab conflict with Compiz-fusion
Ah, OK, so this is a Java configuration issue then. I am therefore marking this bug as invalid. ** Changed in: compiz (Ubuntu) Status: New => Invalid -- Ubuntu 7.10: Mathematica and Matlab conflict with Compiz-fusion https://bugs.launchpad.net/bugs/153045 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 153045] Re: Ubuntu 7.10: Mathematica and Matlab conflict with Compiz-fusion
This might be a JAVA problem, rather than a compiz problem, perhaps similar to bug #151021 Either way upgrading JAVA to the latest release shouldn't hurt... then again, you never know with JAVA... -- Ubuntu 7.10: Mathematica and Matlab conflict with Compiz-fusion https://bugs.launchpad.net/bugs/153045 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 150132] Re: Compiz breaks gedit workspace grouping behavoir
Confirmed reproducible. -- Compiz breaks gedit workspace grouping behavoir https://bugs.launchpad.net/bugs/150132 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 67385] Re: Opening a file in gedit on a gnome-vfs share fails
Well, I have Gutsy Release Candidate, and I was just able to open a text document on a gnome-vfs SAMBA share, so I guess it's been fixed in Gutsy. The only issue is that gedit prompted me to allow it to access my keyring in order to connect to the SAMBA share (my GNOME keyring contains my credentials to access the SAMBA share). Perhaps that was the issue the whole time? -- Opening a file in gedit on a gnome-vfs share fails https://bugs.launchpad.net/bugs/67385 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 125919] Re: [Gutsy RC] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa)
** Summary changed: - [Gutsy Tribe 2] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa) + [Gutsy RC] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa) ** Description changed: - Gutsy tribe 2 does not detect the wireless interface on Apple's latest - revision of the MacBook Pro. Have seen on ubuntu forums that compiling - madwifi drivers from scratch fix this. + Gutsy Release Candidate does not detect the wireless interface on + Apple's latest revision of the MacBook Pro. Ubuntu forums include + instructions on compiling madwifi drivers from source, which do detect + the wireless adapter. http://ubuntuforums.org/showthread.php?t=474144 -- [Gutsy RC] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125919 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 125919] Re: [Gutsy Tribe 2] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa)
Confirmed, the adapter is only recognized with the manually built SVN drivers from madwifi.org on the MacBook Pro 15" 3d revision (SantaRosa). -- [Gutsy Tribe 2] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125919 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 50651] Re: smbfs: mount_data version 1684370019 is not supported
Perhaps this is simpler than we all think? Does this solution help? Taken from http://www.webservertalk.com/archive214-2004-6-268430.html -- Hi I had this problem immediately after upgrading to Mandrake 10.0 and the 2.6 kernel. Creating the following sym links worked for me: code: ln -s /usr/bin/smbmount /sbin/mount.smbfs ln -s /usr/bin/mount.cifs /sbin/mount.cifs Installing the Samba 3 package (which comes with Mandrake 10.0) does not create this links. -- smbfs: mount_data version 1684370019 is not supported https://bugs.launchpad.net/bugs/50651 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 63402] Re: Edgy Beta cannot boot
Yes, it seems to be fixed in 2.6.17, but are the Edgy ISO images updated? -- Edgy Beta cannot boot https://bugs.launchpad.net/bugs/63402 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 146341] Re: Buttons not appearing in Apple HD trailers website
By the way, if you're using Gutsy (or are planning to upgrade), it's Intel driver has been recently patched. Please check to see if you still have this issue after updating your system. -- Buttons not appearing in Apple HD trailers website https://bugs.launchpad.net/bugs/146341 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 105638] Re: MacBook iSight (isight_usb) reports 640x480, but fails to work at that resolution
** Tags added: macbookpro -- MacBook iSight (isight_usb) reports 640x480, but fails to work at that resolution https://bugs.launchpad.net/bugs/105638 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 127584] Re: isight doesn't work
*** This bug is a duplicate of bug 105638 *** https://bugs.launchpad.net/bugs/105638 ** This bug has been marked a duplicate of bug 105638 MacBook iSight (isight_usb) reports 640x480, but fails to work at that resolution -- isight doesn't work https://bugs.launchpad.net/bugs/127584 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 67385] Re: Opening a file in gedit on a gnome-vfs share fails
Sergio, what underlying protocol were you using? In other words, what type of gnome-vfs share was it? FTP, WebDAV, SSH/SFTP, Samba? -- Opening a file in gedit on a gnome-vfs share fails https://bugs.launchpad.net/bugs/67385 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 128795] Re: [Gutsy] bluetooth device goes away after suspend or hibernate
** Tags added: macbookpro -- [Gutsy] bluetooth device goes away after suspend or hibernate https://bugs.launchpad.net/bugs/128795 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 146341] Re: Buttons not appearing in Apple HD trailers website
I've seen this before with pretty much all major drivers (nvidia, nv, fglrx and i810/intel). I don't think it's driver specific, I think this is a totem-mozilla package issue. Given the fact that you're probably using all the win32 codecs (gstreamer-bad and gstreamer-ugly) debugging this might be a challenge, if not impossible... Just my $0.02, I may be completely wrong. -- Buttons not appearing in Apple HD trailers website https://bugs.launchpad.net/bugs/146341 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 125916] Re: [gutsy] nvidia binary driver not working on MacBook Pro rev.3 (santa rosa)
Confirmed: package nvidia-glx-new and linux-restricted-modules undated to nVidia driver version 100.14.19. http://packages.ubuntu.com/gutsy/misc/nvidia-glx-new http://changelogs.ubuntu.com/changelogs/pool/restricted/l/linux-restricted-modules-2.6.22/linux-restricted-modules-2.6.22_2.6.22.4-12.3/changelog shows that the nvidia-new kernel module was updated to version 100.14.19 since revision inux-restricted-modules-2.6.22.4-12.1. ** Changed in: linux-restricted-modules-2.6.22 (Ubuntu) Status: Confirmed => Fix Released -- [gutsy] nvidia binary driver not working on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125916 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 125914] Re: [Gutsy Tribe 2] nv xorg module not working on MacBook Pro rev.3 (santa rosa)
*** This bug is a duplicate of bug 125916 *** https://bugs.launchpad.net/bugs/125916 ** This bug is no longer a duplicate of bug 125915 [Gutsy Tribe 2] nv not working on MacBook Pro rev.3 (santa rosa) ** This bug has been marked a duplicate of bug 125916 [gutsy] nvidia binary driver not working on MacBook Pro rev.3 (santa rosa) -- [Gutsy Tribe 2] nv xorg module not working on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125914 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 125915] Re: [Gutsy Tribe 2] nv not working on MacBook Pro rev.3 (santa rosa)
*** This bug is a duplicate of bug 125916 *** https://bugs.launchpad.net/bugs/125916 ** This bug has been marked a duplicate of bug 125916 [gutsy] nvidia binary driver not working on MacBook Pro rev.3 (santa rosa) -- [Gutsy Tribe 2] nv not working on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125915 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 120512] Re: cloop don't work with 7.04 (amd64)
Confirmed same issue, similar error with 7.04 on amd64, -server kernel, all latest updates applied, including the today's kernel release. [ 50.744421] cloop: Initializing cloop v2.02 [ 50.744645] cloop: loaded (max 8 devices) [ 50.744653] cloop: out of kernel mem for block buffer (0 bytes) [ 77.977289] cloop: Initializing cloop v2.02 [ 77.977320] kobject_add failed for cloop0 with -EEXIST, don't try to register things with the same name in the same directory. [ 77.977329] [ 77.977330] Call Trace: [ 77.977365] [] kobject_add+0x18e/0x1d0 [ 77.977383] [] register_disk+0x5c/0x280 [ 77.977392] [] add_disk+0x34/0x40 [ 77.977397] [] :cloop:cloop_init+0x1b3/0x2fc [ 77.977414] [] sys_init_module+0x1905/0x1ab0 [ 77.977431] [] __up_write+0x21/0x130 [ 77.977447] [] system_call+0x7e/0x83 ... SNIP ... [ 77.977888] kobject_add failed for cloop7 with -EEXIST, don't try to register things with the same name in the same directory. [ 77.977891] [ 77.977892] Call Trace: [ 77.977894] [] kobject_add+0x18e/0x1d0 [ 77.977898] [] register_disk+0x5c/0x280 [ 77.977902] [] add_disk+0x34/0x40 [ 77.977905] [] :cloop:cloop_init+0x1b3/0x2fc [ 77.977909] [] sys_init_module+0x1905/0x1ab0 [ 77.977915] [] __up_write+0x21/0x130 [ 77.977921] [] system_call+0x7e/0x83 [ 77.977924] [ 77.977925] cloop: loaded (max 8 devices) [ 77.977931] cloop: out of kernel mem for block buffer (0 bytes) Steps to reproduce: === apt-get install cloop-utils dd if=/dev/zero of=./1gig.img bs=1024 count=1048576 mke2fs -j ./1gig.img tune2fs -O dir_index ./1gig.img tune2fs -O has_journal -o journal_data ./1gig.img create_compressed_fs -L -2 -q -m ./1gig.img ./1gig.cimg modprobe cloop file=./1gig.cimg -- cloop don't work with 7.04 (amd64) https://bugs.launchpad.net/bugs/120512 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 125916] Re: [gutsy] nvidia binary driver not working on MacBook Pro rev.3 (santa rosa)
Latest updates to gutsy, as of September 24, ship with the 100.14.19 nvidia driver. Can someone confirm and if so, this bug should be closed. -- [gutsy] nvidia binary driver not working on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125916 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 125916] Re: [gutsy] nvidia binary driver not working on MacBook Pro rev.3 (santa rosa)
Confirmed. Please upgrade the nvidia-glx-new package to 100.14.19 before Gutsy is released. Thanks! -- [gutsy] nvidia binary driver not working on MacBook Pro rev.3 (santa rosa) https://bugs.launchpad.net/bugs/125916 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 119248] Re: feisty-updates not enabled by default
Although I can't say I had this problem with Feisty (mind you I distupgraded from Edgy...), I have to admit that the "Wishlist" priority on this bug seems to be somewhat improper in this case. Aren't updates more important than that? In this case (Flash), this happens to be a security update. Just my $0.02 on the issue. -- feisty-updates not enabled by default https://bugs.launchpad.net/bugs/119248 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 125986] Re: [MASTER] No flash after update of flashplugin-nonfree
What does about:plugins show? The upgrade package worked OK for me, I see the Flash player version OK. -- [MASTER] No flash after update of flashplugin-nonfree https://bugs.launchpad.net/bugs/125986 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 125986] Re: [MASTER] No flash after update of flashplugin-nonfree
I have one confirmation (soon may become two) from a user here: https://answers.launchpad.net/ubuntu/+question/10061 I quote: "Thanks Rouben, adding the feisty-proposed repository solved the problem. Installed the latest version of flashplugin with that, and running perfectly on firefox. Thanks" -- [MASTER] No flash after update of flashplugin-nonfree https://bugs.launchpad.net/bugs/125986 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 128849] Re: flashplugin-nonfree won't install; please update flashplugin-nonfree with MD5 sum of latest Adobe Flash package
*** This bug is a duplicate of bug 125986 *** https://bugs.launchpad.net/bugs/125986 ** This bug has been marked a duplicate of bug 125986 [MASTER] No flash after update of flashplugin-nonfree -- flashplugin-nonfree won't install; please update flashplugin-nonfree with MD5 sum of latest Adobe Flash package https://bugs.launchpad.net/bugs/128849 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 42564] Re: Upgrade to Trac 0.9.6 for dapper (security fixes)
Don't mean to nag, but is there any prospect of this upgrade ever being released to Dapper? -- Upgrade to Trac 0.9.6 for dapper (security fixes) https://bugs.launchpad.net/bugs/42564 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
[Bug 113487] Re: Please backport istanbul for feisty
Unless I am mistaken, this *was* a request to backport 0.2.2. As per original bug description: "0.2.1 is useless for me due to bug #69825." Shall we move it back to "confirmed"? -- Please backport istanbul for feisty https://bugs.launchpad.net/bugs/113487 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 113487] Re: Please backport istanbul for feisty
Thanks for the updates everyone! Can someone confirm if the Baltix bug still stands? As far as I can tell, it should be rejected. The backport task for Ubuntu remains unaffected by this. -- Please backport istanbul for feisty https://bugs.launchpad.net/bugs/113487 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 69614] Re: Include latest available release candidate of avidemux in feisty
Updated package released http://packages.ubuntu.com/feisty/graphics/avidemux ** Changed in: avidemux (Ubuntu) Status: Fix Committed => Fix Released -- Include latest available release candidate of avidemux in feisty https://bugs.launchpad.net/bugs/69614 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 113487] Re: Please backport istanbul for feisty
This has nothing to do with istanbul itself, just backport request. Therefore the istanbul-related bug report is rejected. The backport request still stands and is NOT rejected. ** Changed in: istanbul (Ubuntu) Status: Unconfirmed => Rejected -- Please backport istanbul for feisty https://bugs.launchpad.net/bugs/113487 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 42564] Re: Upgrade to Trac 0.9.6 for dapper (security fixes)
** Changed in: trac (Ubuntu Dapper) Status: Unconfirmed => Confirmed -- Upgrade to Trac 0.9.6 for dapper (security fixes) https://bugs.launchpad.net/bugs/42564 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
[Bug 75895] Re: please backport trac from feisty to dapper
Rejected, see bug #106095. ** Changed in: python-support (Ubuntu) Status: In Progress => Rejected ** Changed in: dapper-backports (upstream) Status: Needs Info => Rejected -- please backport trac from feisty to dapper https://bugs.launchpad.net/bugs/75895 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 42564] Re: Upgrade to Trac 0.9.6 for dapper (security fixes)
Thanks Stefan, for referring this to the SWAT team! Much appreciated! -- Upgrade to Trac 0.9.6 for dapper (security fixes) https://bugs.launchpad.net/bugs/42564 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75895] Re: please backport trac from feisty to dapper
Backport request for python-support from Feisty to Dapper opened. Bug #106095. -- please backport trac from feisty to dapper https://bugs.launchpad.net/bugs/75895 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31729] Re: trac should recommend or suggest postgresql
Confirmed; The latest release of Trac is capable of using either Postgresql or MySQL, although the support for latter is considered experimental. ** Changed in: trac (Ubuntu) Status: Unconfirmed => Confirmed -- trac should recommend or suggest postgresql https://bugs.launchpad.net/bugs/31729 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 42564] Re: Upgrade to Trac 0.9.6 for dapper (security fixes)
Subscribing motu-sru to this bug in order to request a SRU for trac 0.9.6 under dapper. Reason: security fixes. Current release in Dapper repos: 0.9.3, which is vulnerable. -- Upgrade to Trac 0.9.6 for dapper (security fixes) https://bugs.launchpad.net/bugs/42564 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75895] Re: please backport trac from feisty to dapper
According to Max Ischenko's blog comments, once python-support from Edgy is installed, one can install Edgy's trac without having to resort to --force-depends... Therefore, perhaps it's more prudent to request a python-support backport from Edgy as a dependency of the trac backport request? ** Also affects: python-support (Ubuntu) Importance: Undecided Status: Unconfirmed ** Changed in: python-support (Ubuntu) Assignee: (unassigned) => Rouben Status: Unconfirmed => In Progress -- please backport trac from feisty to dapper https://bugs.launchpad.net/bugs/75895 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73556] Re: suphp 0.6.2 backport request to dapper (0.6.1) and edgy (0.6.1) from feisty
b/i/r +1 edgy b/i/r +1 dapper The patch mentioned above works! ** Changed in: dapper-backports (upstream) Assignee: Paul McClure => (unassigned) Status: Needs Info => Confirmed ** Changed in: edgy-backports (upstream) Status: Needs Info => Confirmed -- suphp 0.6.2 backport request to dapper (0.6.1) and edgy (0.6.1) from feisty https://bugs.launchpad.net/bugs/73556 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75895] Re: please backport trac from feisty to dapper
** Summary changed: - please backport trac 0.10.2 from feisty to dapper + please backport trac from feisty to dapper ** Description changed: Hi there. - Trac (http://trac.edgewall.org/) is at version 0.10.3 in feisty, and - 0.10.2 backported from feisty to edgy: + Trac (http://trac.edgewall.org/) is at version 0.10.3-1 in feisty, and + already backported from feisty to edgy: - http://packages.ubuntu.com/feisty/web/trac (0.10.3) - http://packages.ubuntu.com/edgy-backports/web/trac (0.10.2) + http://packages.ubuntu.com/feisty/web/trac (0.10.3-1) + http://packages.ubuntu.com/edgy-backports/web/trac (0.10.3-1) - The version in Dapper is still 0.9. I'm not sure if the proper procedure - here is to backport from feisty to edgy and then to dapper, or directly - to dapper in parallel, but I'd greatly appreciate a 0.10 based trac in - Dapper. + The version in Dapper is still 0.9.x. Thanks in advance. - Mark -- please backport trac from feisty to dapper https://bugs.launchpad.net/bugs/75895 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98645] Re: MASTER: Direct rendering not supported
Is this fixable/applicable at all? According to the Nouveau project website (http://nouveau.freedesktop.org/) 3D support is hardly there at the moment, so it looks like it will take some time for them to implement it. Meanwhile, the nv driver was never really meant for DRI or truly accellerated graphics. It's simply not designed to do that, that's why project Nouveau was started in the first place. For these reasons, I am compelled to set the status of this bug to "Rejected". Please feel free to reverse this change if you feel like there's a strong reason to compell the Xorg developers to implement DRI, although in my personal opinion, it would probably be better to focus on Nouveau. My suggestions: a) Get the binary nVidia driver if you absolutely need efficient/proper hardware 3D accelleration. It's far from being rock solid, but it certainly outperforms the nv driver. b) If you feel compelled about requesting 3D/DRI support in nv, I suggest staring here: http://wiki.x.org/wiki/nv Just my $0.02... ** Changed in: xserver-xorg-video-nv (Ubuntu) Status: Confirmed => Rejected -- MASTER: Direct rendering not supported https://bugs.launchpad.net/bugs/98645 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76332] Re: Trac 0.10.3-1 needed in edgy-backports
Since this backport got approved for Edgy, would it be possible to do the same for Dapper? -- Trac 0.10.3-1 needed in edgy-backports https://bugs.launchpad.net/bugs/76332 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 42564] Re: Upgrade to Trac 0.9.6 for dapper (security fixes)
** Summary changed: - Upgrade to Trac 0.9.5 for dapper (security fixes) + Upgrade to Trac 0.9.6 for dapper (security fixes) ** Description changed: - Hello, - - http://projects.edgewall.com/trac/wiki/ChangeLog - - The 0.9.4 and 0.9.5 resolve several security fixes and lot of bugs. - I think it should be in dapper (which has "only" the 0.9.3). - It won't cause any damage, it's only bugs and security fixes. - + The 0.9.4 - 0.9.6 releases resolve several security fixes and lot of bugs. Current version in Dapper is 0.9.3 which has bugs and security vulnerabilities. + Trac changelog: http://projects.edgewall.com/trac/wiki/ChangeLog Thanks -- Upgrade to Trac 0.9.6 for dapper (security fixes) https://bugs.launchpad.net/bugs/42564 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
[Bug 51609] Re: Broken translation
Sorry for the late reply... I've been tied up with other things. You can edit these "POT" files with just a text editor. There are detailed instructions available here on how to do it (make sure to read the phoen chapter, it's got a few pages): http://i18n.kde.org/docs/translation-howto/gui-translation.html Once you have translated all the files, I suggest getting in touch with KDE's Slovenian internatiolization team: http://l10n.kde.org/team-infos.php?teamcode=sl They should be able to direct you further on how to submit your work to the KDE project. Again, my apologies for such a late reply, and many, many thanks for doing this!!! Let me know if I can be of any further help. -- Broken translation https://launchpad.net/bugs/51609 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 75895] Re: please backport trac 0.10.2 from feisty to dapper
** This bug is no longer flagged as a security issue -- please backport trac 0.10.2 from feisty to dapper https://launchpad.net/bugs/75895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67385] Re: Opening a file in gedit on a gnome-vfs share fails
There's been a patch out for gnome-vfs recently (if you keep your system up to date, you should already have it by now). Can anyone who has installed this patch reproduce this issue? I can't anymore... ** Changed in: gnome-vfs2 (Ubuntu) Status: Unconfirmed => Needs Info -- Opening a file in gedit on a gnome-vfs share fails https://launchpad.net/bugs/67385 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 51609] Re: Broken translation
Just to clarify, the link for the Slovenian translation is http://i18n.kde.org/stats/gui/trunk/sl/playground-sysadmin/index.php also please note that in teh above example, anything with "pl" in it needs to be replaces with "sl" to indicate Slovenian. -- Broken translation https://launchpad.net/bugs/51609 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 75895] Re: please backport trac 0.10.2 from feisty to dapper
According to the trac Changelog (http://trac.edgewall.org/wiki/ChangeLog), the 0.9.x releases below 0.9.6 and 0.10.x releases below 0.10.1 are security fixes. Dapper still has the 0.9.3 release of trac, which is vulnerable. The Ubuntu security team won't handle this one directly (https://wiki.ubuntu.com/SecurityUpdateProcedures#head- 956470dacaf2223cce3b465cf2820daf9ac19c62), so I'm hoping that one of the backporters will take the initiative... ** Changed in: trac (Ubuntu) Status: Unconfirmed => Confirmed -- please backport trac 0.10.2 from feisty to dapper https://launchpad.net/bugs/75895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75895] Re: please backport trac 0.10.2 from feisty to dapper
** Also affects: trac (Ubuntu) Importance: Undecided Status: Unconfirmed ** This bug has been flagged as a security issue -- please backport trac 0.10.2 from feisty to dapper https://launchpad.net/bugs/75895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73556] Re: suphp 0.6.2 backport request to dapper (0.6.1) and edgy (0.6.1) from feisty
This is a request for a MOTU SRU for the suphp package for both Edgy and Dapper as per the backporting team's request. This package has already been updated in Feisty. Due to the nature of the problem (see bug description), this could possibly be a serious bug resulting in loss of user data or possibly crashes (memory management issue). ** Changed in: suphp (Ubuntu) Assignee: (unassigned) => MOTU Stable Release Updates Status: Fix Released => Unconfirmed -- suphp 0.6.2 backport request to dapper (0.6.1) and edgy (0.6.1) from feisty https://launchpad.net/bugs/73556 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63402] Re: Edgy Beta cannot boot
Just curious: since this issue obviously affects the Edgy's LiveCD, does that mean that 6.10.1 ISO images will be released with the updated 2.6.17 kernel? -- Edgy Beta cannot boot https://launchpad.net/bugs/63402 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63402] Re: Edgy Beta cannot boot
Thank you so much for responding and providing the requested information, Daniel. Your help and cooperation is much appreciated! I am now assigning the bug to the Ubuntu Linux kernel developers for further analysis. Note to kernel team: Prior comments on this bug include a kernel call trace, as well as a proposed patch for the sata_promise.c driver which seems to work around the problem according to the patch submitter. ** Changed in: linux-source-2.6.17 (Ubuntu) Assignee: (unassigned) => Ubuntu Kernel Storage Team Status: Needs Info => Confirmed -- Edgy Beta cannot boot https://launchpad.net/bugs/63402 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31719] Re: grub xfs_freeze horribly broken
*** This bug is a duplicate of bug 8058 *** ** This bug has been marked a duplicate of bug 8058 grub-install hangs with xfs root/boot -- grub xfs_freeze horribly broken https://launchpad.net/bugs/31719 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64592] Re: Could not install GRUB (hd0)
*** This bug is a duplicate of bug 8058 *** ** This bug has been marked a duplicate of bug 8058 grub-install hangs with xfs root/boot -- Could not install GRUB (hd0) https://launchpad.net/bugs/64592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 13851] Re: Grub will not install to XFS Formatted Partition
*** This bug is a duplicate of bug 8058 *** Given that this bug was a) reported a long time ago b) is reported against an unsupported release c) is most likely a duplicate of bug #8058 I think it's fairly safe to mark it as such for good housekeeping practice. Please feel free to revert the change if you feel that's necessary. By the way, if LILO has the same issue, there should probably be a separate bug report for it, unless the reporter confused the two. ** This bug has been marked a duplicate of bug 8058 grub-install hangs with xfs root/boot -- Grub will not install to XFS Formatted Partition https://launchpad.net/bugs/13851 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
