*** This bug is a duplicate of bug 1883089 ***
https://bugs.launchpad.net/bugs/1883089
As the fix this was a duplicate of has been abandoned, can this still be
addressed somehow? Is there anything I can do to move this forward?
--
You received this bug notification because you are a member
Public bug reported:
We currently have a maas 1.9.5 setup on trusty that has 4 subnets
defined in it under 10.x.0.0, one /24, 2 /23s and a /21. With the
latest version of maas installed it appears that it is writing out two
zones configs for x.10.in-addr.arpa in the named.conf.maas file, which
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668123
Title:
lxc fails to start with cgroup error
To manage notifications about
I've had this occur on another system, and this time I could debug it a
little more freely. This is an interesting output:
# dpkg --purge --simulate systemd
dpkg: dependency problems prevent removal of systemd:
snapd depends on systemd (>= 204-5ubuntu20.20); however:
Package systemd is to be
> Sidenote) the 18GB of /var/lib/juju/db (with backups, of backups, of backups)
> was not helpful, I'll need to talk to sosreport people about that. This is
> what made the report so huge.
I did notice that, but I figured getting you all of the data was better than
fiddling around trying to not
It's uploading slowly to https://private-
fileshare.canonical.com/~bradm/lp1668123/, once you see the .md5 file in
place and the sosreport is 7.7G, it'll be done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've generated a sosreport, but its 7.7G. How would you like me to get
this to you?
The interesting part is that all this was deployed via juju, so I don't
know how we got into this state. It also appears to be the only node in
this state, so its a bit confusing as to how it got to be this way.
Public bug reported:
After rebooting a KVM instance hosting LXCs, we get the following error:
$ sudo lxc-ls --fancy
lxc: cgmanager.c: lxc_cgmanager_escape: 331 call to
cgmanager_move_pid_abs_sync(name=dsystemd) failed: invalid request
and the LXCs won't start up. In the error logs it
Public bug reported:
nova-compute process across 2 Openstack deployments died around the same
time as the recent libc-bin upgrade:
2016-07-12 00:59:26 status half-configured libc-bin:amd64 2.19-0ubuntu6.9
2016-07-12 00:59:26 status installed libc-bin:amd64 2.19-0ubuntu6.9
Digging into the
Public bug reported:
We ran into a situation over the past couple of days where we had 2
different ceph-osd nodes crash in such a way that they caused ps listing
to hang when enumerating the process. Both had a call trace associated
with them:
Node 1:
Jul 4 07:46:15 provider-cs-03 kernel:
I've just tried upgrading a system to the haproxy from your PPA, and it
now only logs to /var/log/syslog. The rsyslog.d file has disappeared
completely, and its no longer logging to /var/log/haproxy.log. Is that
the intended outcome from this? Or should it be logging to just
This just occured on another cloud, this time with nova-consoleauth
1:2015.1.4-0ubuntu2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572320
Title:
nova-consoleauth (2:12.0.2-0ubuntu1~cloud0)
I've upgraded systemd across my cluster to 229-4ubuntu6, removed all my
custom tweaks to systemd settings, reloaded the daemon and both rabbitmq
and mysql appear to be working fine on my openstack cluster. I'll be
throwing a bit more load at it, but usually by this point mysql has
fallen over, so
Public bug reported:
I'm trying to install a PPC64EL node with Xenial via MAAS 1.9.2 using
Juju 1.25.5 and it seems to be failing due to a possible multipath
issue. The node is setup in maas with a default single partition. The
boot logs show:
Begin: Running /scripts/init-premount ... done.
FWIW I'm also seeing limits hit in other areas, rabbitmq-server seems to
be a common one. I'm also randomly seeing:
Failed to allocate directory watch: Too many open files
on the command line. I suspect its related to the percona and rabbitmq
services hitting limits, but I'm not exactly
Public bug reported:
I've been setting up a Mitaka Openstack using the cloud archive running
on Trusty, and am having problems working with EFI enabled instances on
ARM64.
I've done some work with wgrant and gotten things to a stage where I can
boot instances, using the aavmf images.
However,
Note these are freshly bootstrapped clouds, as per an irc conversation
with alexisb and anastasiamac_.
I took a working juju environment deploying to canonistack, just changed the
default series, did a juju bootstrap and then a juju
deploy local:xenial/ubuntu --to lxc:0, and got an error as
Note these are freshly bootstrapped clouds, as per an irc conversation
with alexisb and anastasiamac_.
I took a working juju environment deploying to canonistack, just changed the
default series, did a juju bootstrap and then a juju
deploy local:xenial/ubuntu --to lxc:0, and got an error as
** Tags added: canonical-bootstack
--
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/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To manage notifications
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To manage notifications about this bug go to:
Public bug reported:
There appears to be some issue with deploying to lxc containers using
juju 1.25.3 on Xenial.
When deploying with xenial to canonistack-lcy02:
bradm@serenity:~/src/juju$ juju deploy local:xenial/ubuntu --to lxc:0
Added charm "local:xenial/ubuntu-2" to the environment.
ERROR
Public bug reported:
There appears to be some issue with deploying to lxc containers using
juju 1.25.3 on Xenial.
When deploying with xenial to canonistack-lcy02:
bradm@serenity:~/src/juju$ juju deploy local:xenial/ubuntu --to lxc:0
Added charm "local:xenial/ubuntu-2" to the environment.
ERROR
Public bug reported:
While debugging something, I ran the kvm-ok script on a VM running on
openstack, and got an interesting error:
ubuntu@juju-bradm-lcy02-machine-0:~$ sudo kvm-ok
INFO: /dev/kvm does not exist
HINT: sudo modprobe kvm_intel
INFO: Your CPU supports KVM extensions
Public bug reported:
The current rsyslogd configuration as provided by the rsyslogd package
causes double logging to occur.
Steps to Reproduce:
1) Install haproxy via whatever normal means (apt-get etc)
2) Configure it to listen on at least one port, even just the stats port
3) Visit the URL
Public bug reported:
The current rsyslogd configuration as provided by the rsyslogd package
causes double logging to occur.
Steps to Reproduce:
1) Install haproxy via whatever normal means (apt-get etc)
2) Configure it to listen on at least one port, even just the stats port
3) Visit the URL
This does indeed appear to work correctly, I've deployed a container
using juju:
ubuntu@apollo:~$ dpkg-query -W lxc
lxc 1.0.8-0ubuntu0.3
ubuntu@apollo:~$ sudo lxc-ls --fancy
NAME STATEIPV4IPV6 AUTOSTART
This does indeed appear to work correctly, I've deployed a container
using juju:
ubuntu@apollo:~$ dpkg-query -W lxc
lxc 1.0.8-0ubuntu0.3
ubuntu@apollo:~$ sudo lxc-ls --fancy
NAME STATEIPV4IPV6 AUTOSTART
FWIW and a totally expected result, I just downgraded the LXC packages
on these hosts and redeployed, and things came up ok.
$ dpkg-query -W lxc
lxc 1.0.7-0ubuntu0.10
I don't think this changes anything, but just putting it here for
completeness.
--
You received this bug notification
FWIW and a totally expected result, I just downgraded the LXC packages
on these hosts and redeployed, and things came up ok.
$ dpkg-query -W lxc
lxc 1.0.7-0ubuntu0.10
I don't think this changes anything, but just putting it here for
completeness.
--
You received this bug notification
Public bug reported:
I've just tried using juju to deploy to a container with trusty-proposed
repo enabled, and I get an error message about 'failed to retrieve the
template to clone'. The underlying error appears to be:
tar --numeric-owner -xpJf
Public bug reported:
I've just tried using juju to deploy to a container with trusty-proposed
repo enabled, and I get an error message about 'failed to retrieve the
template to clone'. The underlying error appears to be:
tar --numeric-owner -xpJf
Public bug reported:
Issue
---
When nagios3 is configured to have livestatus from check-mk-livestatus as a
broker module, and checks have a downtime applied to them it will crash when
the logs rotate. This shows up in /var/log/nagios3/nagios.log as:
[1445238000] Caught SIGSEGV,
Public bug reported:
Issue
---
When nagios3 is configured to have livestatus from check-mk-livestatus as a
broker module, and checks have a downtime applied to them it will crash when
the logs rotate. This shows up in /var/log/nagios3/nagios.log as:
[1445238000] Caught SIGSEGV,
Public bug reported:
Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
servers lock up with a similar looking cpu lockup bug. All 3 of these
servers are nova-compute nodes in an OpenStack cluster, with a
reasonable amount of load on them. The symptoms are the load shoots up
The first of the lockups. These all required us to hard reset the
servers via the ilo.
** Attachment added: "CPU Lockup 1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478312/+files/cpu-lockup-1.log
--
You received this bug notification because you are a
2nd of the lockups.
** Attachment added: "CPU Lockup 2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478313/+files/cpu-lockup-2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
3rd of the lockups
** Attachment added: "CPU Lockup 3"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478314/+files/cpu-lockup-3.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unfortunately we're unable to test the latest upstream kernel in this
situation. These servers are running a production system, and as they
use bcache we need a kernel that supports it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479438/+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/1500739
Title:
CPU
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479437/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500739
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479444/+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/1500739
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479445/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479442/+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/1500739
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479441/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479439/+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/1500739
Title:
CPU
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479440/+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/1500739
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479436/+files/CurrentDmesg.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 trusty uec-images
** Description changed:
Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
servers lock up with a similar looking cpu lockup bug. All 3 of these
servers are nova-compute nodes in an OpenStack cluster,
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479443/+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/1500739
Title:
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1356392
Title:
lacks sw raid1 install support
To manage notifications about this bug go to:
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1356392
Title:
lacks sw raid1 install support
To manage notifications about this bug go to:
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1186662
Title:
isc-dhcp-server fails to renew lease file
To manage notifications about this bug go to:
Public bug reported:
/etc/dhcp/dhclient-exit-hooks.d/ntp doesn't check if /etc/ntp.conf has
been updated since the last time dhclient ran. A simple addition of a
check to see if /etc/ntp.conf is newer than /var/lib/ntp/ntp.conf.dhcp,
and if so letting it add the servers would be sufficient.
Public bug reported:
/etc/dhcp/dhclient-exit-hooks.d/ntp doesn't check if /etc/ntp.conf has
been updated since the last time dhclient ran. A simple addition of a
check to see if /etc/ntp.conf is newer than /var/lib/ntp/ntp.conf.dhcp,
and if so letting it add the servers would be sufficient.
Public bug reported:
When using ssh and managing ssh port forwards with ~C to remove a
forward that doesn't exist, the following occurs:
user@host:~$
ssh -KD12345
Unkown port forwarding.
ie, the mispelling of the work Unknown as 'Unkown'.
This occurs at least on a server running on
Public bug reported:
When using ssh and managing ssh port forwards with ~C to remove a
forward that doesn't exist, the following occurs:
user@host:~$
ssh -KD12345
Unkown port forwarding.
ie, the mispelling of the work Unknown as 'Unkown'.
This occurs at least on a server running on
Hi,
Brad Marshall, could you please test the latest mainline kernel
(3.18-rc5) and advise to the results?
Done, roughly the same results - still timeouts, still having to reset
the bluetooth service to get things going again sometimes.
Also, did this issue not occur in a release prior
Hi,
Brad Marshall, which previous release(s) specifically did it occur in?
As well, could you please quantify how much less frequently?
I did my initial install on Raring, and I've upgraded across every
release since then. I do remember it happening occasionally on the
earlier ones - maybe
If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?
Done, and it doesn't seem to change anything.
If it doesn't, could you please both specify what happened
Er, how can I specify what happened when its not changed? :) I'm still
seeing
Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
Yes, it occured in previous versions, just not as frequently I think.
Would it be possible for you to test the latest upstream kernel? Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds .
Please test the
Public bug reported:
I'm using a Razor Orochi 2013 mouse with my Dell XPS13 laptop via
bluetooth on Ubuntu 14.10, and have noticed a seeming increase in the
frequency of the timeouts I'm seeing.
The symptoms are when I don't use my mouse for a while, it seems to go
to sleep, and reasonably
: nrpe-external-master
scope: container
I've got a branch at lp:~brad-
marshall/charms/trusty/cinder/add-n-e-m-interface with the change in it.
** Affects: swift (Ubuntu)
Importance: Undecided
Status: New
** Affects: ceilometer (Juju Charms Collection)
Importance: Undecided
: nrpe-external-master
scope: container
I've got a branch at lp:~brad-
marshall/charms/trusty/cinder/add-n-e-m-interface with the change in it.
** Affects: swift (Ubuntu)
Importance: Undecided
Status: New
** Affects: ceilometer (Juju Charms Collection)
Importance: Undecided
Unfortunately I no longer have this hardware in a workable state, and
have upgraded to a new laptop, so I am unable to provide any further
debugging information. I suspect we may have to close off this bug
unless someone else is having the same issue.
--
You received this bug notification
I had plugged it in before, but for some reason now its detecting it -
perhaps I had some upgrades or something between testing that resolved
it. I've attached the Pulse Audio verbose logging I get now when I plug
my headset in.
** Attachment added: pulseverbose-working-headset.log
Hi,
seem your subsystem Id did not have any entry for the headset Mic in
alc269_fixup_tbl
So whats the fix here? Is there a work around I can temporarily use to
get mine working while a longer term fix is put in place?
Brad.
--
You received this bug notification because you are a member of
there are two models and you need to find out the pin detect of headphone or
MicJack
is used when headset is pluuged using hda-jack-sense-test
I'm a bit confused here, because while getting hda-jack-sense-test going, the
headphones suddenly
started working. I get:
$ hda-jack-sense-test
Public bug reported:
Hi,
After upgrading my Dell XPS13 laptop to Saucy, I am unable to hear any
useful sound out of the headphone jack. When I plug my headphones into
the jack I can see the Built-in Audio for the Speakers briefly flick
over to Headphones and then either flick back to Speakers
the icon near the Jack indicate it is a headset jack (headphone with Mic)
http://www.dell.com/us/dfh/p/xps-13-l321x-mlk/pd
Yes, that is correct.
are you using headphone (TRS) or headset (TRRS) connector
Its a headset that I use successfully with my Android phone, one of the
Logitech UE
Public bug reported:
We appear to have a performance regression with puppet 2.7.11-1ubuntu2.4
that we recently upgraded to, particularly on our more heavily loaded
puppet master. When we're running 2.4, many of our puppet clients get
the following:
err: Could not retrieve catalog from remote
Public bug reported:
We appear to have a performance regression with puppet 2.7.11-1ubuntu2.4
that we recently upgraded to, particularly on our more heavily loaded
puppet master. When we're running 2.4, many of our puppet clients get
the following:
err: Could not retrieve catalog from remote
Hi Chris,
No, I have a hybrid ATI/Intel card in my laptop, not Nvidia. I didn't
try clearing out my configs piecemeal, I just moved the whole lot, so
I'm not sure which subset of my config was busted. I'm fine with
marking it Won't Fix if thats what you'd prefer since I found a work
around and
This appears to have been something in my personal config - a test user
didn't replicate the issue, and after moving all relevant directories
out of the way (.compiz, .config, .dbus, .gconf, .gnome2* and .local), I
was able to get a clean unity session up.
There must be some kind of cruft in my
Public bug reported:
After logging into a ubuntu session in lightdm it fails to provide a
usable interface of any sort. After logging in and seeing the dash
appear briefly, the launcher, hud, dock, top menu or any interface at
all does not appear. If I fire up a terminal when the dash briefly
apport information
** Tags added: apport-collected regression single-occurrence
** Description changed:
After upgrading from qantal to raring on a HP Pavillion DV6-3030TX,
using the open source radeon drivers, X fails to start. Once I reboot
the machine it asks me if I want to start a
This latest set of apport data is from logging into a unity session
after todays upgrades - I get a working x session, but no dash,
launcher, hud etc starts up. If I start any application from the
console displaying to :0 it does start up as expected.
--
You received this bug notification
apport information
** Attachment added: xserver.outputs.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597209/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597208/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597207/+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/1158590
Title:
apport information
** Attachment added: make.log.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597206/+files/make.log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158590
Title:
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597205/+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/1158590
Title:
X
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597204/+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/1158590
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597203/+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/1158590
Title:
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597202/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597201/+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/1158590
Title:
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597200/+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/1158590
Title:
X
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597199/+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/1158590
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597198/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: MonitorsUser.xml.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597196/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597197/+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/1158590
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597195/+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/1158590
Title:
X
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597193/+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/1158590
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597194/+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/1158590
Title:
X
apport information
** Attachment added: LightdmGreeterLogOld.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597192/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: LightdmGreeterLog.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597191/+files/LightdmGreeterLog.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/1158590/+attachment/3597190/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597189/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158590
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597188/+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/1158590
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597186/+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/1158590
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1158590/+attachment/3597187/+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/1158590
1 - 100 of 125 matches
Mail list logo
