load.
By checking the 5. point, we are checking we didn't impact gresources.
>From https://github.com/ubuntu/yaru/issues/917.
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Assignee: Didier Roche (didrocks)
Status: In Progress
** Changed in: gnome-shell (Ubu
[ Regression potentiale ]
+ [ Regression potential ]
If this code change triggers any error, the OSD isn't displayed, but the
Shell stays up.
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: gnome-shell (Ubuntu)
Status: New => In
Upstream MP: https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/266
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798612
Title:
OSD shows volume level = 100% even if volume > 100% on first
Public bug reported:
[ Rationale ]
Display bug in volume OSD on volume keypress if volume > 100% (amplified)
[ Test case ]
1. Ensure OSD is not displayed on screen avec volume > 100% via the amplified
setting.
2. Press volume + or volume - on your keyboard.
-> OSD is shown, but volume level is
** Description changed:
1. Proceed an OEM installation, select English
2. Then, proceed to step 2 (mark for validation)
3. After reboot, on user creation, select a different language like French.
-> Once the user is created and logged in, his session is still in English.
Same for login
** Description changed:
1. Proceed an OEM installation, select English
2. Then, proceed to step 2 (mark for validation)
3. After reboot, on user creation, select a different language like French.
-> Once the user is created and logged in, his session is still in English.
Same for login
** Summary changed:
- german
+ OEM setup: user language selection not taken into account
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798554
Title:
OEM setup: user language selection not taken
Public bug reported:
1. Proceed an OEM installation, select English
2. Then, proceed to step 2 (mark for validation)
3. After reboot, on user creation, select a different language like French.
-> Once the user is created and logged in, his session is still in English.
Same for login screen.
**
@Till-kamppeter: yes, but not now. Ideally, could you file ITP's to
Debian, mentioning that those should be maintained under the Debian
Printing Team umbrella. The best would be if you maintained the packages
in Debian yourself, which I could just mentor (upload for you).
--
You received this
Fixed in https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-
shell/commit/?id=ddc4f511abd64d69c1150a41475d0a1ebac01dbb
** Description changed:
- Dark purple (noise) background flashes up briefly (for a split second)
- during the login animation.
+ [Impact]
- The login screen and
Fixed in gnome-shell as this is a separate parameter. Nice catch!
** Package changed: yaru-theme (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: gnome-shell (Ubuntu)
Status: New => Triaged
Public bug reported:
1. Boot live CD, don't press any key
2. In maybe-ubiquity, choose a language != English
-> SGNOME Shell menus are still is English "Wired connection" for instance, or
the date in the panel. Same when configuring WIFI network.
3. Even clicking on the next step ("Install
When you are telling that you select French, or English, and so, all
dialects should be installed for them, why do we have that separation in
different packages though? Shouldn't we only have one "English",
"French", … package?
I don't understand the difference between:
$ locale -a | grep ^fr
Confirm what Iain is seeing, in maybe-ubiquity mode with kvm, if you
select then the live session.
More info:
* if you enable accessibility in maybe-ubiquity and right away:
- try to select options (languages) in maybe-ubiquity, nothing is read by orca
- switch right away to Try ubuntu, the
I think we should answer some questions first in term of fundamentals.
1.
For instance, if I install fr_FR, I don't expect to have fr_CA installed (and
it's not the case here), nor fr.
Why would that be different for English? I thinks en_US should only install
en_US + the common (shared)
** Description changed:
- Impact
- ==
+ [Impact]
New release in the stable 3.28 series.
https://gitlab.gnome.org/GNOME/evince/commits/gnome-3-28
https://gitlab.gnome.org/GNOME/evince/blob/gnome-3-28/NEWS
- Other Info
- ==
- I am not working on this update now.
+ [Test
Public bug reported:
Multiple issues arise when installing any languages in ubuntu:
1. if you select en_GB, en_US is selected instead
2. if you select fr_FR, fr_FR + en_US is selected
3. As soon as en_US is selected (which is always right now), en is then
selected, which in turns requests
Assigning it to gdm, even if the loop is in mutter, as we are going to
workaround it there.
** Package changed: mutter (Ubuntu) => gdm (Ubuntu)
** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
didrocks | yes ;) I wonder what would happen if, while this is worked on, we
remove the udev rule to not regress some of our nvidia users for 18.10 release
next week (as
| a workaround)
Public bug reported:
This happens on some nvidia card, with the nvidia blob driver
(fallbacked to Xorg for gdm).
1. Boot your laptop
2. Log into gdm
-> once your user session is loaded, gdm GNOME Shell process goes crazy, up to
100%, continously.
GNOME Shell (for user gdm) restarts in loops
Public bug reported:
Preliminary note: I can't reproduce it anymore since 11th October 2018.
Was hitting it in my VM 100% beforehand though. The VM was set at 1Gb
(default Boxes value at the time), so maybe hitting OOM killing too
hard. I can't dist-upgrade anymore with 1Gb of memory (VM hangs)
** Patch added: "call_shell_refresh_quirk.diff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1797353/+attachment/5199937/+files/call_shell_refresh_quirk.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Package changed: ubiquity (Ubuntu) => osinfo-db (Ubuntu)
** Description changed:
+ After investigation, the issue is that we only get 1Gb allocated in GNOME
Boxes for new ubuntu installations, which is starving and getting OOM.
+ The requirements has been bumped with pre-seeded snaps in
Ah, interesting. I just checked cosmic GNOME Boxes configuration for an
ubuntu iso, and indeed, it configures 1GB of RAM. I think it used to
configure more? Maybe something we should change in GNOME Boxes upstream
so that people testing ubuntu aren't imapcted by it?
I don't know how Iain saw
Public bug reported:
Following "Install (entire disk) in Ubuntu Desktop amd64 in Cosmic
Daily" test case, on 20181003.1 desktop live image.
Using Qemu (host is an up to date cosmic) and starting in ubiquity-only mode:
- when clicking on continue on the <…> step, the UI is freezing for a minute,
Public bug reported:
With hplip version (3.17.10) of ubuntu 18.04, i got a "filter failed"
issue with cups and cannot print correctly. After installing another
version of hplip (3.18.9) , ghostscript is broken (cannot find color
profile), thus still no printing. All was well working with ubuntu
Public bug reported:
We want to ship in cosmic +1 gsconnect extension by default in ubuntu.
However, upstream did a big rewrite this cycle. We shipped a WIP snapshot in
July with their content.
Upstream has now merged their rewrite in master and are close to cut a
candidate release. As we want
* "upstream split the source in four, old src:vulkan is going away and
src:vulkan-loader will be the one to be promoted once it's accepted from NEW."
-> it seems as of now (like 9 months later), the source is still named vulkan,
but I see vulkan-loader in NEW. The content of the package is
** Package changed: ubuntu-meta (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795410
Title:
cannot bring up window menu via keybinding (alt-space or otherwise)
To
Thanks Gunnar! FYI, this particular change won't be included anyway.
Still keep it opened for the rest of the description
** Summary changed:
- UIF exception: GtkPopover, GtkMenu and GtkSwitch styling
+ UIF exception: GtkSwitch styling
** Description changed:
+ We would like to include a fix
** Also affects: ubuntu-docs
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/1794942
Title:
UIF exception: GtkPopover, GtkMenu and GtkSwitch styling
To
** Description changed:
We decided to not show up gnome-initial-setup after upgrade during first
relogin. Consequently, we need to report automatically submission on
upgrade to ensure our current hw submission and upgrade information per
distro matches our user base.
Note that the
Public bug reported:
We decided to not show up gnome-initial-setup after upgrade during first
relogin. Consequently, we need to report automatically submission on
upgrade to ensure our current hw submission and upgrade information per
distro matches our user base.
Note that the
*** This bug is a duplicate of bug 1743216 ***
https://bugs.launchpad.net/bugs/1743216
** This bug has been marked a duplicate of bug 1743216
perl crashed with SIGABRT in _dbus_abort()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: websockify (Ubuntu)
Status: New => Incomplete
** Changed in: spice-html5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1108935
Title:
** Changed in: vulkan (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742711
Title:
MIR: vulkan(-loader)
To manage notificati
I've generated a report with a version pre 7.3, then, upgrade apport and
report it with 7.4 and I didn't trigger any crash.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you
As we discussed, I'm working on the immediate issue: moving to a separate
binary package.
This is done on
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1794024
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In Bionic, we ship a communitheme snap, which shows up an additional gdm
entry named "ubuntu communitheme".
We want those users on Bionic -> Cosmic upgrade (and later, bionic LTS
-> f LTS) to fallback to the ubuntu session to not pick the theme in the
snap.
However, we
** Package changed: gnome-shell (Ubuntu) => pkgbinarymangler (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793476
Title:
Missing French translations for some strings
To manage
nts.
** Changed in: tracker-miners (Ubuntu)
Assignee: Didier Roche (didrocks) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770877
Title:
[MIR] tracker-
Looks mostly good. The debian packaging is fine, use dh_missing --fail-
missing to ensure we ship everything we want. It has autopkgtests doing
unit testing under X. The only missing thing is the trailing commas on
deps! :p
Some questions:
* Any chance we can get a .symbol instead of a shlibs
Are you sure this is due to the above patch, can you try without it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691678
Title:
Scrollbars escape the bottom and right side of the Terminal window
Ok, so the current fix in UNAPPROVED will prevent that at least ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791324
Title:
/usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-
I'm closing this, as Frederik told, there are multiple ways of achieving
that, and not that no other way is supported upstream, in GNOME Shell.
If you want another way, please open the issue on the GNOME Shell
upstream gitlab issue tracker.
You would note that you can do it:
- via the user-themes
I installed it on bionic and confirmed that on a default configuration,
the new settings is taken.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification
** Changed in: evince (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790609
Title:
Update evince to 3.28.3
To man
e Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: apport (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: ubuntu-meta (Ubuntu)
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/1783571
Title:
Set Yaru as default
To manage notifications about this
Thanks a lot! I was just looking at the same issue and got directed to
the bug. The diff is good, I've just sponsored it to cosmic.
Thanks again ;)
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of
As discussed on IRC, I have provided a local build and ran GNOME Shell
with it for a whole day. I have also changed the network status and
didn't notice any regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Portuguese, Croatian, Czech, Danish, Dutch, Esperanto,
French, German, Icelandic, Indonesian, Italian, Latvian, Lithuanian,
Polish, Russian, Serbian and Spanish translations.
** Affects: network-manager-applet (Ubuntu)
Importance: Undecided
Assignee: Didier Roche (didrocks)
S
** Changed in: gnome-session (Ubuntu)
Assignee: Marco Trevisan (Treviño) (3v1n0) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790532
Title:
ubuntu-settings-migr
I don't think this is really an issue, I tried to ensure they all have
the same prefix so that they are easily searchable for people, which was
my main concern here. "name-theme". I'm setting it to "Won't fix" right
now, but feel free if you want to get it to debian and this is a
blocker.
Not
Let's triage it for next cycle.
** Changed in: yaru-theme (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787629
Title:
Split out yaru-theme-gtk2
To manage
** Description changed:
- Currently the guided methods of the Ubuntu installer only address single
- disk setup. When a user have several disks on his machine he has to use
- the manual partitioning which is prone to failure for inexperienced
- users.
+ [Impact]
+ * Currently the guided methods
** Description changed:
+ [Impact]
+ * OEM images provided by Canonical and other companies use a tracking id
called Distribution Channel Descriptor (DCD). There is interest of reporting
this as part of ubuntu-report one.
+
+ [Test Case]
+ * Install the new version from -proposed
+ * run
** Also affects: ubuntu-report (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: ubuntu-report (Ubuntu Bionic)
Status: New => Triaged
** Changed in: ubuntu-report (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received th
** Also affects: ubuntu-report (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: ubuntu-report (Ubuntu Bionic)
Status: New => Triaged
** Changed in: ubuntu-report (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: ubuntu-
** Changed in: ubuntu-report (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786432
Title:
Collect DCD file
To manage notifications about this bug go to:
Sorry for being unclear, the "no need to SRU that" was intended for the
optional ubiquity removal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786432
Title:
Collect DCD file
To manage
I just have one question: do we keep the OEM field in ubiquity (the
boolean true/false?). I think once we get DCD, this is of less value.
No need to SRU that, but maybe for bionic, WDYT?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
failed : Ubuntu doesn't create UEFI and Grub partitions again ?
Thanks. Didier
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29
Will be part of the next package upload:
https://github.com/ubuntu/yaru/commit/ab30ddcb4cbac9046952ebc3031b4bc622d677c7
** Changed in: yaru-theme (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
on b-d-i, you mean only adding sassc, as the 2 others are needed in the
clean target. Does it really achieve anything?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783600
Title:
[MIR] yaru-theme
Bumping standards version/adding b-d-i in upstream (will be in the next
upload, I don't think the MIR will block on that, correct?)
For the gtk2 support, we need it especially for Qt applications. We
discussed that in our team meeting and ubuntu-desktop channel and it
doesn't seem that we'll
I didn't spot anything blocking. Simple code acting on /sys element.
However, not very useful since limited to nouveau and not nvidia binary
driver. Note that I couldn't test it myself.
** Changed in: switcheroo-control (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this
** Changed in: ubuntu-report (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-report (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sounds like a transient archive issue or something unrelated to the
ubuntu-report package itself which downloads properly right now.
Marking as incomplete, feel free to reopen or report again if that issue
persistent for you when downloading/updating from a new version.
** Changed in:
As a reminder, ubuntu-settings is failing due to a meson issue:
https://github.com/mesonbuild/meson/issues/3914.
The stack has been tested locally and everything works well, including
transition with removal of older alternatives and fallback to plan Shell
for GDM without the theme installed.
**
Instead of:
there are no keys for the files whose name begins with "Announce"
please read:
there are no keys for the fields whose name begins with "Announce"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In the file org.gnome.orca.gschema.xml shipped in the orca package for
bionic (amd64) there are no keys for the files whose name begins with
"Announce" in the Say All group of fields of the General Tab of the
Screen Reader Preferences GUI of Orca.
As a consequence, the user
yaru MIR is https://bugs.launchpad.net/ubuntu/+source/yaru-
theme/+bug/1783600
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Availability]
In Cosmic, universe, all archs.
[Rationale]
This is our new default theme for ubuntu desktop.
[Security]
No issue reported, very new package. It doesn't contain code, only
assets (images, sounds, css compiled from sass). The source has some
upstream/
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
Note: Need as well Yaru 18.10.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783571
Title:
Set Yaru as default
To manage notifications about this bug go to:
Public bug reported:
Set Yaru as default ubuntu 18.10 theme.
** Affects: ubuntu-settings (Ubuntu)
Importance: Undecided
Status: New
** Merge proposal linked:
https://code.launchpad.net/~didrocks/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/350879
--
You
Are you sure that your configuration was still set to manual and not
"never"? (there is a timeout bug in whoopsie-preferences which reset the
condition to "never" if g-c-c is kept opened).
I just tried with the -proposed version, generated a crash which can be
reported (note as well that some
Interesting, I was sure we upstreamed completely systemd-fsckd. Anyway,
+1 for me, let me assign to xnox who is doing most of systemd uploads
nowdays so that he attaches it to next upload.
Many thanks!
** Changed in: systemd (Ubuntu)
Assignee: Didier Roche (didrocks) => Dimitri John Led
There is no schedule schema changes as of now, so current replaces: is
still good and we'll see later on if we fork the schema or not. Sounds
good for the current states at least.
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Triaged => Fix Released
--
You received
** Changed in: qtcreator-plugin-ubuntu (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1461590
Title:
schroot and click-chroot-ag
Thanks for submitting this patch and sorry for the time to review it!
The patch looks good to me, I would love though to get that directly
upstream rather than us carrying a distro-patch for a small issue like
this, do you mind doing a PR there? https://github.com/systemd/systemd/
** Changed in:
** Changed in: ubuntu-settings (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: ubuntu-settings (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: ubuntu-settings (Ubuntu)
Importance: Undecided => Medium
** Changed i
** Also affects: ubuntu-settings (Ubuntu Bionic)
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/1782190
Title:
Set default interface font size to 11 for
Thanks! I indeed didn't try the server side, I don't see how this is a
new issue though compared to apport-noui.service? The same service files
start/restart/stop rules are just moved to apport package via apport-
autoreport.service. So, if there is a race on install until the next
reboot, the
.*) directly.
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: apport (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: apport (Ubuntu)
Importance: Undecided => High
** Changed in: apport (Ubun
** Description changed:
[ Impact ]
A lot of users are bother by the number of whoopsie dialog. We introduced on
"G-C-C privacy option don't allow sending manual report" bug
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a
way for users to change from always
Nope. The bug is present in Debian for long:
https://bugs.debian.org/838831
** Bug watch added: Debian Bug tracker #838831
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838831
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The autopkgtests are sometimes passing, sometimes stuck for more than 2h:
http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64.
It's blocking randomly on different tests.
All tests that are stucked, implements closing a request via a timeout
(and then, executing
You will have to reimplement something similar to what Unity switcher
did I think. The implementation is different, so it needs to be a proper
implementation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FTR, discussed with Brian, my proposed solution sounds to make sense, keeping
an unseeded apport-noui:
- have the systemd units (path and service) moved to apport binary package
- let apport-noui only touching/remove in maintainerscript script the
autoreport file (this is the same file created
** Description changed:
[ Impact ]
- * The current label "Manual" is in fact shutting down whoopsie completely
and not providing any graĥical way to set manual reports (which is our default
on 18.04)
- * We want to SRU gnome-initial-setup for 18.04.1 so that sending reports is
linked to
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: update-notifier (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: update-notifier (Ubuntu)
Importance: Undecided => High
** Changed in: update-notifier (Ubuntu Bionic)
Importance
@Brian: I just had a deeper look after an initial tests, and brought
jibel along.
Indeed, there are quite some flaws on those options which never worked
(but was shipped since 12.04). On top of that, I found another
regression that happened probably during the upstart -> systemd
transition.
** Description changed:
The goal for autoreporting via whoopsie is to have a silent mode where
whoopsie automatically reports crashes. However, this one requires apport-noui
to be installed, which we don't by default.
apport-noui is just a set of systemd unit starting whoopsie-upload-all
Public bug reported:
This is a regression since we moved from upstart to a systemd service.
apport-gtk UI is always started, even in autoreport mode.
The file condition path for autoreport isn't in the systemd unit.
This is also the case when never reporting is enabled.
** Affects:
Public bug reported:
The goal for autoreporting via whoopsie is to have a silent mode where whoopsie
automatically reports crashes. However, this one requires apport-noui to be
installed, which we don't by default.
apport-noui is just a set of systemd unit starting whoopsie-upload-all (part of
If there is a need for a 3rd party package for it, it means that
whoopsie-preferences is broken for quite some years: the automatic
option was present in g-c-c for years in ubuntu, and just use whoopsie-
preferences API to turn this automatic send mode. Note that the API
doesn't report any error
** Description changed:
[ Impact ]
A lot of users are bother by the number of whoopsie dialog. We introduced on
"G-C-C privacy option don't allow sending manual report" bug
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a
way for users to change from always
** Branch linked: lp:~didrocks/apport/whoopsie-auto-ui
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778497
Title:
Add a remember option to whoopsie so that users can diminish crash
interactions
601 - 700 of 16202 matches
Mail list logo
