[Bug 568183] Re: Non-selected Raid Array Corruption from Installer
*** This bug is a duplicate of bug 191119 *** https://bugs.launchpad.net/bugs/191119 Thanks for the answer, but now that I think about it, I'm not sure NEW_LABEL alone would cause wholesale RAID array corruption. Correct me if I'm wrong because I'm not an expert on how parted works, but that bug with NEW_LABEL would only overwrite the RAID superblock and not the data? In which case, the RAID array would just start up in degraded mode and have to be re-synced. In my case, and in the original bug report, and in NickJ's case, the array was not degraded, but rather the data on the array was corrupted. Even supposing the NEW_LABEL command did cause the corruption, while it may have been an upstream bug that physically wrote to the disk and caused that problem, the root of all evil is still the installer that incorrectly told parted there was a file system present on a device that's a component of the RAID array. Are you saying that parted is also responsible for detecting which file systems are present as well, and the installer only reports it? In any case it needs to be fixed, because only bad things can happen if the installer doesn't know what file systems are actually present. In any case, there needs to be basic safeguards in place which prevent the installer from writing directly to partitions with a RAID superblock, has a RAID autodetect partition type, or are in a logical volume. I guess you could argue that this would rather be an enhancement, in the way you could argue that a car without brakes is not a defect, but rather brakes would be a nice-to-have enhancement. -- Non-selected Raid Array Corruption from Installer https://bugs.launchpad.net/bugs/568183 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 191119] Re: Installer corrupts raid drive
(copying comment from bug 568183) Thanks for the answer, but now that I think about it, I'm not sure NEW_LABEL alone would cause wholesale RAID array corruption. Correct me if I'm wrong because I'm not an expert on how parted works, but that bug with NEW_LABEL would only overwrite the RAID superblock and not the data? In which case, the RAID array would just start up in degraded mode and have to be re-synced. In my case, and in the original bug report, and in NickJ's case, the array was not degraded, but rather the data on the array was corrupted. Even supposing the NEW_LABEL command did cause the corruption, while it may have been an upstream bug that physically wrote to the disk and caused that problem, the root of all evil is still the installer that incorrectly told parted there was a file system present on a device that's a component of the RAID array. Are you saying that parted is also responsible for detecting which file systems are present as well, and the installer only reports it? In any case it needs to be fixed, because only bad things can happen if the installer doesn't know what file systems are actually present. In any case, there needs to be basic safeguards in place which prevent the installer from writing directly to partitions with a RAID superblock, has a RAID autodetect partition type, or are in a logical volume. I guess you could argue that this would rather be an enhancement, in the way you could argue that a car without brakes is not a defect, but rather brakes would be a nice-to-have enhancement. -- Installer corrupts raid drive https://bugs.launchpad.net/bugs/191119 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 191119] Re: Installer corrupts raid drive
Linux000, don't bother; I have practically written a dissertation on why it isn't likely to be a grub problem in one of these bugs. -- Installer corrupts raid drive https://bugs.launchpad.net/bugs/191119 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 570765] Re: [Lucid] no GRUB menu entry for other operating systems
If you're going to fix this before the release, how about also fixing bug 568183 / bug 191119 as well? Those bugs can actually destroy your data on RAID partitions, even if the user did not elect to use the RAID partitions during the install. This has been confirmed by several people at this point. -- [Lucid] no GRUB menu entry for other operating systems https://bugs.launchpad.net/bugs/570765 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 570765] Re: [Lucid] no GRUB menu entry for other operating systems
I reported it, but I believe it's the same bug as 191119, which is similar (although the reporter didn't give as much information). That bug coincides with when they changed how file systems are detected in the installer. -- [Lucid] no GRUB menu entry for other operating systems https://bugs.launchpad.net/bugs/570765 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 570765] Re: [Lucid] no GRUB menu entry for other operating systems
Well, I posted it on the mailing list. Impute used that data to file the report. -- [Lucid] no GRUB menu entry for other operating systems https://bugs.launchpad.net/bugs/570765 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 570765] Re: [Lucid] no GRUB menu entry for other operating systems
If I may editorialize, the logic people are using to evaluate the bug is pretty amusing: 1. It can't exist, because a problem this big would have been reported much earlier. 2. It can't be a dup of bug 191119, because that bug was reported much earlier. -- [Lucid] no GRUB menu entry for other operating systems https://bugs.launchpad.net/bugs/570765 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 570765] Re: [Lucid] no GRUB menu entry for other operating systems
Chris, if that's the case, I'm afraid for people's data. That RAD bug is still there. It's going to be interesting to see how they answer questions about this when people ask why their data had to be lost... -- [Lucid] no GRUB menu entry for other operating systems https://bugs.launchpad.net/bugs/570765 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 570765] Re: [Lucid] no GRUB menu entry for other operating systems
Charlie, The problem is that there's no evidence that those bugs have even been seen or evaluated by the appropriate personnel, despite being clearly ubuntu installer problems that result in file system corruption and the loss of data. Bug 19119, for example, managed to go over 2 years without being addressed, despite being confirmed at the time by multiple people. Bug 568183 has also been confirmed by multiple people, yet it's still marked as 'new' and still has not been assigned to anyone. If this bug *does* have the attention of the appropriate personnel, it would seem that a 3-sentence reminder is reasonable to let them know of the existence of the others. -- [Lucid] no GRUB menu entry for other operating systems https://bugs.launchpad.net/bugs/570765 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 560152] Re: installing lucid over existing software raid 1 does not work
*** This bug is a duplicate of bug 542210 *** https://bugs.launchpad.net/bugs/542210 Hi, NickJ, If I interpret Whoop correctly, his problem was that he tried to install Ubuntu to 2 separate machines while leaving his RAID /home partition alone on each. The end result was the installer goofed his install and gave him that failed to remove conflicting files message, but in both cases his /home RAID partition was undamaged. His end result was a botched install, on the first machine to sda1, and on the second machine to md0(?), but neither RAID /home directory had any problems. Whoop, if this is not the case, please let me know. In your case, NickJ, you also tried to install Ubuntu while leaving your RAID /home partition alone, but things diverge soon after that. 1. In your case, although you elected to not format or modify your RAID /home partition, the installer told you that the partition tables would be changed, anyway. Whoop makes no mention of this in his case. And he has screen shots of his install which also don't show anything abnormal. 2. In your case, the installer actually corrupted your RAID /home partition, despite you telling the installer not to touch it. This did not happen in Whoop's case. This next part gets logically convoluted, but bear with me. You both started off with similar starting positions, and you both used similar procedures, but you had markedly different results. Therefore, there must be a different bug at play in your case. If you also received the failed to remove conflicting files error, it logically follows that you must have been blessed with two bugs. Lucky you! Additionally, the results you mention in 1 and 2 above are cornerstones of the bugs I mentioned. See that first long email in bug 568183, which is currently a duplicate of bug 191119. Long story short: it was likely *you* who fixed your second bug when you rebuilt your corrupted RAID arrays, and the fix to this bug fixed your remaining problem. BTW, how did you wind up recovering your RAID drives? -- installing lucid over existing software raid 1 does not work https://bugs.launchpad.net/bugs/560152 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 191119] Re: Installer corrupts raid drive
It probably won't work in a VM, because of the way a VM's virtual storage devices work. They discard everything that's not being used at that moment, otherwise you'd have to allocate the full size of the drive. Thus, you probably couldn't have any defunct file systems sitting around. -- Installer corrupts raid drive https://bugs.launchpad.net/bugs/191119 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 191119] Re: Installer corrupts raid drive
Yup, and I thank you for it. And if this bug does get fixed, I imagine those people whose data won't be hosed as a result would thank you too. -- Installer corrupts raid drive https://bugs.launchpad.net/bugs/191119 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 560152] Re: installing lucid over existing software raid 1 does not work
*** This bug is a duplicate of bug 542210 *** https://bugs.launchpad.net/bugs/542210 NickJ, your problem is actually bug 191119 or bug 568183 (the latter is currently a dup of the former). -- installing lucid over existing software raid 1 does not work https://bugs.launchpad.net/bugs/560152 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 191119] Re: Installer corrupts raid drive
Note that in bug 560152, NickJ's problem is actually this bug. -- Installer corrupts raid drive https://bugs.launchpad.net/bugs/191119 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 542210] Re: /boot destroyed during install even when formatting disabled (alternate installer)
This is likely a cause of bug 191119 and bug 568183 as well. However, those bugs are not dups; in those bugs existing RAID partitions are corrupted, even if they aren't used during the install. Looking at this report, I would guess the RAID partition corruption is because the installer is trying to use that NEW_LABEL command on the incorrectly detected file systems on the devices comprising the RAID array. The root cause of those bugs is those incorrectly detected file systems. See those bugs for details. Until those bugs are fixed, I would VERY STRONGLY not recommend installing on a production system, or even a test system for that matter. Jason and Ben: very well done investigating this. Collin: not-so-well done. -- /boot destroyed during install even when formatting disabled (alternate installer) https://bugs.launchpad.net/bugs/542210 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 568183] Re: Non-selected Raid Array Corruption from Installer
*** This bug is a duplicate of bug 191119 *** https://bugs.launchpad.net/bugs/191119 Yup, that bug is likely the cause of the corruption of the RAID partitions. If I had to make a guess, that NEW_LABEL command was being used on the incorrectly detected file systems, thus overwriting RAID data. I have no idea how that command works so please correct me if that can't be the case. However, an underlying issue with this bug (and bug 191119) is the installer incorrectly detecting those defunct file systems on the devices comprising the RAID array. Because of that, I'm hesitant to call it a dup, but I don't care so long as the bugs get fixed. As for bug 191119, are you saying the NEW_LABEL command wasn't used on earlier versions of the installer? -- Non-selected Raid Array Corruption from Installer https://bugs.launchpad.net/bugs/568183 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 568183] Re: Non-selected Raid Array Corruption from Installer
*** This bug is a duplicate of bug 191119 *** https://bugs.launchpad.net/bugs/191119 Thanks for taking the time to help investigate this. Check out my reply to you in the mailing list thread for suggestions on recreating the bug. Number 3 especially is required. -- Non-selected Raid Array Corruption from Installer https://bugs.launchpad.net/bugs/568183 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 568183] Re: Non-selected Raid Array Corruption from Installer
*** This bug is a duplicate of bug 191119 *** https://bugs.launchpad.net/bugs/191119 BTW, please use post to bug #191119. Subscribers to this bug will be notified if you post there, but not vice-versa. -- Non-selected Raid Array Corruption from Installer https://bugs.launchpad.net/bugs/568183 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 191119] Re: Installer corrupts raid drive
I'm adding this message from the thread to provide as much information for people trying to recreate this bug as possible; Top-posting for (my) convenience on this one... It's nice to see someone actually trying to recreate the bug instead of just flapping their gums trying to sound smart. If you have the time, could you try recreating it again? I have some suggestions to make it more like my scenario (in fact, number 3 below is required for the problem to occur, and number 4 below is likely to be required). I know these suggestions are long, but it would be appreciated. In for a penny, in for a pound, eh? You'll have to do the first install again, but you won't have to actually go through with the second install. You can cancel after getting past the partitioning screen. I've noticed that when things go awry there are two tell-tale signs: 1. On the partitioning screen, the original (now defunct) file system(s) will be detected and show up. 2. Once you select finish partitioning, the installer will show a list of partition tables that will be modified. One or more RAID partitions will show up on the list, irregardless of that fact that you didn't select them for anything. If those signs are present, the RAID array will be hosed. If the signs are not there, the install will go fine and there's no need to continue. Additionally, you don't have to worry about test data or even mounting the RAID array. When doing the second install, if you post exactly which file systems were detected on the manual partitioning screen and which partitions were shown on the to be modified list once you hit finish partitioning, I'd appreciate it. Now on to the suggestions: 1. It sounds like in your setup you installed for the second time after setting up the RAID array, but before the array finished resyncing for the first time. In my setup, the array had been around for a while and was fully resynced. In fact, I (likely) waited for the array to be fully resynced before even installing XFS on it. If you *did* wait for the drive to finish resyncing before the second install, please RSVP because your array was indeed corrupted, but since it was only one drive the array was somehow able to resync and recover. 2. I was using the ubuntu 10.4 beta 2 server 64-bit disk for the (second) install when things went south. Could you try that one? 3. REQUIRED. It sounds like when doing the second install, you just installed to an existing partition. In order for the problem to occur, you have to remove/create a partition (even though you're leaving the RAID partitions alone). If you recreate the partitions I used (6, below), this will be taken care of. 4. POSSIBLY REQUIRED. When creating the RAID array with the default options as you did in your first test, by default the array is created in degraded mode, with a drive added later and resynced. This makes the initial sync faster. Since I'm a neurotic perfectionist, I always create my arrays with the much more manly and macho --force option to create them properly. Its very possible that doing the initial resync with a degraded array will overwrite the defunct file system, while doing the initial sync in the more proper way will not. Please use the --force option when creating the array to take this possibility into account. 5. My array has 4 drives. If possible, could you scare up a fourth drive? If not, don't worry about it. Especially if you do number 7. 6. Prior to/during the infamous install, my partitions were as follows. If feasible, recreating as much of this as possible would be appreciated: sd[abcd]1 25GB sd[abcd]2 475GB My RAID5 array was sd[abcd]2 set up as md1, and my file systems were: sda1: ext4/ md1: xfs /data sd[bcd]1: (partitioned, but not used) Note I had no swap partition originally. On the manual partition screen of the ill-fated install, I left the sd[abcd]2 partitions alone (RAID array), deleted all the sd[abcd]1 partitions, and created the following partitions: sd[abcd]1: 22GB RAID5 md2 / sd[abcd]3*: 3GB RAID5 md3 (swap) * POSSIBLY REQUIRED: Note that partition 2 of the drives' partition tables was already taken by the RAID, so I created the 3GB partitions as partition 3, even though the sectors in partition 3 physically resided before the sectors in partition 2. This is perfectly legal, if not normal (fdisk will warn you about this). Please try to recreate this condition if you can, because it's very possible that was the source of the problems. BTW, all partitions were primary partitions. If you don't have that much space, you can likely get away with making sd[abcd]2 as small as needed. 7. I simplified when recreating this bug, but in my original scenario I had 2 defunct file systems detected by the installer: one on sda2 and one on sdd2 (both ext4). That's why I couldn't just
[Bug 191119] Re: Installer corrupts raid drive
Logic 101: There is nothing in this report that would even remotely suggest that it's a GRUB problem. By your logic, it could be anything that writes directly to the hard drive, not just GRUB. While it's true that the absence of evidence is not evidence of absence, the absence of evidence *should* tell you to concentrate your effort on the evidence you *do* have. Following your logic, we should also create a separate bug report because it's possible that invaders from Mars, who have cunningly hidden themselves from us thus far, came down and corrupted the original reporter's RAID array right when he was installing Ubuntu. There's no evidence of that (just just there's no evidence it was a GRUB problem), but it *is* technically possible. Also, there is plenty of evidence to suggest it *isn't* GRUB. As I mentioned in my emails several times: 1. GRUB only writes in the first few kilobytes of the disk, which is safely out of the way of the data. Any other GRUB stuff is written to a file system. 2. I've replicated the problem, and simply wiping the left over file system fixes it. If it were a GRUB problem, the problem would continue. Additionally, if this issue were a separate GRUB problem: 3. Ubuntu 8.04 used GRUB version 1, which was extremely mature and well vetted by that point. 4. It would affect ALL distributions that use that version of GRUB, and ALL installs where the user has a RAID drive, and EVERY time the user installs GRUB. This is clearly not the case. 5. The installer actually installs GRUB on ALL of your hard drives (since it doesn't know which one will be active; some other OSs change the active drive at boot), so if that were true, ALL drives would have been corrupted. The reporter clearly stated that only one RAID drive was affected, and he just had to start in degraded mode and resync. Please, stay in school. If you're not in school, go back. -- Installer corrupts raid drive https://bugs.launchpad.net/bugs/191119 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 568183] Re: Non-selected Raid Array Corruption from Installer
*** This bug is a duplicate of bug 191119 *** https://bugs.launchpad.net/bugs/191119 I have no idea what you mean by 'loader-RAID5'... It likely doesn't matter what type of RAID is being used. I also tested on the live CD with the same problem. mdadm isn't present on the live CD and the array wasn't assembled. Once again, the big problem is that the installer writes directly to devices with a RAID superblock. And also once again, the broader problem is the way the installer detects file systems: the installer assumes that any bits it finds lying around on a hard drive are still valid, when in fact they could be left over from previous configurations. -- Non-selected Raid Array Corruption from Installer https://bugs.launchpad.net/bugs/568183 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 568183] Re: Non-selected Raid Array Corruption from Installer
*** This bug is a duplicate of bug 191119 *** https://bugs.launchpad.net/bugs/191119 ** This bug has been marked a duplicate of bug 191119 Installer corrupts raid drive -- Non-selected Raid Array Corruption from Installer https://bugs.launchpad.net/bugs/568183 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 568183] Re: Non-selected Raid Array Corruption from Installer
*** This bug is a duplicate of bug 191119 *** https://bugs.launchpad.net/bugs/191119 Please don't remove the duplicate tag. There are 3 parts to every bug report: 1. an initial set of conditions 2. a procedure that was followed 3. actual results which differ from expected results The reporter started with similar conditions (a RAID array that was unused during the install), followed the same procedure (installed to a device that was not part of the RAID array), and received the same results (a corrupted RAID array because the install wrote directly to a member of the RAID array). Unless you can produce any shred of evidence that can differentiate any of the 3 items above, they are the same bug report. -- Non-selected Raid Array Corruption from Installer https://bugs.launchpad.net/bugs/568183 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 191119] Re: Installer corrupts raid drive
I forgot to mention in my first post that once the problem shows itself, it persists indefinitely across attempts to install Ubuntu. The way I was able to fix the problem at that point was to physically zero out the defunct file system on the disk. This should be obvious, but I'll say it anyway: if zeroing out the defunct file system fixes the problem, then it stands to reason that the cause of the problem is the presence of the defunct file system. In other words, the installer is detecting the defunct file system and screwing up as a result. -- Installer corrupts raid drive https://bugs.launchpad.net/bugs/191119 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 191119] Re: Installer corrupts raid drive
Please see bug #568183 for steps on recreating the issue. -- Installer corrupts raid drive https://bugs.launchpad.net/bugs/191119 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 191119] Re: Installer corrupts raid drive
No, it is NOT fucking fixed. I can't believe it's been OVER TWO YEARS and no one has bothered to even look at this easily reproducible issue? And because of it my (and who knows how many other people's) data is hosed. What issues DO you investigate, if you don't investigate corrupted file systems during the install? I've defended you guys ad nauseum in the past, but I can't avoid it any more: you guys are just plain lazy. I guess you just want a bullet on your resume saying that you're a contributer to Ubuntu, but don't actually want to do any work. I can't just say that you're useless, because useless people just don't do anything and are a drain on society. YOU allowed people's data to be lost because of your buggy garbage that you call code, and you didn't bother to fix it because you're lazy. ** Changed in: parted (Ubuntu) Status: Incomplete = Confirmed -- Installer corrupts raid drive https://bugs.launchpad.net/bugs/191119 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 568183] Re: Non-selected Raid Array Corruption from Installer
*** This bug is a duplicate of bug 191119 *** https://bugs.launchpad.net/bugs/191119 Dup of bug #191119 ** This bug has been marked a duplicate of bug 191119 Installer corrupts raid drive -- Non-selected Raid Array Corruption from Installer https://bugs.launchpad.net/bugs/568183 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 568183] Re: Non-selected Raid Array Corruption from Installer
*** This bug is a duplicate of bug 191119 *** https://bugs.launchpad.net/bugs/191119 Yes, this is a a dup of 19119. Just because his hardware RAID is reporting the problem it doesn't follow that the hardware caused the problem. -- Non-selected Raid Array Corruption from Installer https://bugs.launchpad.net/bugs/568183 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 419501] Re: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)' failed.
Just remember, the point of spring break is to TAKE A BREAK. -- apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)' failed. https://bugs.launchpad.net/bugs/419501 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 178038] Re: npviewer.bin crashed with SIGSEGV
Karun, please explain why you marked the bug as invalid. ** Changed in: nspluginwrapper (Ubuntu) Status: Invalid = Confirmed -- npviewer.bin crashed with SIGSEGV https://bugs.launchpad.net/bugs/178038 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 450554] Re: when upgrading to Karmic from earlier versions of Ubuntu, warn that Maven is no longer supported
Happily, maven has been fixed so this has been rendered moot. :) ** Changed in: update-manager (Ubuntu) Status: New = Invalid -- when upgrading to Karmic from earlier versions of Ubuntu, warn that Maven is no longer supported https://bugs.launchpad.net/bugs/450554 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 416312] Re: Upgrade maven to 2.2.1
w00t! -- Upgrade maven to 2.2.1 https://bugs.launchpad.net/bugs/416312 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 411578] Re: ant shouldn't recommend ant-gcj
I believe this was fixed for a while, but now -gcj is back to recommends. what gives? ** Changed in: ant (Ubuntu) Status: New = Confirmed -- ant shouldn't recommend ant-gcj https://bugs.launchpad.net/bugs/411578 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 411579] Re: ant-optional shouldn't recommend ant-optional-gcj
I believe this was fixed for a while, but now -gcj is back to recommends. what gives? ** Changed in: ant (Ubuntu) Status: New = Confirmed -- ant-optional shouldn't recommend ant-optional-gcj https://bugs.launchpad.net/bugs/411579 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 411596] Re: libxerces2-java shouldn't recommend libxerces2-java-gcj
thanks! -- libxerces2-java shouldn't recommend libxerces2-java-gcj https://bugs.launchpad.net/bugs/411596 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 411590] Re: libjaxp1.3-java shouldn't recommend libjaxp1.3-java-gcj
thanks! -- libjaxp1.3-java shouldn't recommend libjaxp1.3-java-gcj https://bugs.launchpad.net/bugs/411590 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 411592] Re: libxalan2-java shouldn't recommend libxalan2-java-gcj
thanks! -- libxalan2-java shouldn't recommend libxalan2-java-gcj https://bugs.launchpad.net/bugs/411592 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 416312] Re: Upgrade maven to 2.2.1
i haven't played with it much yet, but it looks like 2.2.1 is in the main repo as well! -- Upgrade maven to 2.2.1 https://bugs.launchpad.net/bugs/416312 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 427539] Re: [FFe] Sync libmaven packages from Debian unstable
Mathias, I'm not sure I understand your comment. Isn't it the maintainer's job to maintain Maven? By your logic, if I don't know enough about the trip computer in my car to maintain it, I shouldn't rely on my car? Also, I love Ubuntu and have been using it exclusively since Breezy, but it does have a bit of a reputation for having bugs that go unfixed (often for years) unless a critical mass of people are vocal enough about them. Clearly, maintainers are volunteers and don't have the time to fix every bug, and that's why I would think that comments such as the ones you mentioned are critical for helping you decide which get priority. -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libgoogle-collections-java in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 427539] Re: [FFe] Sync libmaven packages from Debian unstable
Mathias, I'm not sure I understand your comment. Isn't it the maintainer's job to maintain Maven? By your logic, if I don't know enough about the trip computer in my car to maintain it, I shouldn't rely on my car? Also, I love Ubuntu and have been using it exclusively since Breezy, but it does have a bit of a reputation for having bugs that go unfixed (often for years) unless a critical mass of people are vocal enough about them. Clearly, maintainers are volunteers and don't have the time to fix every bug, and that's why I would think that comments such as the ones you mentioned are critical for helping you decide which get priority. -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 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 437016] Re: gnome-about-me crashed with SIGSEGV in pixman_image_composite()
It only crashed that one time... -- gnome-about-me crashed with SIGSEGV in pixman_image_composite() https://bugs.launchpad.net/bugs/437016 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 417164] Re: latest plexus packages breaks Maven
According to bug #427539, they aren't going to fix this for Karmic and will likely just drop the Maven package entirely. I hope they warn people who are considering upgrading... -- latest plexus packages breaks Maven https://bugs.launchpad.net/bugs/417164 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 427539] Re: [FFe] Sync libmaven packages from Debian unstable
I agree with comment #37. Also, during the upgrade process from earlier versions of Ubuntu you must warn people (before they commit to the upgrade) that maven will no longer work. -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libgoogle-collections-java in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 427539] Re: [FFe] Sync libmaven packages from Debian unstable
Bug #417164 and Bug #416312 explain why Maven no longer works. -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libgoogle-collections-java in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 427539] Re: [FFe] Sync libmaven packages from Debian unstable
Whoops, wrong bug report... -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libgoogle-collections-java in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 427539] Re: [FFe] Sync libmaven packages from Debian unstable
I agree with comment #37. Also, during the upgrade process from earlier versions of Ubuntu you must warn people (before they commit to the upgrade) that maven will no longer work. -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 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 450554] [NEW] when upgrading to Karmic from earlier versions of Ubuntu, warn that Maven is no longer supported
Public bug reported: I imagine this belongs in the update-manager package but I'm not sure, since it involves a special case when upgrading from previous versions of Ubuntu. Previous versions of Ubuntu had a working version of Apache Maven in the repository, and many people depend on it for software development. However, as discussed in bug #427539 and others, the current version of Maven doesn't work and won't be fixed until Lucid. Most likely it will be removed from the repository entirely. Because of this, the upgrade process must warn people who have Maven installed that upgrading to 9.10 will remove Maven or render it non- functional. This should be done before people commit to the upgrade. Additionally, the release notes should mention that Maven is no longer supported so that new installers can make an informed decision about which version of Ubuntu to install. ** Affects: ubuntu Importance: Undecided Status: New -- when upgrading to Karmic from earlier versions of Ubuntu, warn that Maven is no longer supported https://bugs.launchpad.net/bugs/450554 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 450554] Re: when upgrading to Karmic from earlier versions of Ubuntu, warn that Maven is no longer supported
Bug #417164 and Bug #416312 explain why Maven no longer works. -- when upgrading to Karmic from earlier versions of Ubuntu, warn that Maven is no longer supported https://bugs.launchpad.net/bugs/450554 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 427539] Re: [FFe] Sync libmaven packages from Debian unstable
Bug #417164 and Bug #416312 explain why Maven no longer works. -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 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 427539] Re: [FFe] Sync libmaven packages from Debian unstable
Whoops, wrong bug report... -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 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 417164] Re: latest plexus packages breaks Maven
A duplicate of itself? :) ** Changed in: maven2 (Ubuntu) Status: Invalid = Confirmed -- latest plexus packages breaks Maven https://bugs.launchpad.net/bugs/417164 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 445484] [NEW] incorrect completion for new upstart commands
Public bug reported: Binary package hint: bash-completion Upstart adds four new commands for controlling services: status, start, stop, and restart. On lines beginning with these commands, bash-completion should offer the list of services, similar to how the service command currently does. For example, starting a line with: $ sudo status g and pressing the TAB key should offer gdm and any other services beginning with the letter 'g' (grub-common). Currently completion offers files in the current directory starting with 'g'. ProblemType: Bug Architecture: amd64 CheckboxSubmission: c2fec9292a0fc6a96471b15811ba9a27 CheckboxSystem: 090f50ffa15f2babaae2e4e2bf775960 Date: Wed Oct 7 10:15:06 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: bash-completion 1:1.0-3ubuntu2 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.39-generic SourcePackage: bash-completion Uname: Linux 2.6.31-12-generic x86_64 ** Affects: bash-completion (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- incorrect completion for new upstart commands https://bugs.launchpad.net/bugs/445484 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 445484] Re: incorrect completion for new upstart commands
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/33231310/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/33231311/XsessionErrors.txt -- incorrect completion for new upstart commands https://bugs.launchpad.net/bugs/445484 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 411588] Re: libitext-java shouldn't recommend libitext-java-gcj
Anybody home? ** Changed in: libitext-java (Ubuntu) Status: New = Confirmed -- libitext-java shouldn't recommend libitext-java-gcj https://bugs.launchpad.net/bugs/411588 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 445513] Re: can't connect to VPN
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/33232733/Dependencies.txt ** Attachment added: Gconf.txt http://launchpadlibrarian.net/33232734/Gconf.txt ** Attachment added: IpAddr.txt http://launchpadlibrarian.net/33232736/IpAddr.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/33232737/IwConfig.txt ** Attachment added: NetDevice.eth0.txt http://launchpadlibrarian.net/33232739/NetDevice.eth0.txt ** Attachment added: NetDevice.lo.txt http://launchpadlibrarian.net/33232741/NetDevice.lo.txt ** Attachment added: NetDevice.pan0.txt http://launchpadlibrarian.net/33232742/NetDevice.pan0.txt ** Attachment added: NetDevice.wlan0.txt http://launchpadlibrarian.net/33232744/NetDevice.wlan0.txt ** Attachment added: NetDevice.wmaster0.txt http://launchpadlibrarian.net/33232745/NetDevice.wmaster0.txt ** Attachment added: PciNetwork.txt http://launchpadlibrarian.net/33232746/PciNetwork.txt ** Attachment added: RfKill.txt http://launchpadlibrarian.net/33232747/RfKill.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/33232748/XsessionErrors.txt ** Attachment added: nm-system-settings.conf.txt http://launchpadlibrarian.net/33232749/nm-system-settings.conf.txt -- can't connect to VPN https://bugs.launchpad.net/bugs/445513 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 445513] [NEW] can't connect to VPN
Public bug reported: Binary package hint: network-manager When I try to connect to my office VPN, I get an error message like, Can't connect to VPN because the VPN service stopped unexpectedly. This connection worked fine in Jaunty and up until recently in Karmic. Relevant syslog messages: Oct 7 10:28:46 europa NetworkManager: info Starting VPN service 'org.freedesktop.NetworkManager.vpnc'... Oct 7 10:28:46 europa NetworkManager: info VPN service 'org.freedesktop.NetworkManager.vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 5304 Oct 7 10:28:46 europa NetworkManager: WARN vpn_service_watch_cb(): VPN service 'org.freedesktop.NetworkManager.vpnc' exited with error: 1 Oct 7 10:28:46 europa NetworkManager: info Policy set 'Guest-CNE' (wlan0) as default for routing and DNS. Oct 7 10:28:52 europa NetworkManager: info VPN service 'org.freedesktop.NetworkManager.vpnc' did not start in time, cancelling connections ProblemType: Bug Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory CheckboxSubmission: c2fec9292a0fc6a96471b15811ba9a27 CheckboxSystem: 090f50ffa15f2babaae2e4e2bf775960 Date: Wed Oct 7 10:55:17 2009 DistroRelease: Ubuntu 9.10 IfupdownConfig: auto lo iface lo inet loopback IpRoute: 10.1.24.0/23 dev wlan0 proto kernel scope link src 10.1.24.193 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 10.1.24.1 dev wlan0 proto static NonfreeKernelModules: nvidia Package: network-manager 0.8~a~git.20091005t192303.1d28ad1-0ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.39-generic SourcePackage: network-manager Uname: Linux 2.6.31-12-generic x86_64 WifiSyslog: Oct 7 10:28:46 europa NetworkManager: info Starting VPN service 'org.freedesktop.NetworkManager.vpnc'... Oct 7 10:28:46 europa NetworkManager: info VPN service 'org.freedesktop.NetworkManager.vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 5304 Oct 7 10:28:46 europa NetworkManager: WARN vpn_service_watch_cb(): VPN service 'org.freedesktop.NetworkManager.vpnc' exited with error: 1 Oct 7 10:28:46 europa NetworkManager: info Policy set 'Guest-CNE' (wlan0) as default for routing and DNS. Oct 7 10:28:52 europa NetworkManager: info VPN service 'org.freedesktop.NetworkManager.vpnc' did not start in time, cancelling connections ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- can't connect to VPN https://bugs.launchpad.net/bugs/445513 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 428783] Re: shadow remains on desktop after closing applet window
Of course i checked both the main repo and the US mirror and it wasn't there. But it's there as of today so good enough. -- shadow remains on desktop after closing applet window https://bugs.launchpad.net/bugs/428783 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 427539] Re: [FFe] Sync libmaven packages from Debian unstable
Well put Martin! For a while there I thought everyone had gone nuts. I know no one wants extra work this close to a release but there are a lot of people (myself included) who depend on Maven. -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 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 428783] Re: shadow remains on desktop after closing applet window
I updated to the latest packages and the shadow is still here for me... ** Changed in: compiz (Ubuntu) Status: Fix Released = Confirmed -- shadow remains on desktop after closing applet window https://bugs.launchpad.net/bugs/428783 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 408030] Re: Problem when resizing and the Panels
This is still not working. It looks as though none of the bugs that compiz (1:0.8.3+git20091005-0ubuntu5) was supposed to address have been... ** Changed in: compiz (Ubuntu) Status: Fix Released = Confirmed -- Problem when resizing and the Panels https://bugs.launchpad.net/bugs/408030 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 408030] Re: Problem when resizing and the Panels
Actually, it looks like the clock shadow fix is the only other issue addressed by this version that's also not working. -- Problem when resizing and the Panels https://bugs.launchpad.net/bugs/408030 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 428783] Re: shadow remains on desktop after closing applet window
The clock applet. Additionally, issue #408030 also is not resolved for me, but other issues in this version are (at least the polkit focus issue) are working. Here's some possibly relevant information: amd64 nVidia driver 185 clean install as of about 5 days ago For those that it's working, what's you hardware? -- shadow remains on desktop after closing applet window https://bugs.launchpad.net/bugs/428783 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 428783] Re: shadow remains on desktop after closing applet window
Yup, I rebooted a couple of times. -- shadow remains on desktop after closing applet window https://bugs.launchpad.net/bugs/428783 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 428783] Re: shadow remains on desktop after closing applet window
added a picture showing the shadow and compiz version ** Attachment added: problem still exists for me http://launchpadlibrarian.net/33050354/Screenshot-2.png -- shadow remains on desktop after closing applet window https://bugs.launchpad.net/bugs/428783 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 428783] Re: shadow remains on desktop after closing applet window
Acer FX laptop 1920x1200 nVidia 9800 GTS -- shadow remains on desktop after closing applet window https://bugs.launchpad.net/bugs/428783 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 428783] Re: shadow remains on desktop after closing applet window
So the question is, why is my system showing as fully updated then? -- shadow remains on desktop after closing applet window https://bugs.launchpad.net/bugs/428783 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 428783] Re: shadow remains on desktop after closing applet window
Dave, how did you get them? According to synaptic, the only one that was updated was compiz. -- shadow remains on desktop after closing applet window https://bugs.launchpad.net/bugs/428783 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 428783] Re: shadow remains on desktop after closing applet window
It looks like the packages were built for x86 but not amd64... -- shadow remains on desktop after closing applet window https://bugs.launchpad.net/bugs/428783 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 428783] Re: shadow remains on desktop after closing applet window
Or at least the packages were not released on amd64. ** Changed in: compiz (Ubuntu) Status: Fix Released = Fix Committed ** Changed in: compiz (Ubuntu) Status: Fix Committed = Confirmed -- shadow remains on desktop after closing applet window https://bugs.launchpad.net/bugs/428783 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 428783] Re: shadow remains on desktop after closing applet window
No, it's not in http://us.archive.ubuntu.com/ubuntu/dists/karmic/main /binary-amd64/Packages.gz which is what counts. -- shadow remains on desktop after closing applet window https://bugs.launchpad.net/bugs/428783 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 436973] Re: package linux-image-2.6.31-11-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
I think this occurred right after I did a clean install of a daily build (first update). It hasn't happened since. -- package linux-image-2.6.31-11-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 https://bugs.launchpad.net/bugs/436973 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 435036] Re: acerhdf: unknown (unsupported) BIOS version Gateway
The fix to bug 435958 seems like it should have fixed this as well, but it didn't. :( -- acerhdf: unknown (unsupported) BIOS version Gateway https://bugs.launchpad.net/bugs/435036 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 427539] Re: [FFe] Sync libmaven packages from Debian unstable
great! perhaps we can get this 'wishlist' item added then :) -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 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 436425] Re: nm-connection-editor crashed with SIGSEGV in gtk_container_remove()
same here. i tried to edit a vpn connection. ** Changed in: network-manager-applet (Ubuntu) Status: Incomplete = Confirmed -- nm-connection-editor crashed with SIGSEGV in gtk_container_remove() https://bugs.launchpad.net/bugs/436425 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 438820] [NEW] desktop install boots to TTY1 instead of GDM
Public bug reported: Binary package hint: upstart After recent updates to Karmic on my laptop (when most of the Sys-V stuff was replaced by upstart), booting my laptop brings me to TTY1 instead of GDM. Only after I manually switch to TTY7 will GDM finish loading and display the graphical login prompt. I tried a clean reinstall of Karmic and I still have the same problem, so I imagine it's some sort of race condition with the new upstart stuff. My computer is a Gateway FX laptop. Ignore anything attached to this report; i had to submit it from my desktop at work which has Jaunty installed. Forcing people to use ubuntu-bug to create a bug report is ridiculous. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: upstart 0.3.9-8 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: upstart Uname: Linux 2.6.28-15-generic i686 ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- desktop install boots to TTY1 instead of GDM https://bugs.launchpad.net/bugs/438820 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 438820] Re: desktop install boots to TTY1 instead of GDM
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/32684093/Dependencies.txt -- desktop install boots to TTY1 instead of GDM https://bugs.launchpad.net/bugs/438820 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 438820] Re: desktop install boots to TTY1 instead of GDM
As I said, ignore the stuff above. ** Summary changed: - desktop install boots to TTY1 instead of GDM + desktop install of Karmic boots to TTY1 instead of GDM ** Description changed: Binary package hint: upstart After recent updates to Karmic on my laptop (when most of the Sys-V stuff was replaced by upstart), booting my laptop brings me to TTY1 instead of GDM. Only after I manually switch to TTY7 will GDM finish loading and display the graphical login prompt. I tried a clean reinstall of Karmic and I still have the same problem, so I imagine it's some sort of race condition with the new upstart stuff. My computer is a Gateway FX laptop. Ignore anything attached to this report; i had to submit it from my desktop at work which has Jaunty installed. Forcing people to use ubuntu-bug to create a bug report is ridiculous. - - ProblemType: Bug - Architecture: i386 - DistroRelease: Ubuntu 9.04 - Package: upstart 0.3.9-8 - ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: upstart - Uname: Linux 2.6.28-15-generic i686 ** Summary changed: - desktop install of Karmic boots to TTY1 instead of GDM + desktop install of Karmic boots to TTY1 instead of GDM on TTY7 ** Description changed: Binary package hint: upstart After recent updates to Karmic on my laptop (when most of the Sys-V stuff was replaced by upstart), booting my laptop brings me to TTY1 instead of GDM. Only after I manually switch to TTY7 will GDM finish loading and display the graphical login prompt. I tried a clean reinstall of Karmic and I still have the same problem, so I imagine it's some sort of race condition with the new upstart stuff. My computer is a Gateway FX laptop. - Ignore anything attached to this report; i had to submit it from my + Ignore anything attached to this report; I had to submit it from my desktop at work which has Jaunty installed. Forcing people to use ubuntu-bug to create a bug report is ridiculous. ** Description changed: Binary package hint: upstart After recent updates to Karmic on my laptop (when most of the Sys-V stuff was replaced by upstart), booting my laptop brings me to TTY1 instead of GDM. Only after I manually switch to TTY7 will GDM finish loading and display the graphical login prompt. I tried a clean reinstall of Karmic and I still have the same problem, so I imagine it's some sort of race condition with the new upstart stuff. - My computer is a Gateway FX laptop. + My computer is a Gateway FX laptop with 64-bit Karmic. Ignore anything attached to this report; I had to submit it from my desktop at work which has Jaunty installed. Forcing people to use ubuntu-bug to create a bug report is ridiculous. -- desktop install of Karmic boots to TTY1 instead of GDM on TTY7 https://bugs.launchpad.net/bugs/438820 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 438820] Re: desktop install of Karmic boots to TTY1 instead of GDM on TTY7
*** This bug is a duplicate of bug 434361 *** https://bugs.launchpad.net/bugs/434361 ** This bug has been marked a duplicate of bug 434361 gdm sometimes fails to switch to VT7 after new upstart merge -- desktop install of Karmic boots to TTY1 instead of GDM on TTY7 https://bugs.launchpad.net/bugs/438820 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 427539] Re: [FFe] Sync libmaven packages from Debian unstable
* compatible* -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 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 427539] Re: [FFe] Sync libmaven packages from Debian unstable
The new version of libplexus is not compatable with Maven 2.0.9, so Maven does not work at all. This is a blocker bug, not a wishlist item. Please change. -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 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 427539] Re: [FFe] Sync libmaven packages from Debian unstable
I meant that the Maven that is currently in Karmic (2.0.9) does is completely broken (does not work at all with the synced version of libplexus). In this case Maven must be synced with libplexus in order for Maven to work. Since libplexus has already been synced, syncing the Maven package is no longer optional (unless having a Maven package in Karmic that doesn't work is considered acceptable). Therefore this can't be considered a wishlist item on Karmic. -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 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 427539] Re: [FFe] Sync libmaven packages from Debian unstable
The other alternative would be to slot the old versions of Maven's dependencies. -- [FFe] Sync libmaven packages from Debian unstable https://bugs.launchpad.net/bugs/427539 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 411588] Re: libitext-java shouldn't recommend libitext-java-gcj
Can someone bump up the priority on this? Almost all of the other Java libraries have been changed in this manner for Karmic, and this is the only library package left that's preventing Maven from installing properly. -- libitext-java shouldn't recommend libitext-java-gcj https://bugs.launchpad.net/bugs/411588 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 436973] [NEW] package linux-image-2.6.31-11-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: upgrading packages via update-manager ProblemType: Package Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alvin 6179 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf450 irq 21' Mixer name : 'Nvidia ID 5' Components : 'HDA:14f15051,107b0698,0010 HDA:14f12c06,10250093,0010 HDA:10de0005,10de0101,0010' Controls : 14 Simple ctrls : 7 Date: Fri Sep 25 20:42:38 2009 DistroRelease: Ubuntu 9.10 ErrorMessage: subprocess new pre-installation script returned error exit status 128 MachineType: Gateway P-7805u Package: linux-image-2.6.31-11-generic (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=d49dcbcc-ab51-4ad8-bf15-8470756981ce ro quiet splash ProcVersionSignature: Ubuntu 2.6.31-10.35-generic RelatedPackageVersions: linux-backports-modules-2.6.31-10-generic N/A linux-firmware 1.19 SourcePackage: linux Title: package linux-image-2.6.31-11-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Uname: Linux 2.6.31-10-generic x86_64 dmi.bios.date: 09/17/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 9C.11.00 dmi.board.vendor: Gateway dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr9C.11.00:bd09/17/2008:svnGateway:pnP-7805u:pvrGatewayMG1:rvnGateway:rn:rvrNotApplicable:cvnGateway:ct10:cvrN/A: dmi.product.name: P-7805u dmi.product.version: Gateway MG1 dmi.sys.vendor: Gateway ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package -- package linux-image-2.6.31-11-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 https://bugs.launchpad.net/bugs/436973 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 436973] Re: package linux-image-2.6.31-11-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/32466954/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/32466955/AplayDevices.txt ** Attachment added: AptOrdering.txt http://launchpadlibrarian.net/32466956/AptOrdering.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/32466957/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/32466958/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/32466959/Card0.Codecs.codec.0.txt ** Attachment added: Card0.Codecs.codec.1.txt http://launchpadlibrarian.net/32466960/Card0.Codecs.codec.1.txt ** Attachment added: Card0.Codecs.codec.2.txt http://launchpadlibrarian.net/32466961/Card0.Codecs.codec.2.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/32466962/CurrentDmesg.txt ** Attachment added: Dmesg.txt http://launchpadlibrarian.net/32466963/Dmesg.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/32466964/DpkgTerminalLog.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/32466965/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/32466966/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/32466967/Lsusb.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/32466968/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/32466969/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/32466970/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/32466971/ProcModules.txt ** Attachment added: RfKill.txt http://launchpadlibrarian.net/32466972/RfKill.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/32466973/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/32466974/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/32466975/WifiSyslog.txt -- package linux-image-2.6.31-11-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 https://bugs.launchpad.net/bugs/436973 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 435036] [NEW] acerhdf: unknown (unsupported) BIOS version Gateway
Public bug reported: When trying to boot Karmic, I get this error in dmesg: [ 15.943654] acerhdf: Acer Aspire One Fan driver, v.0.5.16 [ 15.943658] acerhdf: unknown (unsupported) BIOS version Gateway /P-7805u/9C.11.00 , please report, aborting! This appears similar to other bug reports, but I didn't see one for this particular computer model (Gateway FX - really made by Acer). ** Affects: ubuntu Importance: Undecided Status: New -- acerhdf: unknown (unsupported) BIOS version Gateway https://bugs.launchpad.net/bugs/435036 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 435036] Re: acerhdf: unknown (unsupported) BIOS version Gateway
** Attachment added: full dmesg output http://launchpadlibrarian.net/32296850/dmesg -- acerhdf: unknown (unsupported) BIOS version Gateway https://bugs.launchpad.net/bugs/435036 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 417301] Re: update-manager crashed with GError in __init__()
ditto #16 -- update-manager crashed with GError in __init__() https://bugs.launchpad.net/bugs/417301 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 417964] Re: Authentication always required to unmount media
I just installed the latest updates. The 'eject' button on my laptop DVD works once for me after I reboot, but after I re-insert the disc, the eject button doesn't work again. I can eject through Nautilus without a password, however... ** Changed in: devicekit-disks (Ubuntu Karmic) Status: Fix Released = Confirmed -- Authentication always required to unmount media https://bugs.launchpad.net/bugs/417964 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 417964] Re: Authentication always required to unmount media
The eject button on the DVD *will* work subsequent times only after I manually unmount (for example, using the Unmount option in Nautilus. ** Changed in: devicekit Status: Fix Released = Confirmed -- Authentication always required to unmount media https://bugs.launchpad.net/bugs/417964 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 417964] Re: Authentication always required to unmount media
To avoid any confusion, after inserting the disc wait until it's automatically mounted. After the disc is mounted, you can't use the eject button on the DVD drive any more. -- Authentication always required to unmount media https://bugs.launchpad.net/bugs/417964 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 48216] Re: renaming computer does not update correctly the files: hosts, hostnames
ah, thanks -- renaming computer does not update correctly the files: hosts, hostnames https://bugs.launchpad.net/bugs/48216 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 411580] Re: libantlr-java shouldn't recommend libantlr-java-gcj
yup ** Changed in: antlr (Ubuntu) Status: Fix Released = Confirmed -- libantlr-java shouldn't recommend libantlr-java-gcj https://bugs.launchpad.net/bugs/411580 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 411580] Re: libantlr-java shouldn't recommend libantlr-java-gcj
whoops ** Changed in: antlr (Ubuntu) Status: Confirmed = Fix Released -- libantlr-java shouldn't recommend libantlr-java-gcj https://bugs.launchpad.net/bugs/411580 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 386307] Re: -java package should not recommend -java-gcj counterpart on all architectures
yup, i created separate bugs for the ones that Maven depends on, at least. :) -- -java package should not recommend -java-gcj counterpart on all architectures https://bugs.launchpad.net/bugs/386307 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 416025] Re: gdebi-gtk crashed with TypeError in get_dependencies()
yup, the latest updates worked for me as well. i didn't need to reinstall gdebi. -- gdebi-gtk crashed with TypeError in get_dependencies() https://bugs.launchpad.net/bugs/416025 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 416025] Re: gdebi-gtk crashed with TypeError in get_dependencies()
can we add 'ant' and 'ant-optional' to this list? -- gdebi-gtk crashed with TypeError in get_dependencies() https://bugs.launchpad.net/bugs/416025 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 386307] Re: -java package should not recommend -java-gcj counterpart on all architectures
can we add 'ant' and 'ant-optional' to this list? -- -java package should not recommend -java-gcj counterpart on all architectures https://bugs.launchpad.net/bugs/386307 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 416025] Re: gdebi-gtk crashed with TypeError in get_dependencies()
whoops, wrong bug! disregard #8 -- gdebi-gtk crashed with TypeError in get_dependencies() https://bugs.launchpad.net/bugs/416025 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 386307] Re: -java package should not recommend -java-gcj counterpart on all architectures
also, 'libitext-java' would be nice since it's needed by Maven. here are others that i'm aware of: (canonical) libdb4.6-java libdb4.7-java libsac-java libsxltc-java (universe) libaxis-java libbcmail-java libbcpg-java libbctsp-java libitext-java libswt3.2-gtk-java -- -java package should not recommend -java-gcj counterpart on all architectures https://bugs.launchpad.net/bugs/386307 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
