jibel - thanks. It does indeed look like bug 1234743 as the trace shows
a lot of the following events:
:sys:cpu-device-online
:sys:cpu-device-offline
:sys:power_supply-device-changed
This would explain the Session consuming a lot of CPU since those events
are generated by the kernel, picked up by
Also, please could you run
http://people.canonical.com/~jhunt/upstart/scripts/get_state.sh as user
phablet and attach to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
sessio
Apparently, the high cpu load stop when the upstart-event-bridge is
stopped. This lends weight to the high cpu issue being caused the a
kernel udev event issue (like bug 1234743).
However, what is not explained is why the Session Init retains the
memory it consumes once the upstart-event-bridge is
@jibel - that get_state.out appears to have either been run as root, or
atleast outside the session init environment. Please could you re-run as
user phablet?
Also, please could you attach /var/log/udev ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Can someone try running "/sbin/initctl notify-disk-writeable" and see if
the session inits memory consumption drops? Alternatively, run the
session init as "init --user --debug --no-log".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>From info provided by jibel...
Forcing a log flush (#25) doesn't resolve the high memory usage (as we'd
expect, but worth ruling out).
The state file in #24 looks sane to me; forcing a re-exec of the Session
Init does cause the memory to fall to reasonable levels. This almost
feels like a compil
To summarise: there are 2 problems here:
1) The kernel spamming userspace with udev messages on mako+maguro
(grouper doesn't appear to be affected but not independently verified
yet).
2) Upstart not releasing memory once the kernel has finished spamming
userspace (artificially forced by running "
Could someone run the "make check" tests for the libnih package on a
mako/maguro device?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart leaks massive amounts of memory
I can no recreate the issue with memory not being freed by running:
http://paste.ubuntu.com/6205552/.
This is recreatable on i386 desktop images so although problem (1) in
#27 is h/w specific, problem (2) is not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Attempting to run the script in #30 against a session init as below
*outside* of a the standard gui environment with no .conf files does not
trigger the issue:
$ mkdir -p /tmp/conf /tmp/log
$ init --debug --no-startup-event --confdir /tmp/conf --logdir /tmp/log --user
Same outcome running like th
As the description shows, the reason we do not run the upstart-dbus-
bridge at the system level is due to security concerns.
Unless the Security Team feel otherwise, it is probably best to simply
document that this bridge does not run by default and if an admin wishes
to enable it, they can - we c
** Changed in: upstart (Ubuntu Saucy)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart leaks massive amounts
Valgrind run as:
valgrind -v -v -v -v --show-reachable=yes --track-origins=yes --leak-
check=full init --debug --user
** Attachment added: "valgrind session init consuming ~500MB (no suppressions)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+attachment/3866123/+files/valgri
Valgrinding the session init shows that most of the memory is correctly
freed at quiesce time.
** Attachment added: "valgrind session init consuming ~250MB (with
suppressions)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+attachment/3866119/+files/valgrind-250M.log.gz
--
Yo
The problem is triggered by init/control.c:control_emit_event_emitted().
It looks like Upstart itself is clearing up memory, but either dbus
isn't, or upstart is missing a dbus unref call.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
The working theory at this stage is that
init/control.c:control_disconnected() is not cleaning up the dbus
connections created by the upstart-udev-bridge for each event it
requests upstart emit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
init/control.c:control_disconnected() could do with a call to
dbus_connection_close(), but each connection is being unref'd correctly
fwics.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title
To be clear, adding a call to dbus_connection_close() in
control_disconnected() did not resolve the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes session u
Persistent D-Bus connections are as expected (1 / bridge and 1 for
unity-panel-service).
Ephemeral D-Bus connections are being handled correctly and removed from the
control_conns list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Still unclear why memory is being cached in Upstart address space, but
I'm starting to think this might be a libdbus issue.
What is triggering the memory rise though is unity-panel-service:
stopping this from running results in no memory increase within the
Session Init.
** Also affects: unity (U
Right - recall that I am testing on i386 as I don't have mako/maguro :)
However, note that on Touch, the upstart code in unity8
(plugins/Unity/Indicators/indicatorsmanager.cpp) is almost identical to
the upstart code in unity-panel-service (unity/services/panel-
service.c).
Is it possible to some
Re #41, interesting that unity-panel-service *is* installed on Touch
image though :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes session upstart to consume massiv
Public bug reported:
krillin:
phablet@ubuntu-phablet:~$ cat /etc/ubuntu-build
161
phablet@ubuntu-phablet:~$ cat /etc/device-build
20141106-572f18d
phablet@ubuntu-phablet:~$
'strace -p $pid -s 1024 -Ffv' attached.
** Affects: ubuntu-system-settings (Ubuntu)
Importance: Undecided
I think this could be related to bug 1393427 since I am still unable to
install updates (there are more now).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394250
Title:
system-settings consuming 1
Hi Fabian,
The problem you are having seem to be related to mtp-server respawning
continuously. This may not be the same issue as originally reported, so
please open a new bug against the mtp-server package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Currently, the system-image package requires system-image-common. The
latter provides /etc/system-image/client.ini which is configurated for a
Touch environment.
However, to allow system-image to be used on systems other than Touch,
it would be useful to have the ability to s
That should be "ubuntu-bug 1373588" of course :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373588
Title:
Starting/Stopping services causes "init: Error while reading from
descriptor: Bad fil
Thanks for reporting. Please run "ubuntu-bug 373588" which will attach
required logs to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373588
Title:
Starting/Stopping services causes "init
As discussed on irc, the problem seemed to be that the plymouth-ready
event was not being emitted since udev was not tagging a graphics device
with PRIMARY_DEVICE_FOR_DISPLAY, so it looked like the problem was
udev/kernel related.
According to jibel, if he enters the grub boot menu lightdm will
re
I have now recreated using utopic-desktop-amd64.iso (20140923) and
http://people.canonical.com/~jhunt/upstart/conf/rebooter.conf to force
continuous reboots.
It appears that the problem only occurs if "quiet splash" is specified
since I ran 25 boots without those options and was unable to recreate
Note also that I do have PRIMARY_DEVICE_FOR_DISPLAY=1 in /var/log/udev.
Recreation is under kvm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into graphical inte
It's looking like either "quiet" or more likely "splash" is the
triggering factor here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into graphical interface afte
After removing both 'quiet' and 'splash' options from
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, and running 'sudo
update-grub', I am no longer able to recreate the bug (over 100 boots on
a 64-bit kvm instance using utopic-desktop-amd64.iso (20140923)).
@elfy: can you provide details on how
205 boots and no problem with the 2 options removed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into graphical interface after installation
To manage notificat
@arges: can you try reproducing without "quiet splash" as that seems to
be the best lead we have so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into graphic
Public bug reported:
Please add package lp:~ubuntu-foundations-team/+junk/ubuntu-core-config
to the archive.
This package is required for the Ubuntu Core project.
** Affects: ubuntu
Importance: Undecided
Assignee: James Hunt (jamesodhunt)
Status: Fix Committed
** Tags
See also bug 1374446.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374445
Title:
Add new package initramfs-tools-ubuntu-core
To manage notifications about this bug go to:
https://bugs.launchpad.n
See also bug 1374445.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374446
Title:
Add new package ubuntu-core-config
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
This is a native package licenced under GPLv3.
** Tags added: needs-packaging
** Changed in: ubuntu
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: ubuntu
Status: New => In Progress
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
Please add package lp:~ubuntu-foundations-team/+junk/initramfs-tools-
ubuntu-core to the archive.
This package is required for the Ubuntu Core project.
** Affects: ubuntu
Importance: Undecided
Assignee: James Hunt (jamesodhunt)
Status: Fix Committed
This is a native package licenced under GPLv3.
** Tags added: needs-packaging
** Changed in: ubuntu
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: ubuntu
Status: New => In Progress
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
/lib/systemd/system/ifup@.service specifies:
ExecStart=/sbin/ifup --allow=hotplug %I
This really needs to be:
ExecStart=/sbin/ifup --allow=hotplug %I
Since otherwise, for systems that don't use network-manager, the service
will only bring up interfaces which have speci
Upstart only gained the ability to re-exec statefully in Raring. The man
page for telinit on Lucid explains that state is not preserved and also
warns that running this command is not recommended.
Note that upstart has to re-exec itself on Lucid if certain key packages
are upgraded to ensure a cle
$ systemctl status networking
networking.service - LSB: Raise network interfaces.
Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
`-50-insserv.conf-$network.conf
Active: active (exited) since Mon 2014-09-29 09:22:44 UTC; 1min 51s ago
I too am unable to recreate this problem - dbus should certainly not be
running in recovery mode because dbus is 'start on local-filesystems',
but that event will not have been emitted since mountall is not run in
recovery mode.
Can you confirm you are entering recovery mode from the grub menu
(Ad
@elfy - is plymouth is still crashing for you?
$ sudo grep SEGV /var/log/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into graphical interface after insta
> UPSTART_EVENTS=runlevel
> UPSTART_INSTANCE=
> UPSTART_JOB=rcS
This is the cause of your problem - you are not actually in recovery mode. What
is your /proc/cmdline? Have you modified /etc/default/grub or any of the
initramfs configuration?
--
You received this bug notification because you are
Your cmdline shows that you are actually in single-user-mode, not
recovery mode. On a standard system, selecting "recovery mode" from the
grub boot menu will add 'recovery' to the boot command line, which will
trigger recovery mode to be started.
--
You received this bug notification because you
With your cursor on "Ubuntu, with Linux 3.16.0-18-generic (recovery
mode)", press 'e' and you should see 'recovery' specified somewhere on
the line that starts 'linux'. If not, your grub config is incorrect for
some reason.
To test if recovery mode works, again having pressed 'e', remove
'single'
*** This bug is a duplicate of bug 1198180 ***
https://bugs.launchpad.net/bugs/1198180
** This bug has been marked a duplicate of bug 1198180
possible leak in upstart 1.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
This almost sounds like bug 1235649, but unlikely given that the
upstart-udev-bridge uses the correct NIH D-Bus calls.
I suspect the reason for the memory growth is that the events that are
being created cannot be destroyed until some other job has finished with
them. Once that happens, memory wil
Hi Antii,
Having taken a look at them, I don't think they are actually relevant
since they are identical apart from the obvious fields (id, uuid, ssid,
psk).
I'll try and do further tests over the w/e with both networks...
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
The pin code entry screen has what appears to be a 1 pixel high line
horizontal line that goes almost to the left and right borders of the
screen, just above the unlock keypad.
I can see the value of such a horizontal rule but it is _so_ thin that
when I looked at it earlier
root@ubuntu-phablet:~# cat /etc/ubuntu-build
32
root@ubuntu-phablet:~# cat /etc/device-build
20140908-d8c11f3
device: krillin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368798
Title:
horizona
Public bug reported:
1) Add contact.
2) Touch '+' to add a picture.
3) Select a data source (gallery, camera, file manager, etc).
4) Slow swipe from right to show all running apps windows.
5) Observe an app window that has a spinner on a white dialog background with
text "Transfer in progress" al
*** This bug is a security vulnerability ***
Public security bug reported:
$ adb shell sudo id
[sudo] password for phablet: you should not be able to see this!!!
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: android-tools-adb 4.2.2+git20130218-3ubuntu35
ProcVersionSignature: Ubuntu 3.16.
phablet@ubuntu-phablet:~$ cat /etc/ubuntu-build
40
phablet@ubuntu-phablet:~$ cat /etc/device-build
20140908-d8c11f3
phablet@ubuntu-phablet:~$
krillin.
** Also affects: indicator-location (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you ar
*** This bug is a security vulnerability ***
Public security bug reported:
This is a pretty significant security issue that affects:
- networking - able to switch networks without entering pin to unlock phone
- GPS - can toggle.
- bluetooth - can toggle.
- upcoming events - can view.
** Affects
Public bug reported:
Something changed in the last few images that seems to have broken the
system images download progress bar.
If you click pause, then resume the progress jumps significantly showing
that the bar is not updating.
phablet@ubuntu-phablet:~$ cat /etc/ubuntu-build
40
phablet@ubun
*** This bug is a security vulnerability ***
Public security bug reported:
This is atleast a privacy issue but could also be a security depending
on exactly what apps the user has pinned to their launcher.
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Tags: ave
phablet@ubuntu-phablet:~$ cat /etc/ubuntu-build
40
phablet@ubuntu-phablet:~$ cat /etc/device-build
20140908-d8c11f3
krillin
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Android gives the user a warning if they attempt to raise the volume to
100% when headphones are plugged.
This is a sensible precaution both to save the user from tinnitus and to
avoid any potential legal repercussions.
** Affects: indicator-sound (Ubuntu)
Importance: U
This is worse that I originally though since you can actually *launch*
any app on the launcher without unlocking the phone. You can't see it,
but it is running (unlocking confirms this).
** Summary changed:
- able to left swipe and see launcher icons without unlocking phone
+ able to left swipe a
You can also re-order the launcher icons.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1369457
Title:
able to left swipe and launch apps without unlocking phone
To manage notifications about this
To start an app:
1) Swipe left to show launcher.
2) Keeping finger down in (1) long press an app icon in the launcher.
3) Remove both fingers from screen.
4) Swipe left to show launcher again.
5) Launcher should remain on screen allowing you to touch an app icon to launch
it. See attached.
** At
Note sure if this is also a bug (I think it is), but in testing this, I
have inadvertantly managed to delete the system settings icon by moving
it. It seems the operation failed as shown in the screenshot.
** Attachment added: "floating-system-settings.png"
https://bugs.launchpad.net/ubuntu/+s
That failed operation has seemingly corrupted a list somewhere since now
touching my gmail icon actually launches system settings (spoofing
potential here). Attached screenshot shows this.
** Attachment added: "gmail-is-now-system-settings.png"
https://bugs.launchpad.net/ubuntu/+source/unity8/
Personally, I'm happy for the lock screen to show date+time but I would
prefer everything else to be hidden (or ateast hideable with a system-
setting) until the phone is unlocked.
The majority of users may not mind if the notification bar is displayed
when the screen is locked (Android does this)
Update to #6: rebooting the phone brought back the original set of icons
such that touching system-settings launches the correct app and ditto
for gmail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Ah thanks - didn't know about those options! Disabled both now :-)
> The use case for launching apps from the lockscreen is that as a user, you
> think "oh I want to go to facebook",
> click facebook, we start the app in the background so that once you enter
> your passcode, it's sitting there r
Back link to test plan: https://wiki.ubuntu.com/Process/TestPlans
/systemd-shim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357252
Title:
upstart can race with cgmanager when using remove-on-empt
Just installed #41 and the problem is no longer seen so, #40 must have
fixed it :-)
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
*** This bug is a duplicate of bug 1235245 ***
https://bugs.launchpad.net/bugs/1235245
** This bug has been marked a duplicate of bug 1235245
upstart-monitor cannot run without gtk libraries installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: upstart (Ubuntu)
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/1235245
Title:
upstart-monitor cannot run without gtk libraries installed
Confirmed - thanks!
** Description changed:
Actually, there are a couple of problems here:
1) If you "reverse pinch" to zoom into an image, this appears to trigger
"zoom to maximum size" (aka double-tap). Reverse pinch should just "zoom
- on".
+ in".
2) Having zoomed into an image,
Testing on krillin image #44, the problem is no longer seen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365492
Title:
selecting previously visited site from address bar does nothing
To manage n
** Also affects: upstart (Ubuntu)
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/1338637
Title:
continuous re-exec can result in a build-up of inotify fds
** Summary changed:
- continuous re-exec can result in a build-up of inotify fds
+ continuous re-exec can result in a build-up of inotify fds [SRU]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/133863
** Description changed:
+ = PROBLEM =
+
+ The version of Upstart currently in trusty (1.12.1-0ubuntu4.2) suffers
+ from a couple of problems which in combination could make upgrading
+ difficult on systems with high uptimes.
+
+ The 2 issues are:
+
+ == bug 901038 ==
+
+ The issue here is that
** Attachment added: "Output of force-reexec.sh on a trusty system
demonstrating the problem."
https://bugs.launchpad.net/upstart/+bug/1338637/+attachment/4207316/+files/typescript.bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Attachment added: "Output of force-reexec.sh on a trusty system with fixes
for both bugs, showing the problem has been resolved."
https://bugs.launchpad.net/upstart/+bug/1338637/+attachment/4207317/+files/typescript.good
** Description changed:
= PROBLEM =
The version of Upstart cu
The fix for bug 901038 is available upstream but is not yet in Utopic.
Since this is a fundamental system tool, we need to wait until this has
had testing in utopic prior to progressing this SRU.
Plan:
1) Get lp:~jamesodhunt/upstart/bug-1360208 reviewed and landed upstream
(hopefully this week)
** Description changed:
= PROBLEM =
The version of Upstart currently in trusty (1.12.1-0ubuntu4.2) suffers
from a couple of problems which in combination could make upgrading
difficult on systems with high uptimes.
The 2 issues are:
== bug 901038 ==
The issue here is that
A test branch is available here: lp:~jamesodhunt/ubuntu/trusty/upstart
/SRU-bugs-901038+1338637
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338637
Title:
continuous re-exec can result in a build-
A few questions:
1) Has this problem always been present for you since upgrading both systems to
utopic?
2) Do you have any other systems running utopic that do not manifest the issue?
3) How are you shutting the systems down? Via the Unity menu or via the command
line.
4) When you say that the
Can you try replacing your /etc/init.d/umountroot and
/etc/init.d/umountfs with the ones from
http://bazaar.launchpad.net/~jamesodhunt/ubuntu/trusty/sysvinit/log-
open-files-on-shutdown/revision/193 and attaching an updated syslog
file?
The end of your syslog shows that wpa_supplicant is still run
Looks like the shutdown never got as far as running umountroot. Do you
have a /var/log/shutdown-lsof.log that you can attach to this bug?
I see that all the nullmailer output has gone, but we're still left with
wpa_supplicant and dnsmasq output at the end of the log. As such, could
you try shuttin
Public bug reported:
/usr/share/doc is stripped down to only the copyright files and yet...
$ du -sh /usr/share/doc
19M /usr/share/doc
Compressing even just the copyrights gives an appreciable gain:
$ cp -a /usr/share/doc /tmp/foo
$ find /tmp/foo/ -type f -exec gzip -9 {} \; && du -sh /tmp/
As I say, I think we could generate some sort of ascii cache file that
if available could be read to speed the operation up. This cache file
would be generated as part of the build, not by the phone.
Agreed, this is all non-essential but nice to have :)
--
You received this bug notification beca
Public bug reported:
I just upgraded my phone and was presented with 1 system image update
and 3 click apps that needed to be updated.
Would it be reasonable to hide click app updates unless there is no
system image update available? In my case, I opted for the system image
update which included
Public bug reported:
touching the tab at the bottom of the live preview window brings up the
camera settings. The background live video is blurred to show you are in
the settings view.
However, having changed a setting, the window remains blurred,
presumably to allow the user to make other change
Public bug reported:
If I drag up from the bottom (below the "take picture" icon), the
settings view does appear but there is no icon to suggest that.
** Affects: camera-app (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member o
Public bug reported:
1) Visit a web site by clicking in the address bar and specifying the URL.
2) Visit a different site by clicking in the address bar and specifying the URL.
3) Touch in the address bar and type a few characters from the URL for the site
in (1).
4) The browser will prompt with
Thanks for reporting. Please modify /etc/X11/Xsession.d/99upstart as
mentioned on irc and change the STARTUP variable to:
STARTUP="upstart --user --debug 1>&2"
Then, logout and:
- login via console
- rm ~/.xsession-errors
- login graphically
- attach .xsession-errors
It doesn't appear that the
@cjohnston: are you using nvidia hardware? Do you get a full desktop if
you 'sudo restart lightdm' from a console?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365535
Title:
Desktop fails to start
This sounds like a unity issue as I've seen no evidence of Upstart
misbehaving yet. That .xsession-errors log would be useful to have if
you can attach it though.
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a m
Public bug reported:
I had just woken up the phone (screen was displaying the welcome
greeter) but had not yet unlocked the device (I have set a pin code)
when a mail notification appeared on screen that divulged the sender.
This is a privacy issue.
** Affects: indicator-messages (Ubuntu)
I
** Changed in: upstart
Status: In Progress => Fix Released
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart (Ubuntu)
Status: New
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365875
Title:
mail notification displayed even when phone locked
To manage notifications ab
Public bug reported:
When I re-connect to a known network, I am prompted for the WPA2
password. However, clicking cancel then successfully connects to this
network!
This is only happening for one of my networks. Not currently sure why
since the other main network I use is also WPA2 protected and
801 - 900 of 1868 matches
Mail list logo
