Public bug reported:
In my MAAS test setup, nodes now fail to enlist or commission. They
used to work, I think before we changed to the new import script.
Both for enlistment and commissioning the nodes netboot properly, as far
as I can see, but they fail to do what they booted for. They never
I wasn't getting any new files from the import script. Am now re-
running the entire import from scratch.
--
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/1300026
Title:
Yay! A fresh import solved it.
** Changed in: maas
Status: Incomplete = Invalid
** Changed in: maas (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Public bug reported:
In my MAAS test setup, nodes now fail to enlist or commission. They
used to work, I think before we changed to the new import script.
Both for enlistment and commissioning the nodes netboot properly, as far
as I can see, but they fail to do what they booted for. They never
I wasn't getting any new files from the import script. Am now re-
running the entire import from scratch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300026
Title:
Enlistment/commissioning boot
Public bug reported:
My display's native resolution is 2560×1440 pixels. Prior to, I think,
Saucy I could only reach this resolution by adding it using xrandr, and
then calling xrandr on boot/login to select that resolution. The
Display preferences did not show any higher options than
Yay! A fresh import solved it.
** Changed in: maas
Status: Incomplete = Invalid
** Changed in: maas (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
My display's native resolution is 2560×1440 pixels. Prior to, I think,
Saucy I could only reach this resolution by adding it using xrandr, and
then calling xrandr on boot/login to select that resolution. The
Display preferences did not show any higher options
** Project changed: maas = maas (Ubuntu)
** Changed in: maas (Ubuntu)
Milestone: 14.04 = None
--
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/1299989
Title:
maas-dns fails to
** Project changed: maas = maas (Ubuntu)
** Changed in: maas (Ubuntu)
Milestone: 14.04 = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1299989
Title:
maas-dns fails to install without
See bug 1284964 for a possible explanation: the enlist_userdata calls
dig to look up a hostname, but does not check for errors — and dig
prints the error message to stdout, not stderr, so it ends up in the
hostname field.
--
You received this bug notification because you are a member of Ubuntu
See bug 1284964 for a possible explanation: the enlist_userdata calls
dig to look up a hostname, but does not check for errors — and dig
prints the error message to stdout, not stderr, so it ends up in the
hostname field.
--
You received this bug notification because you are a member of Ubuntu
I'm seeing this too, on all my Ubuntu devices. Restarting doesn't help,
nor does reinstalling the CA certificates, nor does re-authenticating
with Ubuntu SSO.
Looking at the web UI, it looks as if the server has forgotten about all
my devices! On the website I only see my web session as a
Ah, found the logs back. Always a bit confusing under ~/.cache!
Here's a log entry for the failure in the UI, while trying to remove the
local device:
2014-02-11 21:12:23,994 - ubuntuone.controlpanel.qt.device - ERROR - Error
while invoking function on_remove_device_button_clicked at 0x28ac050
I did get such an email, but it did not ask me to remove and re-add my
devices. It asked me to remove and re-add my account. Not sure what
that means exactly. It also said that the change might log me out, and
this change would be needed to get it working again. Reading this back
I can only
To be exact, the email said that the change would log me out but also
that the change had already happened. The logical conclusion as I read
it now would have been if I am not logged out already, I do not need to
do anything.
--
You received this bug notification because you are a member of
As far as I'm concerned we can just close this bug. It's been more than
3½ years, and I think I've seen it working in the meantime (if probably
on different hardware).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: maas
Milestone: None = 14.04
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas
For the historical record:
* createsuperuser is a Django built-in command, not our code.
* We have our own MAAS-tailored version, createadmin.
* The email field must be unique and non-null, but can be empty.
* MAAS already creates a system user with empty email address.
* A null email
** Changed in: maas
Milestone: None = 14.04
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
For the historical record:
* createsuperuser is a Django built-in command, not our code.
* We have our own MAAS-tailored version, createadmin.
* The email field must be unique and non-null, but can be empty.
* MAAS already creates a system user with empty email address.
* A null email
Don't know if this matters, but...
The blog article suggests WSGIProcessGroup %{GLOBAL}. We have
WSGIApplicationGroup %{GLOBAL}, but WSGIProcessGroup maas.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pymongo in Ubuntu.
Don't know if this matters, but...
The blog article suggests WSGIProcessGroup %{GLOBAL}. We have
WSGIApplicationGroup %{GLOBAL}, but WSGIProcessGroup maas.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: maas
Status: Triaged = Fix Committed
--
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/1236361
Title:
need new simple streams based maas-import-ephemerals
To
** Changed in: maas
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236361
Title:
need new simple streams based maas-import-ephemerals
To manage notifications
** Changed in: maas
Milestone: None = 13.10
--
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/1236361
Title:
need new simple streams based maas-import-ephemerals
To manage
** Changed in: maas
Milestone: None = 13.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236361
Title:
need new simple streams based maas-import-ephemerals
To manage notifications about this
Public bug reported:
Automatically reported crash. I think it happened while upgrading.
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: unity-webapps-common 2.4.16+13.10.20130715-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic i686
I don't know — update-manager launched automatically.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215425
Title:
update-manager crashed with Package linux-headers-3.11.0-2 isn't
available in
Looks like this was caused by a missing en_US entry in Julian's
/usr/share/locale.
I'm seeing another, but possibly related failure where the error is that
the database is not running; filed as bug 1171696.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Looks like this was caused by a missing en_US entry in Julian's
/usr/share/locale.
I'm seeing another, but possibly related failure where the error is that
the database is not running; filed as bug 1171696.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That worked around it, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168299
Title:
Can't upgrade to raring: libvisio download fails with Forbidden
To manage notifications about this bug
apport information
** Attachment added: VarLogDistupgradeAptlog.txt
https://bugs.launchpad.net/bugs/1168299/+attachment/3645209/+files/VarLogDistupgradeAptlog.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 dist-upgrade
** Description changed:
My apologies if I'm reporting this on the wrong package. I've been
trying for 4—5 days now to upgrade a Quantal system to Raring, but the
part where it downloads packages always fails, saying libvisio
apport information
** Attachment added: VarLogDistupgradeLspcitxt.txt
https://bugs.launchpad.net/bugs/1168299/+attachment/3645210/+files/VarLogDistupgradeLspcitxt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: VarLogDistupgradeMainlog.txt
https://bugs.launchpad.net/bugs/1168299/+attachment/3645211/+files/VarLogDistupgradeMainlog.txt
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because
There, hope that did it (apport did say “dpkg-query: no packages found
matching ubuntu-release-upgrader” but it seems to be okay).
I took this bug back to New status, because I've sometimes had bugs
remain in Incomplete at this stage, and just expire in the end.
--
You received this bug
Public bug reported:
My apologies if I'm reporting this on the wrong package. I've been
trying for 4—5 days now to upgrade a Quantal system to Raring, but the
part where it downloads packages always fails, saying libvisio can't be
downloaded.
The http error is Forbidden.
I know this is
(FWIW somebody landed a fix recently to suppress the initialization of
NodeGroup.maas_url if the given URL had localhost as its hostname. It
seems like a better way to deal with the maas_url part of the problem.)
--
You received this bug notification because you are a member of Ubuntu
Server
(Correction: I meant to say that AIUI, that fix suppresses _any_
initialization of maas_url, regardless of whether the calling code
thinks it's dealing with the master cluster)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
(FWIW somebody landed a fix recently to suppress the initialization of
NodeGroup.maas_url if the given URL had localhost as its hostname. It
seems like a better way to deal with the maas_url part of the problem.)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
(Correction: I meant to say that AIUI, that fix suppresses _any_
initialization of maas_url, regardless of whether the calling code
thinks it's dealing with the master cluster)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I can't make use of Bluetooth on a Quantal laptop, freshly installed
with the release version of Quantal and kept up-to-date from there.
Symptoms:
* No bluetooth icon shows up in my menu bar, even though I've enabled
bluetooth in the bluetooth preferences.
* The add
Public bug reported:
I'm trying to report a bug in Unity, but ubuntu-bug crashes when I try
to do so. It's a UnicodeDecodeError in
__AptDpkgPackageInfo.get_modified_files (packaging_impl.py line 256 in
this version).
Traceback: http://paste.ubuntu.com/1367075/
Based on that error I'd expect to
Public bug reported:
I just created a keyfile on a new machine by running euca-add-keypair
and directing its output into a key file. The key didn't work, for no
immediately clear reason. Turns out my keyfile now contains this text:
KeyPairExists: Key pair '...' already exists.
Would have
Public bug reported:
I just created a keyfile on a new machine by running euca-add-keypair
and directing its output into a key file. The key didn't work, for no
immediately clear reason. Turns out my keyfile now contains this text:
KeyPairExists: Key pair '...' already exists.
Would have
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
--
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/1070774
Title:
The hostname of a node can still be changed
Small Q/A failure: renaming an accepted nodegroup that has no interfaces
will oops. See bug 1077075 (and don't get confused by the similarity in
bug numbers...)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
The Q/A failure has been fixed in both the trunk and 1.2 branches.
--
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/1070775
Title:
The zone name (attached to a cluster controller) can
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070774
Title:
The hostname of a node can still be changed once the node
Small Q/A failure: renaming an accepted nodegroup that has no interfaces
will oops. See bug 1077075 (and don't get confused by the similarity in
bug numbers...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Q/A failure has been fixed in both the trunk and 1.2 branches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070775
Title:
The zone name (attached to a cluster controller) can still be changed
Stealing this bug from Julian since he's packing, not packaging right
now. :)
** Changed in: maas (Ubuntu)
Assignee: Julian Edwards (julian-edwards) = Jeroen T. Vermeulen (jtv)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Stealing this bug from Julian since he's packing, not packaging right
now. :)
** Changed in: maas (Ubuntu)
Assignee: Julian Edwards (julian-edwards) = Jeroen T. Vermeulen (jtv)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
This bug is absolute hell on a MacBook Pro: I can't turn the touchpad
off while typing in KDE, and it's huge and quite sensitive, so I'm
constantly having text selected/deleted/inserted, and my cursor moved,
while typing. Sometimes the mouse pointer moves over to a button and
then clicks it,
The same patch as in the merge-proposal diff also needs to be applied in
the package. Two of those three instances of the problem have already
been fixed upstream though.
** Also affects: python-tx-tftp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
The same patch as in the merge-proposal diff also needs to be applied in
the package. Two of those three instances of the problem have already
been fixed upstream though.
** Also affects: python-tx-tftp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas
Status: Triaged = In Progress
--
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
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059453
Title
I do believe it tries to be careful not to delete other packages' files
in the process. Did you see any files left in those locations?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Update for the record. As we have since found out, it's much worse than
just needing an expect fork. Somewhere along the line, before it gets
around to running the start-cluster-controller code proper, maas-
provision does a whole bunch of other forks. The question is whether we
can make
I do believe it tries to be careful not to delete other packages' files
in the process. Did you see any files left in those locations?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059973
Title:
Update for the record. As we have since found out, it's much worse than
just needing an expect fork. Somewhere along the line, before it gets
around to running the start-cluster-controller code proper, maas-
provision does a whole bunch of other forks. The question is whether we
can make
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas (Ubuntu)
Status: Triaged = In Progress
** Branch linked: lp:~jtv/maas/pkg-bug-1059485
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas (Ubuntu)
Status: Triaged = In Progress
** Branch linked: lp:~jtv/maas/pkg-bug-1059485
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I was running the nouveau driver before; it turns out unity does work
with the nvidia driver! Mystery solved.
Unfortunately the nvidia driver doesn't seem to do brightness control —
the screen's at full blast, which is considerable on this laptop. Not
something I can work with under current
Daniel, the output from unity_support_test -p is:
Xlib: extension GLX missing on display :0.
Error: GLX is not available on the system
Omer, the output from starting unity in tty1 and switching to tty7 (well, I
bumbled a bit) goes like: http://paste.ubuntu.com/1229067/
(The unity process
Output from running unity in a text console:
unity-panel-service: no process found
compiz (core) - Info: Loading plugin: core
compiz (core) - Info: Starting plugin: core
No protocol specified
compiz (core) - Fatal: Couldn't open display :0
compiz (core) - Info: Stopping plugin: core
compiz (core)
Public bug reported:
I just upgraded from Precise to the Quantal beta, and now Unity is no
longer working for me. I'm guessing it's caused by Compiz not working.
The update manager had warned me that the desktop might be slow, but
there's no desktop at all.
The system shows my background image;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054845
Title:
Unity not working on mid-2009 MacBook Pro
To manage notifications about this bug go to:
Yup, that works. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957699
Title:
[bcm5974] Two-finger right-click no longer working
To manage notifications about this bug go to:
No way of knowing — wakeup from suspend doesn't work for me in Precise.
:(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/704962
Title:
0a5c:4500 Can't connect to bluetooth headset after suspend
To
Public bug reported:
At some point yesterday or today, a file I've been editing regularly in
GEdit disappeared from my Ubuntu One folder. I haven't been editing it
with anything else. There have been a few network outages, but not
many. I may have made changes to other synchronized files, but
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017384
Title:
Lost file after saving in GEdit
To manage notifications about this bug go to:
Public bug reported:
Actually, I think this happened when I subsequently purged couch (and
related libraries etc.) from my system.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: couchdb 1.0.1-0ubuntu18
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988156
Title:
package couchdb 1.0.1-0ubuntu18 failed to install/upgrade: subprocess
installed pre-removal script returned error exit status 1
To
Split off the pserv txlongpoll parts as bug 977752 (we can do these
within the MAAS code).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975450
Title:
bind all services not required by the nodes
Turns out there was no need to split off a bug: the MAAS bugtask on this
bug was meant for that. Marked the new bug as a duplicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975450
Title:
bind
The branch I attached makes pserv listen only to 127.0.0.1. THIS DOES
NOT FIX TXLONGPOLL. That would take upstream changes to make the
interface binding configurable. So we'll still need to firewall off the
txlongpoll port.
** Branch linked: lp:~jtv/maas/bug-977752
--
You received this bug
** Changed in: maas (Ubuntu Precise)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975435
Title:
purpose of maas-gc cron job is undocumented
To manage
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975450
Title
** Changed in: maas (Ubuntu Precise)
Status: Triaged = In Progress
** Changed in: maas (Ubuntu Precise)
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
This time, “synclient ClickFinger3=2” gives me a working middle mouse
button but still no right-click.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957699
Title:
[bcm5974] Right-click no longer
It gets weirder. After running that command, *most* attempts at mid-
clicking work. Some come out as left clicks though, and one came out as
a right-click just now.
Normally I'd suspect the trackpad hardware, but then why does two-
fingered scrolling work?
--
You received this bug
I'm still having the problem. It worked temporarily when I ran
“synclient ClickFinger3=2”. It's gone again when I reboot, which
unfortunately is never very long without a working suspend.
Strangely enough, just once during this current session I saw right-
click work. But when I tried again it
Ah! I think I'm getting a handle on this. I think the right-click must
have gotten more sensitive to movement during the attempt to click.
Right-click works sometimes now, but I have to hold both my fingers
really really still as I push down the trackpad.
This is compounded by another problem
Argh. I can right-click again, which gets me around bug 957699, but I
still can't middle-click.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933355
Title:
Middle-click on MacBook Pro touchpad no
Given that this is not the bug it was thought to be, can we re-open it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933355
Title:
Middle-click on MacBook Pro touchpad no longer works
To manage
Yay! I can right-click again. Thanks.
Note though that the three-fingered gestures stopped working for me in
Oneiric, and never came back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933355
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957699
Title:
Right-click no longer working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/957699/+subscriptions
Public bug reported:
This is on a mid-2009 MacBook Pro, with the buttonless trackpad. You
push down the trackpad to click; doing so with 2 fingers means right-
click and using 3 fingers means middle-click.
The middle-click version stopped working during Precise alpha testing.
Then, attempts to
I think the problem may have gone away in the meantime. I haven't seen
it for a while, and I'm no longer near the network I originally noticed
it in. It was the normal network-manager wi-fi password dialog, not the
keyring one. And it needed the network's password, not any personal
password.
I just made it crash again, but there's no crash notice after I log in.
I tried “sudo service apport start force_start=1”; it says “service
already running” — not surprising for a beta, but “ps -ef | grep -i
apport” shows nothing.
--
You received this bug notification because you are a member
Tried it again after stopping and restarting Apport. No luck. My
Xorg.0.log isn't very helpful either; ends in a bunch of lines like…
[ 46515.…] (II) XKB: reuse xkmfile /var/lib/xkb/server-
B9E2FA0EEF8A91EF1CC7991FC61772F1BA8D5E13.xkm
There's nothing in /var/log/gdm from the past 2 or 3 weeks.
Logs produced by the crash, once the NoTrapSignals option was set.
** Attachment added: logs.tar.bz2
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/943968/+attachment/2828028/+files/logs.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Disabling signal trapping seems to have done the trick. I'll attach the
logs the crash produced that time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943968
Title:
Trackpad swipe crashes X
To
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943968
Title:
Trackpad swipe crashes X
To manage notifications about this bug go to:
Public bug reported:
X has been crashing lately when I swiped my full hand across the
trackpad to clean it.
At least that's what I think it's been doing: screen goes black, I do
see a mouse pointer at some point, and I end up back at the login
screen.
ProblemType: Bug
DistroRelease: Ubuntu
apport information
** Attachment added: peripherals.txt
https://bugs.launchpad.net/bugs/933355/+attachment/2748679/+files/peripherals.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933355
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/933355/+attachment/2748667/+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/933355
101 - 200 of 541 matches
Mail list logo
