Public bug reported:
This syncs juju with the upstream release bringing the latest bugfixes
and enhancements.
[SRU Information]
juju-core has a stable release exception, including for major version updates,
https://wiki.ubuntu.com/JujuUpdates.
[Impact]
A full list of targeted bugs can be seen a
Public bug reported:
This syncs juju with the upstream release bringing the latest bugfixes
and enhancements.
[SRU Information]
juju-core has a stable release exception, including for major version updates,
https://wiki.ubuntu.com/JujuUpdates.
[Impact]
A full list of targeted bugs can be seen a
Public bug reported:
It seems as per https://github.com/Azure/azure-cli/issues/1792 there was
an update to argcomplet that is incompatible.
** Affects: azure-cli (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bug
Public bug reported:
After installing azure-cli, when trying to run the command it errors
with the message:
Error loading command module 'storage'
__init__() got multiple values for keyword argument 'default_completer'
Traceback (most recent call last):
(there is 2 error messages here, but will
@kaihengfeng, which kernel would that be? In grub I only see (taken from "dpkg
--list | grep linux-image | grep ii"):
- linux-image-4.12.0-11-generic
- linux-image-4.13.0-041300rc6-generic
I take it I would have to install a previous kernel to check this one
out?
--
You received this bug n
I installed the requested kernel[0] and the issue still remains[1].
Tagging as requested.
[0] $ uname -a
Linux Prodigal 4.13.0-041300rc6-generic #201708201831 SMP Sun Aug 20 22:32:57
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[1] http://pastebin.ubuntu.com/25366599/
** Changed in: linux (Ubuntu)
I installed the requested kernel[0] and the issue still renames. Tagging
as requested.
[0] $ uname -a
Linux Prodigal 4.13.0-041300rc6-generic #201708201831 SMP Sun Aug 20 22:32:57
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Public bug reported:
I recently upgraded to artful (xenial -> zesty -> artful).
Now when I plug in my docking station I see this[1] in syslog and no
network device appear.
The docking station is a ThinkPad OneLink+ Dock, my laptop a ThinkPad X1
Carbon 4th gen.
[1] http://pastebin.ubuntu.com/253
Public bug reported:
I use the command "setxkbmap -layout us -option ctrl:swapcaps" to set
capslock as control.
Whenever I plug in any USB device or my docking station this gets
'reset' and I have to run the command again.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.12.0-
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673652
Title:
SRU juju-mongodb 3.2.12-0ubuntu1 to yakkety and xenial
To manage notifications about this bug g
I should also note that the test runs as the ubuntu user whish does has
sudo access to the whole machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers
These tests are run across different archs using the same script (the
same user etc.). Nothing has changed in how it's run but we're only
seeing this failure on Zesty.
I should be able to get the PolicyKit output from the journal in case
that is of use.
--
You received this bug notification beca
Hi Brian, Team,
We've been running some tests using the SRU (3.2.12-0ubuntu1~16.04)
version of juju-mongodb and are happy with the results (nothing but
passing tests :-) ).
We tested things that had an lxd component as we had control over being
able to use proposed (juju itself cannot do that yet
Public bug reported:
When using the frontend DistUpgradeViewNonInteractive the stdout logging
during the install/update is garbled as each character is shown as a
single character bytestream, example:
b'\r'b'E'b'x'b't'b'r'b'a'b'c'b't'b'i'b'n'b'g'b'
'b't'b'e'b'm'b'p'b'l'b'a'b't'b'e'b's'b' 'b'f'b'
** Changed in: autopilot
Status: Fix Committed => 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/1524000
Title:
PyGIWarning: UbuntuAppLaunch was imported without specifying a vers
** Changed in: autopilot
Assignee: (unassigned) => Christopher Lee (veebers)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1524000
Title:
PyGIWarning: UbuntuAppLaunch was imported with
** Branch linked: lp:~canonical-platform-
qa/autopilot/depends_for_gsettings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477233
Title:
autopilot now depends on "/usr/bin/gsettings" and ubuntu-key
** Changed in: autopilot (Ubuntu)
Status: Confirmed => 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/1471598
Title:
Autopilot uses mouse events, puts device in windowed mode
To
** Branch linked: lp:~canonical-platform-qa/autopilot/overlay_fix-touch-
device
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471598
Title:
Autopilot uses mouse events, puts device in windowed mode
Digging into this its not 'Mouse' events triggering this (you cannot create a
Mouse instance on a device without installing all the XLib stuff).
It's the creation of a Touch device that is triggering this. You can observe
this by shelling into a device and starting python3 terminal:
>>> from au
It seems I was debugging something similar with rhuddie the other day
(without solution). In case it's useful I'll mention it here:
What I observed was the test in question would stop then start the
maliit-server, then the test immediately clicked on a text input and
failed as the OSK never came u
** Changed in: autopilot
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/1376996
Title:
test_customised_proxy_classes_have_extension_classes started failing
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425721
Title:
Extension classes with multiple base classes aren't merged correctl
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376996
Title:
test_customised_proxy_classes_have_extension_classes started failin
** Description changed:
The test
"autopilot.tests.functional.test_introspection_features.IntrospectionFeatureTests.test_customised_proxy_classes_have_extension_classes"
is now failing (but was passing when CI ran it when it was merged.)
+
+ [Impact]
+
+ * The autopilot self test started
This is still relevant but we expect to be a lot clearer with this bug
description. We have a task on our backlog to produce a report (or
similar) of what needs improved and the best practices to do so. So in
the near future this bug will have some better relevant details.
--
You received this bu
Good point :-) Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435978
Title:
subunit file often missing attachments
To manage notifications about this bug go to:
https://bugs.launchpad.net/a
Rodney, so I take it that it is safe to remove Autopilot as an
"affects"? Seems like it's a purely testtools issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435978
Title:
subunit file often mi
** Description changed:
After a recent dist-upgrade on vivid the following code now raises an
exception:
- $ python3 -c "from Xlib import display; display.Display()"
+ $ python3 -c "from Xlib import display; display.Display()"
- Error:
+ Error:
Traceback (most recent call last):
-
Public bug reported:
After a recent dist-upgrade on vivid the following code now raises an
exception:
$ python3 -c "from Xlib import display; display.Display()"
Error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/Xlib/display.py", line 80, in
** Changed in: autopilot
Status: Fix Committed => Fix Released
** Changed in: autopilot (Ubuntu)
Status: New => 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/1408317
Title:
** Changed in: autopilot
Status: Fix Committed => 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/1409778
Title:
autopilot and autopilot sdk helper documentation needs API website
** Changed in: autopilot
Status: Fix Committed => 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/1414632
Title:
Skipped tests are not clearly visible in logs
To manage notificati
** Changed in: autopilot
Status: Fix Committed => 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/1306330
Title:
Custom proxy classes don't inherit special Qt abilities
To manage
** Changed in: autopilot
Status: Fix Committed => 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/1411096
Title:
Autopilot tests fail on vivid because the name of the calculator
** No longer affects: autopilot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422797
Title:
Qtmir aborts if it cannot connect to Mir
To manage notifications about this bug go to:
https://bugs.laun
** Attachment added: "2nd file mentioned in comment"
https://bugs.launchpad.net/autopilot/+bug/1422797/+attachment/4326989/+files/whoopsie.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422797
Attaching the 2 logs mentioned in my previous comment
** Attachment added: "Subunit file mentioned in above comment"
https://bugs.launchpad.net/autopilot/+bug/1422797/+attachment/4326873/+files/test_results.subunit
--
You received this bug notification because you are a member of Ubuntu
Bugs
Late in the day I was able to check out some logs, here are my (raw)
thoughts and observations regarding what happened in case they might be
of use.
Logs found here: http://rtm-
dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/243:20150224:20150216-fe747ac/349/camera_app/
[camera_app.t
Ok right, so installed the linked updated version of autopkgtest and it
gets further for me (I see some tests pass).
I do see, however, this message:
Testability driver loaded. Wire protocol version is "1.4".
Testability driver loaded. Wire protocol version is "1.4".
Unable to register object on D
A quick note as per comment on IRC:
veebers: I believe what is happening is that a test is causing
camera-app to crash, and while it is crashing (and apport running) all
subsequent tests that are run during that time frame fail
...
veebers: yes, and figuring out why the camera-app is crashing
Where else is it expected that this helper would be used? I imagine that
initially it'll be only used in the filemanager app?
If so it should go there and if it's needed in other tests than the toolkit is
a better place than autopilot for it.
Thoughts?
--
You received this bug notification bec
I tested the existing proposal and it attempts to load the module but
fails with the message (bigger log here[1]):
.. snip ..
Testability driver loaded. Wire protocol version is "1.4".
Testability driver loaded. Wire protocol version is "1.4".
Unable to register object on D-Bus! Testability interf
** Description changed:
Currently writing an autopilot test that restarts unity8 with testability
(much like the current unity8 tests) and launches the webbrowser app from the
app scope (by clicking the icon).
The first run through this works fine, but the second time it doesn't work as
the
Public bug reported:
Currently writing an autopilot test that restarts unity8 with testability (much
like the current unity8 tests) and launches the webbrowser app from the app
scope (by clicking the icon).
The first run through this works fine, but the second time it doesn't work as
the browse
** Changed in: autopilot-legacy (Ubuntu)
Status: In Progress => Fix Released
** Changed in: autopilot
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352889
This bug is fixed in trunk (unknown revno). Was resolved with the newer
work on "class UpstartApplicationLauncher(ApplicationLauncher)"
** Changed in: autopilot
Status: Invalid => Fix Released
** Changed in: autopilot (Ubuntu)
Status: Invalid => Fix Released
--
You received this b
This bug is no longer valid as it was resolved with the updated "class
UpstartApplicationLauncher(ApplicationLauncher):" code.
** Changed in: autopilot
Status: New => Invalid
** Changed in: autopilot (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification becau
** Changed in: autopilot
Status: Fix Committed => 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/1348399
Title:
Autopilot does not honor the object cache when creating the root
This crash file was taken from the gatekeeper run[1]. Note this run does
include the silo ppa with the code under test but I didn't see any
mention of libautopilot-qt in it so thought it would be of interest.
The crash happens at the start of the 'testing sudoku_app' log.
[1]http://q-jenkins.ubunt
Hi,
This bug is affecting the gatekeeper testing for releasing libautopilot-
qt[1] and holding up any possible release of this code. (and will affect
any other up coming test runs too).
This is a test run without the testing silo so it's not the new libautopilot-qt
causing the crash.
[1] http://
Hi Adam, sorry for the delay.
Installing python3-gi (and python3-gi-cairo) version 3.12.0-1ubuntu1
fixed the issue for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Using the python gi.repository (gir1.2-gtk-3.0) if I import Gdk make a
specific method call and then import GdkX11 the API for GdkX11 is
different than if I had imported both before the method call.
To reproduce:
Run the script found here (details in comments):
http://pasteb
Public bug reported:
When using the gi.repository bindings on Utopic a segfault occurs if an
expected environment variable isn't set.
On Utopic machines we have a debian/rules build step fail due to a
segfault that happens when the expected environment variables are not
available.
In Trusty this
** Description changed:
- When there is a failure to import a module this failure is logged but
- also means that everything else will be logged to stdout from that point
- on.
+ When failing to import a module the gi.repository import.py module logs an
error with `logging.error(..)` causing a lo
** Description changed:
When there is a failure to import a module this failure is logged but
also means that everything else will be logged to stdout from that point
on.
+
+ The Issue:
+ When failing to import a module the gi.repository import module adds a
handler, that sends output t
Public bug reported:
When there is a failure to import a module this failure is logged but
also means that everything else will be logged to stdout from that point
on.
To reproduce/test:
Run the python script found here: http://pastebin.ubuntu.com/7693393/
Expected output: Nothing. No logging a
** Changed in: autopilot
Status: Confirmed => Invalid
** Changed in: autopilot
Status: Invalid => 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/1269649
Title:
Improve the
** Changed in: autopilot (Ubuntu)
Status: New => Confirmed
** Changed in: autopilot
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224527
Title:
autopilot vis
** Also affects: autopilot
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/1274139
Title:
autopilot should rather use upstart to stop an application rather
** Also affects: autopilot
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/1276364
Title:
Autopilot vis should allow print_tree dump
To manage notification
** Also affects: autopilot
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/1267105
Title:
/usr/lib/ubiquity/bin/ubiquity:11:GtkNode::MatchStringProperty:xp
As per the discussion in our meeting, the plan is to investigate other
methods of testing qtcreator. Part of this bug was resolved/fixed but
there is too any unknowns.
** Also affects: autopilot
Importance: Undecided
Status: New
** Changed in: autopilot
Status: New => Won't Fix
** Changed in: autopilot
Status: Confirmed => 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/1281253
Title:
Test:
autopilot.tests.functional.test_ap_apps.QtTests.test_bamf_geom
** Changed in: autopilot
Status: New => 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/1274292
Title:
Webapps tests are failing with a Search error "Many results Returned"
To man
Public bug reported:
(text extract from an email)
We're having an interesting issue with the pinch touch gesture in autopilot
that seems to be related to the recent upgrade of Qt.
I've found that if I create a UInput device before launching qmlscene the pinch
gesture works as expected, but if w
This is an issue with xpathselect related to the colons in the name
(i.e. Internal::MainWindow).
I have a branch fix for this, in progress . . .
** Also affects: xpathselect
Importance: Undecided
Status: New
** Changed in: xpathselect
Assignee: (unassigned) => Christopher
** Summary changed:
- autopilot crashed with StateNotFoundError in get_new_state(): State not found
for class with name 'ApplicationLauncherIcon' and id '237142'.
+ autopilot vis crashed with StateNotFoundError in get_new_state(): State not
found for class with name 'ApplicationLauncherIcon' and
Public bug reported:
Copying html_logo file over improperly checks for file basename instead
of relative name (taken from[1])
To quote:
"1.2.1 inserted a check to see if the html_logo file existed before
attempting to copy it over to _static; however, the check is on the basename of
the file
I like the idea of returning True or False. It means that callers don't need to
worry about catching pesky exceptions :-)
It also means that we don't have to write another specific method just to make
sure the greeter _wasn't_ swiped away.
--
You received this bug notification because you are a
Public bug reported:
There is an issue with how the emulator handles changing states and
currently can't handle changing into CAPSLOCK mode.
** Affects: ubuntu-keyboard (Ubuntu)
Importance: Undecided
Assignee: Christopher Lee (veebers)
Status: New
--
You received thi
** Branch linked: lp:~veebers/autopilot/1.4_fixing_backend_being_none
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233972
Title:
A recent change causes some gallery-app tests to fail with _Backend
*** This bug is a duplicate of bug 1229561 ***
https://bugs.launchpad.net/bugs/1229561
** This bug has been marked a duplicate of bug 1229561
Automated regression test for Bug #1227714 (OSK doesn't close after the
application closes)
--
You received this bug notification because you are
Marking other bug as duplicate, no need to have 2 bugs for one defect.
Copying details to this one so not lost.
Original Bug Text:
Steps to reproduce:
1. Flash the latest daily current to Nexus 4
2. Launch the pre installed Calculator app
3. Launch the web browser app and tap on URL field to br
Original Comment from dupe bug:
I can confirm with a variant where you don't kill the browser, which is
not a "user" way to terminate an application on the phone but instead
when in the browser with OSK displayed, reveal the launcher and press
the calculator app, OSK should hide but it doesn't.
-
** Tags removed: touch-needs-autopilot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227714
Title:
OSK doesn't close after the application closes
To manage notifications about this bug go to:
http
Public bug reported:
Automated regression test for Bug #1227714 (OSK doesn't close after the
application closes).
A test to show when this bug is resolved.
** Affects: ubuntu-keyboard (Ubuntu)
Importance: Undecided
Assignee: Christopher Lee (veebers)
Status: New
** Tag
Public bug reported:
The keyboard fails to show a 'password' layout with the input hints:
'Qt.ImhHiddenText', 'Qt.ImhSensitiveData' (as per the design spec.).
** Affects: ubuntu-keyboard (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you a
Public bug reported:
There is a very short delay between a key press and when the shift key is able
to respond to a press.
Currently there is no way to tell if the shift key is ready to accept taps, so
the work-around of a sleep(.2) is used before pressing the shift key.
Related: bug #1229001
Public bug reported:
There is a very short delay between a key press and when the shift key
is able to respond to a press (i.e. a then shift in quick succession,
the shift key will not respond).
I am able to tap other keys in quick succession (i.e a and backspace)
without issue.
** Affects: ubun
Public bug reported:
Working with the autopilot tests, have exposed the layout.activeView
('url', 'telephone' etc.) the activeView detail doesn't seem to be
either exposed correctly or updated as expected.
I added debugging to the Keyboard.qml and there was no messages
outputted.
onActiveV
Public bug reported:
For instance typing in the Notes app; Tapping on a new note the keyboard
appears but is in lowercase mode. Also typing abc. doesn't shift the
keyboard into uppercase mode.
** Affects: ubuntu-keyboard (Ubuntu)
Importance: Undecided
Status: New
--
You received t
I've since learned that I should be using:
from gi.repository import Notify
Marked as invalid as I got it wrong.
** Changed in: notify-python (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
In a python terminal I do the following:
>>> import pynotify;
>>> from gi.repository import Gdk
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/gi/__init__.py", line 27, in
from ._gi import _API, Repository
ImportError:
I'm still experiencing this error with the fixed version:
$ lttng list -u
Spawning a session daemon
lttng-sessiond: error while loading shared libraries: liblttng-ust-ctl.so.0:
cannot open shared object file: No such file or directory
Error: Session daemon died (exit status 127)
$ dpkg -l liblt
Removed attachments as they were from a different machine.
** Description changed:
Using a preseed command to dist-upgrade during the install (utilising
UTAH to provision the machine) fails when attempting to process grub-pc.
Excerpt from install log:
>Apr 10 02:29:53 dx-autopilot-a
Public bug reported:
Using a preseed command to dist-upgrade during the install (utilising
UTAH to provision the machine) fails when attempting to process grub-pc.
Excerpt from install log:
>Apr 10 02:29:53 dx-autopilot-ati in-target: Setting up grub-common
>(2.00-13ubuntu3) ...
<13>Apr 10 02:2
Public bug reported:
grub-probe error causing dpkg error.
Doing a dist upgrade on a fresh install (using iso: Ubuntu 13.04 "Raring
Ringtail" - Alpha i386 (20130319)) installing linux-
image-3.8.0-13-generic receive this error:
Setting up linux-image-3.8.0-13-generic (3.8.0-13.23) ...
Running dep
Oops, was barking up the wrong tree with this one. Marking invalid.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1123752
Title:
Insta
Public bug reported:
Installing on the Intel machine in the Magners lab using cobbler/utah.
I have taken a screenshot of the casper.log file as I couldn't netcat it
or anything else.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Screenshot o
D'oh sorry Brian I should have included that initially.
I'm using the daily Raring images (from:
http://cdimage.ubuntu.com/cdimage/daily-live/current/)
No I'm unable to get to a tty.
The machine seems to be completely hung and un-responsive.
(The screenshot shows the output from first boot-up).
Public bug reported:
Starts to boot into the installer but hangs (consistently) at a certain spot.
(appears to be: System V runlevel compatibility, but there are a couple of
blank starting/stopping lines too).
Screenshot attached showing what is displayed on screen.
Unable to attach a log as it
This appears to still be happening.
I've been able to attach an apport .crash file with the latest information.
** Attachment added: "Apport supplied crash file."
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1076871/+attachment/3445690/+files/_usr_bin_Xorg.0.crash
I agree that it doesn't make sense to start Spread (as there isn't
anything to show).
But shouldn't the key events be caught and ignored by compiz instead of
being passed on? (i.e. Super-W on an empty desktop will start the
nautilus file search (bottom right-hand corner a text-box appears).
This
Public bug reported:
I'm currently trying to get a succinct list of Autopilot Unity tests
that expose this crash. Currently it happens somewhere within the ~400
tests.
This is the apport stacktrace I was able to grab from the remote
machine:
dpkg-source: info: extracting xorg-server in xorg-serv
I was having the same issue for a couple weeks till I did a search and found
this forum.
All I did to fix was type in ... LANG=en_US.UTF-8 into a terminal as root
exactly the way it is and this problem goes away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059289
Title:
"Open Recent" doesn't work as expected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+
Public bug reported:
When I try to open a recent document using the menu item: "Open Recent"
it doesn't open the selected file but appears to just open the first in
the recent list.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: inkscape 0.48.3.1-1ubuntu6
ProcVersionSignature: Ubuntu 3.5.0
** Attachment added: "Screenshot"
https://bugs.launchpad.net/bugs/1055906/+attachment/3340080/+files/DoubleTerminal_screenshot.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1055906
Title:
Tw
Public bug reported:
After a recent dist-upgrade (running 12.10 Quantal) I was unable to open
a terminal using Ctrl-Alt-t I checked the settings and saw that there
are 2 entries for Launch Terminal (please see attached screenshot).
I initially only saw the first and attempted to reset it by editi
1 - 100 of 112 matches
Mail list logo
