I agree you are entirely right on principle; I thought the appearance of
xserver 1.11 in PPAs presaged its appearance in Oneiric, but you set me
straight on that. There would be no sense having packages in the same
repository break one another. Anyone's Oneiric which failed to boot
after an
Public bug reported:
I'm sure this comes as no news, but the dependency on xorg-video-abi-10
and xorg-input-abi-12 will be bad news if and when xserver 1.11 oozes
out of its present cage in X.Org Edgers and into Oneiric repositories.
Forgive me if this is entirely misdirected. Maybe Robert or
Anecdotally, updating mountall from 2.25ubuntu1 (natty) to 2.31
(oneiric) is what appears to croak my system (which is virtualized). The
system hangs at mountall on the next cold boot.
I thought it was either base-files or initscripts, but since upgrading
either one of these takes mountall with
On Fri, Jul 15, 2011, Steve Langasek wrote:
Oneiric is a development release which is currently in the alpha stage of
its development cycle. Total unusability is a very real and ordinary risk
of running the software at this stage.
I'm not complaining, since I'm not one of your developers, and
While I might still have a valid bug (inability to build kernel modules
from source is a real problem, especially for things like VMware Tools,
in all post-BKL kernels), I've given up completely on Ubuntu virtual
kernels for precisely the application for which they were expressly
designed. For
I'm sure you've already seen today's drop in SF [2011.07.19-450511]
which supposedly fixes the gcc compilation issues, so I won't torture
you gentlemen further.
I see new code related to FUSE blocking filesystems which they don't
talk about, probably because it's coming from upstream, and VMware
I'm sure you've already seen today's drop in SF [2011.07.19-450511]
which supposedly fixes the gcc compilation issues, so I won't torture
you gentlemen further.
I see new code related to FUSE blocking filesystems which they don't
talk about, probably because it's coming from upstream, and VMware
My report appears to be invalid. My Plymouth hadn't been updated to take
the /run transition into account, even if initramfs had been. At least
that's the conclusion I draw. After reverting to a stable baseline,
updating Plymouth, then updating base-files and initscripts, everything
worked, even
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807845
Title:
dpkg crashed with SIGSEGV in debsums
To manage notifications about this bug go to:
Thank you gentlemen for looking into this. I do not have your skills, so
while I suspect something is still wrong somewhere, it's difficult to
isolate in a way that would be useful to you. On one virtualized system,
Plymouth boots to a black screen, which I'm willing to overlook since
the login
Excuse me if it is inappropriate to say this here, but a seemingly
related series of breaking changes still persists. First, X lost all
input devices. Then, there was a hang on boot. The Plymouth logo stopped
spinning and the system just croaked; the login screen never appeared.
The latest
Public bug reported:
Please excuse me if I am reporting against the wrong package, or even if
this report is invalid altogether, but I was told in no uncertain terms
that today's update of initramfs-tools resolved this issue. It does
not. I survived the botched, uncoordinated migration to /run,
Thanks in advance for putting up with the observations of a clueless
outsider ;-)
* The transitional-package approach, which I think is what you used for
open-vm-toolbox in ppa15, worked nicely.
* The conflicting-package approach, which I think is what you are using
for open-vm-toolbox in ppa19,
Thanks in advance for putting up with the observations of a clueless
outsider ;-)
* The transitional-package approach, which I think is what you used for
open-vm-toolbox in ppa15, worked nicely.
* The conflicting-package approach, which I think is what you are using
for open-vm-toolbox in ppa19,
Nate, I wish I was more than a newcomer; I'd gladly help you, since I am
getting obsessed to an unhealthy and unnatural degree with making VMware
work from am end-user perspective. I realize this is sick ;-)
If I weren't so frustrated that the Debian package maintainers seem to
be indifferent,
Nate, I wish I was more than a newcomer; I'd gladly help you, since I am
getting obsessed to an unhealthy and unnatural degree with making VMware
work from am end-user perspective. I realize this is sick ;-)
If I weren't so frustrated that the Debian package maintainers seem to
be indifferent,
I think that response was beneath you. PLEASE DO NOT USE ALL CAPS TO
SHOUT AT ME. Don't worry, I won't bother you again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/776103
I think that response was beneath you. PLEASE DO NOT USE ALL CAPS TO
SHOUT AT ME. Don't worry, I won't bother you again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/776103
Title:
package
Nate, I believe you are on the right track.
I know this is not the type of feedback you need (or want) in this
venue. After all, my virtual platform is Debian Sid, not Oneiric; and my
kernel is 2.6.39-2, not 3.0-rcx. But the underlying problems seem to
be from the same causes.
And I know all the
Nate, I believe you are on the right track.
I know this is not the type of feedback you need (or want) in this
venue. After all, my virtual platform is Debian Sid, not Oneiric; and my
kernel is 2.6.39-2, not 3.0-rcx. But the underlying problems seem to
be from the same causes.
And I know all the
Nate, your efforts are much appreciated and I'll be following them with
great interest. While I still use the proprietary VMWare Tools [8.4.6
Build 385536] on my Ubuntu 11.04 guest [kernel 2.6.39-3], they seem to
be quite broken on Debian Sid [kernel 2.6.39-1].
I was quite sure they would still
Nate, your efforts are much appreciated and I'll be following them with
great interest. While I still use the proprietary VMWare Tools [8.4.6
Build 385536] on my Ubuntu 11.04 guest [kernel 2.6.39-3], they seem to
be quite broken on Debian Sid [kernel 2.6.39-1].
I was quite sure they would still
Thanks for the suggestion, Daniel.
On those few occasions when I am really desperate to hear sound, I fall
back to the 2.6.38-10-generic kernel (2.6.38-10-virtual has no sound
either).
In fact, there has really been no sound since Maverick.
I believe that's because I've installed the
Public bug reported:
Binary package hint: alsa-source
root@ubuntu:~# hwinfo --sound
52: PCI 201.0: 0401 Multimedia audio controller
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_1274_1371
Unique ID: GA8e.FGsk7T8RAT9
Parent ID: 7EWs.3XzZP_1GzlF
SysFS ID:
** Attachment added: module-assistant buildlog attached
https://bugs.launchpad.net/bugs/795815/+attachment/2164715/+files/alsa-source.buildlog.2.6.39-3-virtual.1307758419
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
25 matches
Mail list logo
