[Bug 233849] Re: rsync doesn't delete deleted files
Have you tried rsync -av --delete --exclude=".gvfs/" /home/david/ /media/disk/Backup (notice the modified --exclude parameter, particularly the trailing slash) -- rsync doesn't delete deleted files https://bugs.launchpad.net/bugs/233849 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 233849] Re: rsync doesn't delete deleted files
Make that... rsync -av --delete --delete-excluded --exclude=".gvfs/" /home/david/ /media/disk/Backup -- rsync doesn't delete deleted files https://bugs.launchpad.net/bugs/233849 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 104505] Re: /var/cache/apt filling up my /var partition
Are you sure you've filed this against the right package? APT not apt-cacher, uses /var/cache/apt. Apt-cacher uses /var/cache/apt-cacher. The only reason these folders will fill up with anything is if you're downloading software via apt (i.e. synaptic, apt-get, adept, aptitude, etc.), and most (if not all) of these programs tell you that they need to download X and that Y space will be used after installation when you hit "install". -- /var/cache/apt filling up my /var partition https://bugs.launchpad.net/bugs/104505 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 285269] Re: UUID conversion fails to handle separate /boot
@John: You may want to open a Question on Launchpad Questions for your particular case, so as to avoid creating noise on this bug. In response to your query: Try hd(0,4) or hd(0,5) -- if you created a "logical" partition, the partition numbers start at 4 (counting from 0, e.g. hd(0,4)) or 5 (counting from one, e.g. sda5). Basically you need to give grub the ID of your separate /boot, not of the root ubuntu partition itself. Alternatively, if you can boot the Live CD mode of the installer, you can mount your new install and do a "chroot" into the install, and then run the update from the command line to install the new grub packages. Then you can run update-grub. One other thing -- if you have a copy of the old menu.lst file (perhaps called menu.lst~ or something) in /boot/grub (if you have a seperate /boot, look for a small ext partition with a folder called "grub" in it) -- you can try moving the current menu.lst to something like menu.lst.broken and then copying the old menu.lst back in place. Note that this will likely put you back in the hardy kernel instead of the intrepid one, so you will want to run a dist upgrade again once you get it to boot. -- UUID conversion fails to handle separate /boot https://bugs.launchpad.net/bugs/285269 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 286007] Re: jockey-gtk crashed with DBusException in call_blocking()
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/18697420/Dependencies.txt ** Attachment added: "Devices.txt" http://launchpadlibrarian.net/18697421/Devices.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/18697422/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/18697423/ProcStatus.txt ** Attachment added: "Traceback.txt" http://launchpadlibrarian.net/18697424/Traceback.txt ** Visibility changed to: Public -- jockey-gtk crashed with DBusException in call_blocking() https://bugs.launchpad.net/bugs/286007 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 286233] [NEW] grub configured with wrong uuid when a /boot partition is present
Public bug reported: Binary package hint: grub-installer The Interpid Daily Alternate CD from October 17th installs GRUB with the UUID of the root (/) partition, even when a /boot partition is present. This causes the first boot to fail until the offending line is replaced with a corrected root or uuid line. [EMAIL PROTECTED]:~$ lsb_release -rd Description:Ubuntu intrepid (development branch) Release:8.10 ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Also affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- grub configured with wrong uuid when a /boot partition is present https://bugs.launchpad.net/bugs/286233 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 286233] Re: grub configured with wrong uuid when a /boot partition is present
Generated menu.lst config file ** Attachment added: "menu.lst.orig" http://launchpadlibrarian.net/18709739/menu.lst.orig -- grub configured with wrong uuid when a /boot partition is present https://bugs.launchpad.net/bugs/286233 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 286233] Re: grub configured with wrong uuid when a /boot partition is present
[EMAIL PROTECTED]:/boot/grub$ ls -l /dev/disk/by-uuid total 0 lrwxrwxrwx 1 root root 10 2008-10-19 15:40 22474639-59c8-48f8-a1a7-cf8f002b67c5 -> ../../sda5 lrwxrwxrwx 1 root root 10 2008-10-19 15:40 54627783-5c87-4fbd-92e2-917dae447dc4 -> ../../sda8 lrwxrwxrwx 1 root root 10 2008-10-19 15:40 75f67f32-4549-412d-84c6-4554097d5548 -> ../../sda6 lrwxrwxrwx 1 root root 10 2008-10-19 19:40 7C2E-584E -> ../../sdb1 lrwxrwxrwx 1 root root 10 2008-10-19 15:40 7c6b616b-7ca5-44eb-b11c-5c5b13e4df09 -> ../../sda7 lrwxrwxrwx 1 root root 10 2008-10-19 15:40 9f0c4bc2-2174-438b-b955-429b0dcd2923 -> ../../sda9 lrwxrwxrwx 1 root root 10 2008-10-19 15:40 C4E02A3EE02A36D8 -> ../../sda1 -- grub configured with wrong uuid when a /boot partition is present https://bugs.launchpad.net/bugs/286233 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 286233] Re: grub configured with wrong uuid when a /boot partition is present
contents of /etc/fstab ** Attachment added: "fstab" http://launchpadlibrarian.net/18709744/fstab -- grub configured with wrong uuid when a /boot partition is present https://bugs.launchpad.net/bugs/286233 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 260675] Re: [intrepid] Wacom Xorg module is incompatible with the kernel module shipped in kernel packages.
If you want someone to notice that the file should be placed in /usr/share/hal/fdi/policy/20thirdparty/ by default, you should file another bug, so that the status of that change can be tracked. -- [intrepid] Wacom Xorg module is incompatible with the kernel module shipped in kernel packages. https://bugs.launchpad.net/bugs/260675 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 58537] Re: Amarok Takes 30 Seconds To Stop Playing Music After You Quit The Program
Are you outputting via either ARTS or PulseAudio? (This would likely be under the engine options.) Both sound systems take about 30 seconds to free up the sound card after all connected applications stop playing sound, although that can be reconfigured. -- Amarok Takes 30 Seconds To Stop Playing Music After You Quit The Program https://bugs.launchpad.net/bugs/58537 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 58537] Re: Amarok Takes 30 Seconds To Stop Playing Music After You Quit The Program
At risk of being too technical, Amarok itself doesn't play music. The current version actually calls another application (known as an "engine") to play the music -- and the music playing runs in another thread/process so that when the GUI lags, (which WILL happen due to stupidness in the way X is designed) your music doesn't skip. So, A) it takes time for the "quit" message to get from one application to another, and B) if there's a bug in the configuration of the engine, that would likely cause this behaviour. 30 seconds seems like a lot to me, but perhaps it's just me. Does upgrading to the Amarok in Hardy or Intrepid fix the issue? Of course, if the whole "using an engine" is the cause of the bug, then you may want to help with testing of Amarok 2, which uses some new- fangled KDE 4 library to play sound instead. Oh... and for what it's worth, last I checked, XMMS is no longer being maintained, so if it breaks and there's a bug, there's nobody that can fix it. *shrugs* -- Amarok Takes 30 Seconds To Stop Playing Music After You Quit The Program https://bugs.launchpad.net/bugs/58537 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to amarok in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 286233] Re: grub configured with wrong uuid when a /boot partition is present
*** This bug is a duplicate of bug 285269 *** https://bugs.launchpad.net/bugs/285269 ** This bug has been marked a duplicate of bug 285269 grub error 15 after intrepid-beta install -- grub configured with wrong uuid when a /boot partition is present https://bugs.launchpad.net/bugs/286233 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 285269] Re: grub error 15 after intrepid-beta install
@Mike Wescott: I don't think that the comment was incorrect per se... I think it refers to a "drive" in the sense that a "partition" is a "drive". Also, a debdiff[0] is, as far as I know, the generally accepted form of a patch, and once one is created you can then ask for your fix to be sponsored [1]. Otherwise, I plan on reinstalling later this week on a few machines... if I get the chance I'll try your patch out. [0] https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff [1] https://wiki.ubuntu.com/SponsorshipProcess -- grub error 15 after intrepid-beta install https://bugs.launchpad.net/bugs/285269 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 202174] Re: Please update to version 2.6
That is because the upstream Debian version changed -- the 1.0.0-1 version was pulled in by the auto-sync bot. See: http://packages.debian.org/sid/libasio-dev http://packages.debian.org/changelogs/pool/main/a/asio/asio_1.0.0-1/changelog http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461920 -- Please update to version 2.6 https://bugs.launchpad.net/bugs/202174 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 276021] Re: Network card not detected with the 2.6.27-4 kernel
*** This bug is a duplicate of bug 263555 *** https://bugs.launchpad.net/bugs/263555 The e1000e driver was disabled because it is suspected to cause problems with integrated gigabit chipsets. Your Ethernet controller, while it is only a 10/100 one, should be serviced by the e1000e driver in Intrepid, probably because of similarities in the chipset. It's a duplicate in the sense that your bug won't be resolved until bug #263555 is fixed in a way that will allow the driver to be re-enabled. My understanding is that there are many people (including people from Intel) who are working to resolve the issue. -- Network card not detected with the 2.6.27-4 kernel https://bugs.launchpad.net/bugs/276021 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 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
The current "fix" is to disable the driver to prevent damage to your hardware. Various developers are still working on finding the actual cause of the problem, please be patient. You are recommended to use the latest stable LTS (8.04) for anything mission-critical. -- [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk https://bugs.launchpad.net/bugs/263555 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 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Well, those patches were released in the last two or three days -- basically, we have to wait for upstream kernel devs who are capable/willing to reproduce the issue to test the patches, and then consider how to get that code into the Ubuntu kernel. (Directly applying patches? Go through Debian first? etc. etc.) Another issue is that the kernel freeze is on October 16th[1]. I don't think it would be nice to ship with e1000e blacklisted, so if the resolution isn't tested/approved by then, a release manager will need to grant an exemption to push the release date back into November. [1] https://wiki.ubuntu.com/IntrepidReleaseSchedule -- [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk https://bugs.launchpad.net/bugs/263555 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 260675] Re: [intrepid] Wacom Xorg module is incompatible with the kernel module shipped in kernel packages.
Fix Committed means that the fix is in the source tree -- a package has _not_ been released yet. -- [intrepid] Wacom Xorg module is incompatible with the kernel module shipped in kernel packages. https://bugs.launchpad.net/bugs/260675 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 260675] Re: [intrepid] Wacom Xorg module is incompatible with the kernel module shipped in kernel packages.
I do recall there was one other issue where any X application that started up when X was configured for a tablet but a tablet was not plugged in caused warnings (usually three) to be emitted to the console. I think this was back around dapper, or so. There were a great deal of false bug reports about that. While auto-detection is ideal for most (if not all) hardware, I suspect doing it "correctly" for wacom tablets in such a way that it doesn't negatively affect users who have never heard of a tablet, let alone seen one, will take some time and work. I suspect that some restructuring of both the driver and the X input infrastructure would be required. Anyway, to answer your question, good locations to start would probably be in Launchpad Questions, or in a separate bug report, depending on your level of knowledge and expertise. -- [intrepid] Wacom Xorg module is incompatible with the kernel module shipped in kernel packages. https://bugs.launchpad.net/bugs/260675 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 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
If you have no network whatsoever, you'll need to grab the package using another machine or OS, use a daily build CD image, or downgrade to a version where the driver was not disabled and then upgrade to the current one. http://packages.ubuntu.com/intrepid/linux-image-2.6.27-5-generic http://packages.ubuntu.com/intrepid/linux-image-2.6.27-5-server (As Colin mentioned, it will take a while for linux-* packages to be updated to automatically bring in the new package.) -- [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk https://bugs.launchpad.net/bugs/263555 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 262550] Re: WARNING: Intrepid might burn down MacBook Pro
What does lsmod give you? Perhaps you don't have the right modules loaded, for whatever reason... Also, the following command tells us which kernel packages you have installed. dpkg -l 'linux-*' Also try the instructions at https://wiki.ubuntu.com/DebuggingACPI and see if they are of any help in finding the nature of the problem. -- WARNING: Intrepid might burn down MacBook Pro https://bugs.launchpad.net/bugs/262550 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 178895] Re: Audacity does not mesh with PulseAudio
As far as I can see, the issue with jackd should be a separate bug with a separate title and description. -- Audacity does not mesh with PulseAudio https://bugs.launchpad.net/bugs/178895 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 264303] Re: Please sync openafs (1.4.7.dfsg1-6) from debian
Well, a sync would generally seem to be a wishlist... but on the other hand, openafs does regress in intrepid without this sync. But it's rather late... I think there's a special process that needs to occur for this package to make it into the archive. -- Please sync openafs (1.4.7.dfsg1-6) from debian https://bugs.launchpad.net/bugs/264303 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 202174] Re: Please update to version 2.6
No, that would go in a separate bug titled "2.6 does not integrate with Nautilus" or some such. Which this bug may or may not then block on. -- Please update to version 2.6 https://bugs.launchpad.net/bugs/202174 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 202174] Re: Please update to version 2.6
On that note, is anybody else surprised at the large number of NMUs in the Abiword changelog? -- Please update to version 2.6 https://bugs.launchpad.net/bugs/202174 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun in Hardy
Okay, I'm installing linux-image-2.6.25-1-generic (version 2.6.25-1.2ubuntu5) and linux-ubuntu-modules-2.6.25-1-generic (version 2.6.25-1.1ubuntu8); I'll report the results in this thread in a few moments. -- /dev/input/wacom device missing for Bamboo Fun in Hardy https://bugs.launchpad.net/bugs/195636 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun in Hardy
Yes, the new Intrepid Ibex kernel based on 2.6.25 in the kernel PPA creates the /dev/input/wacom device, both with the device plugged in on startup, and when it is plugged in while the system is running. Notes: With the new kernel, the X server provides the expected behavior as documented in wacom-tools upstream; i.e. that the X server must be (re-)started after the Bamboo Fun is plugged in. (This is not the kernel's fault; it creates the devices correctly now.) Potentially relevant to anyone who reads this later: The Wacom-related sections of my X.Org config are from Gutsy; I did not try this with a config-less X.org setup. -- /dev/input/wacom device missing for Bamboo Fun in Hardy https://bugs.launchpad.net/bugs/195636 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 258716] [NEW] Latest stable version of pyglet is 1.1
Public bug reported: According to http://pyglet.org/ the latest stable/recommended version of pyglet is 1.1 and offers many major improvements. ** Affects: pyglet (Ubuntu) Importance: Undecided Status: New -- Latest stable version of pyglet is 1.1 https://bugs.launchpad.net/bugs/258716 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 258716] Re: Latest stable version of pyglet is 1.1
Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494367 -- Latest stable version of pyglet is 1.1 https://bugs.launchpad.net/bugs/258716 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 254468] Re: momentary video garbage upon drawing new objects
I recall seeing this sort of garbage in early versions of compiz; but it seems to have been "worked around", since it's quite clearly not there any more. How does compiz get around the lack of backfilling, and is it something that could also be done by KDE's compositing manager? -- momentary video garbage upon drawing new objects https://bugs.launchpad.net/bugs/254468 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 178895] Re: Audacity does not mesh with PulseAudio
Since we're part DebianImportFreeze, a request must be filed for it to be synced into Jaunty. It appears Stéphane Graber has already done this (bug 317254). Users who are watching this bug may also wish to subscribe to bug 317254 so that they can keep track of its status. -- Audacity does not mesh with PulseAudio https://bugs.launchpad.net/bugs/178895 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 254468] Re: MASTER: momentary video garbage upon drawing new objects (particularly in KDE)
** Also affects: intrepid-backports Importance: Undecided Status: New -- MASTER: momentary video garbage upon drawing new objects (particularly in KDE) https://bugs.launchpad.net/bugs/254468 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 254468] Re: MASTER: momentary video garbage upon drawing new objects (particularly in KDE)
The "Fix Released" status is correct -- the fix has been released -- in Jaunty. If you would like to see these changes in an earlier version of Ubuntu, please take a look at the Backports and StableReleaseUpdates policies: https://help.ubuntu.com/community/UbuntuBackports https://wiki.ubuntu.com/StableReleaseUpdates Regarding the user who believes this is a security concern, you may want to notify the security team, and verify that they are aware of the problem, first. https://wiki.ubuntu.com/SecurityUpdateProcedures -- MASTER: momentary video garbage upon drawing new objects (particularly in KDE) https://bugs.launchpad.net/bugs/254468 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 215845] Re: Fast scrolling with the wheel induces "jump" backward
In order for it to be backported, it must first exist in the current development version (Jaunty, at the time of writing). That, in turn probably requires it to be in Debian. You may wish to file a bug on the Debian bug tracker asking for abiword 2.6.6 to be packaged, noting that this bug is fixed in it. -- Fast scrolling with the wheel induces "jump" backward https://bugs.launchpad.net/bugs/215845 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 342036] Re: System Monitor Network Plasmoid Graph Displays Negative Values
** Attachment added: "snapshot1.png" http://launchpadlibrarian.net/23809426/snapshot1.png -- System Monitor Network Plasmoid Graph Displays Negative Values https://bugs.launchpad.net/bugs/342036 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 342036] [NEW] System Monitor Network Plasmoid Graph Displays Negative Values
Public bug reported: I noticed that when I have the "System Monitor - Network" plasmoid on my desktop, it sometimes will display a graph with large negative values. I find that this behavior often exhibits itself after I have transferred a large amount of data (e.g. 4 GB) in a short period of time over my LAN. I expect the graph to properly show my bandwidth usage even when I transmit a large quantity of data on my network. mich...@kiwi:~$ lsb_release -rd Description:Ubuntu jaunty (development branch) Release:9.04 mich...@kiwi:~$ apt-cache policy kdeplasma-addons kdeplasma-addons: Installed: 4:4.2.1-0ubuntu2 Candidate: 4:4.2.1-0ubuntu2 Version table: *** 4:4.2.1-0ubuntu2 0 500 http://ca.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status Screenshot attached of the graph generated by the plasmoid (on the left) and a bandwidth usage graph from the last day generated by cacti (on the right). ** Affects: kdeplasma-addons (Ubuntu) Importance: Undecided Status: New -- System Monitor Network Plasmoid Graph Displays Negative Values https://bugs.launchpad.net/bugs/342036 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdeplasma-addons in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 254468] Re: MASTER: momentary video garbage upon drawing new objects (particularly in KDE)
I believe this particular bug is fixed for me, using intel driver with 9.4 beta, but I am now seeing garbage in other places (particularly when switching between applications). Intend on filing new bugs when I get a chance. -- MASTER: momentary video garbage upon drawing new objects (particularly in KDE) https://bugs.launchpad.net/bugs/254468 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 267504] [NEW] openafs-modules-source 1.4.6 fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h removed
Public bug reported: In the 2.6.27 kernel, asm/semaphore.h was removed and replaced with a generic C implementation in linux/semaphore.h. http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-02/msg13760.html This prevents the current version of openafs-modules-source from building on 2.6.27. ** Affects: openafs Importance: Undecided Status: New ** Affects: openafs (Ubuntu) Importance: Undecided Status: New ** Tags: linux-2.6.27 ** Tags added: linux-2.6.27 ** Also affects: openafs Importance: Undecided Status: New -- openafs-modules-source 1.4.6 fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h removed https://bugs.launchpad.net/bugs/267504 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 267504] Re: openafs-modules-source 1.4.6 fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h removed
Upstream bug: http://rt.central.org/rt/Ticket/Display.html?id=111634 (Launchpad currently can't perform remote watch on this bug tracker...) -- openafs-modules-source 1.4.6 fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h removed https://bugs.launchpad.net/bugs/267504 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 267504] Re: openafs-modules-source 1.4.6 fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h removed
... For some reason, I can't add that tracker in "also affects project", but it automatically does a remote bug watch when I link to it? o.O -- openafs-modules-source 1.4.6 fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h removed https://bugs.launchpad.net/bugs/267504 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 267504] Re: openafs-modules-source 1.4.6 fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h removed
** Changed in: openafs Importance: Undecided => Unknown Bugwatch: None => rt.central.org/rt/ #111634 Status: New => Unknown -- openafs-modules-source 1.4.6 fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h removed https://bugs.launchpad.net/bugs/267504 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 267504] Re: openafs-modules-source fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h replaced with linux/semaphore.h
** Summary changed: - openafs-modules-source 1.4.6 fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h removed + openafs-modules-source fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h replaced with linux/semaphore.h ** Description changed: In the 2.6.27 kernel, asm/semaphore.h was removed and replaced with a generic C implementation in linux/semaphore.h. http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-02/msg13760.html - This prevents the current version of openafs-modules-source from - building on 2.6.27. + This prevents the current version of openafs-modules-source from building on 2.6.27. + - + Update: A debdiff attached to this bug report by Björn Torkelsson requires the sync request in bug #264303 to be processed first. -- openafs-modules-source fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h replaced with linux/semaphore.h https://bugs.launchpad.net/bugs/267504 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 267504] Re: openafs-modules-source fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h replaced with linux/semaphore.h
fwyzard, is that patch from upstream, or have you considered sending that patch upstream to OpenAFS? >From my understanding, Bjorn's debdiff combines (accepted and committed) patches from the upstream bug tracker, so eventually the patch can be removed once upstream makes a release with said code and that release propagates to Debian, and in turn, Ubuntu. -- openafs-modules-source fails to build with 2.6.27-2 kernel in intrepid: asm/semaphore.h replaced with linux/semaphore.h https://bugs.launchpad.net/bugs/267504 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 410810] [NEW] Empathy should have option to only allow contacts on contact list to start a conversation with the user
Public bug reported: Binary package hint: empathy I tend to get unsolicited messages on my chat accounts. In other clients, e.g. Pidgin, or the official network clients (GTalk, MSN, etc.) there is an option to only allow contacts on my contact list to see my status and start conversations/chats with me. When someone else wishes to add me to their contact list, they are required to ask my permission, and it is not possible to start a chat/conversation without adding me to their contact list. Empathy does not appear to have this feature, as of karmic. ** Affects: empathy (Ubuntu) Importance: Undecided Status: New -- Empathy should have option to only allow contacts on contact list to start a conversation with the user https://bugs.launchpad.net/bugs/410810 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 407793] [NEW] [i865g][Karmic Alpha 3] X corruption and freeze when clicking "Other" on GDM login screen
Public bug reported: Binary package hint: xserver-xorg-video-intel 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu. mich...@kiwi:~/dri_debug$ lsb_release -rd Description:Ubuntu karmic (development branch) Release:9.10 2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic. mich...@kiwi:~/dri_debug$ apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.8.0-0ubuntu1 Candidate: 2:2.8.0-0ubuntu1 Version table: *** 2:2.8.0-0ubuntu1 0 500 http://ca.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status mich...@kiwi:~/dri_debug$ apt-cache policy gdm gdm: Installed: 2.27.4-0ubuntu6 Candidate: 2.27.4-0ubuntu6 Version table: *** 2.27.4-0ubuntu6 0 500 http://ca.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status 3) What you expected to happen The screen would display a "username" field and allow me to type in my username. 4) What happened instead The screen displays the username field, but black boxes (corruption?) appear above and below it, and the computer stops responding to all keyboard input, with the exception of Alt-SysRq keys. Hitting Caps Lock does NOT make the respective keyboard LED go on, but hitting Num Lock does. It is possible to move the cursor with the mouse, but clicking does not do anything. --- As per https://wiki.ubuntu.com/X/Troubleshooting/Freeze # When did you first notice it? Did you change any settings (Desktop Effects?) or update your system prior to first noticing it? Freezes have generally been intermittent on this machine since Jaunty, but it hasn't been possible to reproduce with any sort of consistency. Doing a clean install of Karmic Alpha 3 causes this particular freeze to always happen when doing these particular steps. # What frequency does it occur? Just once? Hourly? Daily? Occurs every time I start the computer. # Try to determine actions which reproduce it or make it more/less likely to reproduce. Always reproduceable by clicking "Other" in gdm. -- As per (https://wiki.ubuntu.com/X/Reporting) - Paste in output of lspci -nn | grep VGA mich...@kiwi:~/dri_debug$ lspci -nn | grep VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02) Get a full backtrace (X/Backtracing) How complete is the X failure? + Does ctrl+alt+f1 take you to a console? No. + Does ctrl+alt+backspace restart X? No. + Does mouse pointer still move? Yes. + Does the keyboard LED come on when hitting the CAPSLOCK key? No. + Can you ssh into the system from another computer? Yes. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- [i865g][Karmic Alpha 3] X corruption and freeze when clicking "Other" on GDM login screen https://bugs.launchpad.net/bugs/407793 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 407793] Re: [i865g][Karmic Alpha 3] X corruption and freeze when clicking "Other" on GDM login screen
** Attachment added: "Batchbuffer dump for -intel (includes Xorg.0.log)" http://launchpadlibrarian.net/29781868/dri_debug-20090801-1940-kiwi.tgz -- [i865g][Karmic Alpha 3] X corruption and freeze when clicking "Other" on GDM login screen https://bugs.launchpad.net/bugs/407793 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 407793] Re: [i865g][Karmic Alpha 3] X corruption and freeze when clicking "Other" on GDM login screen
** Attachment added: "Photo of corruption that occurs with the freeze" http://launchpadlibrarian.net/29781917/100_8756.jpg -- [i865g][Karmic Alpha 3] X corruption and freeze when clicking "Other" on GDM login screen https://bugs.launchpad.net/bugs/407793 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 400485] Re: Empathy sounds not in default ubuntu theme
** Description changed: Binary package hint: empathy 2.6.31-3-generic #19-Ubuntu SMP Tue Jul 14 16:04:41 UTC 2009 i686 GNU/Linux empathy: - Installed: 2.27.3-2ubuntu3 - Candidate: 2.27.3-2ubuntu3 - Version table: - *** 2.27.3-2ubuntu3 0 - 500 http://us.archive.ubuntu.com karmic/main Packages - 100 /var/lib/dpkg/status + Installed: 2.27.3-2ubuntu3 + Candidate: 2.27.3-2ubuntu3 + Version table: + *** 2.27.3-2ubuntu3 0 + 500 http://us.archive.ubuntu.com karmic/main Packages + 100 /var/lib/dpkg/status Empathy sounds are not a part of the default theme in Ubuntu. Since its a big possibility that it will be default in ubuntu, then the sounds should be a part of the default ubuntu theme. -- Empathy sounds not in default ubuntu theme https://bugs.launchpad.net/bugs/400485 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 400485] Re: Empathy sounds not in default ubuntu theme
I'm aware of that. I didn't actually intend to change the description, but I think the edge server may have mangled with the whitespace when I unintentionally submitted my changes to the server by clicking the edit icon twice. Sorry for the noise. -- Empathy sounds not in default ubuntu theme https://bugs.launchpad.net/bugs/400485 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 193343] Re: pycentral crashed with AttributeError in byte_compile()
*** This bug is a duplicate of bug 93518 *** https://bugs.launchpad.net/bugs/93518 Jussi, I believe you replicated bug #193446 instead, unless I'm reading kaiarne's traceback wrong. -- pycentral crashed with AttributeError in byte_compile() https://bugs.launchpad.net/bugs/193343 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 193343] Re: pycentral crashed with AttributeError in byte_compile()
*** This bug is a duplicate of bug 93518 *** https://bugs.launchpad.net/bugs/93518 Further searching indicates this is likely a duplicate of bug #93518. ** This bug is no longer a duplicate of bug 192992 [hardy] pycentral crashed with ValueError in parse_versions() ** This bug has been marked a duplicate of bug 93518 [apport] pycentral crashed with AttributeError in install() -- pycentral crashed with AttributeError in byte_compile() https://bugs.launchpad.net/bugs/193343 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 193446] Re: problems updating in 8.04
** Also affects: python-central (Ubuntu) Importance: Undecided Status: New -- problems updating in 8.04 https://bugs.launchpad.net/bugs/193446 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun in Hardy
** Summary changed: - /dev/input/wacom device missing for Bamboo Fun + /dev/input/wacom device missing for Bamboo Fun in Hardy ** Description changed: Binary package hint: wacom-tools In Hardy, with my Bamboo Fun 4x5 tablet plugged in at startup, /dev/input/wacom devices are not created and the wacom module is not loaded. If I manually execute "sudo modprobe wacom" the devices are still not created. In Gutsy, I had to manually build wacom-tools 0.7.9 from source and replace the kernel module with the one built by the wacom-tools compile process. I would assume that after the upload of wacom-tools 0.7.9 in Hardy, this would be fixed, but it doesn't appear to be. + It appears this is because the wacom module in the Hardy kernel is older + than the module included with the Linux Wacom Project's source. (The + earliest versions of the wacom tools source to include a module with + support the Bamboo Fun are 0.7.7-12 and 0.7.8-3.) + ProblemType: Bug Architecture: i386 Date: Mon Feb 25 20:30:46 2008 DistroRelease: Ubuntu 8.04 Package: wacom-tools 1:0.7.9.3-2ubuntu2 PackageArchitecture: i386 SourcePackage: wacom-tools Uname: Linux pineapple 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux ** Description changed: Binary package hint: wacom-tools In Hardy, with my Bamboo Fun 4x5 tablet plugged in at startup, /dev/input/wacom devices are not created and the wacom module is not loaded. If I manually execute "sudo modprobe wacom" the devices are still not created. In Gutsy, I had to manually build wacom-tools 0.7.9 from source and replace the kernel module with the one built by the wacom-tools compile process. I would assume that after the upload of wacom-tools 0.7.9 in Hardy, this would be fixed, but it doesn't appear to be. It appears this is because the wacom module in the Hardy kernel is older than the module included with the Linux Wacom Project's source. (The earliest versions of the wacom tools source to include a module with - support the Bamboo Fun are 0.7.7-12 and 0.7.8-3.) + support the Bamboo Fun are 0.7.7-12 and 0.7.8-3.) According to Fedor + Isakov, the earliest vanilla kernel with support for the Bamboo Fun is + 2.6.25-rc7. ProblemType: Bug Architecture: i386 Date: Mon Feb 25 20:30:46 2008 DistroRelease: Ubuntu 8.04 Package: wacom-tools 1:0.7.9.3-2ubuntu2 PackageArchitecture: i386 SourcePackage: wacom-tools Uname: Linux pineapple 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux ** Description changed: Binary package hint: wacom-tools In Hardy, with my Bamboo Fun 4x5 tablet plugged in at startup, /dev/input/wacom devices are not created and the wacom module is not loaded. If I manually execute "sudo modprobe wacom" the devices are still not created. In Gutsy, I had to manually build wacom-tools 0.7.9 from source and replace the kernel module with the one built by the wacom-tools compile process. I would assume that after the upload of wacom-tools 0.7.9 in Hardy, this would be fixed, but it doesn't appear to be. It appears this is because the wacom module in the Hardy kernel is older than the module included with the Linux Wacom Project's source. (The earliest versions of the wacom tools source to include a module with support the Bamboo Fun are 0.7.7-12 and 0.7.8-3.) According to Fedor - Isakov, the earliest vanilla kernel with support for the Bamboo Fun is - 2.6.25-rc7. + Isakov (see comment below), the earliest vanilla kernel with support for + the Bamboo Fun is 2.6.25-rc7. ProblemType: Bug Architecture: i386 Date: Mon Feb 25 20:30:46 2008 DistroRelease: Ubuntu 8.04 Package: wacom-tools 1:0.7.9.3-2ubuntu2 PackageArchitecture: i386 SourcePackage: wacom-tools Uname: Linux pineapple 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux -- /dev/input/wacom device missing for Bamboo Fun in Hardy https://bugs.launchpad.net/bugs/195636 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 202174] Re: Please update to version 2.6
I'm not a ubuntu dev; just a passer-by user, but since you check for pdftoabw at runtime, perhaps you want to have poppler-utils as a "suggests:" or "recommends:" now to match the dropped libpoppler dependency? -- Please update to version 2.6 https://bugs.launchpad.net/bugs/202174 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 202174] Re: Please update to version 2.6
The tendency to split packages is a debian/ubuntu thing that sometimes catches users (and developers!) off guard if you're unaware of it -- the primary reason, IIRC, is to allow people to save space by removing parts of software they don't need. (For example, there are separate linux- image- (kernel image only), linux-headers- (kernel headers only), and linux-source- (kernel source only) packages in Ubuntu/Debian.) This is useful for e.g. embedded systems (Debian targets, I think, about 11 archs; some of which are for smaller form factors) and live CDs/DVDs and other places where space is tight. http://packages.ubuntu.com/ provides an interface to allow searching for existing packages, as well as the contents of existing packages. (For Debian, http://packages.debian.org/ is similar -- AFAIK the two are based on the same codebase.) I found poppler-utils by searching for packages which contained "pdftoabw" on that page. -- Please update to version 2.6 https://bugs.launchpad.net/bugs/202174 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 203402] Re: Permissions error with Kodak ZD710 prevents opening of camera
Hmm... that's interesting. I also use permission bits rather than ACLs on my system. However, considering that /dev is mounted on tmpfs I'm not sure what effect this should have, if any. Also, the setfacl man page states the following: "If setfacl is used on a file system which does not support ACLs, setfacl operates on the file mode permission bits. If the ACL does not fit completely in the permission bits, setfacl modifies the file mode permission bits to reflect the ACL as closely as possible, writes an error message to standard error, and returns with an exit status greater than 0." Perhaps what would be interesting is to see what the debugging output from Gutsy is to see if there are any noticeable differences. I don't have time right now, but if I get the chance in a few days I'll probably try attaching the camera to one of the Gutsy systems here... ** Summary changed: - Permissions error with Kodak ZD710 prevents opening of camera + Permissions error with USB PTP Camera prevents opening of camera in Hardy -- Permissions error with USB PTP Camera prevents opening of camera in Hardy https://bugs.launchpad.net/bugs/203402 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 202174] Re: Please update to version 2.6
Just curious, did 2.6 make it into hardy, or is this now something that must wait for hardy+1? -- Please update to version 2.6 https://bugs.launchpad.net/bugs/202174 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 178895] Re: Audacity does not mesh with PulseAudio
kripkenstein: By "works", do you mean: 1) Plays audio. 2) Records audio. 3) Both 1) and 2) Also, what pulseaudio packages do you have installed? Is there anything regarding libao that is not stock Ubuntu (perhaps a development version)? How are ALSA and Pulseaudio installed/configured? Are you using the Pulseaudio ALSA device? Also, what kind of "sound card" do you use? (I have "integrated" sound here, using the snd_intel8x0 module.) I'm also perplexed -- I don't know of the "Pulseaudio" option of which you speak. -- Audacity does not mesh with PulseAudio https://bugs.launchpad.net/bugs/178895 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 22336] Re: CPU overheats during high usage "throttling "
Just curious, but on pentium-based laptops, are p4_clockmod (etc.) getting loaded by default? If not, should they be? (I find on my desktop P4 computer, I get "throttling " and have to load p4_clockmod manually (in /etc/modules or via modprobe) in order to get throttling support. For me, this is significant, because even P4-based desktops I've seen seem to get too hot over extended periods of "normal" use.) -- CPU overheats during high usage "throttling " https://bugs.launchpad.net/bugs/22336 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 104219] Re: Translation template was not imported to Feisty
Is there any documentation about how "most packages in Ubuntu" build, and how the build scripts generate .pot files? Just in case e.g. someone comes along with a new (translatable) package and wants to have translations in Launchpad as well, and avoid this bug, would they be able to find information on how to do it? -- Translation template was not imported to Feisty https://bugs.launchpad.net/bugs/104219 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 85488] Re: some usb_devices fault if usb_suspend enabled
I like this idea, but (IMO, at least) it would be important for such a dialog to also automatically capture the USB IDs of the devices in question and post them to some place where the quirks list could be updated, perhaps similar to or as a part of the automated bug reporting system now in Ubuntu. (That said, it seems a lot more obvious to capture "app XYZ has crashed" (Segmentation Faults, etceteras) so the dialog might not be something that pops up automatically... the user may have to activate it manually, or it may pop up in cases where it doesn't apply, in which case we have to find a way to A) reverse the change, and B) triage or otherwise verify IDs which appear on any auto-generated list actually exhibit this problem, and can have their functionality restored by adding them to the quirks list.) But wouldn't that be a feature request (i.e. requiring a separate bug report under "wishlist" or specification)? -- some usb_devices fault if usb_suspend enabled https://bugs.launchpad.net/bugs/85488 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 85488] Re: some usb_devices fault if usb_suspend enabled
@Mark: Sitsofe is testing with the *Gusty* (you could say "alpha", "next version" or "testing") kernels, trying his best to ensure that this problem *does not affect the next release*. Whether it is worthwhile or not, at least he is TRYING to help fix the problem. If you would like to contact Canon, you are free to do so and report back with the results. If they respond with valuable information (sans NDA) then there should be no reason why that information could not also be integrated into later bug fixes. (Fortunately or unfortunately, the development model here seems to be that fixes can only go into the next version unless it's a security fix. Perhaps that needs to be changed, but that is a discussion for another (wishlist priority) bug report.) -- some usb_devices fault if usb_suspend enabled https://bugs.launchpad.net/bugs/85488 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 85488] Re: some usb_devices fault if usb_suspend enabled
@Sitsofe: It appears that in a later message, the patch was rejected. Those messages are from earlier this month. That said, following the thread leads to this message, which I find somewhat amusing: http://lkml.org/lkml/2007/8/3/81 Funny how someone said that "the chances are no distribution is going to ship with CONFIG_USB_SUSPEND enabled" -- when Feisty did precisely that, months ago! However, it is good to see that lkml seems to have developed a bit of a routine for dealing with most USB quirks, assuming the new sane-backends in gutsy doesn't fix your problem. (Yes, they are still using the blacklist.) Provided you are willing to compile small patches into a kernel and report what level of quirkiness the device needs to be accommodated for, similar to what this user did, your quirky device can now be added to the upstream code in a matter of hours! :) (Of course, figuring out how to do the compile takes a bit of work...) http://lkml.org/lkml/2007/8/14/131 -- some usb_devices fault if usb_suspend enabled https://bugs.launchpad.net/bugs/85488 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 85488] Re: some usb_devices fault if usb_suspend enabled
At the time of writing, gutsy does not appear to contain the fixes from Debian's "sane-backends", unless the fix was merged in separate from the entire new version... Debian: 1.0.19~cvs20070730-1 http://packages.debian.org/unstable/source/sane-backends http://packages.debian.org/changelogs/pool/main/s/sane-backends/sane-backends_1.0.19~cvs20070730-1/changelog Ubuntu: 1.0.19~cvs20070505-3ubuntu1 http://packages.ubuntu.com/gutsy/source/sane-backends http://changelogs.ubuntu.com/changelogs/pool/main/s/sane-backends/sane-backends_1.0.19~cvs20070505-3ubuntu1/changelog Until this occurs, the only way that this will be "fixed" is if the kernel has been fixed for your device. Did you try Tribe 3? According to https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/85488/comments/351 , https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/85488/comments/380 , and https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/85488/comments/384 , it appears the "quirk listing" for your device _should_ have made it into the 2.6.22-9.19 kernel, and it appears also to be in the latest git, but my Gutsy machine says that the latest (again, at the time of writing) is 2.6.22-10.33, so I'm not 100% sure about other changes between that last message and now. -- some usb_devices fault if usb_suspend enabled https://bugs.launchpad.net/bugs/85488 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 85488] Re: some usb_devices fault if usb_suspend enabled
Unfortunately, I think the problem here is twofold: Firstly, the problem doesn't seem to affect *all* USB devices -- simply those who don't conform to usb_suspend, and violate the USB specification*. Secondly, I think the issue is that there is a workaround -- but both enabling the workaround and not enabling the workaround will cause regressions either way. (In other words, regardless of what is done, _something_ will stop working, give or take.) *That said, I think that simply not conforming to a specification seems like a ridiculous reason to cause problems for a device, although I don't think the intent was malicious... or intentional for that matter. As has been noted above, there are workarounds -- recompiling a custom kernel without usb_suspend, or creating and/or installing a program to constantly poll the device, thus preventing usb_suspend from kicking in. As fishor's post has noted, there is now code in the linux kernel which will disable usb_suspend on devices which have been specified as having the quirk of faulting under this bug. How long it will take for the code to propagate to users is another issue entirely. Considering the 6-month release cycle of Ubuntu, it might not be until October or even next April before the "fixed" code gets to end users -- and even then, it will only help users who A) encounter the problem, B) find out the cause, and C) report the bug before the necessary release/sync deadlines. (If it weren't for the fact that Ubuntu releases every six months, this might have taken even longer than that.) If your device is uncommon, it would be a good idea to investigate avenues for reporting device IDs to the kernel developers so they can fix the problem for you upstream. Even if the real fix takes six to twelve months to get to you, hopefully this particular won't come back to that device for a long, long time once it's fixed properly. (Unfortunately, A workaround, downgrading, or use under an alternate OS/PC might be necessary in the meantime... or perhaps foregoing the device in the case of non-essential devices... Alternatively, users have the option of compiling and running bleeding-edge code, with all of the additional bugs that comes with that decision.) In either case, a fix is in the works, and will eventually make its way to machines installed with a future version of *buntu. As Mark noted, Red Hat has a workaround that works for their kernel -- is there anyone who has such a device who can confirm whether that workaround also works on a Ubuntu machine? (This won't fix the problem, but it will make it go away. However, it will also negate any "power savings" for laptop users that would have come with this particular new feature with the kernel.) 1. Open Applications, then Terminal. 2. A box should appear. In the box, type "sudo gedit /boot/grub/menu.lst" (without quotes) and hit enter. 3. Look about halfway down for a line that starts "# defoptions=" (without quotes; NOTE: use the line with ONE "#" symbol) 4. At the end of this line, add a space, then "usbcore.autosuspend=0" (without quotes) 5. Save and quit gedit. 6. In the box you used earlier, type "sudo /usr/sbin/update-grub" and hit enter. 7. Restart your computer. Kubuntu/KDE users can instead try the following: Instead of Step 1, hit the K menu and click "Run Command...". Instead of Step 2, type "sudo kwrite /boot/grub/menu.lst". In step 6, you'll have to click the K menu and click "Run Command..." again to bring up another box. Note that you won't get any feedback unless you run the command "in a terminal window" (under options) because update-grub is NOT a graphical application... and therefore you should wait about thirty seconds to two minutes for update-grub to do its work before restarting. (Or you can run it in a terminal window and wait for "" to appear in the title bar, assuming you don't mind looking at a vibrantly coloured box that flashes text before your eyes.) -- some usb_devices fault if usb_suspend enabled https://bugs.launchpad.net/bugs/85488 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 85488] Re: some usb_devices fault if usb_suspend enabled
My apologies, I am simply a user like you guys -- attempting to be helpful. Nobody (until now) _denied_ that the solution worked -- which is why I reiterated the comment. Now that we know that option doesn't work means that the fix probably involves some RH-specific patch, or RH systems are somehow different from Ubuntu. (Not surprising, but it's important to know.) Ben Collins, who *is* on the kernel team, has already stated his rationale on the importance of CONFIG_USB_SUSPEND, in https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/85488/comments/14 (above). -- some usb_devices fault if usb_suspend enabled https://bugs.launchpad.net/bugs/85488 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 85488] Re: some usb_devices fault if usb_suspend enabled
@jengel: What constitutes a "newer kernel"? Does the 2.6.20-16.29 in Feisty count? And do negative values have special meaning, or can we assume "-1" for the time being? @cank1090: IIRC, Herd CDs are also live-install combo CDs, like any other -- would it be possible for you to burn the ISO to e.g. a CD-R or CD-RW and try scanning from the live CD? @Sitsofe Wheeler: I would presume the kernel team doesn't want to go through periods of inconsistency, where we switch the USB_SUSPEND toggle on and off and on and off... it would probably infuriate users in both classes when A says "it worked two months ago, then stopped, it worked again last week, and now it stopped again", and B says "that didn't work two months, ago, it did a few weeks ago, stopped two weeks ago", etc. -- IMO it would be ideal if we could fix this at the "source" and publish those kinds of changes properly, than give the impression that users won't be able to even guess when their hardware will/will not be working. It's too bad compiling a kernel correctly is both time-consuming and hard to get right even after doing it a few times. Based on jengel's comment... Can somebody on Feisty who has confirmed the problem, and confirmed autosuspend=0 doesn't work, try using "-1", and failing that, deleting the entire "usbcore..." and adding "usbcore.autosuspend_delay=-1" instead(1)? Simply change the value instead of adding, and run "sudo /usr/sbin/update-grub" again. I don't expect it to work, because it appears the documentation for that "feature" appeared in version 2.6.21 (2)... and my Feisty system has .20, but it's important to be certain that a workaround doesn't work _before_ saying it doesn't work (just in case the functionality went in before the documentation or I'm viewing a weird patch or the versions differ or something else)... (1) http://www.redhat.com/archives/fedora-kernel-list/2007-June/msg00101.html (2) http://www.linuxhq.com/kernel/v2.6/21/Documentation/kernel-parameters.txt -- some usb_devices fault if usb_suspend enabled https://bugs.launchpad.net/bugs/85488 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 85488] Re: some usb_devices fault if usb_suspend enabled
@jengel: Well if the code _appears_ to do that, then we can probably work with that until the fix comes out and/or people tell us to do differently. @SilverLoz: Thank you very much for trying our suggestions. As stated above, I wasn't expecting the boot-time flag to work in 2.6.20 (a.k.a. Feisty kernels) simply because it seems the patch to add that functionality appeared in 2.6.21. Knowing helps, though. The boot-time flag _should_ work in Gutsy, which uses 2.6.22... at least in theory. Would it be possible for you (or someone else with a USB device who is affected by this problem) to download a Gusty *buntu Tribe ISO, burn it to a CD-R/RW, and then try appending "usbcore.autosuspend=-1" to the kernel command line before scanning from the LiveCD environment? (Once I get the ISO downloaded myself I'll try and write up more detailed instructions, but I actually haven't tried Gutsy yet, so I'm not fully familiar with what changes (particularly interface changes), if any, are currently in Gusty.) -- some usb_devices fault if usb_suspend enabled https://bugs.launchpad.net/bugs/85488 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 85488] Re: some usb_devices fault if usb_suspend enabled
@t2000kw: If that is your decision, then by all means. Ubuntu is not for everyone (yet). However, I wouldn't be surprised if Canonical's support teams might have been able to provide you a custom workaround (if necessary) if you had bought the right kind of SLA, similar to how other companies deal with these sorts of bug reports. On the flip side -- what must-have features could Feisty possibly have had for you such that you couldn't continue using Edgy? >From what I can tell, Gutsy Tribe 4 seems to be well on its way to fixing this issue, although it currently has its own breakage in other areas. -- some usb_devices fault if usb_suspend enabled https://bugs.launchpad.net/bugs/85488 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun
Okay; thank you. (Actually, the adding of the upstream task was accidental; I was trying to add the linux package, not the linux upstream task, and I wasn't sure what to do with the upstream task afterwards.) -- /dev/input/wacom device missing for Bamboo Fun https://bugs.launchpad.net/bugs/195636 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 195636] [NEW] /dev/input/wacom device missing for Bamboo Fun
Public bug reported: Binary package hint: wacom-tools In Hardy, with my Bamboo Fun 4x5 tablet plugged in at startup, /dev/input/wacom devices are not created and the wacom module is not loaded. If I manually execute "sudo modprobe wacom" the devices are still not created. In Gutsy, I had to manually build wacom-tools 0.7.9 from source and replace the kernel module with the one built by the wacom-tools compile process. I would assume that after the upload of wacom-tools 0.7.9 in Hardy, this would be fixed, but it doesn't appear to be. ProblemType: Bug Architecture: i386 Date: Mon Feb 25 20:30:46 2008 DistroRelease: Ubuntu 8.04 Package: wacom-tools 1:0.7.9.3-2ubuntu2 PackageArchitecture: i386 SourcePackage: wacom-tools Uname: Linux pineapple 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux ** Affects: linux Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: wacom-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- /dev/input/wacom device missing for Bamboo Fun https://bugs.launchpad.net/bugs/195636 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun
** Attachment added: "lsb-release" http://launchpadlibrarian.net/12217590/lsb-release ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/12217591/Dependencies.txt ** Also affects: linux Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- /dev/input/wacom device missing for Bamboo Fun https://bugs.launchpad.net/bugs/195636 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun
** Attachment added: "dmesg-annotated.log" http://launchpadlibrarian.net/12217615/dmesg-annotated.log -- /dev/input/wacom device missing for Bamboo Fun https://bugs.launchpad.net/bugs/195636 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun
** Attachment added: "dmesg.log" http://launchpadlibrarian.net/12217619/dmesg.log -- /dev/input/wacom device missing for Bamboo Fun https://bugs.launchpad.net/bugs/195636 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun
contains the output of dpkg -l 'linux-*' ** Attachment added: "dpkg-linux.txt" http://launchpadlibrarian.net/12217620/dpkg-linux.txt -- /dev/input/wacom device missing for Bamboo Fun https://bugs.launchpad.net/bugs/195636 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun
contains the output of dpkg -l 'wacom-*' ** Attachment added: "dpkg-wacom.txt" http://launchpadlibrarian.net/12217631/dpkg-wacom.txt -- /dev/input/wacom device missing for Bamboo Fun https://bugs.launchpad.net/bugs/195636 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun
** Attachment added: "lsb-release" http://launchpadlibrarian.net/12217633/lsb-release -- /dev/input/wacom device missing for Bamboo Fun https://bugs.launchpad.net/bugs/195636 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun
** Attachment added: "lspci-vvnn.log" http://launchpadlibrarian.net/12217644/lspci-vvnn.log -- /dev/input/wacom device missing for Bamboo Fun https://bugs.launchpad.net/bugs/195636 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun
** Attachment added: "lsusb.log" http://launchpadlibrarian.net/12217653/lsusb.log -- /dev/input/wacom device missing for Bamboo Fun https://bugs.launchpad.net/bugs/195636 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun
** Attachment added: "uname-a.log" http://launchpadlibrarian.net/12217658/uname-a.log -- /dev/input/wacom device missing for Bamboo Fun https://bugs.launchpad.net/bugs/195636 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 195636] Re: /dev/input/wacom device missing for Bamboo Fun
** Attachment added: "version.log" http://launchpadlibrarian.net/12217662/version.log -- /dev/input/wacom device missing for Bamboo Fun https://bugs.launchpad.net/bugs/195636 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 148687] Re: Kopete intenal sqlite database fails when stored on NFS
The SQLite database is used by the "Statistics Plugin"; you can turn it on and off by going to Settings -> Configure Plugins... >From what I can tell the Statistics plugin records when contacts were last seen online (and perhaps other similar things I haven't noticed yet). According to the SQLite FAQ, SQLite doesn't work well over NFS. (http://www.sqlite.org/faq.html) "SQLite uses reader/writer locks to control access to the database. But use caution: this locking mechanism might not work correctly if the database file is kept on an NFS filesystem. This is because fcntl() file locking is broken on many NFS implementations. You should *avoid putting SQLite database files on NFS* if multiple processes might try to access the file at the same time." (emphasis added) As far as I can tell, the messages don't cause problems if you have one Kopete running at any given time, although if you launch kopete from a Terminal (emulator, or xterm, or uxterm or konsole or whatever you call it) it can be kind of annoying. -- Kopete intenal sqlite database fails when stored on NFS https://bugs.launchpad.net/bugs/148687 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 178895] Re: Audacity does not mesh with PulseAudio
At the following page, it's recommended to stop pulseaudio entirely when running audacity... http://www.pulseaudio.org/wiki/PerfectSetup#Audacity As far as I can tell, in Gutsy, Audacity uses PortAudio as its audio subsystem, and right now PortAudio doesn't appear to support PulseAudio as a backend. Apparently, somebody started work on such a backend (https://tango.0pointer.de/pipermail/pulseaudio- discuss/2007-November/000890.html) but it's not in active development. Personally, I've also found that recording from audacity launched via padsp causes crashes on my system when I record audio (although not when I play audio). While I think configuration might be a factor, the fact that few people have been recommending the use of padsp and audacity makes me think that it's not a supported configuration for one reason or another. -- Audacity does not mesh with PulseAudio https://bugs.launchpad.net/bugs/178895 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 84591] Re: feisty 20070210/herd5 persistent mode doesn't work
A) When you booted, did you add the word "persistence" to the boot options line? (I believe you have to hit one of the F-keys before Ubuntu starts booting...) B) Have you tried the daily CD build? -- feisty 20070210/herd5 persistent mode doesn't work https://bugs.launchpad.net/bugs/84591 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 178895] Re: Audacity does not mesh with PulseAudio
Well, here's a pulseaudio bug from a year ago: http://www.pulseaudio.org/ticket/50 But I don't think the recording problem got solved. Technically speaking, in terms of an ideal solution, the "bug" should probably be in PortAudio which fails to have a PortAudio backend, as far as I can tell. However, those error messages, Nick, are probably a result of padsp not performing as expected. (But that may be by design -- it's impossible to emulate mmaped audio through padsp.) Audacity worked just fine with plain ALSA and plain OSS, last I checked on Gutsy. (Can anybody reconfirm this bug with Hardy?) -- Audacity does not mesh with PulseAudio https://bugs.launchpad.net/bugs/178895 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 178895] Re: Audacity does not mesh with PulseAudio
correction: ... in PortAudio which fails to have a *PulseAudio* backend ... -- Audacity does not mesh with PulseAudio https://bugs.launchpad.net/bugs/178895 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 196861] Re: desktop icons created by prism don't work
The problem in question is introduced by debian/patches/fix_desktop_launcher.patch which contains the following line: +cmd += "Exec=xulrunner-1.9 /usr/lib/prism/application.ini -webapp " + id + "\n"; Attached is an updated patch, which points to /usr/share/prism/application.ini instead. ** Attachment added: "Updated patch to match real location of application.ini" http://launchpadlibrarian.net/12688939/fix_desktop_launcher.patch -- desktop icons created by prism don't work https://bugs.launchpad.net/bugs/196861 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 90978] Re: udev rules break usb printers
In response to the question portion: 2.3.0 is greater than 2.2.1. -- udev rules break usb printers https://bugs.launchpad.net/bugs/90978 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 203402] Re: Permissions error with Kodak ZD710 prevents opening of camera
result of uname -a ** Attachment added: "uname-a.log" http://launchpadlibrarian.net/12716189/uname-a.log -- Permissions error with Kodak ZD710 prevents opening of camera https://bugs.launchpad.net/bugs/203402 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 203402] Re: Permissions error with Kodak ZD710 prevents opening of camera
results of sudo udevmonitor -e when device is plugged in (only) ** Attachment added: "udev.log" http://launchpadlibrarian.net/12716188/udev.log -- Permissions error with Kodak ZD710 prevents opening of camera https://bugs.launchpad.net/bugs/203402 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 203402] Re: Permissions error with Kodak ZD710 prevents opening of camera
results of sudo udevmonitor -e when the device is plugged in and then unplugged ** Attachment added: "udevmonitor-e" http://launchpadlibrarian.net/12716089/udevmonitor-e -- Permissions error with Kodak ZD710 prevents opening of camera https://bugs.launchpad.net/bugs/203402 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 203402] Re: Permissions error with Kodak ZD710 prevents opening of camera
contents of /proc/version_signature ** Attachment added: "proc_version_signature.log" http://launchpadlibrarian.net/12716064/proc_version_signature.log -- Permissions error with Kodak ZD710 prevents opening of camera https://bugs.launchpad.net/bugs/203402 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 203402] Re: Permissions error with Kodak ZD710 prevents opening of camera
output of lsusb ** Attachment added: "lsusb.log" http://launchpadlibrarian.net/12716055/lsusb.log -- Permissions error with Kodak ZD710 prevents opening of camera https://bugs.launchpad.net/bugs/203402 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 203402] Re: Permissions error with Kodak ZD710 prevents opening of camera
output of lspci -vvnn ** Attachment added: "lspci-vvnn.log" http://launchpadlibrarian.net/12716054/lspci-vvnn.log -- Permissions error with Kodak ZD710 prevents opening of camera https://bugs.launchpad.net/bugs/203402 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 203402] Re: Permissions error with Kodak ZD710 prevents opening of camera
output of lshal ** Attachment added: "lshal.txt" http://launchpadlibrarian.net/12715963/lshal.txt -- Permissions error with Kodak ZD710 prevents opening of camera https://bugs.launchpad.net/bugs/203402 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 203402] Re: Permissions error with Kodak ZD710 prevents opening of camera
contents of /etc/lsb-release ** Attachment added: "lsb-release" http://launchpadlibrarian.net/12715960/lsb-release -- Permissions error with Kodak ZD710 prevents opening of camera https://bugs.launchpad.net/bugs/203402 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 203402] Re: Permissions error with Kodak ZD710 prevents opening of camera
output of id haldaemon ** Attachment added: "id-haldaemon.log" http://launchpadlibrarian.net/12715958/id-haldaemon.log -- Permissions error with Kodak ZD710 prevents opening of camera https://bugs.launchpad.net/bugs/203402 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 203402] Re: Permissions error with Kodak ZD710 prevents opening of camera
output of id ** Attachment added: "id.log" http://launchpadlibrarian.net/12715956/id.log -- Permissions error with Kodak ZD710 prevents opening of camera https://bugs.launchpad.net/bugs/203402 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 203402] Re: Permissions error with Kodak ZD710 prevents opening of camera
output of dmesg ** Attachment added: "dmesg.log" http://launchpadlibrarian.net/12715955/dmesg.log -- Permissions error with Kodak ZD710 prevents opening of camera https://bugs.launchpad.net/bugs/203402 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
