*** 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
(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
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
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
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
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.
--
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
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
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
*** 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
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.
--
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,
*** 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
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
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
*** 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
*** 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
*** 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
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
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
*** 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
*** 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
*** 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
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:
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
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
*** 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
*** 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
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
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
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
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
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,
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
** 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
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.
--
** 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:
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
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,
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
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
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
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
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,
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
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
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
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
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.
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
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
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
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
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.
--
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
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
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
** 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.
--
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
*** 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
* 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
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
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
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
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
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
** 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
**
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
** 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.
--
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
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)
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
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
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
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
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
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
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.
--
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
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
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
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
1 - 100 of 187 matches
Mail list logo
