** Changed in: gnome-online-accounts (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1353951
Title:
gnome online
** Description changed:
- Gnome online accounts requires autentication on startup, but even typing the
correct password in the box, the program says the password is wrong. By the way
evolution and other programs work well with online accounts. I'm using
Ubuntu-gnome 14.04 LTS 64bit on
** Changed in: evolution-data-server (Ubuntu)
Status: Confirmed = Triaged
** Also affects: evolution-data-server (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: signon-plugin-oauth2 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects:
** Changed in: unity (Ubuntu)
Status: Confirmed = Invalid
** Changed in: unity
Status: Confirmed = Invalid
** Changed in: appmenu-qt
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
In trusty unapproved queue
** Changed in: evolution-data-server (Ubuntu Trusty)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
** Description changed:
As discussed on IRC, I tried to change the favorites key, and 3 trials
on 10 didn't make any change in what the launcher displays. seb128
reproduced it as well. (just be aware that we just create the .desktop
file just before).
The exact same code seems to
** Description changed:
As discussed on IRC, I tried to change the favorites key, and 3 trials
on 10 didn't make any change in what the launcher displays. seb128
reproduced it as well. (just be aware that we just create the .desktop
file just before).
The exact same code seems to
Le 20/09/2014 00:08, Aron Xu a écrit :
---
- fcitx:
* BLOCKER: presagege is missing as a build-dep, do you mind either not
building with it (optional dep) or add it and check it matches the MIR
criterias?
Added and checked presage and libtinyxml (b-d/dep of presage) to MIR.
Live
Looking good with all the incoming changes. Thanks Tim!
** Changed in: tracker (Ubuntu)
Status: Incomplete = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
** Summary changed:
- utopic unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through
gsettings isn't picked up
+ utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition
through gsettings isn't picked up
--
You received this bug notification because you are a member
** Changed in: unity
Milestone: None = 7.3.2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1364070
Title:
utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1)
if the current version has
report_crashes=false
** Affects: whoopsie (Ubuntu)
Importance: Undecided
Assignee: Didier Roche (didrocks)
Status: Triaged
** Tags: systemd-boot
** Changed in: whoopsie (Ubuntu)
Status: New = Triaged
--
You received this bug notification
Public bug reported:
on vivid, with whoopsie 0.2.41:
if type valgrind /dev/null 21; then \
APPORT_REPORT_DIR=/tmp/tmp.ScDOedTr3S ./tools/check_valgrind; \
fi
Please run 'make make check' first.
** Affects: whoopsie (Ubuntu)
Importance: Undecided
Status: New
--
You
FYI, discussing it at http://lists.freedesktop.org/archives/systemd-
devel/2014-November/025334.html
** Changed in: systemd (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Patch added: 0001-Add-display-managers-autopkg-tests.patch
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400680/+attachment/4276871/+files/0001-Add-display-managers-autopkg-tests.patch
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You
Public bug reported:
See attached patch
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
Attached patch
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: New
** Patch added:
0001-Add-xdiagnose-graphical-as-a-fallback-if-display-man.patch
Public bug reported:
Same patches for master branch
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: New
** Patch added: 0001-Add-display-managers-autopkg-tests.patch
** Patch added: 0002-Reset-display-manager-symlink-to-match-e-X-d-d-m.patch
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1401099/+attachment/4277575/+files/0002-Reset-display-manager-symlink-to-match-e-X-d-d-m.patch
--
You received this bug notification because you are a member of
** Changed in: systemd (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) = Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1316796
Title:
systemd
Right on the dependency, I thought only on the ubuntu destkop case, but
yeah, should downgrade to suggests :)
Nice idea on the .d! Definitively doing that then (and so, can close
this bug report) :)
Cheers,
** Changed in: systemd (Ubuntu)
Status: New = Invalid
--
You received this bug
in: grilo-plugins (Ubuntu)
Assignee: Didier Roche (didrocks) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1394731
Title:
[MIR] grilo-plugins
Status
finished to check up the packaging and code source, so apart from the
comments above, that will be a +1 for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1394731
Actually, this is not a systemd behavior but seems to be a syslog one.
1. rm /var/log/syslog
2. reboot
- no log (under systemd or upstart)
3. touch /var/log/syslog
4. chmod syslog:adm /var/log/syslog
5. reboot
- logs availables
The cause is that /var/log is 755 and root:syslog (I wonder why it's
Note that the bug will still be present under upstart, but nothing new,
for reference: http://irclogs.ubuntu.com/2014/12/16/%23ubuntu-
desktop.html#t13:10 :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Excellent, thanks Tim! Promoted to main:
$ ./change-override -c main -S tracker -s utopicOverride component to main
tracker 1.0.2-1ubuntu4 in utopic: universe/utils - main
gir1.2-tracker-1.0 1.0.2-1ubuntu4 in utopic amd64:
universe/introspection/optional/100% - main
gir1.2-tracker-1.0
Public bug reported:
As discussed on IRC, I tried to change the favorites key, and 3 trials
on 10 didn't make any change in what the launcher displays. seb128
reproduced it as well. (just be aware that we just create the .desktop
file just before).
The exact same code seems to work 100% of the
** Summary changed:
- utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition
through gsettings isn't picked up
+ vivid, utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher
addition through gsettings isn't picked up
--
You received this bug notification because
Thanks Andrea for looking deeper into this! Opened the upstream bug for
it.
** Bug watch added: GNOME Bug Tracker #744030
https://bugzilla.gnome.org/show_bug.cgi?id=744030
** Also affects: glib via
https://bugzilla.gnome.org/show_bug.cgi?id=744030
Importance: Unknown
Status:
** Description changed:
+ Found an easy way to reproduce it during brussels sprint:
+ 1. start deja-dup or update-manager
+ 2. kill -9 compiz; metacity
+ 3. compiz --replace
+
+
+ ===
+
Update manager is showing up in the dock but I can click on the icon all
day and nothing
Le 10/02/2015 18:14, Aron Xu a écrit :
On Mon, Jan 12, 2015 at 11:27 PM, Didier Roche didro...@ubuntu.com
wrote:
---
- fcitx:
* NEEDS FIXING: I guess the autostart binary (in fcitx-bin) shouldn't be
in usr/bin, but more in an exec path like libexec for instance. You told
upstream liked
** Changed in: fcitx (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: fcitx-hangul (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: fcitx-anthy (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: fcitx-m17n (Ubuntu)
Status: Confirmed = Fix
Public bug reported:
When using the option to use the volume above 100%, indicator-sounds interferes
with the percentage reported in notify-osd:
- enable in pulseaudio capplet for allow volume being above 100%
- press volume up or down medium keys
- notice that the progress reported by
Public bug reported:
if setting init=/lib/systemd/systemd-bootchart, this one doesn't
reexecute systemd as expected:
opening output file '/run/log/bootchart-timestamp': No such file or directory
opening output file '/run/log/bootchart-timestamp': No such file or directory
and then, triggers a
ack with 0.2.13-3ubuntu3, please upload something depending on it and
I'll promote the needed parts.
** Changed in: grilo-plugins (Ubuntu)
Status: Incomplete = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
For reference:
16:29:53didrocks | pitti: right, seems it's overlayfs messing with
ConditionPathIsMountPoint
That's also why:
r = path_is_mount_point(etc_machine_id, false);
returns 0, it's considered as a mount point in a overlayfs FS.
--
You received this bug notification because
@Steve: I think I understand what happens.
On package upgrade, if the job is disabled, then, there is an upstart .override
file written to disable it and so, that behavior shouldn't be triggered. I
guess this case happens currently if you disable through ubuntu-control-center
after a new
General comment: why resetting fcitx-hangul, fcitx-m17n, fcitx-
sunpinyin and fcitx-table-extra from incomplete to confirmed? Seems that
no release to fix the blockers have been uploaded, so previous state
remains the same. Please get an upstream release and an upload to ubuntu
to fix the
Thanks for your bug report and help to make ubuntu better. Journal logs
will be helpful to know exactly what happens during your slow boot, do
you mind pasting journalctl -b output here (and eventually boot in
debug mode: add systemd.log_level=debug in grub to boot with it).
Please turn back the
** Changed in: systemd (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1433426
Title:
systemd crashed with SIGSEGV in
@Scott: I'm assigning to Martin so that he can see it once he's back
from holidays.
I don't feel myself confident enough in the network interactions of
systemd to ensure this is the right way to get it fixed.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
Seems the test was may be run in a middle of an archive publication and
further tests did run, right? Not really related to systemd in that
case, feel free to reopen if it's not the case.
** Changed in: systemd (Ubuntu)
Status: New = Invalid
--
You received this bug notification because
Just a note: grilo itself isn't an issue as per see, but we have
multiple examples of those instances I guess throughout the archive
(even kubuntu things).
As Steve told, let's focus on the main issue (actually I see many):
1. what to do in similar case where we have a build-dep/dep for
Override component to main
fcitx-cloudpinyin 0.3.4-2 in vivid: universe/utils - main
fcitx-module-cloudpinyin 0.3.4-2 in vivid amd64: universe/utils/optional/100%
- main
fcitx-module-cloudpinyin 0.3.4-2 in vivid arm64: universe/utils/optional/100%
- main
fcitx-module-cloudpinyin 0.3.4-2 in vivid
As stated on the mailing list few months ago
(https://lists.ubuntu.com/archives/ubuntu-devel-
discuss/2014-December/015154.html), Ubuntu never offered a choice of
init system, and won't start doing that. systemd is mandatory to be the
supported ubuntu path. That's the reason why ubuntu-standard
that's interesting:
$ ls -l /sbin/init
lrwxrwxrwx 1 root root 20 mars 11 11:22 /sbin/init - /lib/systemd/systemd
$ /sbin/init --help
init [OPTIONS...] {COMMAND}
Send control commands to the init daemon.
$ /lib/systemd/systemd --help
systemd [OPTIONS...]
Starts up and maintains the system or
If you are getting the same thing using upstart, I doubt this is a
systemd issue TBH (especially as we didn't get any update recently).
Can you go to a tty and attach hre the journal logs? (journalctl -b output)
also the ouptut of sudo systemctl status -l ddms would helpful.
Thanks!
**
Note that if you are using a virtualization system, you can have be hit
by bug #1433198. Upgrading to xorg-server 2:1.17.1-0ubuntu3 will fix it.
(It fixes some failed autopkgtests as well)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Would be interesting to know why ddms wasn't enabled for you
automatically, if you can provide some details, like did you get other
display-manager installed, that would helpful.
Happy that you have a booting machine again though :)
--
You received this bug notification because you are a
Oh, that's interesting, duplicated line is supported normally AFAIK. That's the
case here, I have as well:
/usr/lib/tmpfiles.d/00rsyslog.conf:d /var/log 0775 root syslog -
/usr/lib/tmpfiles.d/var.conf:d /var/log 0755 - - -
and systemd-tmpfiles-setup didn't fail here.
You have truncated lines in
@Michael: did you try with 219-4ubuntu7? I know that scott did some more
fixes to the network functionalities following his previous patch.
@Scott: mind having a look?
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Scott Moser (smoser)
--
You received this bug notification
Quite agree this is a bug (low priority though). We'll give it a look.
However, it seems you have another bug, you shouldn't get 40s of black
screen and be transitionned quickly to plymouth (as with upstart). Mind
filing another bug report with additional debug information (let's keep
this bug
It seems that they are 2 independent issues that were mixed in this bug
report. As Vasco seems to have something closer to the initial issue,
let's use if for it. i'll try ssdm and poke Eugene if more info were
needed.
--
You received this bug notification because you are a member of Ubuntu
dino99: I guess plymouth wasn't running for you when fsck started,
right?
I conditioned the fact that the messages are sent to plymouth if the pid
file is present (see http://lists.freedesktop.org/archives/systemd-
devel/2015-March/029174.html)
** Changed in: systemd (Ubuntu)
Status: New
Fix proposed at http://lists.freedesktop.org/archives/systemd-
devel/2015-March/029163.html
** Changed in: systemd (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
* qtelepathy-qt5:
debian/rules:
- any change someone spend some time to look at the races in the failing tests
and run them? (at least as adt tests).
- optional, but please consider using dh_install --fail-missing instead of
--list-missing and rm in debian/tmp the file you don't want to
Thanks for looking at this!
Hum, we have 0.32.4 in ubuntu, and you are proposing to sync to 0.32.6.
However, there is no NEWS file with infos, is it a bug fix release? If
so, please state it explicetly here (and turn the status back to new),
otherwise, please request a FFe.
** Changed in: pixman
** Changed in: whoopsie-preferences (Ubuntu)
Assignee: (unassigned) = Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie-preferences in
Ubuntu.
https://bugs.launchpad.net/bugs/1412719
Title
** Description changed:
There is a potential conffiles prompt when upgrading to vivid if
report_metrics has been enabled, as we remove the report_crashes and use
service enablement.
Moving that value to a non conffiles (/ect/whoopsie) and using that in
whoopsie-preferences.
+
+ The
Following up discussion on bug #1394731, Seb subscribed ubuntu-desktop
to the bug report. However, only the libs are going to be maintained by
the Canonical desktop team (and the build-deps needed for nautilus). So
demoting all non libs that are not required by Nautilus.
Supported libraries are
On another note, it will be great that every archive admin members
follow the same procedure when promoting a package to main. The bug is
still opened and not fixed release, I was not even aware then that it's
been promoted already. I don't think I handle that promotion on the 04
of march, which
Fixed, I added as well Michael's upstart job enhancement in this upload
(even if that doesn't fix the real issue, still a nice addition). Didn't
merge into upstream trunk as I don't have access right, but Brian would
merge them back.
** Changed in: upstart
Status: Confirmed = Invalid
**
@Steve: this should be agreed and written that way then. AFAIK, for
things where a canonical team wasn't interesting but an official flavor
was depending on, we agreed that trusted flavor would be in charge (or
report) critical bugs to us.
In that specific case, should we reject the MIR then? The
** Also affects: whoopsie-preferences (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1431432
Title:
conffiles prompt
** Also affects: whoopsie-preferences (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie-preferences in
Ubuntu.
https://bugs.launchpad.net/bugs/1412719
Title:
Thanks for poking upstream about their testsuites, please track it :)
With that and the changes, looks good to me, do not hesitate to poke for
the actual promotion once needed.
** Changed in: media-hub (Ubuntu)
Status: Incomplete = Fix Committed
** Changed in: telepathy-qt5 (Ubuntu)
** Changed in: unity-music-lens
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/969697
Title:
music lens doens't find rhythmbox
** Changed in: systemd (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1429171
Title:
systemd-fsckd[232]: Couldn't
For the record, we got the canonical desktop team subscribed to it as
well.
Accepting extra-cmake-modules, nothing to spot on this trivial package
with a great test suite.
** Changed in: extra-cmake-modules (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification
** Changed in: unity (Ubuntu)
Assignee: Didier Roche (didrocks) = (unassigned)
** Changed in: unity
Assignee: Didier Roche (didrocks) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu
Public bug reported:
There is a potential conffiles prompt when upgrading to vivid if
report_metrics has been enabled, as we remove the report_crashes and use
service enablement.
Moving that value to a non conffiles (/ect/whoopsie) and using that in
whoopsie-preferences.
** Affects: whoopsie
Were you running without rebooting with an older version of systemd than
219-4ubuntu3? This one contains the upstream commit
6487ada88d63e4998113f4c57fa10b7c865f8026, which was supposed to fix
that.
Putting as incomplete as long as you can't reproduce with latest
version.
** Changed in: systemd
** Attachment added: delayed-udev-plymouth-boot
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439301/+attachment/4363165/+files/delayed-udev-plymouth-boot
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
One autopkgtest fails since 219-5ubuntu1. This one checks that plymouth
is started around the same time than fsckd, and that fsckd/fsck doesn't
fail if plymouth crashes.
The issue comes from debian/patches/v219-stable, which is a backport of
it later on with Control+C tests on
plymouth and eventually checking the protocol output.
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Didier Roche (didrocks)
Status: In Progress
** Patch added: 0001-Add-autopkgtests-for-systemd-fsckd.patch
https
-to-force-tmpfs-on-tmp.patch
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Didier Roche (didrocks)
** Changed in: systemd (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
://lists.freedesktop.org/archives/systemd-
devel/2015-March/028966.html
** Changed in: systemd (Ubuntu)
Assignee: Didier Roche (didrocks) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu
IRC context from today:
didrocks | apw: I just tried t_name_to_handle_at.c from man name_to_handle_at
apw | didrocks, it seems to be returning ENOSUPP for me
apw | didrocks, well it failed, as expected
didrocks | apw: so, I guess this is expected that overlayfs doesn't support it
Oh also, did you get a plymouth crash file (in /var/crash), and if so,
report it via apport-bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1435126
Title:
slow boot:
Hey ronwilhoite.
The boot after a long delay only happened once, right? (when your disk
was under fsck). I'm more surprised why plymouth wasn't started for you,
is it started on a normal boot, and not on that special boot?
Can you please (in the case plymouth doesn't show up) to run: systemctl
I wonder if this is really systemd related, we know that unity-settings-
daemon reveal some similar issues (though, most of the time, they are
all lost and even restarting it isn't succifient as it misses some env
variable to leak in the session).
So, let's figure out if it's systemd related
Do you have the same issue when booting up with systemd?
** Tags removed: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1435061
Title:
KDE 5 is corrupted,
Martin, I'm afraid to not be knowledgeable enough in the network changes
you have made. Mind having a look once your are back?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
It seems then that the accelerometer is taking a long time to
initialize, right?
Mind starting a debug boot (systemd.log_level=debug in grub init line)
and pasting the journactl -b output so that we get all related logs?
Thanks!
--
You received this bug notification because you are a member of
Thanks for reporting this patch and help to make ubuntu better.
It's mostly the same people working on implementing systemd in debian
and ubuntu (and we push most of our patches to debian experimental for
non RC bugs, and then sync in ubuntu), so let's continue the discussion
on the debian bug
Hey postadelmaga: the file is in /lib/systemd/system/mysqld.service in
debian and ubuntu. Those services are shipped in the mysql package, so
closing the systemd tag (adding the tag though).
I looked at mysql upstream, and their service files doesn't let the
limit of files to opened up. Do you
Thanks for this bug report.
Do you mind attaching to this bug report the journalctl -b output after
having tried to suspend closing the lid?
Also,
gdbus call --system -d org.freedesktop.login1 -o /org/freedesktop/login1 -m
org.freedesktop.login1.Manager.ListInhibitors output
would help us to
Sure, let's wait for Michael and Martin to comment on this, they are
more up to date on the network side of systemd than I am (Martin will be
back at the end of week FYI). Thanks for your patch!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Also affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: ubuntu-touch-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-meta in
Ubuntu.
https://bugs.launchpad.net/bugs/1422681
Title:
split out
** Also affects: autopkgtest (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-meta in
Ubuntu.
https://bugs.launchpad.net/bugs/1422681
Title:
split out
Please post a new debdiff as we discussed on IRC, thanks! (setting to
incomplete to remove from the list meanwhile)
** Changed in: upstart (Ubuntu)
Status: In Progress = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Confirming that I got the same mount loop issue than Mitchell with the
line #15, (thousands of mounts). The worst is that as the sessions are
not cleaned up on a forced shutdown, the next login after reboot will
restart the schroots, and so the mount hell.
Has to do that either with another admin
This was done a while ago
** Changed in: session-migration (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to session-migration in
Ubuntu.
https://bugs.launchpad.net/bugs/1256062
Done, now xdiagnose only triggers if an installed display manager is
configured as default but couldn't start. This should fix your boot
issue.
We won't fail graphical.target anymore if the only available dm was
uninstalled, however, I do recommend you set then your default target to
** Changed in: upstart (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1435492
Title:
Xsession.d script assumes that
I guess the model for scope should be similar than the ones for apps:
when installed, if the scope tries to reach the network for the first
time, then we get the allow scope_name to acess the network. You set
it to yes and no. Similar behavior if the scope wants to access the GPS
position and so
Public bug reported:
Default project template brings some warnings due to the Ubuntu
components import. This doesn't make the new developers feeling in easy
territory.
import Ubuntu.Components 1.1 (or 1.2) brings numerous:
Errors while reading typeinfo files:
Failed to parse
Public bug reported:
Some annotation tags are missing to bring back the style in qtcreator.
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided
Status: New
** Tags: devexp
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
Some components are still 1.0, other 1.3. It can be hard for the
developer to understand exactly which version to import, what version is
compatible or part of the same framework that the other one.
The goal is to get a common agreements with all components we ship as
part
1 - 100 of 339 matches
Mail list logo
