Downloaded Daily Build for AMD64 4/8/16 15:59 at 4/8/16 15:49. Can't
explain why time stamp was 10 minutes ahead of current time. This fix
does not seem to be incorporated with this build. Even though the fix
package accountsservice - 0.6.40-2ubuntu9 is available, it does no good
unless it is
I downloaded 4/7/16 15:37 Gnome AMD64 iso and this problem still exists.
I see that the issue was marked as Fixed. Is this drop supposed to
contain the fix or is there a delay in seeing this in the drop?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Attempted Remove and designated packages not found.
On Wed, Mar 16, 2016 at 4:47 PM, kevin gunn
wrote:
> just double checking, can you
>
> $ sudo apt-get remove mir-client-platform-mesa3 mir-client-platform-
> mesa2 mir-client-platform-mesa1
>
> these are very old, if
Attaching two screen shots. First is at Signon prompt waiting for Password.
Second is after password entered and "Enter" key depressed.
ieldI don't get another Signon Screen. I get a hung state with an
intermediate screen with No Password entry field. Seems like the signon
request is accepted and
Public bug reported:
Attempted to Install and Login using Unity8 on top of Ubuntu 16.04 Desktop
Build.
Am amble to Signon to Unity Desktop distributed by build however when I attempt
to singon to Unity8, the password accepts but the Signon Screen does not go
away. The only thing I can do is
Public bug reported:
unknown
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu7
ProcVersionSignature: Ubuntu 4.2.0-16.19-lowlatency 4.2.3
Uname: Linux 4.2.0-16-lowlatency x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Thu Oct 15 05:09:04 2015
Public bug reported:
APT-GET UPDATE hung and finally crashed.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: udev 225-1ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
Uname: Linux 4.2.0-11-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Fri Oct
I'm sorry, I don't know how to proceed with this issue.
Early on, you asked for Verbose Logging from Virtualbox. I supplied the
Machine Log for the failing Guest and I knew Verbose was probably Defaulted
to Off.
Since then, I have found the commands to change the running machine
"VBoxManage
My interpretation of this update is that I believe you are trying to
suggest that I apply this patch to correct a scaling problem with HDA,
Is that what you are trying to communicate?
Also, I understand that this code is or maybe broken but why are we working
on Intel HDA when the default ICH
LocutusOfBorg, I am in desperate need of help on this issue in several
areas.
I would have hoped this would have been much easier to report and let you
experts work the issue however even though I can describe what I am seeing,
it is very difficult to supply the respective folks with enough
I have no idea what "the output of alsa-info.sh" is. Is this some sort of
Shell script that needs to be run?
If so, when do you run it,
a) One time only,
b)Before changing the Slider Position,
Giving me these short segments of details without specific instructions is
causing me to give up on
I went ahead and followed documentation on the VirtualBox Forum to fork the
current VirtualBox Source. I believe that I have resolved all of the
installation errors that were due to errors in the packaging and
obsolescence of packages in the Ubuntu Release I am running on. i have not
attempted to
I had to make corrections to the aplay command specified. The file to be
played back must exist for the results to be displayed. The attached txt
file has the results from the aplay command on the Lubuntu Distribution.
I have to go off the net soon to participate in Daytime activities.
I still
Attempting to attached two zip files. First logs and Screenshots from
Lubuntu 15.10 Distribution. Second is Logs and screenshots from Mate 15.10.
On Sat, Aug 29, 2015 at 3:11 AM, Raymond 1487...@bugs.launchpad.net
wrote:
if (pbus-pcms[0].r[0].slots (1 AC97_SLOT_PCM_SLEFT)) {
I'll attempt to describe the patterns and symptoms I am noticing and with a
subsequent email attach ScreenShot files to support those observations.
With this latest round of testing the Ubuntu 15.10 daily drops, most of
the distributions are behaving correctly in that Volume Slider does control
Regarding this update and the previous update referencing a Verbose VBox
Log.
Trying to find out what a Verbose Log is or how to activate Verbose
logging, I looked for Verbose in the user manual and got hits in Chapter 8
of
the User's manual. I see references to VBoxmanage command syntax. It is
First, you dd not answer my question on whether or not I could attach the
files directly to this email and whether you would be able to get them or
do I need to upload them somewhere?
Second, I want to clarify the Verbose Log you want. Is that the Log from
Show Log CTRL+L? If so, I assume you
I discovered that the Volume Slider problem exists even after the clean
install of Virtual Box 5.0.2.
I have screenshots that document the errant behavior.
I am not used to submitting documentation for problems other than typing in
descriptive text when prompted.
Can I attach the screenshot
VirtualBox ticket 14508 created to report this issue. Any comments from the
Audio team can be submitted referencing that ticket number.
On Thu, Aug 27, 2015 at 3:34 AM, LocutusOfBorg
costamagnagianfra...@yahoo.it wrote:
Hi, can you please report then on the upstream Virtualbox ticket page?
or
You made a lot of updates to this record and I cannot tell whether or not
you hit on issues that requires coding changes on the Ubuntu Audio side.
I did want to report that I seem to have found a resolution that I am
satisfied with.
To summarize, I mentioned that after backing off from Virtual
I believe I have discovered the cause of the problem.
Your prompting me to look at the Open Issues for VirtualBox pointed out
that I was on V5.0.0 and when I went to the Downloads Page, V5.0.2 was
currently available.
VirtualBox will send a push notification when the team indicates and
important
Correction to last comments concerning problem resolution.
I inadvertently referred to backing off from Version 5.0.2 to VirtualBox
Release 4.33.
The correct backoff release number is 4.3.30-101610.
On Fri, Aug 21, 2015 at 8:36 AM, Gene Soo genesoo77...@gmail.com
wrote:
I believe I have
I don't know how to proceed with the following recommendation:
you can select the emulated hda and stac9221 hda codec
When I get into the Audio Settings for this guest, I have two Pull Downs I
can control.
First is Host Audio Driver: Pulse Audio(Default), Null Audio Driver, OSS
Audio Driver,
speed. I am inclined not to pursue
this testing unless I hear back that I must run on this ALSA Driver. I am
afraid that pursuing permanent run on this ALSA Driver would cause a
Multigroup Support issue involving your team as well as VirtualBox Support.
On Fri, Aug 21, 2015 at 12:58 AM, Gene Soo
Let me start out by asking an important question.
In the Generated Problem Report between Title and Bug Description is the
following statement.
Status in alsa-driver package in Ubuntu:
Incomplete
Is Audio support code still under development for this Volume Slider
function or should it be
Last Update for tonight.
I understand it is monumentally difficult to support all of the varieties
of hardware that exist and because of that, I make myself available to test
or provide information for my specific operating environment.
For the most part, I expect that the OS packages that I
.
Altering Virtual Box Hardware Audio Drive from Pulse Audio to ALSA Audio
has no effect on correcting Volume Slider's lack of controlling Master Out
Channel(s) for Kubuntu-KDE, Lubuntu, Xubuntu..
On Fri, Aug 21, 2015 at 1:20 AM, Gene Soo genesoo77...@gmail.com
wrote:
Additional Comments regarding
I don't understand this response.
I am not an experienced programmer with respect to these platforms and have
no control what Virtual Box presents back to the OS.
I will say that this problem effects multiple distributions.
Particularly Kubuntu-KDE, Edubuntu, Lubuntu, Xubuntu.
Luckily, the
Public bug reported:
Volume Slider is only controlling PCM channel and is not controlling
Master. In effect, Master is restricting the audio level to the default
of approximately 45 Percent. In order to raise the Master Volume Level,
alsamixer is capable of changing Master. Without manually
Lots of questions, I'll attempt to answer as best as I can.
First. Host OS Level:
uname -a
Linux gwsux79 3.13.0-62-generic #102-Ubuntu SMP Tue Aug 11 14:29:36 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
Second, Sound Card/Sound Support: I don't understand the question about
Real Sound Card Support
Public bug reported:
None
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: uuid-runtime 2.26.2-6ubuntu3
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Wed Aug 5 10:50:06 2015
31 matches
Mail list logo