Re: Installation of Saucy Salamander X86_64

[Jackson Doak]

Add yourself to the affects list of the bug, and report your results
at iso.qa.ubuntu.com. It's better to report something that isn't a bug
than to not report an actual bug

On Tue, Oct 15, 2013 at 5:15 AM, mss-devel  wrote:
>
> El 14/10/13 15:09, Martin Ss escribió:
>
>> The installation of Saucy was performed correctly
>> But, these are warnings in /var/log/kern.log
>>
>> Oct 14 14:39:13 virtualhome-VirtualBox kernel: [0.00] tsc: Fast
>> TSC calibration failed
>> Oct 14 14:39:13 virtualhome-VirtualBox kernel: [0.138424] acpi
>> PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
>> Oct 14 14:39:13 virtualhome-VirtualBox kernel: [0.138560] acpi
>> PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI
>> configuration space under this bridge.
>> Oct 14 14:39:13 virtualhome-VirtualBox kernel: [1.358625] e1000:
>> module verification failed: signature and/or required key missing - tainting
>> kernel
>> Oct 14 14:39:13 virtualhome-VirtualBox failsafe: Failsafe of 120 seconds
>> reached.
>> Oct 14 14:39:18 virtualhome-VirtualBox NetworkManager[640]:  failed
>> to allocate link cache: (-10) Operation not supported
>> Oct 14 14:39:20 virtualhome-VirtualBox NetworkManager[640]:  DNS:
>> plugin dnsmasq update failed
>> Oct 14 14:39:40 virtualhome-VirtualBox NetworkManager[640]:  (eth0):
>> IP6 addrconf timed out or failed.
>>
>>  I know that the TSC calibration fail is not certainly a bug. Neither the
>> ACPI warning, since my hardware seems not support ACPI for PCIe devices.
>> But I am not sure with : "signature and/or required key missing - tainting
>> kernel ". Maybe a module is truly missing, but since Ubuntu 12.04 this
>> warning is known. So, I'm 100% sure if this is a real bug.
>
> Sorry, I mean, I'm not 100% sure if the signature missing warning is a real
> bug
>
> --
> Ubuntu-quality mailing list
> Ubuntu-quality@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: Installation of Saucy Salamander X86_64

[mss-devel]

El 14/10/13 15:09, Martin Ss escribió:

The installation of Saucy was performed correctly
But, these are warnings in /var/log/kern.log

Oct 14 14:39:13 virtualhome-VirtualBox kernel: [0.00] tsc: 
Fast TSC calibration failed
Oct 14 14:39:13 virtualhome-VirtualBox kernel: [0.138424] acpi 
PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
Oct 14 14:39:13 virtualhome-VirtualBox kernel: [0.138560] acpi 
PNP0A03:00: fail to add MMCONFIG information, can't access extended 
PCI configuration space under this bridge.
Oct 14 14:39:13 virtualhome-VirtualBox kernel: [1.358625] e1000: 
module verification failed: signature and/or required key missing - 
tainting kernel
Oct 14 14:39:13 virtualhome-VirtualBox failsafe: Failsafe of 120 
seconds reached.
Oct 14 14:39:18 virtualhome-VirtualBox NetworkManager[640]:  
failed to allocate link cache: (-10) Operation not supported
Oct 14 14:39:20 virtualhome-VirtualBox NetworkManager[640]:  
DNS: plugin dnsmasq update failed
Oct 14 14:39:40 virtualhome-VirtualBox NetworkManager[640]:  
(eth0): IP6 addrconf timed out or failed.


 I know that the TSC calibration fail is not certainly a bug. Neither 
the ACPI warning, since my hardware seems not support ACPI for PCIe 
devices.
But I am not sure with : "signature and/or required key missing - 
tainting kernel ". Maybe a module is truly missing, but since Ubuntu 
12.04 this warning is known. So, I'm 100% sure if this is a real bug.
Sorry, I mean, I'm not 100% sure if the signature missing warning is a 
real bug


--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Installation of Saucy Salamander X86_64

[Martin Ss]

The installation of Saucy was performed correctly
But, these are warnings in /var/log/kern.log

Oct 14 14:39:13 virtualhome-VirtualBox kernel: [0.00] tsc: Fast TSC
calibration failed
Oct 14 14:39:13 virtualhome-VirtualBox kernel: [0.138424] acpi
PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
Oct 14 14:39:13 virtualhome-VirtualBox kernel: [0.138560] acpi
PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI
configuration space under this bridge.
Oct 14 14:39:13 virtualhome-VirtualBox kernel: [1.358625] e1000: module
verification failed: signature and/or required key missing - tainting kernel
Oct 14 14:39:13 virtualhome-VirtualBox failsafe: Failsafe of 120 seconds
reached.
Oct 14 14:39:18 virtualhome-VirtualBox NetworkManager[640]:  failed
to allocate link cache: (-10) Operation not supported
Oct 14 14:39:20 virtualhome-VirtualBox NetworkManager[640]:  DNS:
plugin dnsmasq update failed
Oct 14 14:39:40 virtualhome-VirtualBox NetworkManager[640]:  (eth0):
IP6 addrconf timed out or failed.

 I know that the TSC calibration fail is not certainly a bug. Neither the
ACPI warning, since my hardware seems not support ACPI for PCIe devices.
But I am not sure with : "signature and/or required key missing - tainting
kernel ". Maybe a module is truly missing, but since Ubuntu 12.04 this
warning is known. So, I'm 100% sure if this is a real bug.
-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: [ubuntu-studio-users] Ubuntu Studio 13.10 Release Candidate Call for Testing

[reSet Sakrecoer]

Hi all!!

I did the upgrade procedure today, and it worked like a charm! It's
beautyfull! The app menu is looking real good, the loginprompt is
delicious. Basically my love for ubuntustudio is still growing
exponentially. I havn't hard/deep tested all the programs yet. But i will
keep you posted about it.

THANKS A MILLION FOR ALL YOUR EFFORTS!!

Yours truly,
Set H.





On Sun, Oct 13, 2013 at 10:43 AM, Ho Wan Chan  wrote:

> Dear Ubuntu Studio developers, testers and users,
>
> We are about to release Ubuntu Studio 13.10 on the coming Thursday.
> However, we are desperately in need for testing. Please help us test
> the release candidate images!
>
> Testcases for the amd64 images are in
> http://iso.qa.ubuntu.com/qatracker/milestones/305/builds/55592/testcases,
> while i386 image testcases can be found in
> http://iso.qa.ubuntu.com/qatracker/milestones/305/builds/55593/testcases.
> Please also do the upgrade testcases as well, linked in
> http://iso.qa.ubuntu.com/qatracker/milestones/305/builds/55391/testcases
> (for amd64) and
> http://iso.qa.ubuntu.com/qatracker/milestones/305/builds/55392/testcases
> (for i386).
>
> The latest image is available at
> http://cdimage.ubuntu.com/ubuntustudio/dvd/current. We recommend you
> to use zsync to download the image, as the images will be updated
> quite frequently in the coming few days.
>
> The changes compared to Ubuntu Studio 13.04 can be found at
>
> http://ubuntustudio.org/2013/09/ubuntu-studio-13-10-saucy-salamander-beta-2-released/
> (except for one final feature: We added Ardour 3 to the images).
>
> You can find a detailed testing walkthrough and videos at
> https://wiki.ubuntu.com/Testing/ISO/Walkthrough.
>
> If you have any inquiries, feel free to ask in #ubuntustudio-devel on
> Freenode or mail us at ubuntu-studio-de...@lists.ubuntu.com
>
> We appreciate your testing efforts and let's make Ubuntu Studio 13.10
> an amazing release!
>
> Regards,
> Howard Chan (smartboyhw)
> Ubuntu Studio Release Manager
>
> --
> ubuntu-studio-users mailing list
> ubuntu-studio-us...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
>



-- 
Set Hallström
AKA
reSet Sakrecoer
http://sakrecoer.com
-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: Oh my god

[Javier Domingo]

I am now debian user, and experienced a big problem with nvidia's drivers
and nouveau due to a new-generation graphic. I suppose that just switching
to nouveau driver instead of uninstalling nvidia will also work for that. I
wrote a little-fast blog entry in my blog[1], from which you can learn how
to switch between one an another.

Hope it helps someone,

Javier Domingo Cansino

​[1] Nvidia/nouveau in same installation:
http://txomon.com/2012/11/29/how-to-use-nvidia-and-nouveau-in-same-debianubuntu-and-dont-get-nut/
​



2013/10/14 Matteo Sisti Sette 

> Ok, so I got it fixed, and it turns out that:
> - what broke everything was installing nvidia-current.
> - uninstalling nvidia* didn't fix the issue (this is huge: uninstalling
> the package does not completely reverse the installation)
> - I got it completely fixed by manually removing /etc/X11/xorg.conf (after
> apt-get-purging nvidia*) and rebooting. A pretty easy fix, but complicated
> as hell to figure out.
>
>
>
> On 13/10/13 23:39, matteo sisti sette wrote:
>
>> If I understand correctly, many people in this list are developers
>> working in ensuring Ubuntu quality, right? So, since this issue has been
>> reported a lot of times and there are a few bug reports about it in
>> Launchpad and a few questions in askubuntu (none of the answers to
>> which, is working for me), and since this is a huge issue that
>> completely breaks an ubuntu installation to an apparently unrecoverable
>> point, making it a tremendous threat tu Ubuntu quality, I must deduce
>> that a lot of people here must either have observed and thoroughly
>> investigated this issue, or be doing so. So, I think there must be
>> somebody here who has found out some workaround for this. I supplicate
>> some of people to please, please share any working workaround with me.
>>
>>
>> 2013/10/13 matteo sisti sette > >
>>
>> Oh, given how 13.04 got screwed up in two days, which was a
>> supposed-to-be stable release, I don't dare to imagine how a "pretty
>> much ready" version will work
>>
>>
>> 2013/10/13 Jackson Doak > nosk...@ubuntu.com>>
>>
>> That was a bit strange, but welcome to the team.
>> Maybe you could try installing 13.10 since it's pretty much ready.
>>
>> On Mon, Oct 14, 2013 at 7:40 AM, matteo sisti sette
>> > > >>
>>
>> wrote:
>>  > Hi,
>>  >
>>  > The Ubuntu QA team's website invites visitors to join the
>> list and introduce
>>  > themselves, so here I am introducing myself to the list.
>>  >
>>  > I am an Ubuntu user and I have been more and more frustrated
>> by the
>>  > exponentially growing unusability and unstability of Ubuntu
>> throughout the
>>  > last years. But I will focus on unstability here.
>>  >
>>  > Now I am astonished to see the point it has reached.
>>  > I have installed a fresh new Ubuntu 13.04 on a brand new
>> computer.
>>  > First, the Firefox browser stopped working after updating it
>> (simply via
>>  > apt-get) and it turned out to be because ~/.cache/mozilla
>> somehow got the
>>  > wrong owner (root) rendering it unaccessible and preventing
>> Firefox from
>>  > reading the user profofiles and hence to work at all.
>>  >
>>  > But now, after a reboot, I find myself with an empty desktop
>> with no Unity
>>  > launcher nor system bar. None of the workarounds described at
>>  >
>> http://askubuntu.com/**questions/17381/unity-doesnt-**
>> load-no-launcher-no-dash-**appears/
>>  > or
>> 
>> https://bugs.launchpad.net/**ubuntu/+source/unity/+bug/**1212987work.
>>  >
>>  > So after delirious usability killers (I won't mention them
>> here as I want to
>>  > focus on UNSTABILITY), after the impossibility to hibernate,
>> after the
>>  > impossibility to suspend on low battery, after random x.org
>>  crashes started
>>
>>  > to appear which would just suddenly log you out destroying
>> all unsaved data
>>  > at the blinking of an eye, now we have reached the point
>> where you may just
>>  > reboot and find yourself with a completely unusable system,
>> roughly
>>  > equivalent to one that won't even boot. Which means you are
>> forced to either
>>  > waste a couple of days googling for a fix, or reinstall the
>> whole system
>>  > just until this happens again.
>>  >
>>  > End of rant.
>>  > Matteo
>>  >
>>  > --
>>  > Matteo Sisti Sette
>>

Image 96 (20131014) available for testing

[Alan Pope]

Avengers, Apprise!

Happy Columbus / Canadian Thanksgiving day!

The latest "current" image is now 20131014 which relates to system
image *96*. You can see what's new since the last blessed image in
detail via the changelogs:-

http://people.canonical.com/~j-lallement/touch/changes/20131012.html
http://people.canonical.com/~j-lallement/touch/changes/20131013.html
http://people.canonical.com/~j-lallement/touch/changes/20131014.html

Too many individual package changes to list here. See:-

http://people.canonical.com/~ogra/touch-image-stats/20131012.changes
http://people.canonical.com/~ogra/touch-image-stats/20131013.changes
http://people.canonical.com/~ogra/touch-image-stats/20131014.changes

Please update and test accordingly!

The instructions on the wiki are up to update. Either flash cleanly or
update over the air as appropriate.

http://wiki.ubuntu.com/Touch/Install

Cheers,
-- 
Alan Pope
Engineering Manager

Canonical - Product Strategy
+44 (0) 7973 620 164
alan.p...@canonical.com
http://ubuntu.com/

-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Installer 13.10

[James]

While using a USB to install 13.10 (desktop) if a dialogue box appears on top 
of another window you cannot click any options of the box, the mouse simply 
clicks the window beneath it, the only way to select an option within the 
dialogue box that is on top of another window is to press tab until the button 
you want is highlighted then press space bar to select it.

I have reproduced this error 10 times, I was wondering if anyone else has 
experienced this or is it just me.  

Cheers

 
-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality