** Description changed:
Having a ContentStore for a particular scope doesn't enable to import
more than once a file name.
If you use:
ContentStore {
id: appStore
scope: ContentScope.App
}
and then:
peer.request(appStore)
- the state transfer changed go
FYI, I have workarounded it this way:
https://github.com/didrocks/splitthebill/commit/12d380b95a4bf2a1dc58226c814da551dfb2af13
feel free to comment for any better approach.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
The idea would to have at least a fake APP_ID for developping and
testing/iterating on desktop. The import functionality itself works, but
the crash doesn't give a good developer experience.
Maybe we can decide on having an APP_ID=fake in the developer default
template, and
** Description changed:
I just added with Ubuntu Content 1.1 a simple example, here is the
commit:
https://github.com/didrocks/splitthebill/commit/bc914de9511ebbd3b13b03166bdc7c463af1c609
Switching that one, I'm starting to get a lot of warnings in my
application related to
** Tags added: devexp
** Also affects: content-hub (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1433708
Title:
Public bug reported:
The first example of the default index upstream's Content Hub API doesn't work
with current content hub:
https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Content.index/
It needs to be updated as it's the first window on contenthub for most
of our users.
**
** Summary changed:
- Content-Hub crash with an invalid app-id
+ Content-Hub crash with an invalid app-id after transfer and doesn't clean up
temp files
** Description changed:
The idea would to have at least a fake APP_ID for developping and
testing/iterating on desktop. The import
** Description changed:
Having a ContentStore for a particular scope doesn't enable to import
more than once a file name.
If you use:
ContentStore {
- id: appStore
- scope: ContentScope.App
+ id: appStore
+ scope: ContentScope.App
}
and then:
Public bug reported:
With ContentHub 1.1:
I can see cases when you want to attach docs to some database. Those
docs could be pictures or documents. It would be nice to import them
altogether just using one Content picker (for multi-selection)
** Affects: content-hub (Ubuntu)
Importance:
Public bug reported:
Having a ContentStore for a particular scope doesn't enable to import
more than once a file name.
If you use:
ContentStore {
id: appStore
scope: ContentScope.App
}
and then:
peer.request(appStore)
- the state transfer changed go to initiated, in progress
Public bug reported:
If you push a document that contains property being a list of strings,
like:
{
'attachements': [/path/to/foo1.png, /path/to/foo2.png]
}
Retrieving it is making the attachements a ListModel through the QML
type system (outside of u1db's scope thus). The ListModel contains
Public bug reported:
Importing Ubuntu.Components 1.2 in wily (not sure why I didn't noticed
it on vivid), triggers a lot of style related warnings, like:
file:///home/didrocks/work/ubuntu-
sdk/splitthebill/splitthebill/components/AddRemoveInt.qml:39:5: QML
TextField: Theme.createStyleComponent()
Public bug reported:
Just import in qtcreator the Content Hub API, the import line triggers warning:
import Ubuntu.Content 1.1
QML module does not contain information about components contained in
plugins.
Even if only cosmetic as help is accessible, this doesn't give the
developer confidence
** Summary changed:
- ctrl-alt-t doesn't open the terminal on a fresh 15.10 install
+ Media keys (ctrl-alt-t, brightness, play/pause) don't work randomly after
logging
** Description changed:
- I've installed 15.10 and I can't open a terminal using ctrl-alt-t.
+ I've installed 15.10 and I
Public bug reported:
From http://doc.qt.io/qt-5/qml-qtqml-date.html, The QML Date object
extends the JS Date object with locale aware functions..
Some of them indeed works, like getMonth(), getDate(), returning
expected value.
However, when change a date property on a object with setMonth() and
** Description changed:
When putting and getting a QML date in the u1db database, the resulting
strings are stored differently, even if you don't do any type
conversion.
The result is that the resulting date is shifted by the current
timezone, rendering an incorrect date.
Small
** Description changed:
When putting and getting a QML date in the u1db database, the resulting
strings are stored differently, even if you don't do any type
conversion.
The result is that the resulting date is shifted by the current
timezone, rendering an incorrect date.
Small
launchpad seems to continue to report bug twice when clicking on submit,
invalidating.
** Changed in: u1db-qt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to u1db-qt in Ubuntu.
current workaround is to cheat on the saved date in database, meaning,
removing again the timezone to the date object to shift it to UTC (it
will print as time in UTC + (timezone) which is untrue, so only do
that for the database object)
Example, just before putDoc:
tosave[date] = new
** Summary changed:
- [DatePicker] 2 warnings in tst_focus.qml
+ [DatePicker] pathItemCount binding loop when using DatePicker
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
Public bug reported:
When putting and getting a QML date in the u1db database, the resulting
strings are stored differently, even if you don't do any type
conversion.
The result is that the resulting date is shifted by the current
timezone, rendering an incorrect date.
Small example:
date is
Public bug reported:
When putting and getting a QML date in the u1db database, the resulting
strings are stored differently, even if you don't do any type
conversion.
The result is that the resulting date is shifted by the current
timezone, rendering an incorrect date.
Small example:
date is
** Tags added: devexp
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1419667
Title:
[DatePicker] 2 warnings in tst_focus.qml
Status in ubuntu-ui-toolkit
Public bug reported:
with Ubuntu Components 1.2, instantiating a MainView should adjust on start
contentY of the flickable component to header.height.
In the following example, this isn't recalculated properly before an user's
drag.
import QtQuick 2.4
import Ubuntu.Components 1.2
MainView {
Public bug reported:
The animation in the OptionSelector component is very jumpy, even on a
beefy desktop (with Ubuntu Component 1.2).
import QtQuick 2.4
import Ubuntu.Components 1.2
MainView {
id: mainview
objectName: mainView
applicationName: foo.bar
width: units.gu(40)
Public bug reported:
If a flickable only contains OptionSelector(s), the childrenRect isn't
refreshed, and so, the options when expanding aren't shown.
For instance:
import QtQuick 2.4
import Ubuntu.Components 1.2
MainView {
id: mainview
objectName: mainView
applicationName: foo.bar
seems my chrome submitted it twice, setting this one as invalid
** Tags removed: devexp
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
The animation in the OptionSelector component is very jumpy, even on a
beefy desktop (with Ubuntu Component 1.2).
import QtQuick 2.4
import Ubuntu.Components 1.2
MainView {
id: mainview
objectName: mainView
applicationName: foo.bar
width: units.gu(40)
grrr, same, it seems that chrome is submitting it twice…
** Tags removed: devexp
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Hey Tim, Zoltan.
I don't think that what was requested was section label at start, as it
seems to me only the last seen label is stick at start. I guess the
request (at least, the one we can find on other platforms) is this one:
** No longer affects: unity
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1456610
Title:
[media-framework] Expected to be able to select picture in a full
screen
Public bug reported:
If you add an iconName to a button without a set width anchored to one
side only, the sizing isn't correct.
Please find attached 2 screenshots demonstrating this issue: there are 2
buttons, one anchored to the left, the other anchored to the right.
If you set the iconName
** Attachment added: withicons.png
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1478839/+attachment/4435006/+files/withicons.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
As discussed yesterday, agreed that a comment to the docs +
recommendation would make sense (especially as listDocs() would be used
for debugging purpose)
** Tags added: devexp
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags added: devexp
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to u1db-qt in Ubuntu.
https://bugs.launchpad.net/bugs/1271973
Title:
Results from U1db.Query contain only indexed fields, not the whole
document
Status
Seems to me to still be the case with 0.1.5+15.04.20150327-0ubuntu1
using deleteDoc(docId).
The content is indeed vanished, but using db.listDocs() or using the db
as a model returns all docs, including the one I deleted (with empty
content, but still listed)
--
You received this bug
This also happens when you use db.listDocs() API, which is kind of
confusing.
** Also affects: u1db-qt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to u1db-qt in Ubuntu.
** Changed in: openjpeg (Ubuntu)
Assignee: (unassigned) = Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openjpeg in Ubuntu.
https://bugs.launchpad.net/bugs/711061
Title:
[MIR]
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
Public bug reported:
After installing ubuntu-sdk, only ubuntu components have offline doc
support on F1, there is none for QML upstream components.
We should cleanup the dependency to drop the now (soon) unused -doc-html
flavor in favor of the qthelp ones. That way, F1 will bring the full
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
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
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
** 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
** 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
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
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
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
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
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
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
** 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
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
** 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
** 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
** 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)
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
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
://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
-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
201 - 300 of 339 matches
Mail list logo
