Are you confident about multi-threading? I don't see any linker commands
to link against the threading libraries in our build logs:
https://launchpadlibrarian.net/92810645/buildlog_ubuntu-precise-amd64
.cyrus-sasl2_2.1.25.dfsg1-3_BUILDING.txt.gz and I also see extensive
use of fork(2) in the
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mdbtools in Ubuntu.
https://bugs.launchpad.net/bugs/1227033
Title:
mdb-sql crashed with SIGSEGV in _IO_vfprintf_internal()
I think default THREADS=5 in /etc/default/saslauthd, after these all crash [as
above] then thats the end of SASL working. (at least that is what happened for
me, repeatedly).
Setting this to THREADS=0 has worked around the issue (for me anyway) as it
makes it fork instead.
--
You received
Also relevant:
http://www.mail-archive.com/nut-upsuser@lists.alioth.debian.org/msg07865.html
Looks like I'll need a newer version of NUT anyway...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
Thanks Lionel, I will update the SRU description and we will see.
Backporting a much newer version of anything into an older release
always is met with a lot of (justified by experience) reservations. It
probably will need more volunteers to make a case for it (at least
convincing the SRU team
I see your point.
You still have the option to ship the new version as drbd8-utils-lts-raring.
The 8.3 compatibility would still be a bonus for those who downgrade.
Otherwise, maybe you could push it to precise-backports ?
Lionel.
--
You received this bug notification because you are a member
** Description changed:
Request for SRU:
[Impact]
- DRBD will not work (hang) on fresh install using Ubuntu 12.04.3 media, and
will stop working on sites where the Raring Enablement Stacks is manually
installed
+ DRBD will not work (hang) on fresh install using Ubuntu 12.04.3 media, and
We only have builds of juju-core on Arm for Saucy (1.14.0 and 1.14.1
both have official juju tools builds for saucy-1.14.1-armhf.tgz)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Blueprint changed by Stefan Bader:
Work items changed:
Work items:
Add a more recent version of XCP to the Ubuntu Archive: POSTPONED
Write XCP documentation and Openstack: POSTPONED
Test XCP and Openstack: POSTPONED
Write documenation on vmware and Openstack: POSTPONED
Work items
Backports might be an option, too. Though then requiring to be aware of
the problem and manually pick the backports version when upgrading to
the LTS Raring kernel. Usability looks to be simpler with a SRU but I
would defer that decision to the SRU team.
--
You received this bug notification
Further discussion here: https://lists.ubuntu.com/archives/upstart-
devel/2013-October/002772.html
Following that thread, I've come to the following conclusions:
libvirtd is perfectly acceptable in its current behaviour. upstart plans
to support this edge case in the future. The only impact of
This bug was fixed in the package uvtool - 0~bzr36-0ubuntu1
---
uvtool (0~bzr36-0ubuntu1) saucy; urgency=low
* New upstream snapshot:
- Workaround to make sure that libvirtd is running and ready before
attempting to create the volume pool (LP: #1228210).
+
Scott
I've fixed up lesscpy in Saucy for python2 and 3 (it was not built for 2
and broken with 3).
This should get into the cloud-archive IMHO; if you want to run with
online compression then you have to have this package installed. We
did not have the same problem with nodejs/node-lessc as
** Changed in: nagios3 (Ubuntu Saucy)
Assignee: (unassigned) = James Page (james-page)
** Changed in: nagios3 (Ubuntu Saucy)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios3 in Ubuntu.
Changed the env series, same result.
ubuntu@bysen:~$ juju -vvv bootstrap --constraints arch=arm -e maas
2013-10-02 11:18:08 INFO juju.environs.tools tools.go:82 filtering tools by
released version
2013-10-02 11:18:08 INFO juju.environs.tools tools.go:29 reading tools with
major version 1
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-13.05:
Open Cloud Archive for Havana development: DONE
Work items for ubuntu-13.06:
[james-page] Document proposed OpenStack SRU cadence process: DONE
Update Cloud Archive documentation inline with support
** Changed in: nagios3 (Ubuntu Saucy)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios3 in Ubuntu.
https://bugs.launchpad.net/bugs/1231901
Title:
Installing Nagios3 and Apache2 in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Thanks for looking. I'm eager to fix any bugs of this sort with our
apache 2.4 transition to be released this cycle, but will be stuck
without being able to reproduce. Setting this bug Incomplete for now.
Please set back to New once you have steps to reproduce, or to Invalid
if you conclude that
This bug was fixed in the package w3m - 0.5.3-11
---
w3m (0.5.3-11) unstable; urgency=low
* Update 130_siteconf.patch to fix segfault (closes: #718612)
* New patch 180_execdict.patch to fix potentially segfault
* New patch 190_Strchop.patch to fix potentially segfault
* New
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-13.06:
[james-page] Update to latest stable MongoDB release: DONE
Work items for ubuntu-13.08:
[james-page] Update to latest stable MongoDB release: DONE
[james-page] DEP-8 tests for MongoDB: DONE
Uploaded, thanks!
I checked the package in Saucy, and see no process_name.rb there. If I
am right in understanding that this is fixed in Saucy, then, could you
please mark it as Fix Released?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Which kernel was this with?
** Changed in: openvswitch (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1233703
Title:
** Changed in: cloud-archive
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1227153
Title:
cinder missing build-depends on python-netaddr
To
** Changed in: nova (Ubuntu)
Status: New = Confirmed
** Changed in: cloud-archive
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1228433
Title:
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Branch linked: lp:~zulcss/horizon/lesscpy
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1226674
Title:
openstack-dashboard should suggest python-lesscpy
To manage
Public bug reported:
Moonshot power type in maas-enlist is not supported which causes that
enlisted moonshot machines into maas will fail.
** Affects: maas-enlist (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Robie,
Marked as Fix Released as requested.
What about for Precise? Are we going to backport the fix to Precise? In
IS, we currently have puppet ensure that the file is absent / deleted.
Regards,
Haw
** Changed in: puppet (Ubuntu)
Status: Confirmed = Fix Released
--
You received
Haw,
Thanks. For Precise, I just reviewed, tested and uploaded Adam's
debdiff. It's in queue now pending review from the SRU team.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
Iain,
This was decided that we wanted to have in mid cycle due to the
limations of the libvirt-lxc driver in openstack (lack of security,
maintainability, etc), there is a proposal to have this included in the
next release of openstack.
chuck
--
You received this bug notification because you
** Changed in: maas-enlist (Ubuntu)
Assignee: (unassigned) = Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/1234177
Title:
Moonshot power type
Generically, I think that an SRU to get it working with the HWE stack is
reasonable. It will need to be tested with both the original and HWE
stacks, so please update the test procedure to include testing both.
--
You received this bug notification because you are a member of Ubuntu
Server
** Branch linked: lp:ubuntu/saucy-proposed/nagios3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios3 in Ubuntu.
https://bugs.launchpad.net/bugs/1231901
Title:
Installing Nagios3 and Apache2 in Saucy does not enable the cgi
** Branch linked: lp:~zulcss/horizon/1210253
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1210253
Title:
With Havana 2 installed, Launching horizon UI results in the error
** Changed in: keepalived (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1211876
Title:
keepalived reload buggy due to improper
This bug was fixed in the package horizon - 1:2013.2~b3-0ubuntu2
---
horizon (1:2013.2~b3-0ubuntu2) saucy; urgency=low
* Don't use /etc/openstack-dashboard for in-process generated data
(LP: #1233752):
- d/openstack-dashboard.{dirs,postinst}:
+ Create
This bug was fixed in the package nagios3 - 3.4.1-5ubuntu2
---
nagios3 (3.4.1-5ubuntu2) saucy; urgency=low
* d/nagios3-cgi.postinst: Enable cgi module for compatibility with
apache 2.4 (LP: #1231901).
-- James Page james.p...@ubuntu.com Wed, 02 Oct 2013 12:25:10 +0100
**
Public bug reported:
nosetests tests/test_flask.py
.F
==
FAIL: test_custom_clientside_error (test_flask.FlaskrTestCase)
--
Traceback (most recent call
Assuming I should use the init script for this, attached output from
running the following in the container:
strace -o iscsi-start.txt service open-iscsi start
** Attachment added: iscsi-start.txt
Override component to main
cherrypy3 3.2.2-4ubuntu1 in saucy: universe/python - main
python-cherrypy3 3.2.2-4ubuntu1 in saucy amd64: universe/python/optional/100%
- main
python-cherrypy3 3.2.2-4ubuntu1 in saucy arm64: universe/python/optional/100%
- main
python-cherrypy3 3.2.2-4ubuntu1 in saucy
Thanks - unfortunately we need the -f flag added to strace to follow
forks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1226855
Title:
Cannot use open-iscsi inside LXC container
To
This bug was fixed in the package maas - 1.4+bzr1655+dfsg-0ubuntu1
---
maas (1.4+bzr1655+dfsg-0ubuntu1) saucy; urgency=low
* New Upstream release. (LP: #1218526)
* debian/control:
- Depends on python-djorm-ext-pgarray, python-curtin,
python-simplestreams,
This bug was fixed in the package maas - 1.4+bzr1655+dfsg-0ubuntu1
---
maas (1.4+bzr1655+dfsg-0ubuntu1) saucy; urgency=low
* New Upstream release. (LP: #1218526)
* debian/control:
- Depends on python-djorm-ext-pgarray, python-curtin,
python-simplestreams,
@John, I don't dispute that the tools aren't there, but I'm starting to think
juju-core
isn't able to find it.
I created a saucy VM to try and drive this MAAS, it still won't find the
arm tools.
@John (anyone), have you actually seen this work?
ubuntu@saucy:~$ uname -a
Linux saucy
Aha! Attached: strace -f -o iscsi-start_f.txt service open-iscsi start
** Attachment added: iscsi-start_f.txt
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855/+attachment/3855848/+files/iscsi-start_f.txt
--
You received this bug notification because you are a member of Ubuntu
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1234331
Title:
cloud-init should respect
fix-committed in revno 882.
** Changed in: cloud-init
Importance: Undecided = Low
** Changed in: cloud-init
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New = Confirmed
** Changed in: cloud-archive
Importance: Undecided = High
** Changed in: maas
** Changed in: lxc (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1226855
Title:
Cannot use open-iscsi inside LXC container
To manage
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1234331
Title:
cloud-init should respect /etc/growroot-disabled
To manage notifications about
This bug was fixed in the package python-wsme - 0.5b5-1ubuntu2
---
python-wsme (0.5b5-1ubuntu2) saucy; urgency=low
* d/p/fix_403_test_case.patch: Fixup test case for 403 error code;
older versions of python-werkzeug handle this differently which
creates issues in the Ubuntu
Promoted.
** Changed in: simplestreams (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to simplestreams in Ubuntu.
https://bugs.launchpad.net/bugs/1220427
Title:
[MIR] simplestreams
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1231693
Title:
maas-dhcp backport does not start on precise
To manage notifications about this bug go to:
Public bug reported:
Description:Ubuntu 12.04.2 LTS
Release:12.04
nagios3:
Installed: 3.2.3-3ubuntu1
Candidate: 3.2.3-3ubuntu1
The problem is described here http://tracker.nagios.org/view.php?id=238
The solution that worked for me is here
Thanks for the tip Dumitrescu,
I'll rive it a try AMD report here che result.
Regards
Il 29/set/2013 14:50 Vasile Dumitrescu launchpad.vas...@undeva.net ha
scritto:
I added a rtl8139c netcard to the VM and connected through it by RDP -
no more freezes.
It looks like kvm does not play well
complex patch that seemingly works, but we've decided not to do this.
cloud-archive will deliver isc-dhcp-server of quantal version (same as saucy)
to 12.04.
maas packages will not be supported on 12.04 without cloud archive.
This simplifies the code dramatically, and means we can just revert
** Branch linked: lp:~smoser/maas/packaging.1231693
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1231693
Title:
maas-dhcp backport does not start on precise
To manage notifications
1.16 will also fix the local provider, which is broken on saucy with
1.14 due to changes in upstart and lxc.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1219879
Title:
[FFe]
You have been subscribed to a public bug:
We have an issue with Upstart not restarting the autofs job when the
automount process dies, and the Upstart job status gets stuck in the
stop/starting state. The process is not automatically restarted by
Upstart like it is supposed to. Trying to manually
** Package changed: upstart (Ubuntu) = autofs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1176020
Title:
initctl status autofs gets stuck on stop/starting
To manage
** Branch linked: lp:~smoser/maas/packaging.1231693-2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1231693
Title:
maas-dhcp backport does not start on precise
To manage
This bug has been fixed in the Ubuntu Cloud Archive (precise-grizzly):
nova: 1:2013.1.3-0ubuntu1~cloud0
keystone: 1:2013.1.3-0ubuntu1~cloud0
horizon: 1:2013.1.3-0ubuntu1~cloud0
quantum: 1:2013.1.3-0ubuntu1~cloud0
cinder: 1:2013.1.3-0ubuntu2~cloud0
glance:
** Summary changed:
- linux-armadaxp: version to be filled -proposed tracker
+ linux-armadaxp: 3.5.0-1623.31 -proposed tracker
** Description changed:
- This bug is for tracking the version to be filled upload package. This
- bug will contain status and testing results related to that upload.
+
Public bug reported:
This crash file was in /var/crash/ after using the phone for a few
minutes. No specific steps to reproduce.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: maliit-framework 0.99.0+git20130615+97e8335-0ubuntu3
Uname: Linux 3.4.0-3-mako armv7l
ApportVersion:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854584/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854601/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854594/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854600/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854595/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected ubuntu
** Description changed:
After upgrade from 13.04 I can login but there is no panel. The mouse is
still active, also other ttys (console). I also tried a new user with
clean home, but no effect. How can I further inspect this, esp.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854576/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
Title:
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854603/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
Title:
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854580/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854581/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
Title:
Xorg
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854597/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
Title:
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854573/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
Title:
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854602/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
Title:
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854572/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854598/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854582/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
Title:
Xorg
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854574/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854596/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854575/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
apport information
** Attachment added: XorgConf.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854599/+files/XorgConf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232123
Title:
apport information
** Attachment added: NvidiaBugReportLog.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854583/+files/NvidiaBugReportLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1232123/+attachment/3854577/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linuxmint
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1163497
Title:
[Packard Bell EasyNote EN TS44HR] ETPS/2 Elantech Touchpad
Public bug reported:
Nothing happened, I could continue work.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-8-generic x86_64
.tmp.unity.support.test.0:
Public bug reported:
I consistently see my Asus F201E off after I close the lid.
Both options are on do nothing in Power Settings when the lid is
closed.
This is with Raring Ringtail 64bits, up to date with proposed repos
activated.
Please let me know if I can give more information in any
** Changed in: kernel-sru-workflow/upload-to-ppa
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233919
Title:
linux-armadaxp: 3.5.0-1623.31 -proposed tracker
To manage
Public bug reported:
I got this crash right after booting the device with mir enabled.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: hud 13.10.1+13.10.20130918-0ubuntu1
Uname: Linux 3.4.0-3-mako armv7l
ApportVersion: 2.12.5-0ubuntu1
Architecture: armhf
Date: Wed Oct 2 05:57:57 2013
Comment #6 and #10 are still valid for errors in #14. This seems happens
on a number of systems, but it does not cause any function failures.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1149269
reproduces in
Distributor ID: Ubuntu
Description:Ubuntu 12.04.3 LTS
Release:12.04
Codename: precise
Update: 02/10/13
Firefox: 24.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
This bug is for tracking the 3.8.0-32.47 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Description changed:
This bug is for tracking the 3.5.0-42.65 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Attachment added: Stacktrace.txt
https://bugs.launchpad.net/bugs/1233988/+attachment/3854665/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233988
Title:
maliit-server
Are you confident about multi-threading? I don't see any linker commands
to link against the threading libraries in our build logs:
https://launchpadlibrarian.net/92810645/buildlog_ubuntu-precise-amd64
.cyrus-sasl2_2.1.25.dfsg1-3_BUILDING.txt.gz and I also see extensive
use of fork(2) in the
Update to my previous comment (#111). I installed an HDD (Western
Digital Caviar Black) and since (2.5 months) there has been no
problem... until just now. Rebooting does not solve it as it happens
quickly after. My last installation has been without system encryption.
--
You received this bug
StacktraceSource:
#0 0x4007b494 in ?? ()
#1 0x403fa328 in ?? ()
#2 0x403fa328 in ?? ()
StacktraceTop:
?? ()
?? ()
?? ()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233992
Title:
1 - 100 of 1353 matches
Mail list logo
