[Desktop-packages] [Bug 2063383] [NEW] [SRU] Ubuntu Unity takes 90 seconds to log out

2024-04-24 Thread Simon Quigley
Public bug reported:

[ Impact ]

Ubuntu Unity reliably takes 90 seconds to log out. This is due to the
user-level gnome-session.service systemd unit not properly terminating
gnome-session on logout. An attempt is made to send SIGTERM to the
process, which gnome-session does not care about.

Instead, gnome-session-quit should be invoked when the systemd unit
shuts down, which acts effectively and immediately.

[ Test Plan ]

Actual behavior:
 1. Log in to a Unity session on Ubuntu Unity 24.04.
 2. Log out of Ubuntu Unity.
 3. Observe that only the wallpaper is shown for 90 seconds prior to the login 
manager showing again.

Expected behavior:
 1. Log in to a Unity session on Ubuntu Unity 24.04.
 2. Log out of Ubuntu Unity.
 3. Observe that logging out takes a few seconds at most, and you are able to 
log back in as the same user, or a different one.

[ Where problems could occur ]

If the gnome-session or gnome-session-quit binaries change the arguments
they accept by default, log in and log out functionality on Unity
sessions are likely to break.

Additionally, if lightdm or systemd changes in a non-reverse-compatible
way, this increases the chance of a user-facing regression.

** Affects: gnome-session (Ubuntu)
 Importance: High
 Assignee: Simon Quigley (tsimonq2)
 Status: Confirmed

** Affects: gnome-session (Ubuntu Noble)
 Importance: High
 Assignee: Simon Quigley (tsimonq2)
 Status: Confirmed

** Summary changed:

- Ubuntu Unity takes 90 seconds to log out
+ [SRU] Ubuntu Unity takes 90 seconds to log out

** Changed in: gnome-session (Ubuntu)
   Status: New => Confirmed

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-session (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Also affects: gnome-session (Ubuntu Noble)
   Importance: High
 Assignee: Simon Quigley (tsimonq2)
   Status: Confirmed

** Changed in: gnome-session (Ubuntu Noble)
Milestone: None => noble-updates

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2063383

Title:
  [SRU] Ubuntu Unity takes 90 seconds to log out

Status in gnome-session package in Ubuntu:
  Confirmed
Status in gnome-session source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  Ubuntu Unity reliably takes 90 seconds to log out. This is due to the
  user-level gnome-session.service systemd unit not properly terminating
  gnome-session on logout. An attempt is made to send SIGTERM to the
  process, which gnome-session does not care about.

  Instead, gnome-session-quit should be invoked when the systemd unit
  shuts down, which acts effectively and immediately.

  [ Test Plan ]

  Actual behavior:
   1. Log in to a Unity session on Ubuntu Unity 24.04.
   2. Log out of Ubuntu Unity.
   3. Observe that only the wallpaper is shown for 90 seconds prior to the 
login manager showing again.

  Expected behavior:
   1. Log in to a Unity session on Ubuntu Unity 24.04.
   2. Log out of Ubuntu Unity.
   3. Observe that logging out takes a few seconds at most, and you are able to 
log back in as the same user, or a different one.

  [ Where problems could occur ]

  If the gnome-session or gnome-session-quit binaries change the
  arguments they accept by default, log in and log out functionality on
  Unity sessions are likely to break.

  Additionally, if lightdm or systemd changes in a non-reverse-
  compatible way, this increases the chance of a user-facing regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822

2024-04-23 Thread Simon Quigley
** Description changed:

+ [ Impact ]
+ 
+ Ubuntu 24.04 now uses deb822 to represent software sources for deb
+ packages, instead of /etc/apt/sources.list. The complete rationale for
+ this change can be found here: https://discourse.ubuntu.com/t/spec-apt-
+ deb822-sources-by-default/29333
+ 
+ software-properties has two graphical frontends for editing these
+ software sources, one is GTK-based and the other is Qt-based. When the
+ underlying change to deb822 sources was made, the GTK-based frontend and
+ the DBus backend interface gained support.
+ 
+ The original bug report shown below informed us of the lack of deb822
+ support in the Qt frontend, which results in a broken, non-functional
+ interface when attempting to view or edit most values on the first two
+ tabs. The fix for this is to implement a Qt dialog for deb822 sources
+ that somewhat matches the existing GTK interface.
+ 
+ [ Test Plan ]
+ 
+ Install software-properties-qt 0.99.48 or earlier.
+ 
+ Reproducing the bug:
+  1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
+  2. Observe that all four checkboxes on the Ubuntu Software tab (main, 
universe, restricted, and multiverse) are unchecked.
+  3. Move to the Other Software tab and observe that there are no items in the 
list.
+ 
+ Upgrade to software-properties-qt 0.99.49.
+ 
+ Intended functionality:
+  1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
+  2. Observe that one or more checkboxes on the Ubuntu Software tab 
(representing main, universe, restricted, or multiverse) are checked. Toggle 
one or more of the checkboxes.
+  3. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.
+  4. Switch to the Other Software tab, there should be one item in the list.
+  5. Select that item, then click Edit at the bottom of the dialog. Make a 
modification to every field on the screen, or a combination of fields you would 
like to test. All fields should work.
+  6. Click the OK button at the bottom of the dialog to confirm the changes, 
then click Edit for that item again. The changes you made should be reflected 
(meaning, the changes were saved.)
+  7. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.
+ 
+ [ Where problems could occur ]
+ 
+ This is well-tested code. That being said, the following small edge cases 
exist:
+  - If you create a very large amount of rows, it infinitely expands the 
dialog without a scroll wheel. This is the same functionality as the GTK 
frontend.
+  - Error validation is not performed on the deb822 lines, they are simply 
written to the ubuntu.sources file. This is good as a starting point, but also 
relies on the appropriate update notifier handling these errors. This is the 
same functionality as the GTK frontend.
+ 
+ In a future update, this functionality could be broken by one or more of the 
following underlying changes:
+  - Changes to the software-properties backend which are only implemented for 
the GTK frontend.
+  - Changes to the location or formatting of the ubuntu.sources file.
+  - Regressions in the Python bindings for Qt 5, which are rare but possible.
+  - Regressions in Python itself.
+ 
+ [ Other Info ]
+  
+ Ubuntu Studio's live ISO and installed system are affected by this. Only 
Lubuntu's installed system is affected by this.
+ 
+ [ Original Report ]
+ 
  Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software
  sources" not correctly updated after upgrade. Prompt= shows normal and
  not LTS
  
  Used command sudo do-release-upgrade -d
  
  Otherwise the upgrade is good
  
  see attached screenshot
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.46
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Sat Apr 13 11:44:28 2024
  InstallationDate: Installed on 2024-04-13 (0 days ago)
  InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240331)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00

** Also affects: software-properties (Ubuntu Noble)
   Importance: Critical
 Assignee: Simon Quigley (tsimonq2)
   Status: Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/2061214

Title:
  [SRU] Software Sources is not compatible with deb822

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Nob

[Desktop-packages] [Bug 2063109] [NEW] Splash screen not rendering correctly on several flavors

2024-04-22 Thread Simon Quigley
Public bug reported:

On several flavors (I have confirmed Ubuntu Unity and Lubuntu thus far),
if the machine does not have much resources, it falls back to the text-
based Plymouth boot screen.

Steps to reproduce:
 - Find a machine with 1 core and 2 GB of RAM, a virtual machine will do.
 - Boot up a live ISO of Lubuntu or Ubuntu Unity.

Expected result: the appropriate graphical splash screen is shown.
Actual result: Only the text-based splash screen for Plymouth is shown.

** Affects: plymouth (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/2063109

Title:
  Splash screen not rendering correctly on several flavors

Status in plymouth package in Ubuntu:
  New

Bug description:
  On several flavors (I have confirmed Ubuntu Unity and Lubuntu thus
  far), if the machine does not have much resources, it falls back to
  the text-based Plymouth boot screen.

  Steps to reproduce:
   - Find a machine with 1 core and 2 GB of RAM, a virtual machine will do.
   - Boot up a live ISO of Lubuntu or Ubuntu Unity.

  Expected result: the appropriate graphical splash screen is shown.
  Actual result: Only the text-based splash screen for Plymouth is shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2063109/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2054879] [NEW] Syntax warnings after upgrade to Python 3.12

2024-02-24 Thread Simon Quigley
Public bug reported:

Today during regular system updates, I was presented with this
information:

Setting up python3 (3.12.1-0ubuntu1) ...
running python rtupdate hooks for python3.12...
/usr/share/hplip/base/LedmWifi.py:34: SyntaxWarning: invalid escape sequence 
'\d'
  http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/device.py:49: SyntaxWarning: invalid escape sequence '\d'
  http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/g.py:304: SyntaxWarning: invalid escape sequence '\|'
  spinner = "\|/-\|/-"
/usr/share/hplip/base/g.py:354: SyntaxWarning: invalid escape sequence '\d'
  m = re.search('python(\d(\.\d){0,2})', ext_path)#get the python 
version where the .so file is found
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape sequence 
'\#'
  re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape sequence 
'\/'
  re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape sequence 
'\*'
  re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/base/logger.py:439: SyntaxWarning: invalid escape sequence '\<'
  elem_start = re.findall("(\<\W{0,1}\w+) ?", line)[0]
/usr/share/hplip/base/logger.py:440: SyntaxWarning: invalid escape sequence '\]'
  elem_finished = re.findall("([?|\]\]]*\>)", line)[0]
/usr/share/hplip/base/logger.py:442: SyntaxWarning: invalid escape sequence '\S'
  attrs = re.findall("(\S*?\=\".*?\")", line)
/usr/share/hplip/base/models.py:37: SyntaxWarning: invalid escape sequence '\d'
  pat_prod_num = re.compile("""(\d+)""", re.I)
/usr/share/hplip/base/models.py:428: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^r(\d+)-agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:429: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^r(\d+)-agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:430: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^r(\d+)-agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:431: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:432: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-virgin', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:433: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-dvc', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:434: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:435: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:436: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-id', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:437: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-hp-ink', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:438: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-health-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:439: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-health$', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:440: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-known', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:441: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-level', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:442: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-ack', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:443: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:444: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^in-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:445: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^out-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:446: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^model(\d+)', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/password.py:212: SyntaxWarning: invalid escape sequence 
'\['
  cb = cb.replace("[", "\[")
/usr/share/hplip/base/password.py:213: SyntaxWarning: invalid escape sequence 
'\]'
  cb = cb.replace("]", "\]")
/usr/share/hplip/base/queues.py:48: SyntaxWarning: invalid escape sequence '\*'
  NICKNAME_PATTERN = re.compile(b'''\*NickName:\s*\"(.*)"''', re.MULTILINE)
/usr/share/hplip/base/status.py:1335: SyntaxWarning: invalid escape sequence 
'\s'
  pjl_code_pat = re.compile("""^CODE\s*=\s*(\d.*)$""", 

[Desktop-packages] [Bug 2020110] Re: Migrate netplan settings to this package

2024-02-14 Thread Simon Quigley
** Tags added: rls-nn-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2020110

Title:
  Migrate netplan settings to this package

Status in network-manager package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  The current netplan configuration that specifies Network Manager as
  the renderer comes from a livecd-rootfs hack and results in an
  "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was
  decided at the engineering sprint to migrate this to /lib/netplan
  (with a slightly tweaked filename starting 00- for precedence) owned
  by ubuntu-settings which will ease maintenance (and image builds) in
  future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2020110/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2020110] Re: Migrate netplan settings to this package

2024-02-13 Thread Simon Quigley
Per discussions in the appropriate PR for Calamares[1], this should be
done in network-manager itself.

The appeal is more custom approaches. Downstreams and vendors of Ubuntu.

[1] https://github.com/calamares/calamares/pull/2284

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2020110

Title:
  Migrate netplan settings to this package

Status in network-manager package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  The current netplan configuration that specifies Network Manager as
  the renderer comes from a livecd-rootfs hack and results in an
  "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was
  decided at the engineering sprint to migrate this to /lib/netplan
  (with a slightly tweaked filename starting 00- for precedence) owned
  by ubuntu-settings which will ease maintenance (and image builds) in
  future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2020110/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2047780] Re: BlueZ release 5.71

2024-01-10 Thread Simon Quigley
** Changed in: bluez (Ubuntu)
   Status: Fix Released => In Progress

** Summary changed:

- BlueZ release 5.71
+ BlueZ release 5.71 and merge from Debian

** Changed in: bluez (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Simon Quigley (tsimonq2)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780

Title:
  BlueZ release 5.71 and merge from Debian

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration

2023-12-29 Thread Simon Quigley
** Also affects: lxqt-session (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: lxqt-session (Ubuntu)
   Status: New => In Progress

** Changed in: lxqt-session (Ubuntu)
   Importance: Undecided => High

** Changed in: lxqt-session (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2047705

Title:
  Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to
  Yaru and preventing flavors from overriding it with XDG configuration

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in lxqt-session package in Ubuntu:
  In Progress

Bug description:
  Lubuntu uses Qt as the primary framework for most of the apps we ship.
  However, some functionality we ship in Lubuntu doesn't have a Qt
  application that provides that functionality, so we have some GTK3
  apps that we ship as well. Starting in Lubuntu 24.04, we are adding
  and enabling the breeze-gtk-theme package, providing more uniform
  theming between Qt and GTK apps on Lubuntu. However, this bug makes
  this impossible.

  As we do not ship xsettingsd, but instead use the XDG specification
  for shipping configuration, we are attempting to place the default
  configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg-
  Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini.
  This solutions works for GTK2 apps, however GTK3 apps silently ignore
  the vendored configuration file and are using a different theme.

  As it turns out, this is because the /etc directory is given higher
  priority than /etc/xdg/xdg-Lubuntu when searching for XDG
  configuration files, and as it happens, libgtk-3-0 ships a
  /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme.
  GTK3 applications end up selecting this configuration file rather than
  /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini.

  /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's
  settings.ini file should go, as it makes it difficult for flavors who
  rely on XDG configuration to override it without risking a file
  conflict. (Technically I guess a flavor package *could* use dpkg-
  divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but
  that seems like the wrong way to approach this.)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libgtk-3-0 3.24.38-5ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Fri Dec 29 10:08:23 2023
  InstallationDate: Installed on 2023-10-22 (69 days ago)
  InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2047008] Re: [SRU] Add Telit FN990 compositions

2023-12-28 Thread Simon Quigley
Uploaded with a changelog tweak. It looks like there is precedent for
this, but it's in the SRU team's hands now.

DEP-3 patch headers next time? ;)

** Also affects: modemmanager (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: modemmanager (Ubuntu)
   Status: New => Fix Released

** Changed in: modemmanager (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: modemmanager (Ubuntu)
   Importance: Undecided => High

** Changed in: modemmanager (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: modemmanager (Ubuntu Jammy)
 Assignee: (unassigned) => Laider Lai (laiderlai)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/2047008

Title:
  [SRU] Add Telit FN990 compositions

Status in OEM Priority Project:
  New
Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Jammy:
  In Progress

Bug description:
  [SRU] Add Telit FN990 compositions

  [ Impact ]

  The modemmanager v1.20.0 doesn't have Telit FN990 compositions.
  It works with compatibility mode.
  (lp: #2046699)

  [ Test Plan ]

  Under Jammy environment,
  check modemmanager can identify Telit FN990 modem correctly.

  [ Where problems could occur ]

  The Telit FN990 compositions is upstreamed to modemmanager v1.20.6
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2

  Noble and Mantic already working with modemmanager v1.20.6.
  The target platform modem function works well on Mantic.

  The change parts just only add VID/PIDs for Telit's FN990 modems under
  the Telit plugin.

  [ Other Info ]

  N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2047008/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2023-12-24 Thread Simon Quigley
** Changed in: lubuntu-update-notifier (Ubuntu)
   Importance: Undecided => Medium

** Changed in: lubuntu-update-notifier (Ubuntu)
   Status: New => Confirmed

** Changed in: lubuntu-update-notifier (Ubuntu)
Milestone: None => ubuntu-24.04-feature-freeze

** Changed in: lubuntu-update-notifier (Ubuntu)
 Assignee: (unassigned) => Aaron Rainbolt (arraybolt3)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1673258

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in lubuntu-update-notifier package in Ubuntu:
  Confirmed
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in oem-config package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles

2023-12-24 Thread Simon Quigley
I patched this upstream in Calamares a month or two ago, and it made it
into the 3.3.0 tag, which Lubuntu now has.

Calamares will support both, it just now *also* supports Netplan. (If
the NM config doesn't exist, no harm no foul no error.)

** Changed in: calamares (Ubuntu)
   Importance: Undecided => Medium

** Changed in: calamares (Ubuntu)
   Status: New => Fix Released

** Changed in: calamares (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: calamares (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2019940

Title:
  Directly manipulating NetworkManager keyfiles

Status in augeas package in Ubuntu:
  New
Status in calamares package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Invalid
Status in cruft package in Ubuntu:
  Won't Fix
Status in cruft-ng package in Ubuntu:
  Fix Released
Status in dracut package in Ubuntu:
  New
Status in forensic-artifacts package in Ubuntu:
  New
Status in guestfs-tools package in Ubuntu:
  New
Status in guix package in Ubuntu:
  New
Status in ltsp package in Ubuntu:
  Invalid
Status in netcfg package in Ubuntu:
  Won't Fix
Status in netplan.io package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  New
Status in refpolicy package in Ubuntu:
  New
Status in sosreport package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  New
Status in uhd package in Ubuntu:
  New
Status in vagrant package in Ubuntu:
  New

Bug description:
  The affected packages can manipulate NetworkManager keyfiles directly
  on disk, which might not be appropriate anymore on Ubuntu, since the
  Netplan integration was enabled in NetworkManager (starting with
  Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2046944] Re: Sync wireplumber 0.4.17-1 (main) from Debian testing (main)

2023-12-19 Thread Simon Quigley
$ syncpackage -f -b 2046944 -s daissi wireplumber
Source wireplumber -> noble/Proposed: current version 0.4.14-4ubuntu1, new 
version 0.4.17-1
Downloading wireplumber_0.4.17-1.dsc from deb.debian.org (0.003 MiB)
[=>]100%
Downloading wireplumber_0.4.14-4ubuntu1.dsc from archive.ubuntu.com (0.003 MiB)
[=>]100%
Downloading changelog from launchpadlibrarian.net (0.010 MiB)
[=>]100%
New changes:
wireplumber (0.4.17-1) unstable; urgency=medium

  * New upstream version

 -- Dylan Aïssi   Mon, 04 Dec 2023 10:18:53 +0100

wireplumber (0.4.16-1) unstable; urgency=medium

  [ Dylan Aïssi ]
  * New upstream version
  * Drop patch included in upstream release:
  - policy-dsp: add ability to hide parent nodes
  * Bump minimum pipewire to 0.3.68
  * Update symbols file

  [ Andreas Henriksson ]
  * Use ${gir:Depends} and ${gir:Provides}

 -- Dylan Aïssi   Wed, 22 Nov 2023 17:59:06 +0100

wireplumber (0.4.15-2) unstable; urgency=medium

  * Team upload.
  * Cherry-pick upstream patch for ability to hide parent nodes

 -- Andreas Henriksson   Mon, 13 Nov 2023 18:14:25
+0100

wireplumber (0.4.15-1) unstable; urgency=medium

  [ Dylan Aïssi ]
  * New upstream version
  * Install zsh completions file


  * Update symbols file 





  [ Lena Voytek ]
  * d/control: Upgrade lua build dependency to 5.4

 -- Dylan Aïssi   Fri, 13 Oct 2023 12:06:12 +0200
Sponsoring this sync for Dylan Aïssi (daissi)
Sync this package [y|N]? y
Request succeeded; you should get an e-mail once it is processed.
Launchpad bugs to be closed: 2046944
Please wait for the sync to be successful before closing bugs.
Close bugs [Y|n]?

** Changed in: wireplumber (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wireplumber in Ubuntu.
https://bugs.launchpad.net/bugs/2046944

Title:
  Sync wireplumber 0.4.17-1 (main) from Debian testing (main)

Status in wireplumber package in Ubuntu:
  Fix Released

Bug description:
  Please sync wireplumber 0.4.17-1 from Debian.

  The Ubuntu delta was merged in Debian:

  wireplumber (0.4.17-1) unstable; urgency=medium

* New upstream version

   -- Dylan Aïssi   Mon, 04 Dec 2023 10:18:53 +0100

  wireplumber (0.4.16-1) unstable; urgency=medium

[ Dylan Aïssi ]
* New upstream version
* Drop patch included in upstream release:
- policy-dsp: add ability to hide parent nodes
* Bump minimum pipewire to 0.3.68
* Update symbols file

[ Andreas Henriksson ]
* Use ${gir:Depends} and ${gir:Provides}

   -- Dylan Aïssi   Wed, 22 Nov 2023 17:59:06 +0100

  wireplumber (0.4.15-2) unstable; urgency=medium

* Team upload.
* Cherry-pick upstream patch for ability to hide parent nodes

   -- Andreas Henriksson   Mon, 13 Nov 2023 18:14:25
  +0100

  wireplumber (0.4.15-1) unstable; urgency=medium

[ Dylan Aïssi ]
* New upstream version
* Install zsh completions file
* Update symbols file

[ Lena Voytek ]
* d/control: Upgrade lua build dependency to 5.4

   -- Dylan Aïssi   Fri, 13 Oct 2023 12:06:12 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/2046944/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2043306] Re: Sync tepl 6.8.0-2 (universe) from Debian unstable (main)

2023-11-14 Thread Simon Quigley
This bug was fixed in the package tepl - 6.8.0-2
Sponsored for Hans Joachim Desserud (hjd)

---
tepl (6.8.0-2) unstable; urgency=medium

  * Stop using debian/control.in
  * Drop X-Ubuntu-Use-Langpack from debian/control
  * Drop the now unnecessary dh-sequence-gnome from Build-Depends

 -- Amin Bandali   Wed, 08 Nov 2023 16:43:37 +0200

tepl (6.8.0-1) experimental; urgency=medium

  * New upstream release
  * debian/control.in: Add myself to uploaders
  * debian/control.in: Adjust dependencies according to upstream
  * debian/control.in: Update standards version to 4.6.2, no changes needed
  * debian/control.in: Rename library package to match soversion bump
  * debian/libtepl-6-4.symbols: Update symbols following upstream
  * debian/copyright: Bump copyright years and list contributors to
debian/* thus far

 -- Amin Bandali   Wed, 18 Oct 2023 16:05:30 -0400

** Changed in: tepl (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tepl in Ubuntu.
https://bugs.launchpad.net/bugs/2043306

Title:
  Sync tepl 6.8.0-2 (universe) from Debian unstable (main)

Status in tepl package in Ubuntu:
  Fix Released

Bug description:
  Please sync tepl 6.8.0-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* No change upload to trigger a translations import on launchpad,
  the template was not correctly set for the new ABI version and the
  existing translations weren't imported in the previous upload
* No change upload to trigger a translations import on launchpad,
  the template was not correctly set for the new ABI version and the
  existing translations weren't imported in the previous upload
* debian/control.in:
  - remove 'X-Ubuntu-Use-Langpack: yes', the template name changed and the
one wasn't accepted on launchpad so the translations are missing from
the langpacks, we aren't going to get a respin of those for lunar so
go back to have the translations included in the deb. Resolve the
issue when some strings in gedit show untranslated (lp: #2016923)
* Rebuild against latest icu
* Rebuild against latest icu

  X-Ubuntu-Use-Langpack was removed from the control file in Debian too
  
https://salsa.debian.org/gnome-team/tepl/-/commit/f550e49edab938302eae6c2bb582b51148935e1d
  And control.in was dropped which is why the above commit only lists changes 
in one file
  
https://salsa.debian.org/gnome-team/tepl/-/commit/50b77ecd10434a97307886aadb20d755b8c3ab54

  
  Changelog entries since current noble version 6.4.0-7ubuntu2:

  tepl (6.8.0-2) unstable; urgency=medium

* Stop using debian/control.in
* Drop X-Ubuntu-Use-Langpack from debian/control
* Drop the now unnecessary dh-sequence-gnome from Build-Depends

   -- Amin Bandali   Wed, 08 Nov 2023 16:43:37 +0200

  tepl (6.8.0-1) experimental; urgency=medium

* New upstream release
* debian/control.in: Add myself to uploaders
* debian/control.in: Adjust dependencies according to upstream
* debian/control.in: Update standards version to 4.6.2, no changes needed
* debian/control.in: Rename library package to match soversion bump
* debian/libtepl-6-4.symbols: Update symbols following upstream
* debian/copyright: Bump copyright years and list contributors to
  debian/* thus far

   -- Amin Bandali   Wed, 18 Oct 2023 16:05:30 -0400

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tepl/+bug/2043306/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2039460] Re: Please merge network-manager-applet 1.34.0-1 from Debian unstable

2023-11-06 Thread Simon Quigley
By the way...

> Should I always propose the debdiff with the release name instead of
UNRELEASED[...]?

Yes, that's correct. Great question, sorry that I missed it!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/2039460

Title:
  Please merge network-manager-applet 1.34.0-1 from Debian unstable

Status in network-manager-applet package in Ubuntu:
  In Progress

Bug description:
  Builds successfully in Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2039460/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2039460] Re: Please merge network-manager-applet 1.34.0-1 from Debian unstable

2023-11-03 Thread Simon Quigley
This is just a minor note, but "resynchronize" implies a pure sync,
merging is slightly different. Not blocking the sponsorship request.

Sponsoring, thank you!

** Changed in: network-manager-applet (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: network-manager-applet (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/2039460

Title:
  Please merge network-manager-applet 1.34.0-1 from Debian unstable

Status in network-manager-applet package in Ubuntu:
  In Progress

Bug description:
  Builds successfully in Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2039460/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy

2023-07-27 Thread Simon Quigley
Ah, right. Debootstrap is more low-level, thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2028769

Title:
  [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal
  in Jammy

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  [ Impact ]

  Without packages ubuntu-desktop, ubuntu-desktop-minimal it is
  unnecessarily difficult to setup the Ubuntu desktop on systems like
  the SiFive HiFive Unmatched.

  All dependent packages are available.

  We just need to add the riscv64 architecture in debian/control.

  [ Test Plan ]

  Reproducing the issue:

  * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are
  not available for riscv64 in the archive.

  Testing:

  * Install Ubuntu Jammy using the live installer on the SiFive HiFive 
Unmatched board.
  * Install package ubuntu-desktop-minimal.
  * Install package ubuntu-desktop.
  * Reboot
  * Login
  * Check that you have a function desktop by opening a preinstalled 
application.

  [ Where problems could occur ]

  * The packages might not be installable due to missing dependencies.
  * The Gnome desktop might fail.

  [ Other Info ]
   
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy

2023-07-26 Thread Simon Quigley
I'm just generally curious, does debootstrap function differently
with/without this patch?

I'd imagine it either goes off the task, or a level lower than the
metapackages.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2028769

Title:
  [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal
  in Jammy

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  [ Impact ]

  Without packages ubuntu-desktop, ubuntu-desktop-minimal it is
  unnecessarily difficult to setup the Ubuntu desktop on systems like
  the SiFive HiFive Unmatched.

  All dependent packages are available.

  We just need to add the riscv64 architecture in debian/control.

  [ Test Plan ]

  Reproducing the issue:

  * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are
  not available for riscv64 in the archive.

  Testing:

  * Install Ubuntu Jammy using the live installer on the SiFive HiFive 
Unmatched board.
  * Install package ubuntu-desktop-minimal.
  * Install package ubuntu-desktop.
  * Reboot
  * Login
  * Check that you have a function desktop by opening a preinstalled 
application.

  [ Where problems could occur ]

  * The packages might not be installable due to missing dependencies.
  * The Gnome desktop might fail.

  [ Other Info ]
   
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2007623] Re: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main)

2023-02-26 Thread Simon Quigley
Sponsored, thank you!

** Changed in: grilo-plugins (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to grilo-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/2007623

Title:
  Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main)

Status in grilo-plugins package in Ubuntu:
  Fix Committed

Bug description:
  Please merge grilo-plugins 0.3.15-2 (universe) from Debian unstable
  (main)

  Changelog entries since current lunar version 0.3.15-1ubuntu1:

  grilo-plugins (0.3.15-2) unstable; urgency=medium

* debian/control:
  - Stop recommending dleyna-server (Closes: #1030125).
  - Update Standards-Version to 4.6.2 (no changes).
* debian/copyright:
  - Update copyright years.

   -- Alberto Garcia   Tue, 31 Jan 2023 16:45:49 +0100

  Remaining differences with grilo-plugins from Debian unstable:

  - Split package into -base and -extra (Closes: #805609)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/2007623/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2006633] Re: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

2023-02-11 Thread Simon Quigley
Please remember to mention the bug number in the changelog entry.
Additionally, for stylistic purposes, I changed this:

  * Merge from Debian unstable.  The remaining difference is the change
for ignoring test results on i386 to avoir failure.

To this:

  * Merge from Debian Unstable (LP: #2006633). Remaining changes:
- Don't fail the build on tests error for i386

Otherwise, looks good to me, uploading. Please keep this in mind for a
later upload.

Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/2006633

Title:
  Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

Status in librsvg package in Ubuntu:
  New

Bug description:
  Please merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

  Changelog entries since current lunar version 2.54.4+dfsg-1ubuntu1:

  librsvg (2.54.5+dfsg-1) unstable; urgency=medium

* New upstream release
* debian/librsvg2-2.docs: NEWS.md -> NEWS

   -- Jeremy Bicha   Thu, 22 Sep 2022 17:00:54 -0400

  Remaining differences with librsvg from Debian unstable:

* Don't fail the build on tests error for i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2006633/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1993191] Re: apport hook that collects snap's information is outdated

2023-01-26 Thread Simon Quigley
Uploaded to Lunar, currently in the SRU queue for Kinetic, Jammy, and
Focal. Unsubscribing sponsors.

Thanks for your contributions!

** Changed in: chromium-browser (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1993191

Title:
  apport hook that collects snap's information is outdated

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in chromium-browser source package in Focal:
  In Progress
Status in chromium-browser source package in Jammy:
  In Progress
Status in chromium-browser source package in Kinetic:
  In Progress

Bug description:
  
  Impact
  --

  The Apport hook of the Chromium browser is outdated. It collects
  information about core18, but the snap uses core20.

  Moreover, it does not collect information about other interface
  providers.

  Test plan
  -

  1. Install the current chromium-browser.

  2. Generate a report with

apport-bug --save /tmp/c1 chromium-browser
   
  3. Install chromium-browser from proposed.

  4. Generate another report with

apport-bug --save /tmp/c2 chromium-browser

  Note: If the package was built and generated locally, you will need
  APPORT_DISABLE_DISTRO_CHECK=1 in the environment.

  5. Compare the files. The meaningful differences should be in the
  Snap.Info. sections, namely:

- Snap.Info.core18 -> Snap.Info.core20
- {None} -> Snap.Info.cups
- {None} -> Snap.Info.gnome-3-38-2004

  Differences should not be observed in Snap.Info.{chromium,core,gtk-
  common-themes}.

  Regression potential
  

  Being Apport a bug reporting program, an incorrect parsing of the
  SNAP_META file could lead to insertion of unwanted information in the
  report or to suppress the insertion of information about the relevant
  interfaces.

  
  Original report
  ---

  See https://bazaar.launchpad.net/~chromium-team/chromium-
  browser/groovy-stable/view/head:/debian/apport/chromium-
  browser.py#L59.

  It collects information about core18, but the chromium snap was
  rebased on core20 almost a year ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1993191] Re: apport hook that collects snap's information is outdated

2023-01-25 Thread Simon Quigley
Hi, is this still an issue? If so, could you please fill out the
description as an SRU? (Or explain why it should not be.)

Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1993191

Title:
  apport hook that collects snap's information is outdated

Status in chromium-browser package in Ubuntu:
  In Progress
Status in chromium-browser source package in Focal:
  In Progress
Status in chromium-browser source package in Jammy:
  In Progress
Status in chromium-browser source package in Kinetic:
  In Progress

Bug description:
  See https://bazaar.launchpad.net/~chromium-team/chromium-
  browser/groovy-stable/view/head:/debian/apport/chromium-
  browser.py#L59.

  It collects information about core18, but the chromium snap was
  rebased on core20 almost a year ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1991022] Re: [FFe] Socket activation

2023-01-25 Thread Simon Quigley
This package exists in Lunar again and the fix has been released
upstream, marking as Fix Released.

** Changed in: speech-dispatcher (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to speech-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1991022

Title:
  [FFe] Socket activation

Status in speech-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  [Description]

  Systemd socket activation for Speech Dispatcher.

    - Creates the speech-dispatcher.socket;
    - Modifies the server so that it can detect it was automatically launched 
by that socket activation; and
    - Modifies the Autotools files accordingly.

  [Rationale]

  It's relevance is described in [1], of which I quote the essential
  parts [my notes in brackets]:

  > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle 
it inside of the sandbox, so that each application has its own "private" 
instance of Speech Dispatcher running. This works more or less, but it has the 
downside that speech dispatcher cannot coordinate simultaneous messages from 
multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same 
time, the text reading overlaps.
  >
  > In order to solve this issue, I would really like to give sandboxed apps 
access to the Speech Dispatcher instance of the host.

  And then,

  > The only issue I see is having it auto launch. I think it would
  probably be a good step forward for speech-dispatcher to be auto
  launched by a systemd socket like other daemons already do on demand.
  That way the host speech-dispatcher with it's configuration would be
  used by all snaps,

  [Additional information]

  The changes are already merged upstream[2], but still not released.

  I have built and installed the package in Kinetic and verified that
  spd-say still causes the dispatcher spawn and emits sound. Upstream
  test can also confirm this.

  [1]: https://github.com/brailcom/speechd/issues/335
  [2]: https://github.com/brailcom/speechd/pull/763

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1992101] Re: No sound devices listed in Settings

2023-01-25 Thread Simon Quigley
** No longer affects: wireplumber (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pipewire in Ubuntu.
https://bugs.launchpad.net/bugs/1992101

Title:
  No sound devices listed in Settings

Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire package in Debian:
  Fix Released

Bug description:
  Hi, in ubuntu 22.10 beta, there is no sound (only dummy output device
  is present in Settings->Sound). The systemctl --user status pipewire
  is:

   Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: 
enabled)
   Active: active (running) since Thu 2022-10-06 22:51:13 CEST; 27min ago
  TriggeredBy: ● pipewire.socket
 Main PID: 10075 (pipewire)
Tasks: 2 (limit: 115618)
   Memory: 4.7M
  CPU: 65ms
   CGroup: 
/user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
   └─10075 /usr/bin/pipewire

  Oct 06 22:51:13 testosteron systemd[10061]: Started PipeWire Multimedia 
Service.
  Oct 06 22:51:13 testosteron pipewire[10075]: mod.rt: Can't find xdg-portal: 
(null)
  Oct 06 22:51:13 testosteron pipewire[10075]: mod.rt: found session bus but no 
portal
  Oct 06 22:51:13 testosteron pipewire[10075]: mod.rt: RTKit error: 
org.freedesktop.DBus.Error.AccessDenied
  Oct 06 22:51:13 testosteron pipewire[10075]: mod.rt: could not make thread 
10106 realtime using RTKit: Permission denied

  The installed pipewire packages are:
  ii  gstreamer1.0-pipewire:amd64   0.3.57-1
amd64GStreamer 1.0 plugin for the PipeWire 
multimedia server
  ii  libpipewire-0.3-0:amd64   0.3.57-1
amd64libraries for the PipeWire multimedia server
  ii  libpipewire-0.3-common0.3.57-1
all  libraries for the PipeWire multimedia server - 
common files
  ii  libpipewire-0.3-dev:amd64 0.3.57-1
amd64libraries for the PipeWire multimedia server - 
development
  ii  libpipewire-0.3-modules:amd64 0.3.57-1
amd64libraries for the PipeWire multimedia server - 
modules
  ii  pipewire:amd640.3.57-1
amd64audio and video processing engine multimedia 
server
  ii  pipewire-alsa:amd64   0.3.57-1
amd64PipeWire ALSA plugin
  ii  pipewire-audio-client-libraries   0.3.57-1
all  transitional package for pipewire-alsa and 
pipewire-jack
  ii  pipewire-bin  0.3.57-1
amd64PipeWire multimedia server - programs
  ii  pipewire-jack:amd64   0.3.57-1
amd64PipeWire JACK plugin
  ii  pipewire-media-session0.4.1-4 
amd64example session manager for PipeWire
  ii  pipewire-pulse0.3.57-1
amd64PipeWire PulseAudio daemon
  ii  pipewire-tests0.3.57-1
amd64PipeWire multimedia server - tests and examples
  ii  vlc-plugin-pipewire:amd64 3-2 
amd64PipeWire audio plugins for VLC

  Moreover:
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.57-1
  ProcVersionSignature: Ubuntu 5.19.0-18.18-generic 5.19.7
  Uname: Linux 5.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  6 23:15:59 2022
  EcryptfsInUse: Yes
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-06 (0 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1992101/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2003889] Re: Pleae merge wpa 2.10-10 from Debian

2023-01-25 Thread Simon Quigley
Hi Nathan!

I have no problem with the patch, given the author. That being said, it
would be useful to send this delta up to Debian if at all possible.
Please consider it. :)

Also, it's best not to modify changelog entries that exist in Debian.
I'm dropping this before uploading:

 wpa (2:2.10-9) unstable; urgency=medium

-  [ Sebastien Bacher ]
   * debian/patches/allow-legacy-renegotiation.patch:
-Allow legacy renegotiation to fix PEAP issues with some servers
-(Closes: #1010603, LP: #1962541)
+allow legacy renegotiation to fix PEAP issues with some servers
+(Closes: #1010603)

- -- Andrej Shadura   Thu, 05 May 2022 11:23:33 +0100
+ -- Sebastien Bacher   Thu, 05 May 2022 11:31:26 +0200

Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2003889

Title:
  Pleae merge wpa 2.10-10 from Debian

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  I built it successfully in Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2003564] Re: Sync xfonts-scalable 1:1.0.3-1.3 (main) from Debian unstable (main)

2023-01-23 Thread Simon Quigley
This bug was fixed in the package xfonts-scalable - 1:1.0.3-1.3
Sponsored for Hans Joachim Desserud (hjd)

---
xfonts-scalable (1:1.0.3-1.3) unstable; urgency=medium

  * Non-maintainer upload, incorporating changes from the maintainers'
packaging repository

  [ Julien Cristau ]
  * Remove Cyril and David from Uploaders.
  * Add Vcs-* control fields.
  * Use https URL in debian/watch.

  [ Simon McVittie ]
  * d/control: Update Vcs-* for migration to salsa.debian.org
  * Use recommended debhelper compat level 13 (Closes: #965894)
  * d/rules: Add missing build-arch, build-indep targets (Policy §4.9)
  * d/control: Declare that the build does not require (fake)root

 -- Simon McVittie   Sun, 15 Jan 2023 14:18:32 +

** Changed in: xfonts-scalable (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xfonts-scalable in Ubuntu.
https://bugs.launchpad.net/bugs/2003564

Title:
  Sync xfonts-scalable 1:1.0.3-1.3 (main) from Debian unstable (main)

Status in xfonts-scalable package in Ubuntu:
  Fix Released

Bug description:
  Please sync xfonts-scalable 1:1.0.3-1.3 (main) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Update to dh7 to fix the build
* Update to dh7 to fix the build
* Update to dh7 to fix the build

  Current Ubuntu delta:
  
https://patches.ubuntu.com/x/xfonts-scalable/xfonts-scalable_1:1.0.3-1.2ubuntu1.patch

  Debian has updated debhelper dependency from 5 to 13 now.
  Relevant commit:
  
https://salsa.debian.org/xorg-team/font/xfonts-scalable/-/commit/020b14f4ce6c9add3e4a7d71578771c66547656e
  resulting in curent control file:
  https://tracker.debian.org/media/packages/x/xfonts-scalable/control-11.0.3-1.3

  
  Changelog entries since current lunar version 1:1.0.3-1.2ubuntu1:

  xfonts-scalable (1:1.0.3-1.3) unstable; urgency=medium

* Non-maintainer upload, incorporating changes from the maintainers'
  packaging repository

[ Julien Cristau ]
* Remove Cyril and David from Uploaders.
* Add Vcs-* control fields.
* Use https URL in debian/watch.

[ Simon McVittie ]
* d/control: Update Vcs-* for migration to salsa.debian.org
* Use recommended debhelper compat level 13 (Closes: #965894)
* d/rules: Add missing build-arch, build-indep targets (Policy §4.9)
* d/control: Declare that the build does not require (fake)root

   -- Simon McVittie   Sun, 15 Jan 2023 14:18:32 +

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfonts-scalable/+bug/2003564/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1948566] Re: Sync java-atk-wrapper 0.38.0-5 (main) from Debian unstable (main)

2021-10-27 Thread Simon Quigley
This bug was fixed in the package java-atk-wrapper - 0.38.0-5
Sponsored for Hans Joachim Desserud (hjd)

---
java-atk-wrapper (0.38.0-5) unstable; urgency=medium

  [ Debian Janitor ]
  * Bump debhelper from old 12 to 13.
  * Update standards version to 4.5.1, no changes needed.
  * Remove constraints unnecessary since buster:
+ Build-Depends: Drop versioned constraint on java-common.

  [ Samuel Thibault ]
  * libatk-wrapper-java.lintian-overrides: Drop lintian warning for jar name.

 -- Samuel Thibault   Sat, 18 Sep 2021 18:34:13
+0200

java-atk-wrapper (0.38.0-4) unstable; urgency=medium

  * patches/dbus: Also detect at-spi through dbus.

 -- Samuel Thibault   Thu, 26 Aug 2021 02:50:17
+0200

java-atk-wrapper (0.38.0-3) unstable; urgency=medium

  * patches/werror: Only enable -Werror in upstream development
(Closes: Bug#984069).
  * control: Set Rules-Requires-Root to no.
  * rules: Drop ddeb-migration rules, now useless

 -- Samuel Thibault   Sun, 15 Aug 2021 22:56:34
+0200

** Changed in: java-atk-wrapper (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to java-atk-wrapper in Ubuntu.
https://bugs.launchpad.net/bugs/1948566

Title:
  Sync java-atk-wrapper 0.38.0-5 (main) from Debian unstable (main)

Status in java-atk-wrapper package in Ubuntu:
  Fix Released

Bug description:
  Please sync java-atk-wrapper 0.38.0-5 (main) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* No-change rebuild to build packages with zstd compression.
* No-change rebuild to build packages with zstd compression.
* Import an unreleased debian patch to better address the s390x FTBFS
  - debian/patches/werror
* Import an unreleased debian patch to better address the s390x FTBFS
  - debian/patches/werror

  Werror patch has been included in Debian package.

  Changelog entries since current jammy version 0.38.0-2ubuntu3:

  java-atk-wrapper (0.38.0-5) unstable; urgency=medium

[ Debian Janitor ]
* Bump debhelper from old 12 to 13.
* Update standards version to 4.5.1, no changes needed.
* Remove constraints unnecessary since buster:
  + Build-Depends: Drop versioned constraint on java-common.

[ Samuel Thibault ]
* libatk-wrapper-java.lintian-overrides: Drop lintian warning for jar name.

   -- Samuel Thibault   Sat, 18 Sep 2021 18:34:13
  +0200

  java-atk-wrapper (0.38.0-4) unstable; urgency=medium

* patches/dbus: Also detect at-spi through dbus.

   -- Samuel Thibault   Thu, 26 Aug 2021 02:50:17
  +0200

  java-atk-wrapper (0.38.0-3) unstable; urgency=medium

* patches/werror: Only enable -Werror in upstream development
  (Closes: Bug#984069).
* control: Set Rules-Requires-Root to no.
* rules: Drop ddeb-migration rules, now useless

   -- Samuel Thibault   Sun, 15 Aug 2021 22:56:34
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/1948566/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1781597] Re: [SRU] WoWLAN settings are not supported

2020-07-17 Thread Simon Quigley
** Tags removed: verification-done-cosmic
** Tags added: rls-bb-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1781597

Title:
  [SRU] WoWLAN settings are not supported

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Triaged
Status in network-manager source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  WoWLAN lets us wake up the system by sending wake packets over the
  wifi connection. This is something requested by some OEM projects, for
  bionic server images.

  NM 1.12 supports configuring this feature, so this can be achieved by
  backporting that support to 1.10 (bionic version). These are the MPs
  for cosmic and bionic:

  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468
  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465

  [Test Case]

  First, the wifi card must support WoWLAN. This can be checked by
  running

  $ iw phy

  and searching for "WoWLAN support:" in the output. If it is supported,
  with the patch applied a connection configured with wowlan can be
  created with:

  $ sudo nmcli d wifi connect  password 
  $ sudo nmcli c modify  802-11-wireless.wake-on-wlan 8
  $ sudo nmcli c down 
  $ sudo nmcli c up 

  We can check with 'iw' that WoWLAN is active for the connection:

  $ iw phy phy0 wowlan show
  WoWLAN is enabled:
   * wake up on magic packet

  In this case we have configured the connection to wake up the system
  when a 'magic' packet is received. We can then suspend the system with

  $ sudo systemctl suspend

  And we should be able to wake the system from another device with the
  command

  $ sudo etherwake -i  

  [Regression Potential]

  Although the patch is not especially small, it is a backport of
  changes that have been merged upstream, with very little modifications
  to make it compile in 1.10. It is also a rather isolated feature that
  should not conflict with existing ones. The feature will be activated
  only if configured from the command line, so the risk of regressions
  should be small. Note also that the patch will be removed as soon as
  Ubuntu moves to NM 1.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1838823] [NEW] [snap] Allow different channels with different binary packages

2019-08-02 Thread Simon Quigley
Public bug reported:

While the chromium-browser package should install the stable channel, it
might be worth considering creating chromium-browser-beta and chromium-
browser-edge etc. for the different channels.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1838823

Title:
  [snap] Allow different channels with different binary packages

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  While the chromium-browser package should install the stable channel,
  it might be worth considering creating chromium-browser-beta and
  chromium-browser-edge etc. for the different channels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838823/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1838821] [NEW] [deb2snap] Upgrade fails when snap is already installed

2019-08-02 Thread Simon Quigley
Public bug reported:

I have the chromium-browser snap installed, and when upgrading to the
new snap-based Chromium deb, it fails when the snap is already
installed:

Preparing to unpack .../chromium-browser_76.0.3809.87-0ubuntu1~snap1_amd64.deb 
...
=> Installing the chromium snap
==> Checking connectivity with the snap store
==> Installing the chromium snap
snap "chromium" is already installed, see 'snap help refresh'
=> Snap installation complete
=> Connecting the password-manager-service interface (LP: #1836616)
error: cannot resolve connection, slot snap name is empty
dpkg: error processing archive 
/var/cache/apt/archives/chromium-browser_76.0.3809.87-0ubuntu1~snap1_amd64.deb 
(--unpack):
 new chromium-browser package pre-installation script subprocess returned error 
exit status 1
Preparing to unpack .../libidn2-0_2.2.0-1_amd64.deb ...
Unpacking libidn2-0:amd64 (2.2.0-1) over (2.0.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/chromium-browser_76.0.3809.87-0ubuntu1~snap1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

This is a blocker to SRUing the deb2snap transition to stable releases.

** Affects: chromium-browser (Ubuntu)
 Importance: High
 Status: New

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1838821

Title:
  [deb2snap] Upgrade fails when snap is already installed

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I have the chromium-browser snap installed, and when upgrading to the
  new snap-based Chromium deb, it fails when the snap is already
  installed:

  Preparing to unpack 
.../chromium-browser_76.0.3809.87-0ubuntu1~snap1_amd64.deb ...
  => Installing the chromium snap
  ==> Checking connectivity with the snap store
  ==> Installing the chromium snap
  snap "chromium" is already installed, see 'snap help refresh'
  => Snap installation complete
  => Connecting the password-manager-service interface (LP: #1836616)
  error: cannot resolve connection, slot snap name is empty
  dpkg: error processing archive 
/var/cache/apt/archives/chromium-browser_76.0.3809.87-0ubuntu1~snap1_amd64.deb 
(--unpack):
   new chromium-browser package pre-installation script subprocess returned 
error exit status 1
  Preparing to unpack .../libidn2-0_2.2.0-1_amd64.deb ...
  Unpacking libidn2-0:amd64 (2.2.0-1) over (2.0.5-1) ...
  Errors were encountered while processing:
   
/var/cache/apt/archives/chromium-browser_76.0.3809.87-0ubuntu1~snap1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  This is a blocker to SRUing the deb2snap transition to stable
  releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838821/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1836616] Re: [snap] Upgrade from deb to snap forgets saved passwords

2019-08-02 Thread Simon Quigley
This results in a regression as seen in bug 1838821.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1836616

Title:
  [snap] Upgrade from deb to snap forgets saved passwords

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 19.10, when upgrading from the deb package to the snap¹, the
  password-manager-service interface is not auto-connected. As a result,
  chromium is unable to talk to org.freedesktop.Secret.Service over
  D-Bus, and it falls back to the basic unencrypted stored.

  See https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and-
  password-manager-service-interfaces-for-the-chromium-snap/4592 for why
  auto-connection was denied for the password-manager-service interface.

  This is bad user experience, as the transition should be seamless.

  Aside of auto-connection, one possible solution would be to do the
  connection in the deb’s pre-install script (which installs the snap
  from the store, and is executed as root). That has pretty much the
  same security implications though, so it requires input from the
  security team before proceeding.

  Yet another solution would be for the wrapper script (/usr/bin
  /chromium-browser) to extract the stored passwords from the keyring
  and import them into the basic unencrypted sqlite store for the snap,
  but that feels clunky and fragile.

  Or a log message / dialog box at startup to inform the user that they
  should connect the interface manually. But that's not great UX, and
  doesn't provide a seamless transition.

  
  ¹ 
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1836616/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1834211] Re: [SRU] gconf FTBFS in Bionic

2019-07-02 Thread Simon Quigley
Before this is sponsored, I would like to see Brian's comment on the
other bug addressed; does this need to go to Eoan, any other releases,
or Debian?

Thanks, and please resubscribe sponsors when this is answered.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1834211

Title:
  [SRU] gconf FTBFS in Bionic

Status in gconf package in Ubuntu:
  New

Bug description:
  [Impact]

  Two issues make gconf FTBFS in Bionic:

  - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26
  - missing dh-python in B-D

  The debdiff attached below fixes these issues and makes gconf build
  properly.

  [Test Case]

  Just install the needed build dependencies and try to build gconf. It
  will fail with an error from gtk-doc.make. Second issue: if gtk-
  doc.make is patched, the build will fail if dh-python isn't installed.

  [Regression Potential]

  None, you can't break it more than FTBFS :)

  [Other Info]

  Fixes are backported from Cosmic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

2019-07-02 Thread Simon Quigley
Unsubscribing the Sponsors Team as there is no debdiff to sponsor. Poked
the Security Team.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833479

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

Status in jackd2 package in Ubuntu:
  New
Status in jackd2 package in Debian:
  New

Bug description:
  After upgrading to Ubuntu 19.04, I started experiencing sporadic
  crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded
  alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin
  is enabled by default in /etc/alsa/conf.d/50-jack.conf.

  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.

  When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again
  in it's cleanup code. Since it's closing the same file descriptor
  twice, it interacts with other threads that have potentially opened
  file descriptors, and causes the crash.

  This same bug could potentially affect other multi-threaded programs
  that enumerate ALSA devices.

  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1825786] Re: Please merge xkeyboard-config 2.26-2 (main) from Debian unstable (main)

2019-04-22 Thread Simon Quigley
Uploaded.

For the future, please make sure to use the -v argument when generating
your source.changes file for merges.

Thanks!

** Changed in: xkeyboard-config (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1825786

Title:
  Please merge xkeyboard-config 2.26-2 (main) from Debian unstable
  (main)

Status in xkeyboard-config package in Ubuntu:
  Fix Committed

Bug description:
  Proposed upload available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/xkeyboard-config

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1825786/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

2019-04-20 Thread Simon Quigley
Uploaded to Eoan.

If this needs to be SRUed, please adjust the bug description to follow
the template:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

Thanks!

** Changed in: ppp (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ppp in Ubuntu.
https://bugs.launchpad.net/bugs/1778946

Title:
  No dns resolution after closing a vpn/pptp connection

Status in ppp package in Ubuntu:
  In Progress
Status in ppp package in Debian:
  New

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1778946/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1799647] Re: Patch: Add configuration for german provider winSIM

2019-04-20 Thread Simon Quigley
Unsubscribing sponsors, please submit this upstream first.

Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mobile-broadband-provider-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1799647

Title:
  Patch: Add configuration for german provider winSIM

Status in mobile-broadband-provider-info package in Ubuntu:
  New

Bug description:
  I was unable to contribute a patch to the upstream gnome package:
  
https://wiki.gnome.org/Projects/NetworkManager/MobileBroadband/ServiceProviders
  (They seem to have migrated their git servers away)

  I still think this little config change adds value to Ubuntu users, hence I 
am opening this issue.
  Find the patchfile attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1799647/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1786881] Re: Languages always shown with English names

2019-04-20 Thread Simon Quigley
Unsubscribing the sponsors team because there is nothing to sponsor.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1786881

Title:
  Languages always shown with English names

Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  [Impact]
  Selecting a language from Settings always shows the names in English (e.g. 
German) instead of the name in the native language (e.g. Deutsch).

  [Test Case]
  1. Open Settings
  2. Go to "Region & Language" panel
  3. Click on "Language"

  Expected result:
  A list of languages is available, using the native language for each item, 
e.g. "English, Deutsch, ..."

  Observed result:
  A list of languages is available, using the English translations for each 
item, e.g. "English, German, ..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1786881/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1781597] Re: [SRU] WoWLAN settings are not supported

2019-04-20 Thread Simon Quigley
Unsubscribing the Ubuntu Sponsors Team, there is nothing to sponsor.

Bump on the Bionic SRU, is that still going to happen?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1781597

Title:
  [SRU] WoWLAN settings are not supported

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Triaged
Status in network-manager source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  WoWLAN lets us wake up the system by sending wake packets over the
  wifi connection. This is something requested by some OEM projects, for
  bionic server images.

  NM 1.12 supports configuring this feature, so this can be achieved by
  backporting that support to 1.10 (bionic version). These are the MPs
  for cosmic and bionic:

  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468
  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465

  [Test Case]

  First, the wifi card must support WoWLAN. This can be checked by
  running

  $ iw phy

  and searching for "WoWLAN support:" in the output. If it is supported,
  with the patch applied a connection configured with wowlan can be
  created with:

  $ sudo nmcli d wifi connect  password 
  $ sudo nmcli c modify  802-11-wireless.wake-on-wlan 8
  $ sudo nmcli c down 
  $ sudo nmcli c up 

  We can check with 'iw' that WoWLAN is active for the connection:

  $ iw phy phy0 wowlan show
  WoWLAN is enabled:
   * wake up on magic packet

  In this case we have configured the connection to wake up the system
  when a 'magic' packet is received. We can then suspend the system with

  $ sudo systemctl suspend

  And we should be able to wake the system from another device with the
  command

  $ sudo etherwake -i  

  [Regression Potential]

  Although the patch is not especially small, it is a backport of
  changes that have been merged upstream, with very little modifications
  to make it compile in 1.10. It is also a rather isolated feature that
  should not conflict with existing ones. The feature will be activated
  only if configured from the command line, so the risk of regressions
  should be small. Note also that the patch will be removed as soon as
  Ubuntu moves to NM 1.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1757746] Re: Please port your package away from Qt 4

2018-11-10 Thread Simon Quigley
Done.

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1757746

Title:
  Please port your package away from Qt 4

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support
  case.

  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 (like this one) must either get ported
  to Qt 5 and uploaded to the development release or get removed (by
  means of demotion to -proposed or removal of the package) before the
  19.04 release. If it is possible to port your package by the 18.10
  release, please do so.

  If you have any questions about porting or this transition, please ask
  in #ubuntu-qt (preferred) or directly ping me

  [1] https://wiki.debian.org/Qt4Removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1757746/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1799001] [NEW] Theming does not work on LXQt

2018-10-20 Thread Simon Quigley
Public bug reported:

[Impact]

Without this change, LibreOffice does not correctly use the Breeze
theme, which is needed for consistency with the rest of the Lubuntu,
LXQt-based desktop. At times, it is even hard to use because of the
inconsistent theming which can hide buttons at times.

[Test Case]

Update to the version of LibreOffice with this patch and open it on a
Lubuntu 18.10 installation. It should use the Breeze theming rather than
the stock GTK theming on startup.

[Regression Potential]

Little to none. If for some reason the criteria that is used to check
for the LXQt desktop no longer works, which is unlikely in a stable
release, this will no longer work.

[Other Info]

I submitted these upstream (as my first patches \o/):
https://gerrit.libreoffice.org/61641
https://gerrit.libreoffice.org/61751

** Affects: libreoffice (Ubuntu)
 Importance: Medium
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Affects: libreoffice (Ubuntu Cosmic)
 Importance: Medium
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Also affects: libreoffice (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: libreoffice (Ubuntu Cosmic)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: libreoffice (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: libreoffice (Ubuntu Cosmic)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1799001

Title:
  Theming does not work on LXQt

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  Without this change, LibreOffice does not correctly use the Breeze
  theme, which is needed for consistency with the rest of the Lubuntu,
  LXQt-based desktop. At times, it is even hard to use because of the
  inconsistent theming which can hide buttons at times.

  [Test Case]

  Update to the version of LibreOffice with this patch and open it on a
  Lubuntu 18.10 installation. It should use the Breeze theming rather
  than the stock GTK theming on startup.

  [Regression Potential]

  Little to none. If for some reason the criteria that is used to check
  for the LXQt desktop no longer works, which is unlikely in a stable
  release, this will no longer work.

  [Other Info]

  I submitted these upstream (as my first patches \o/):
  https://gerrit.libreoffice.org/61641
  https://gerrit.libreoffice.org/61751

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1799001/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1796516] Re: WiFi connections are broken after update to network-manager 1.12.4

2018-10-06 Thread Simon Quigley
And, now I'm confused, because after a reboot it works fine.

Heisenbug, fun.

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1796516

Title:
  WiFi connections are broken after update to network-manager 1.12.4

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  After updating to 1.12.4-1ubuntu1, several Lubuntu users have reported
  WiFi is broken. I can reproduce this with one of my laptops.

  Bringing the connection up with nmcli reveals this:

  $ nmcli connection up id MY\ SUPER\ SECRET\ SSID
  Error: Connection activation failed: The Wi-Fi network could not be found

  After downgrading to 1.12.2-0ubuntu5 and running `sudo systemctl
  restart network-manager.service`, the WiFi connects without issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1796516/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1796516] Re: WiFi connections are broken after update to network-manager 1.12.4

2018-10-06 Thread Simon Quigley
Oh, wonderful, so I can't reproduce it under Kubuntu.

I'll still keep this open against network-manager though, because I can
reproduce it with nmcli under Lubuntu. So, I'll Git bisect the bad
change in network-manager.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1796516

Title:
  WiFi connections are broken after update to network-manager 1.12.4

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After updating to 1.12.4-1ubuntu1, several Lubuntu users have reported
  WiFi is broken. I can reproduce this with one of my laptops.

  Bringing the connection up with nmcli reveals this:

  $ nmcli connection up id MY\ SUPER\ SECRET\ SSID
  Error: Connection activation failed: The Wi-Fi network could not be found

  After downgrading to 1.12.2-0ubuntu5 and running `sudo systemctl
  restart network-manager.service`, the WiFi connects without issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1796516/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1796516] Re: WiFi connections are broken after update to network-manager 1.12.4

2018-10-06 Thread Simon Quigley
My next step is going to be to confirm this with other flavors; if it's
a generic issue, the next step will be trying to bisect where this went
wrong.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1796516

Title:
  WiFi connections are broken after update to network-manager 1.12.4

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After updating to 1.12.4-1ubuntu1, several Lubuntu users have reported
  WiFi is broken. I can reproduce this with one of my laptops.

  Bringing the connection up with nmcli reveals this:

  $ nmcli connection up id MY\ SUPER\ SECRET\ SSID
  Error: Connection activation failed: The Wi-Fi network could not be found

  After downgrading to 1.12.2-0ubuntu5 and running `sudo systemctl
  restart network-manager.service`, the WiFi connects without issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1796516/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1796516] [NEW] WiFi connections are broken after update to network-manager 1.12.4

2018-10-06 Thread Simon Quigley
Public bug reported:

After updating to 1.12.4-1ubuntu1, several Lubuntu users have reported
WiFi is broken. I can reproduce this with one of my laptops.

Bringing the connection up with nmcli reveals this:

$ nmcli connection up id MY\ SUPER\ SECRET\ SSID
Error: Connection activation failed: The Wi-Fi network could not be found

After downgrading to 1.12.2-0ubuntu5 and running `sudo systemctl restart
network-manager.service`, the WiFi connects without issue.

** Affects: network-manager (Ubuntu)
 Importance: Critical
 Status: Confirmed


** Tags: regression-update rls-cc-incoming

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Critical

** Changed in: network-manager (Ubuntu)
Milestone: None => ubuntu-18.10

** Tags added: regression-update rls-cc-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1796516

Title:
  WiFi connections are broken after update to network-manager 1.12.4

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After updating to 1.12.4-1ubuntu1, several Lubuntu users have reported
  WiFi is broken. I can reproduce this with one of my laptops.

  Bringing the connection up with nmcli reveals this:

  $ nmcli connection up id MY\ SUPER\ SECRET\ SSID
  Error: Connection activation failed: The Wi-Fi network could not be found

  After downgrading to 1.12.2-0ubuntu5 and running `sudo systemctl
  restart network-manager.service`, the WiFi connects without issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1796516/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 583577] Re: "View by Threads with Unread" results in no ability to read some messages

2018-09-29 Thread Simon Quigley
** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: thunderbird (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/583577

Title:
  "View by Threads with Unread" results in no ability to read some
  messages

Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  On a fairly regular basis Thunderbird will show me messages that I
  can't read or otherwise interact with when viewing in "Threads with
  Unread" mode.

  In the attached image there are several threads that clicking on the
  '+' sign has absolutely no action.  I cannot click the green circle to
  mark the messages as read either.

  This doesn't happen ALL the time, but seems to happen in particular
  when duplicate messages are delivered (in this case a yahoo! groups
  mailing list that occasionally sends duplicates)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.4+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Thu May 20 15:22:39 2010
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_CA.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/583577/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1504697] Re: Message>Move does not work first time

2018-09-03 Thread Simon Quigley
** Changed in: thunderbird (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1504697

Title:
  Message>Move does not work first time

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After starting tb, the first time I want to move a message with 
Message>Move nothing happens.
  The drop-down menu just sits there with the "Move" entry highlighted, but no 
sub-menu appears.

  I tried to do a screen shot, but that didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: thunderbird 1:38.3.0+build1-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16
  Uname: Linux 3.16.0-50-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  humphrey   1508 F pulseaudio
   /dev/snd/controlC1:  humphrey   1508 F pulseaudio
  BuildID: 20150930122345
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sat Oct 10 10:20:30 2015
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-09-08 (31 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.101  metric 
1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources:
   prefs.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/000system.js
  Profiles: Profile0 (Default) - LastVersion=38.3.0/20150930122345 (In use)
  RelatedPackageVersions:
   totem-mozilla 3.10.1-1ubuntu4
   rhythmbox-mozilla 3.0.2-0ubuntu2
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.4
  dmi.board.name: 0N185P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.4:bd04/17/2009:svnDellInc.:pnVostro420Series:pvr:rvnDellInc.:rn0N185P:rvrA02:cvnDellInc.:ct3:cvr:
  dmi.product.name: Vostro 420 Series
  dmi.sys.vendor: Dell Inc.
  --- 
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  humphrey   2346 F pulseaudio
   /dev/snd/controlC1:  humphrey   2346 F pulseaudio
  BuildID: 20180710085647
  Channel: Unavailable
  DistroRelease: Ubuntu 16.04
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-12-13 (240 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.1.1 dev enp4s0  proto static  metric 100 
   169.254.0.0/16 dev enp4s0  scope link  metric 1000 
   192.168.1.0/24 dev enp4s0  proto kernel  scope link  src 192.168.1.103  
metric 100
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-3f3dab64-e8aa-4350-afd1-b05560180506
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: thunderbird 1:52.9.1+build3-0ubuntu0.16.04.1
  PackageArchitecture: amd64
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18
  Profiles: Profile0 (Default) - LastVersion=52.9.1/20180710085647 (In use)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RfKill:
   
  RunningIncompatibleAddons: False

[Desktop-packages] [Bug 1787325] Re: Update wayland-protocols to version 1.16

2018-08-16 Thread Simon Quigley
Unsubscribing ~ubuntu-sponsors because there's nothing to sponsor.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wayland-protocols in Ubuntu.
https://bugs.launchpad.net/bugs/1787325

Title:
  Update wayland-protocols to version 1.16

Status in wayland-protocols package in Ubuntu:
  New

Bug description:
  Update wayland-protocols to version 1.16

  The upstream mutter (v3.29.91) code now requires this version.

  https://github.com/wayland-project/wayland-protocols/releases/tag/1.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland-protocols/+bug/1787325/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1749283] Re: configured stats_temp_directory does not get created after reboot

2018-08-16 Thread Simon Quigley
Unsubscribing sponsors for now; Brian is right.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1749283

Title:
  configured stats_temp_directory does not get created after reboot

Status in postgresql-common package in Ubuntu:
  Won't Fix
Status in resource-agents package in Ubuntu:
  In Progress
Status in postgresql-common source package in Xenial:
  Won't Fix
Status in resource-agents source package in Xenial:
  New
Status in postgresql-common source package in Artful:
  Won't Fix
Status in resource-agents source package in Artful:
  New
Status in postgresql-common source package in Bionic:
  Won't Fix
Status in resource-agents source package in Bionic:
  New
Status in postgresql-common package in Debian:
  New

Bug description:
  Default postgres installation in Ubuntu (and Debian) configures
  stats_temp_directory inside /var/run/postgresql:

  $ grep stats_temp /etc/postgresql/10/main/postgresql.conf 
  stats_temp_directory = '/var/run/postgresql/10-main.pg_stat_tmp'

  However, this directory is not created after reboot.

  In most cases this is not a problem as systemd starts postgres via
  pg_ctlcluster, a "multiversion/cluster aware pg_ctl wrapper", and
  pg_ctlcluster will create missing directories before starting
  postgres.

  But in cases where systemd is not starting postgres this is a problem.
  Specifically, when postgres is controlled by pacemaker (using postgres 
resource agent for pacemaker) it is started using pg_ctl wrapper. pg_ctl won't 
create missing directories and therefore postgres fails to start.

  The simplest solution for this issue is to have systemd recreate
  missing directories via /usr/lib/tmpfiles.d/postgresql.conf file.

  Currently only /var/run/postgresql and /var/log/postgresql are created
  using systemd-tmpfiles.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1749283/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1744941] Re: gnome-software crashes in as_app_parse_desktop_file

2018-08-16 Thread Simon Quigley
Unsubscribing sponsors as there's nothing left to sponsor.

Artful is also EOL.

Ping, Iain and Robie.

** Changed in: appstream-glib (Ubuntu Artful)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1744941

Title:
  gnome-software crashes in as_app_parse_desktop_file

Status in appstream-glib package in Ubuntu:
  Fix Released
Status in appstream-glib source package in Xenial:
  In Progress
Status in appstream-glib source package in Artful:
  Won't Fix
Status in appstream-glib source package in Bionic:
  Fix Released

Bug description:
  [ Impact ]

  Malformed .desktop files might causes crashes because
  the returned list is NULL.

  [ Test case ]
   - Download and copy in one of your XDG_DATA_DIRS (i.e. 
~/.local/share/applications)
 this .desktop file:
 
https://github.com/hughsie/appstream-glib/files/1656100/org.gnome.frogr.desktop.gz
   - Run gnome-software it must not crash.

  [ Regression potential ]

  Missing metadata from .desktop files, but really this is just a null-
  checks fix, so not really anything might go worse.

  
  

  See more at upstream bug: https://github.com/hughsie/appstream-
  glib/pull/221

  This affects all the releases since xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1744941/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1385903] Re: imagemagick crashes with "stack smashing detected"

2018-08-16 Thread Simon Quigley
Security sponsors should be subscribed, not just sponsors.

It should get attention soon.

Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libjpeg-turbo in Ubuntu.
https://bugs.launchpad.net/bugs/1385903

Title:
  imagemagick crashes with "stack smashing detected"

Status in libjpeg-turbo package in Ubuntu:
  Confirmed
Status in libjpeg-turbo source package in Precise:
  Won't Fix
Status in libjpeg-turbo source package in Trusty:
  Confirmed
Status in libjpeg-turbo source package in Utopic:
  Won't Fix
Status in libjpeg-turbo source package in Vivid:
  Won't Fix

Bug description:
  Every now and then imagemagick convert crashes like this:

  $ convert -rotate 270 003632r270.jpg koe.jpg
  *** stack smashing detected ***: convert terminated
  Aborted (core dumped)

  This is perfectly reproducible and happens in every Ubuntu 14.04 box
  I have at hand that has ImageMagick in it, but not in 12.04.
  I'll attach the file used in above example (I have several more
  in case someone wants them).
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tt 2149 F pulseaudio
  CurrentDesktop: LXDE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  IwConfig:
   br0   no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic 
root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/09/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 945GM
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2018-08-16 Thread Simon Quigley
Artful is End Of Life, and thus, there is nothing else to sponsor;
sorry.

Please resubscribe ~ubuntu-sponsors if there's something else to
sponsor.

** Changed in: network-manager (Ubuntu Artful)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1733321

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2018-08-16 Thread Simon Quigley
Artful is EOL.

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1714518

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Trusty:
  Triaged
Status in gtk+3.0 source package in Xenial:
  Triaged
Status in gtk+3.0 source package in Artful:
  Won't Fix

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1696418] Re: gnome-help/shell-introduction.page link to removed files

2018-08-16 Thread Simon Quigley
Sponsoring this now with minor tweaks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-user-docs in Ubuntu.
https://bugs.launchpad.net/bugs/1696418

Title:
  gnome-help/shell-introduction.page link to removed files

Status in gnome-user-docs package in Ubuntu:
  Invalid
Status in language-pack-gnome-es-base package in Ubuntu:
  Invalid
Status in gnome-user-docs source package in Trusty:
  In Progress
Status in language-pack-gnome-es-base source package in Trusty:
  Won't Fix

Bug description:
  [Impact]

  The latest language pack update for trusty at 2016-07-20 did (for
  unknown reason) not include the localized gnome-help pages, so gnome-
  help is displayed in English whatever the session language is.

  The proposed upload sets the NO_PKG_MANGLE variable, so the package is
  built without language stripping. This works around the failure with
  the language packs.

  [Test Case]

  Open gnome-help with a non-English language (using Spanish as
  example):

  LANGUAGE=es yelp help:gnome-help

  Current package: Showed in English

  Proposed package: Showed in Spanish

  [Regression Potential]

  Negligible. This is in practice a no-change rebuild.

  [Original description]

  p.e.:
  /usr/share/help/es/gnome-help/shell-introduction.page
  is a link to /usr/share/help-langpack/es/gnome-help/shell-introduction.page

  A lot of pages became broken links since some update of language-pack-
  gnome-*-base lost target files.

  Most of missing files are listed at:
  https://packages.ubuntu.com/trusty/all/language-pack-gnome-*-base/filelist

  (Replace "*" by any packaged language, such as "es")

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-user-guide 3.8.2-1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CasperVersion: 1.340
  CurrentDesktop: GNOME
  Date: Wed Jun  7 13:15:08 2017
  LiveMediaBuild: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-user-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1696418/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1770587] Re: creation of new email account impossible in thunderbird

2018-08-06 Thread Simon Quigley
** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1770587

Title:
  creation of new email account impossible in thunderbird

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  With Ubuntu 18.04, creation of new email account is not possible.
  You have a first screen "Would you like a new email address?" and no button 
is active

  I have restarted with add-on disabled but same issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.7.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jmax   2698 F pulseaudio
  BuildID: 20180416164209
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 11 10:07:03 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Français Language Pack - langpack...@thunderbird.mozilla.org
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-01-31 (830 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IpRoute:
   default via 192.168.0.254 dev wlo1 proto dhcp metric 600 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.32 metric 600
  MostRecentCrashID: bp-da66c229-e498-447a-8233-47b610170721
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.7.0/20180416164209 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (12 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3581
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1A:bd07/20/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124461620100:rvnHewlett-Packard:rn3581:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058F1124461620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1770587/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1782579] Re: lubuntu 32bit daily image 2018-07-18 nmtui-edit won't show; needs xterm (not on image)

2018-07-19 Thread Simon Quigley
** Package changed: xterm (Ubuntu) => nm-tray (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xterm in Ubuntu.
https://bugs.launchpad.net/bugs/1782579

Title:
  lubuntu 32bit daily image 2018-07-18 nmtui-edit won't show; needs
  xterm (not on image)

Status in nm-tray package in Ubuntu:
  New

Bug description:
  i've listed it as relating to XTERM, but in my opinion the daily image
  needs XTERM, and it's missing..

  booting the x86 (32bit) daily image 2018-07-18, and I couldn't access
  "Edit Connections" or "Connection Information" in the bottom right
  applet.

  I compared to a 18.10 image on desktop (which has other DEsktops
  also); it loaded xterm and display info.  I went back to this machine
  (32bit, dell d610) and `sudo apt install xterm` and then the
  "connection information", plus "edit connections" applet opened a
  window & let me do what I wanted to (or see info for connection info).

  missing XTERM package from daily-image in my opinion.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xterm 330-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic i686
  ApportVersion: 2.20.10-0ubuntu5
  Architecture: i386
  CasperVersion: 1.394
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Jul 19 13:45:04 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller 
[8086:2592] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 915GM/GMS/910GML Express Graphics Controller 
[1028:0182]
 Subsystem: Dell Mobile 915GM/GMS/910GML Express Graphics Controller 
[1028:0182]
  LiveMediaBuild: Lubuntu 18.10 "Cosmic Cuttlefish" - Alpha i386 (20180718)
  MachineType: Dell Inc. Latitude D610
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd quiet splash ---
  SourcePackage: xterm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2005
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0D4571
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd03/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0D4571:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D610
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nm-tray/+bug/1782579/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 983777] Re: chromium doesn't see system proxy config

2018-07-06 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Kubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Kubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Kubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 983777

and any other logs that are relevant for this particular issue.

** Changed in: chromium-browser
   Status: Unknown => Incomplete

** Changed in: kubuntu-ppa
   Status: New => Incomplete

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/983777

Title:
  chromium doesn't see system proxy config

Status in Chromium Browser:
  Incomplete
Status in Kubuntu PPA:
  Incomplete
Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  The chromium browser only works when I pass my proxy settings using the proxy 
server parameter: 
  chromium-browser --proxy-server=http://localhost:3128

  Other browsers (firefox, rekonq) just pick up my system wide browser
  settings.

  This issue has been fixed before,
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/858252

  google-chrome has the same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/983777/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1779526] Re: Please merge 2.24.32-2 from Debian Sid

2018-07-05 Thread Simon Quigley
https://launchpad.net/ubuntu/+source/gtk+2.0/2.24.32-2ubuntu1

** Changed in: gtk+2.0 (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1779526

Title:
  Please merge 2.24.32-2 from Debian Sid

Status in gtk+2.0 package in Ubuntu:
  Fix Committed

Bug description:
  2.24.32-2 has been uploaded to Debian Sid fixing a few bugs. Let's
  merge it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1779526/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1779531] Re: Please merge 1.4.0-1 from Debian Sid

2018-07-05 Thread Simon Quigley
Better?

** Patch added: "2-1.4.0-1-to-1.4.0-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1779531/+attachment/5160201/+files/2-1.4.0-1-to-1.4.0-1ubuntu1.debdiff

** Changed in: xinit (Ubuntu)
   Status: Incomplete => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xinit in Ubuntu.
https://bugs.launchpad.net/bugs/1779531

Title:
  Please merge 1.4.0-1 from Debian Sid

Status in xinit package in Ubuntu:
  In Progress

Bug description:
  A new upstream release is available in Debian. Let's merge it.

  Here are the changelog entries since the last upload:

  xinit (1.4.0-1) unstable; urgency=medium

[ Timo Aaltonen ]
* postinst: Check that xinitrc exists before trying to chmod it. (LP:
  #1562033)

[ Julien Cristau ]
* Update Vcs-* control fields for move to salsa.
* Remove Cyril from Uploaders.
* Switch wiki.debian.org, bugs.debian.org and xorg.freedesktop.org URLs in
  packaging to https.
* Let uscan verify tarball signatures.
* New upstream release.
  + 07_Pass-keeptty-on-current-tty.patch, 08_pick-free-display.patch:
delete, applied upstream

   -- Julien Cristau   Mon, 19 Mar 2018 08:41:43
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1779531/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1779531] Re: Please merge 1.4.0-1 from Debian Sid

2018-07-01 Thread Simon Quigley
Here is a debdiff applicable to 1.4.0-1.

** Patch added: "1-1.4.0-1-to-1.4.0-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1779531/+attachment/5158304/+files/1-1.4.0-1-to-1.4.0-1ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xinit in Ubuntu.
https://bugs.launchpad.net/bugs/1779531

Title:
  Please merge 1.4.0-1 from Debian Sid

Status in xinit package in Ubuntu:
  In Progress

Bug description:
  A new upstream release is available in Debian. Let's merge it.

  Here are the changelog entries since the last upload:

  xinit (1.4.0-1) unstable; urgency=medium

[ Timo Aaltonen ]
* postinst: Check that xinitrc exists before trying to chmod it. (LP:
  #1562033)

[ Julien Cristau ]
* Update Vcs-* control fields for move to salsa.
* Remove Cyril from Uploaders.
* Switch wiki.debian.org, bugs.debian.org and xorg.freedesktop.org URLs in
  packaging to https.
* Let uscan verify tarball signatures.
* New upstream release.
  + 07_Pass-keeptty-on-current-tty.patch, 08_pick-free-display.patch:
delete, applied upstream

   -- Julien Cristau   Mon, 19 Mar 2018 08:41:43
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1779531/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1779531] [NEW] Please merge 1.4.0-1 from Debian Sid

2018-07-01 Thread Simon Quigley
Public bug reported:

A new upstream release is available in Debian. Let's merge it.

Here are the changelog entries since the last upload:

xinit (1.4.0-1) unstable; urgency=medium

  [ Timo Aaltonen ]
  * postinst: Check that xinitrc exists before trying to chmod it. (LP:
#1562033)

  [ Julien Cristau ]
  * Update Vcs-* control fields for move to salsa.
  * Remove Cyril from Uploaders.
  * Switch wiki.debian.org, bugs.debian.org and xorg.freedesktop.org URLs in
packaging to https.
  * Let uscan verify tarball signatures.
  * New upstream release.
+ 07_Pass-keeptty-on-current-tty.patch, 08_pick-free-display.patch:
  delete, applied upstream

 -- Julien Cristau   Mon, 19 Mar 2018 08:41:43
+0100

** Affects: xinit (Ubuntu)
 Importance: Wishlist
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xinit in Ubuntu.
https://bugs.launchpad.net/bugs/1779531

Title:
  Please merge 1.4.0-1 from Debian Sid

Status in xinit package in Ubuntu:
  In Progress

Bug description:
  A new upstream release is available in Debian. Let's merge it.

  Here are the changelog entries since the last upload:

  xinit (1.4.0-1) unstable; urgency=medium

[ Timo Aaltonen ]
* postinst: Check that xinitrc exists before trying to chmod it. (LP:
  #1562033)

[ Julien Cristau ]
* Update Vcs-* control fields for move to salsa.
* Remove Cyril from Uploaders.
* Switch wiki.debian.org, bugs.debian.org and xorg.freedesktop.org URLs in
  packaging to https.
* Let uscan verify tarball signatures.
* New upstream release.
  + 07_Pass-keeptty-on-current-tty.patch, 08_pick-free-display.patch:
delete, applied upstream

   -- Julien Cristau   Mon, 19 Mar 2018 08:41:43
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1779531/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1624022] Re: Alias 'browse' to xdg-open

2018-07-01 Thread Simon Quigley
Has this been forwarded to Debian yet?

It's the last bit of the Ubuntu delta, and if we could push that
upstream, we'll have the ability to sync.

Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1624022

Title:
  Alias 'browse' to xdg-open

Status in xdg-utils package in Ubuntu:
  Fix Released
Status in xdg-utils source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  The 'sensible-browser' and 'xdg-open' commands are very useful, but
  it's a bit unwieldy to use everywhere in docs. How about aliasing to
  the simple 'browse', so I can recommend things like:

sudo apt install foo; browse http://locahost:2022/

  That would be crisp clean and friendly for current users.

  [Test Case]

  There is currently no simple 'browse' command.

  [Regression Potential]

  None. There are no name collisions with /usr/bin/browse in Debian or
  Ubuntu.

  [ Other Info ]

  Although the original request was to alias 'sensible-browser' it was
  decided that 'xdg-open' has the more consistent behaviour (in terms of
  selecting the correct web browser to use) and also falls back to
  'sensible-browser'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1624022/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1779529] Re: Please merge 1.1.3-1 from Debian Sid

2018-07-01 Thread Simon Quigley
Here's a debdiff which, when applied, builds fine on my system.

It's applicable to 1.1.3-1.

** Patch added: "1.1.3-1-to-1.1.3-1ubuntu1-1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1779529/+attachment/5158303/+files/1.1.3-1-to-1.1.3-1ubuntu1-1.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1779529

Title:
  Please merge 1.1.3-1 from Debian Sid

Status in xdg-utils package in Ubuntu:
  In Progress

Bug description:
  There's a new upstream release available in Debian. Let's merge it.

  Changelog entries since the last merge:

  xdg-utils (1.1.3-1) unstable; urgency=medium

* New upstream release.
  - Avoid argument injection vulnerability in open_envvar.
Fixes CVE-2017-18266, closes: #898317.
* Remove 01-open-lxqt.patch applied by upstream.
* Fix word expansion on KDE in xdg-email. Closes: #898999.
* Bump debhelper and standards version, no modifications for this.

   -- Nicholas Guriev   Sun, 20 May 2018 01:18:48 +0300

  xdg-utils (1.1.2-2) unstable; urgency=medium

* Update Vcs for salsa.debian.org.
* 01-open-lxqt.patch: Fix support in LXQt, which isn't the same as LXDE.
  Closes: #884436.

   -- Emilio Pozuelo Monfort   Tue, 27 Feb 2018
  10:25:43 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1779529/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1779529] [NEW] Please merge 1.1.3-1 from Debian Sid

2018-07-01 Thread Simon Quigley
Public bug reported:

There's a new upstream release available in Debian. Let's merge it.

Changelog entries since the last merge:

xdg-utils (1.1.3-1) unstable; urgency=medium

  * New upstream release.
- Avoid argument injection vulnerability in open_envvar.
  Fixes CVE-2017-18266, closes: #898317.
  * Remove 01-open-lxqt.patch applied by upstream.
  * Fix word expansion on KDE in xdg-email. Closes: #898999.
  * Bump debhelper and standards version, no modifications for this.

 -- Nicholas Guriev   Sun, 20 May 2018 01:18:48 +0300

xdg-utils (1.1.2-2) unstable; urgency=medium

  * Update Vcs for salsa.debian.org.
  * 01-open-lxqt.patch: Fix support in LXQt, which isn't the same as LXDE.
Closes: #884436.

 -- Emilio Pozuelo Monfort   Tue, 27 Feb 2018 10:25:43
+0100

** Affects: xdg-utils (Ubuntu)
 Importance: Wishlist
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1779529

Title:
  Please merge 1.1.3-1 from Debian Sid

Status in xdg-utils package in Ubuntu:
  In Progress

Bug description:
  There's a new upstream release available in Debian. Let's merge it.

  Changelog entries since the last merge:

  xdg-utils (1.1.3-1) unstable; urgency=medium

* New upstream release.
  - Avoid argument injection vulnerability in open_envvar.
Fixes CVE-2017-18266, closes: #898317.
* Remove 01-open-lxqt.patch applied by upstream.
* Fix word expansion on KDE in xdg-email. Closes: #898999.
* Bump debhelper and standards version, no modifications for this.

   -- Nicholas Guriev   Sun, 20 May 2018 01:18:48 +0300

  xdg-utils (1.1.2-2) unstable; urgency=medium

* Update Vcs for salsa.debian.org.
* 01-open-lxqt.patch: Fix support in LXQt, which isn't the same as LXDE.
  Closes: #884436.

   -- Emilio Pozuelo Monfort   Tue, 27 Feb 2018
  10:25:43 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1779529/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1779526] [NEW] Please merge 2.24.32-2 from Debian Sid

2018-07-01 Thread Simon Quigley
Public bug reported:

2.24.32-2 has been uploaded to Debian Sid fixing a few bugs. Let's merge
it.

** Affects: gtk+2.0 (Ubuntu)
 Importance: Wishlist
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1779526

Title:
  Please merge 2.24.32-2 from Debian Sid

Status in gtk+2.0 package in Ubuntu:
  In Progress

Bug description:
  2.24.32-2 has been uploaded to Debian Sid fixing a few bugs. Let's
  merge it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1779526/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1772919] Re: pam-gnome-keyring.so reveals user’s password credential as a plaintext form

2018-06-30 Thread Simon Quigley
Setting to new because they submitted it upstream.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1772919

Title:
  pam-gnome-keyring.so reveals user’s password credential as a plaintext
  form

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  When I perform memory dump of session-child process, user’s login
  credential, including user accounts and their password, is revealed as
  a plaintext form.

  In ‘pam_sm_authenticate’ function, user’s password is stored in the
  heap memory of ‘pam_handle->data” to perform unlock the keyring in
  later.

  After unlocking the keyring, the pam module does not free/overwrite
  the memory area though the password is no longer used.

  We thus could find user’s login credentials.

  This raises concerns over the credential being misused for illegal
  behavior, such as acquiring user’s session key.

  It would be better to clean the heap memory.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 23 22:53:12 2018
  InstallationDate: Installed on 2018-04-20 (32 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.gnome-keyring-ssh.log: grep: 
/home/sungjungk/.config/autostart/gnome-keyring-ssh.desktop: No such file or 
directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1772919/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1772919] Re: pam-gnome-keyring.so reveals user’s password credential as a plaintext form

2018-06-30 Thread Simon Quigley
Setting to new because he submitted it upstream.

** Changed in: gnome-keyring (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1772919

Title:
  pam-gnome-keyring.so reveals user’s password credential as a plaintext
  form

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  When I perform memory dump of session-child process, user’s login
  credential, including user accounts and their password, is revealed as
  a plaintext form.

  In ‘pam_sm_authenticate’ function, user’s password is stored in the
  heap memory of ‘pam_handle->data” to perform unlock the keyring in
  later.

  After unlocking the keyring, the pam module does not free/overwrite
  the memory area though the password is no longer used.

  We thus could find user’s login credentials.

  This raises concerns over the credential being misused for illegal
  behavior, such as acquiring user’s session key.

  It would be better to clean the heap memory.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 23 22:53:12 2018
  InstallationDate: Installed on 2018-04-20 (32 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.gnome-keyring-ssh.log: grep: 
/home/sungjungk/.config/autostart/gnome-keyring-ssh.desktop: No such file or 
directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1772919/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1776808] Re: Please merge 5.6-4 from Debian Sid

2018-06-13 Thread Simon Quigley
Here is the merge uploaded to my PPA:
https://launchpad.net/~tsimonq2/+archive/ubuntu/upload-
testing/+sourcepub/9178757/+listing-archive-extra

It builds fine.

Unless there are objections, please upload.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1776808

Title:
  Please merge 5.6-4 from Debian Sid

Status in brltty package in Ubuntu:
  In Progress

Bug description:
  Debian Sid has a new upload of brltty which contains some useful
  fixes. Let's merge it.

  Here is the full changelog entry:

  brltty (5.6-4) unstable; urgency=medium

* Cherry-pick python brlapi close fix, to avoid orca accumulating brlapi
  connections.
* Cherry-pick at-spi2 initialization fix.
* Cherry-pick xbrlapi patch to be able to type any keysym.
* Bump Standards-Version to 4.1.4 (no changes).

   -- Samuel Thibault   Thu, 17 May 2018 19:28:00
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1776808/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1776808] [NEW] Please merge 5.6-4 from Debian Sid

2018-06-13 Thread Simon Quigley
Public bug reported:

Debian Sid has a new upload of brltty which contains some useful fixes.
Let's merge it.

Here is the full changelog entry:

brltty (5.6-4) unstable; urgency=medium

  * Cherry-pick python brlapi close fix, to avoid orca accumulating brlapi
connections.
  * Cherry-pick at-spi2 initialization fix.
  * Cherry-pick xbrlapi patch to be able to type any keysym.
  * Bump Standards-Version to 4.1.4 (no changes).

 -- Samuel Thibault   Thu, 17 May 2018 19:28:00
+0200

** Affects: brltty (Ubuntu)
 Importance: Wishlist
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Changed in: brltty (Ubuntu)
   Status: New => In Progress

** Changed in: brltty (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: brltty (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1776808

Title:
  Please merge 5.6-4 from Debian Sid

Status in brltty package in Ubuntu:
  In Progress

Bug description:
  Debian Sid has a new upload of brltty which contains some useful
  fixes. Let's merge it.

  Here is the full changelog entry:

  brltty (5.6-4) unstable; urgency=medium

* Cherry-pick python brlapi close fix, to avoid orca accumulating brlapi
  connections.
* Cherry-pick at-spi2 initialization fix.
* Cherry-pick xbrlapi patch to be able to type any keysym.
* Bump Standards-Version to 4.1.4 (no changes).

   -- Samuel Thibault   Thu, 17 May 2018 19:28:00
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1776808/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 120788] Re: (needs x11 protocol update) XKB cannot map multiple keyboard models

2018-06-13 Thread Simon Quigley
** Changed in: x11proto-core (Ubuntu)
   Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11proto-core in Ubuntu.
https://bugs.launchpad.net/bugs/120788

Title:
  (needs x11 protocol update) XKB cannot map multiple keyboard models

Status in gnome-control-center:
  Unknown
Status in xkeyboard-config:
  Invalid
Status in x11proto-core package in Ubuntu:
  Incomplete

Bug description:
  The X.org XKB protocol has a limitation in that it can map only one
  keyboard model and a max of 4 layouts (bug #56912) in a given X
  session.  The data type used to communicate keyboard mappings between
  the server and client apps simply doesn't provide room for the data
  needed for multiple keyboards.  So a proper solution requires updating
  the X11 protocol to X12 (or at least X11.1), which is something that
  must be done upstream (further, there is risk that changing the
  protocol could cause widespread breakage in client applications if not
  done carefully.)

  So, in other words, this is not something that can be trivially fixed,
  but it's a known issue and will hopefully be dealt with some day.

  [Original Report]
  The gnome-keyboard-properties dialog allows me to define only 1 keyboard 
model; instead the model ought to be specific to each layout.

  I have an English keyboard (Logitech Internet Navigator Keyboard with
  105 keys) and also a French one (AZERTY with 104 keys).  I cannot
  properly define the French one because I cannot select an appropriate
  keyboard model for it without disrupting the definition of the English
  keyboard.  I can only define a single model system-wide.

  [lspci]
  00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory Controller 
[10de:005e] (rev a3)
Subsystem: ASUSTeK Computer Inc. A8N-E Mainboard [1043:815a]
  05:00.0 VGA compatible controller [0300]: nVidia Corporation G70 [GeForce 
7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA controller])

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/120788/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1770067] [NEW] Sync transmission 2.94-1 (main) from Debian unstable (main)

2018-05-08 Thread Simon Quigley
Public bug reported:

Please sync transmission 2.94-1 (main) from Debian unstable (main)

The only delta exists for Unity indicator support, and Ayatana support
has been merged into Debian, so this is no longer needed.

Changelog entries since current cosmic version 2.92-3ubuntu2:

transmission (2.94-1) unstable; urgency=medium

  * New upstream release
  * refresh patches
  * debian/patches/8c8386a7f3f482a9c917f51d28e0042e55f56b3e.patch,
debian/patches/bts885151_fix_ftcbfs_ac_run_ifelse.patch
- dropped, released upstream
  * debian/copyright
- refresh copyright with `decopy`, most importantly add OpenSSL
  exception
  * debian/control
- replace libcurl4-gnutls-dev with libcurl4-openssl-dev as b-d, to reduce
  the memory usage of transmission-daemon; patch provided by Andrey Gursky;
  Closes: #865624

 -- Sandro Tosi <mo...@debian.org>  Sun, 06 May 2018 19:34:20 -0400

transmission (2.93-2) unstable; urgency=medium

  * debian/control
- add qt5-qmake:native to b-d, to make it cross buildable; patch by Helmut
  Grohne; Closes: #896699

 -- Sandro Tosi <mo...@debian.org>  Thu, 26 Apr 2018 22:54:36 -0400

transmission (2.93-1) unstable; urgency=medium

  * New upstream release; Closes: #890325, #857511, #895869
  * debian/patches/*
- drop patches merged upstream
  * debian/control
- bump Standards-Version to 4.1.4 (no changes needed)
- update Homepage field to use HTTPS
- update Vcs-* fields to point to salsa
  * enable Ayatana AppIndicator support; Closes: #894410
  * set QT_SELECT=qt5 rather than build-depending on qt5-default; patch by
Helmut Grohne; Closes: #887849

 -- Sandro Tosi <mo...@debian.org>  Sat, 21 Apr 2018 19:19:08 -0400

** Affects: transmission (Ubuntu)
 Importance: Wishlist
     Assignee: Simon Quigley (tsimonq2)
 Status: New

** Changed in: transmission (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: transmission (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1770067

Title:
  Sync transmission 2.94-1 (main) from Debian unstable (main)

Status in transmission package in Ubuntu:
  New

Bug description:
  Please sync transmission 2.94-1 (main) from Debian unstable (main)

  The only delta exists for Unity indicator support, and Ayatana support
  has been merged into Debian, so this is no longer needed.

  Changelog entries since current cosmic version 2.92-3ubuntu2:

  transmission (2.94-1) unstable; urgency=medium

* New upstream release
* refresh patches
* debian/patches/8c8386a7f3f482a9c917f51d28e0042e55f56b3e.patch,
  debian/patches/bts885151_fix_ftcbfs_ac_run_ifelse.patch
  - dropped, released upstream
* debian/copyright
  - refresh copyright with `decopy`, most importantly add OpenSSL
exception
* debian/control
  - replace libcurl4-gnutls-dev with libcurl4-openssl-dev as b-d, to reduce
the memory usage of transmission-daemon; patch provided by Andrey 
Gursky;
Closes: #865624

   -- Sandro Tosi <mo...@debian.org>  Sun, 06 May 2018 19:34:20 -0400

  transmission (2.93-2) unstable; urgency=medium

* debian/control
  - add qt5-qmake:native to b-d, to make it cross buildable; patch by Helmut
Grohne; Closes: #896699

   -- Sandro Tosi <mo...@debian.org>  Thu, 26 Apr 2018 22:54:36 -0400

  transmission (2.93-1) unstable; urgency=medium

* New upstream release; Closes: #890325, #857511, #895869
* debian/patches/*
  - drop patches merged upstream
* debian/control
  - bump Standards-Version to 4.1.4 (no changes needed)
  - update Homepage field to use HTTPS
  - update Vcs-* fields to point to salsa
* enable Ayatana AppIndicator support; Closes: #894410
* set QT_SELECT=qt5 rather than build-depending on qt5-default; patch by
  Helmut Grohne; Closes: #887849

   -- Sandro Tosi <mo...@debian.org>  Sat, 21 Apr 2018 19:19:08 -0400

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1770067/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1770059] Re: Please merge 5.6-3 from Debian Sid

2018-05-08 Thread Simon Quigley
Attached is a debdiff applicable to 5.6-3, which is the current version
in Sid.

** Patch added: "1-5.6-3-to-5.6-3ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1770059/+attachment/5136511/+files/1-5.6-3-to-5.6-3ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1770059

Title:
  Please merge 5.6-3 from Debian Sid

Status in brltty package in Ubuntu:
  In Progress

Bug description:
  Debian Sid contains a new upstream release of brltty. Let's merge it.

  Changelog entries since the last Ubuntu upload:

  brltty (5.6-3) unstable; urgency=medium

* debian/patches/41-java-bytecode-compat.patch: Bump java compatability to
  1.6 and later (Closes: Bug#893102).

   -- Samuel Thibault   Fri, 16 Mar 2018 15:20:39
  +0100

  brltty (5.6-2) unstable; urgency=medium

* debian/copyright: Fix licence terms.

   -- Samuel Thibault   Tue, 13 Feb 2018 11:35:38
  +0100

  brltty (5.6-1) experimental; urgency=medium

* New upstream release.
  - debian/patches/api_startup.patch: Upstreamed.
  - debian/patches/git-07ecca2240c680373e9c2e5e38241edde9d1a677: Upstreamed.
  - debian/patches/brldefs-install.patch: Upstreamed.
  - debian/patches/git-ba42441d03c6145fe6859c90fb01b1fa16221a2f: Upstreamed.
  - debian/brltty-udeb.udev.rules: Add new device IDs.
  - debian/control: Add liblouis-dev build-dep.
  - debian/rules: Make brltty install appstream data.
* control: Avoid the ALSA PCM package on non-Linux.

   -- Samuel Thibault   Sun, 11 Feb 2018 17:18:14
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1770059/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1770059] [NEW] Please merge 5.6-3 from Debian Sid

2018-05-08 Thread Simon Quigley
Public bug reported:

Debian Sid contains a new upstream release of brltty. Let's merge it.

Changelog entries since the last Ubuntu upload:

brltty (5.6-3) unstable; urgency=medium

  * debian/patches/41-java-bytecode-compat.patch: Bump java compatability to
1.6 and later (Closes: Bug#893102).

 -- Samuel Thibault <sthiba...@debian.org>  Fri, 16 Mar 2018 15:20:39
+0100

brltty (5.6-2) unstable; urgency=medium

  * debian/copyright: Fix licence terms.

 -- Samuel Thibault <sthiba...@debian.org>  Tue, 13 Feb 2018 11:35:38
+0100

brltty (5.6-1) experimental; urgency=medium

  * New upstream release.
- debian/patches/api_startup.patch: Upstreamed.
- debian/patches/git-07ecca2240c680373e9c2e5e38241edde9d1a677: Upstreamed.
- debian/patches/brldefs-install.patch: Upstreamed.
- debian/patches/git-ba42441d03c6145fe6859c90fb01b1fa16221a2f: Upstreamed.
- debian/brltty-udeb.udev.rules: Add new device IDs.
- debian/control: Add liblouis-dev build-dep.
- debian/rules: Make brltty install appstream data.
  * control: Avoid the ALSA PCM package on non-Linux.

 -- Samuel Thibault <sthiba...@debian.org>  Sun, 11 Feb 2018 17:18:14
+0100

** Affects: brltty (Ubuntu)
 Importance: Wishlist
     Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Description changed:

  Debian Sid contains a new upstream release of brltty. Let's merge it.
+ 
+ Changelog entries since the last Ubuntu upload:
+ 
+ brltty (5.6-3) unstable; urgency=medium
+ 
+   * debian/patches/41-java-bytecode-compat.patch: Bump java compatability to
+ 1.6 and later (Closes: Bug#893102).
+ 
+  -- Samuel Thibault <sthiba...@debian.org>  Fri, 16 Mar 2018 15:20:39
+ +0100
+ 
+ brltty (5.6-2) unstable; urgency=medium
+ 
+   * debian/copyright: Fix licence terms.
+ 
+  -- Samuel Thibault <sthiba...@debian.org>  Tue, 13 Feb 2018 11:35:38
+ +0100
+ 
+ brltty (5.6-1) experimental; urgency=medium
+ 
+   * New upstream release.
+ - debian/patches/api_startup.patch: Upstreamed.
+ - debian/patches/git-07ecca2240c680373e9c2e5e38241edde9d1a677: Upstreamed.
+ - debian/patches/brldefs-install.patch: Upstreamed.
+ - debian/patches/git-ba42441d03c6145fe6859c90fb01b1fa16221a2f: Upstreamed.
+ - debian/brltty-udeb.udev.rules: Add new device IDs.
+ - debian/control: Add liblouis-dev build-dep.
+ - debian/rules: Make brltty install appstream data.
+   * control: Avoid the ALSA PCM package on non-Linux.
+ 
+  -- Samuel Thibault <sthiba...@debian.org>  Sun, 11 Feb 2018 17:18:14
+ +0100

** Changed in: brltty (Ubuntu)
   Status: New => In Progress

** Changed in: brltty (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: brltty (Ubuntu)
     Assignee: (unassigned) => Simon Quigley (tsimonq2)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1770059

Title:
  Please merge 5.6-3 from Debian Sid

Status in brltty package in Ubuntu:
  In Progress

Bug description:
  Debian Sid contains a new upstream release of brltty. Let's merge it.

  Changelog entries since the last Ubuntu upload:

  brltty (5.6-3) unstable; urgency=medium

* debian/patches/41-java-bytecode-compat.patch: Bump java compatability to
  1.6 and later (Closes: Bug#893102).

   -- Samuel Thibault <sthiba...@debian.org>  Fri, 16 Mar 2018 15:20:39
  +0100

  brltty (5.6-2) unstable; urgency=medium

* debian/copyright: Fix licence terms.

   -- Samuel Thibault <sthiba...@debian.org>  Tue, 13 Feb 2018 11:35:38
  +0100

  brltty (5.6-1) experimental; urgency=medium

* New upstream release.
  - debian/patches/api_startup.patch: Upstreamed.
  - debian/patches/git-07ecca2240c680373e9c2e5e38241edde9d1a677: Upstreamed.
  - debian/patches/brldefs-install.patch: Upstreamed.
  - debian/patches/git-ba42441d03c6145fe6859c90fb01b1fa16221a2f: Upstreamed.
  - debian/brltty-udeb.udev.rules: Add new device IDs.
  - debian/control: Add liblouis-dev build-dep.
  - debian/rules: Make brltty install appstream data.
* control: Avoid the ALSA PCM package on non-Linux.

   -- Samuel Thibault <sthiba...@debian.org>  Sun, 11 Feb 2018 17:18:14
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1770059/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS

2018-04-14 Thread Simon Quigley
Unsubscribing the Ubuntu Sponsors Team for now, due to Sebastien's
comment that more work needs to be done.

Please resubscribe the Sponsors Team once adequate tests have been
added.

Thank you.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-geoip in Ubuntu.
https://bugs.launchpad.net/bugs/1617535

Title:
  geoip.ubuntu.com does not utilize HTTPS

Status in ubuntu-geoip package in Ubuntu:
  Fix Released
Status in ubuntu-geoip source package in Trusty:
  Triaged
Status in ubuntu-geoip source package in Xenial:
  Triaged
Status in ubuntu-geoip source package in Artful:
  Triaged

Bug description:
  Impact
  --
  It's better to use https where we can. There were concerns about location 
leakage for users using a proxy (such as Tor).

  Test Case
  -

  Regression Potential
  
  As long as Canonical maintains https://geoip.ubuntu.com, things should be 
fine here. Minimal fix.

  
  Original Bug Report
  ---
  geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This 
can potentially be utilized by nation state adversaries to compromise user 
privacy. This service is called multiple times per day by the OS in order to 
track users.

  $ nc -zv geoip.ubuntu.com 80
  Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded!

  $ nc -zv -w 3 geoip.ubuntu.com 443
  nc: connect to geoip.ubuntu.com port 443 (tcp) timed out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-12 Thread Simon Quigley
** Also affects: xorg (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1763273

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1760435] Re: Use Ubuntu language packs for various Unity packages

2018-04-07 Thread Simon Quigley
Landed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1760435

Title:
  Use Ubuntu language packs for various Unity packages

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed
Status in unity-lens-applications package in Ubuntu:
  Confirmed
Status in unity-lens-files package in Ubuntu:
  Confirmed
Status in unity-lens-music package in Ubuntu:
  Confirmed
Status in unity-lens-photos package in Ubuntu:
  Confirmed
Status in unity-lens-video package in Ubuntu:
  Confirmed
Status in unity-scope-calculator package in Ubuntu:
  Confirmed
Status in unity-scope-devhelp package in Ubuntu:
  Confirmed
Status in unity-scope-home package in Ubuntu:
  Confirmed
Status in unity-scope-manpages package in Ubuntu:
  Confirmed

Bug description:
  The Unity family of packages was previously part of standard Ubuntu.
  Thus all the translation templates were made available to the
  translators via Launchpad, and the translations were included in the
  language packs.

  Since those packages are no longer part of standard Ubuntu, they have
  been moved from main to universe. And translations are dropped.

  At the moment, it is feasible for us to keep using langpacks.

  That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control
  and doing an upload.

  See: https://community.ubuntu.com/t/translation-of-unity-packages/4919

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1760435] Re: Use Ubuntu language packs for various Unity packages

2018-04-07 Thread Simon Quigley
> I plan to land it as soon as everything is built and Bileto does the
usual magic.

Manual signoff is done after all builds have completed. Let's see if
Britney has anything to say...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1760435

Title:
  Use Ubuntu language packs for various Unity packages

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed
Status in unity-lens-applications package in Ubuntu:
  Confirmed
Status in unity-lens-files package in Ubuntu:
  Confirmed
Status in unity-lens-music package in Ubuntu:
  Confirmed
Status in unity-lens-photos package in Ubuntu:
  Confirmed
Status in unity-lens-video package in Ubuntu:
  Confirmed
Status in unity-scope-calculator package in Ubuntu:
  Confirmed
Status in unity-scope-devhelp package in Ubuntu:
  Confirmed
Status in unity-scope-home package in Ubuntu:
  Confirmed
Status in unity-scope-manpages package in Ubuntu:
  Confirmed

Bug description:
  The Unity family of packages was previously part of standard Ubuntu.
  Thus all the translation templates were made available to the
  translators via Launchpad, and the translations were included in the
  language packs.

  Since those packages are no longer part of standard Ubuntu, they have
  been moved from main to universe. And translations are dropped.

  At the moment, it is feasible for us to keep using langpacks.

  That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control
  and doing an upload.

  See: https://community.ubuntu.com/t/translation-of-unity-packages/4919

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1760435] Re: Use Ubuntu language packs for various Unity packages

2018-04-07 Thread Simon Quigley
> Anyway, my gut feeling tells me that adding dh-python to Build-Depends
might help.

Indeed, that works.

I've uploaded everything to Bileto, and I plan to land it as soon as
everything is built and Bileto does the usual magic.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1760435

Title:
  Use Ubuntu language packs for various Unity packages

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed
Status in unity-lens-applications package in Ubuntu:
  Confirmed
Status in unity-lens-files package in Ubuntu:
  Confirmed
Status in unity-lens-music package in Ubuntu:
  Confirmed
Status in unity-lens-photos package in Ubuntu:
  Confirmed
Status in unity-lens-video package in Ubuntu:
  Confirmed
Status in unity-scope-calculator package in Ubuntu:
  Confirmed
Status in unity-scope-devhelp package in Ubuntu:
  Confirmed
Status in unity-scope-home package in Ubuntu:
  Confirmed
Status in unity-scope-manpages package in Ubuntu:
  Confirmed

Bug description:
  The Unity family of packages was previously part of standard Ubuntu.
  Thus all the translation templates were made available to the
  translators via Launchpad, and the translations were included in the
  language packs.

  Since those packages are no longer part of standard Ubuntu, they have
  been moved from main to universe. And translations are dropped.

  At the moment, it is feasible for us to keep using langpacks.

  That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control
  and doing an upload.

  See: https://community.ubuntu.com/t/translation-of-unity-packages/4919

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1760435] Re: Use Ubuntu language packs for various Unity packages

2018-04-07 Thread Simon Quigley
I'll take care of this today.

** Changed in: unity (Ubuntu)
   Status: New => Confirmed

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: unity-greeter (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-greeter (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: unity-lens-applications (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-lens-applications (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: unity-lens-files (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-lens-files (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: unity-lens-music (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-lens-music (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: unity-lens-photos (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-lens-photos (Ubuntu)
     Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: unity-lens-video (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-lens-video (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: unity-scope-calculator (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-scope-calculator (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: unity-scope-devhelp (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-scope-devhelp (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: unity-scope-home (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-scope-home (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: unity-scope-manpages (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-scope-manpages (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1760435

Title:
  Use Ubuntu language packs for various Unity packages

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed
Status in unity-lens-applications package in Ubuntu:
  Confirmed
Status in unity-lens-files package in Ubuntu:
  Confirmed
Status in unity-lens-music package in Ubuntu:
  Confirmed
Status in unity-lens-photos package in Ubuntu:
  Confirmed
Status in unity-lens-video package in Ubuntu:
  Confirmed
Status in unity-scope-calculator package in Ubuntu:
  Confirmed
Status in unity-scope-devhelp package in Ubuntu:
  Confirmed
Status in unity-scope-home package in Ubuntu:
  Confirmed
Status in unity-scope-manpages package in Ubuntu:
  Confirmed

Bug description:
  The Unity family of packages was previously part of standard Ubuntu.
  Thus all the translation templates were made available to the
  translators via Launchpad, and the translations were included in the
  language packs.

  Since those packages are no longer part of standard Ubuntu, they have
  been moved from main to universe. And translations are dropped.

  At the moment, it is feasible for us to keep using langpacks.

  That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control
  and doing an upload.

  See: https://community.ubuntu.com/t/translation-of-unity-packages/4919

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1760435] Re: Use Ubuntu language packs for various Unity packages

2018-04-05 Thread Simon Quigley
> I have never used Bileto, and don't know how it works. Are you saying
that packages handled from there need some other set of Build-Depends
than if you simply upload by dput'ing the source?

With Bileto, it's like uploading to the archive. Once the checks are
passed it's all just copied to -proposed.

> Anyway, my gut feeling tells me that adding dh-python to Build-Depends
might help. I'd suggest that you try that for unity-lens-photos to start
with.

Sure.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1760435

Title:
  Use Ubuntu language packs for various Unity packages

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  New
Status in unity-greeter package in Ubuntu:
  New
Status in unity-lens-applications package in Ubuntu:
  New
Status in unity-lens-files package in Ubuntu:
  New
Status in unity-lens-music package in Ubuntu:
  New
Status in unity-lens-photos package in Ubuntu:
  New
Status in unity-lens-video package in Ubuntu:
  New
Status in unity-scope-calculator package in Ubuntu:
  New
Status in unity-scope-devhelp package in Ubuntu:
  New
Status in unity-scope-home package in Ubuntu:
  New
Status in unity-scope-manpages package in Ubuntu:
  New

Bug description:
  The Unity family of packages was previously part of standard Ubuntu.
  Thus all the translation templates were made available to the
  translators via Launchpad, and the translations were included in the
  language packs.

  Since those packages are no longer part of standard Ubuntu, they have
  been moved from main to universe. And translations are dropped.

  At the moment, it is feasible for us to keep using langpacks.

  That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control
  and doing an upload.

  See: https://community.ubuntu.com/t/translation-of-unity-packages/4919

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1760435] Re: Use Ubuntu language packs for various Unity packages

2018-04-05 Thread Simon Quigley
The difference between Bileto and a regular PPA is that Bileto does
landing of source *and* binary packages directly into proposed. So these
need to be addressed prior to landing.

Patches welcome.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1760435

Title:
  Use Ubuntu language packs for various Unity packages

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  New
Status in unity-greeter package in Ubuntu:
  New
Status in unity-lens-applications package in Ubuntu:
  New
Status in unity-lens-files package in Ubuntu:
  New
Status in unity-lens-music package in Ubuntu:
  New
Status in unity-lens-photos package in Ubuntu:
  New
Status in unity-lens-video package in Ubuntu:
  New
Status in unity-scope-calculator package in Ubuntu:
  New
Status in unity-scope-devhelp package in Ubuntu:
  New
Status in unity-scope-home package in Ubuntu:
  New
Status in unity-scope-manpages package in Ubuntu:
  New

Bug description:
  The Unity family of packages was previously part of standard Ubuntu.
  Thus all the translation templates were made available to the
  translators via Launchpad, and the translations were included in the
  language packs.

  Since those packages are no longer part of standard Ubuntu, they have
  been moved from main to universe. And translations are dropped.

  At the moment, it is feasible for us to keep using langpacks.

  That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control
  and doing an upload.

  See: https://community.ubuntu.com/t/translation-of-unity-packages/4919

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1760435] Re: Use Ubuntu language packs for various Unity packages

2018-04-04 Thread Simon Quigley
I have uploaded these packages to Bileto, and I would like an ACK before
landing them.

https://bileto.ubuntu.com/#/ticket/3221

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1760435

Title:
  Use Ubuntu language packs for various Unity packages

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  New
Status in unity-greeter package in Ubuntu:
  New
Status in unity-lens-applications package in Ubuntu:
  New
Status in unity-lens-files package in Ubuntu:
  New
Status in unity-lens-music package in Ubuntu:
  New
Status in unity-lens-photos package in Ubuntu:
  New
Status in unity-lens-video package in Ubuntu:
  New
Status in unity-scope-calculator package in Ubuntu:
  New
Status in unity-scope-devhelp package in Ubuntu:
  New
Status in unity-scope-home package in Ubuntu:
  New
Status in unity-scope-manpages package in Ubuntu:
  New

Bug description:
  The Unity family of packages was previously part of standard Ubuntu.
  Thus all the translation templates were made available to the
  translators via Launchpad, and the translations were included in the
  language packs.

  Since those packages are no longer part of standard Ubuntu, they have
  been moved from main to universe. And translations are dropped.

  At the moment, it is feasible for us to keep using langpacks.

  That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control
  and doing an upload.

  See: https://community.ubuntu.com/t/translation-of-unity-packages/4919

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1436509] Re: cursor not visible but mouse moves on first login after install

2018-04-04 Thread Simon Quigley
Reversing the status change because Lyn informed me she is still
affected.

** Changed in: lubuntu-meta (Ubuntu)
   Status: Incomplete => New

** Changed in: xserver-xorg-input-mouse (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-mouse in Ubuntu.
https://bugs.launchpad.net/bugs/1436509

Title:
  cursor not visible but mouse moves on first login after install

Status in lubuntu-meta package in Ubuntu:
  New
Status in xserver-xorg-input-mouse package in Ubuntu:
  New

Bug description:
  To reproduce install the Lubuntu amd 64 iso from this zsync link zsync 
http://cdimage.ubuntu.com/lubuntu/daily-live/20150324.2/vivid-desktop-amd64.iso.zsync.
 Then install it with manaul partioning and an ext4 / partion. Then the install 
completes and restart now and login. No cursor will appear on the screen at 
first login. 
  is the mouse from lsusb. 
  Bus 001 Device 002: ID 045e:0053 Microsoft Corp. Optical Mouse

  xserver-xorg-input-mouse:
Installed: 1:1.9.1-1
Candidate: 1:1.9.1-1
Version table:
   *** 1:1.9.1-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  
  I expected to boot up and have a cursor. Instead for the first time I logged 
into lubuntu I had no cursor but after I logged out a cursor appeared and 
contiues to appear for succesive secessions. ISO tracker hardware profile is 
here  https://gist.github.com/56618cd1ed68e5b63a0c

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-input-mouse 1:1.9.1-1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Mar 25 11:57:31 2015
  InstallationDate: Installed on 2015-03-25 (0 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324.2)
  SourcePackage: xserver-xorg-input-mouse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1436509/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1744366] Re: xfce power manager shows wrong battery life information (Lbuntu 16.04.3)

2018-04-04 Thread Simon Quigley
Have you tried live CDs of other operating systems to see if this is a
Lubuntu-specific issue?

** Changed in: upower (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1744366

Title:
  xfce power manager shows wrong battery life information (Lbuntu
  16.04.3)

Status in upower package in Ubuntu:
  Incomplete

Bug description:
  As per title xfce power manager (version 1.4.4-4ubuntu2) on my Lubuntu
  16.04.3 shows a wrong battery life. What happens is that I plug in the
  laptop, it tells me the battery is 100% I unplug the write and I can
  see after maybe 10 minutes that the battery level lowered.

  I check and it gives me something like 80% and then, suddenly the
  laptop turns of because the battery is discharged.

  When i plug it back it shows as the battery is either charging
  correctly or charging and the percentage is over 70%.

  The battery is a few months old, so I think the problem lies in xfce
  power manager which displays the wrong information.Bug #1216594 opened
  in 2013 is very similar to my case, however that bug report was closed
  not because it was fixed but because it expired after 60 days.

  I tried 'upower -d' and it gives me the same info as the power manager.
  The output was:
  Device: /org/freedesktop/UPower/devices/line_power_ADP1
native-path:  ADP1
power supply: yes
updated:  XX XX XXX  17:58:48 GMT (815 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
native-path:  BAT0
vendor:   Hewlett-Packard
model:Primary
power supply: yes
updated:  Fri 19 Jan 2018 18:10:34 GMT (109 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   charging
  warning-level:   none
  energy:  22.2592 Wh
  energy-empty:0 Wh
  energy-full: 26.048 Wh
  energy-full-design:  26.048 Wh
  energy-rate: 20.0392 W
  voltage: 16.444 V
  time to full:11.3 minutes
  percentage:  85%
  capacity:100%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
History (charge):
  151638543485.000  charging
History (rate):
  151638543420.039  charging

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  XX XX XXX  18:10:34 GMT (109 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   charging
  warning-level:   none
  energy:  22.2592 Wh
  energy-full: 26.048 Wh
  energy-rate: 20.0392 W
  time to full:11.3 minutes
  percentage:  85%
  icon-name:  'battery-full-charging-symbolic'

  Daemon:
daemon-version:  0.99.4
on-battery:  no
lid-is-closed:   no
lid-is-present:  yes
critical-action: HybridSleep

  Any ideas?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1744366/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1434240] Re: nm-applet icon missing from lxpanel in Lubuntu 14.04

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1434240

and any other logs that are relevant for this particular issue.

** Changed in: network-manager-applet (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1434240

Title:
  nm-applet icon missing from lxpanel in Lubuntu 14.04

Status in network-manager-applet package in Ubuntu:
  Incomplete

Bug description:
  Somehow recently my network applet disappeared from LXpanel. I could
  not figure out what caused this or what to do to restore it. nm-applet
  is still in my autostart and does seem to be working on boot up.
  However, I found Bug #1302462 which seems to fit the problem I am
  facing. Using the workaround mentioned in comment #15 of that bug does
  work. So I believe Lubuntu is also affected by Bug #1302462 since it
  uses the same network manager applet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1434240/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1436509] Re: cursor not visible but mouse moves on first login after install

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1436509

and any other logs that are relevant for this particular issue.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-mouse in Ubuntu.
https://bugs.launchpad.net/bugs/1436509

Title:
  cursor not visible but mouse moves on first login after install

Status in lubuntu-meta package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-mouse package in Ubuntu:
  Incomplete

Bug description:
  To reproduce install the Lubuntu amd 64 iso from this zsync link zsync 
http://cdimage.ubuntu.com/lubuntu/daily-live/20150324.2/vivid-desktop-amd64.iso.zsync.
 Then install it with manaul partioning and an ext4 / partion. Then the install 
completes and restart now and login. No cursor will appear on the screen at 
first login. 
  is the mouse from lsusb. 
  Bus 001 Device 002: ID 045e:0053 Microsoft Corp. Optical Mouse

  xserver-xorg-input-mouse:
Installed: 1:1.9.1-1
Candidate: 1:1.9.1-1
Version table:
   *** 1:1.9.1-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  
  I expected to boot up and have a cursor. Instead for the first time I logged 
into lubuntu I had no cursor but after I logged out a cursor appeared and 
contiues to appear for succesive secessions. ISO tracker hardware profile is 
here  https://gist.github.com/56618cd1ed68e5b63a0c

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-input-mouse 1:1.9.1-1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Mar 25 11:57:31 2015
  InstallationDate: Installed on 2015-03-25 (0 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324.2)
  SourcePackage: xserver-xorg-input-mouse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1436509/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1574593] Re: gdm and lightdm stop afetr upgrade

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1574593

and any other logs that are relevant for this particular issue.

** Changed in: gdm (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1574593

Title:
  gdm and lightdm stop afetr upgrade

Status in gdm package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to 16.04 from 15.10 Ubuntu 64bit, with gnome desktop,
  gdm stop working.

  I had this error:
  [OK] started  GNOME display Manager.kernel modulect mapper.ndemand" 
link was shut down

  and the GDM graphical login screen don't appear.
  I've tried to switch to lightdm, the login screen appear, but it's impossible 
to start any installed dtm (gnome/gnome classic or ubuntu/unity)

  Than i've tried to install also swift, but i've found the same
  problem.

  Now, i've tried to install the complete lubuntu-desktop, it's also don't 
start, but the LDXE desktop yes, 
  For now im'using LDXE, but I need to reuturn to gnome...
  Please help !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1574593/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1584793] Re: Rhythmbox fails to put an icon on the system tray in Lubuntu 14.04

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1584793

and any other logs that are relevant for this particular issue.

** Changed in: rhythmbox (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1584793

Title:
  Rhythmbox fails to put an icon on the system tray in Lubuntu 14.04

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  When I run Rhythmbox and close it while music is playing, I have no
  way to return to it. It should show up in the system tray. I know
  Rhythmbox is running because it's in the process list.

   edg@arthur ~ $ ps ax|grep rhythmbox
   29371 ?Sl 1:16 rhythmbox
   30029 pts/6S+ 0:00 grep --color=auto rhythmbox
   edg@arthur ~ $

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1584793/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1436509] Re: cursor not visible but mouse moves on first login after install

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1436509

and any other logs that are relevant for this particular issue.

** Changed in: lubuntu-meta (Ubuntu)
   Status: New => Incomplete

** Changed in: xserver-xorg-input-mouse (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-mouse in Ubuntu.
https://bugs.launchpad.net/bugs/1436509

Title:
  cursor not visible but mouse moves on first login after install

Status in lubuntu-meta package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-mouse package in Ubuntu:
  Incomplete

Bug description:
  To reproduce install the Lubuntu amd 64 iso from this zsync link zsync 
http://cdimage.ubuntu.com/lubuntu/daily-live/20150324.2/vivid-desktop-amd64.iso.zsync.
 Then install it with manaul partioning and an ext4 / partion. Then the install 
completes and restart now and login. No cursor will appear on the screen at 
first login. 
  is the mouse from lsusb. 
  Bus 001 Device 002: ID 045e:0053 Microsoft Corp. Optical Mouse

  xserver-xorg-input-mouse:
Installed: 1:1.9.1-1
Candidate: 1:1.9.1-1
Version table:
   *** 1:1.9.1-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  
  I expected to boot up and have a cursor. Instead for the first time I logged 
into lubuntu I had no cursor but after I logged out a cursor appeared and 
contiues to appear for succesive secessions. ISO tracker hardware profile is 
here  https://gist.github.com/56618cd1ed68e5b63a0c

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-input-mouse 1:1.9.1-1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Mar 25 11:57:31 2015
  InstallationDate: Installed on 2015-03-25 (0 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324.2)
  SourcePackage: xserver-xorg-input-mouse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1436509/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1620092] Re: Lubuntu 14.04 HWE update problem: libgbm1-lts-xenial does not provide libgbm1

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1620092

and any other logs that are relevant for this particular issue.

** Changed in: mesa-lts-xenial (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa-lts-xenial in Ubuntu.
https://bugs.launchpad.net/bugs/1620092

Title:
  Lubuntu 14.04 HWE update problem: libgbm1-lts-xenial does not provide
  libgbm1

Status in mesa-lts-xenial package in Ubuntu:
  Incomplete

Bug description:
  Installed Lubuntu 14.04 i386.
  I used the apt line for all HWE updates from the ubuntu wiki, to update each 
stack manually.  E.g., for xenial:
  sudo apt-get install --install-recommends linux-generic-lts-xenial 
xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial
  ( https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Desktop )

  * The kernel stacks updated with no problem.
  * When I try to update the graphics HWE stack from *-vivid to *-willy or 
*-xenial, apt wants to uninstall a lot of stuff, among them:
  abiword libabiword-3.0 audacious audacious-plugins lubuntu-desktop

  I did the update with the Xenial stack anyway, and tried to find the
  problem while installing uninstalled (non-lib) stuff back.

  Worked my way to libgbm1 through "X depends on Y, but it is not going
  to be installed" errors.

  libgbm1 has libgbm1-lts-* versions, and libgbm1-lts-xenial
  (11.2.0-1ubuntu2~trusty1) got installed with the xenial HWE stack.

  I noticed that some packages, e.g. libgbm1 and mesa-vdpau-drivers
  stayed installed although they both have -lts-* versions.

  1) Shouldn't the libgbm1-lts-* packages (that do not depend on libgbm1) 
provide libgbm1?
  Or did the API change?

  
http://answers.ros.org/question/203610/ubuntu-14042-unmet-dependencies-similar-for-14043/
  looks connected, but their solution -- to also install some -dev-lts-* pkgs 
-- seems like more of a workaround if they rebuilt the pkg, and I don't think 
it will help a more complex dependency problem.

  2) Did I update the stack incorrectly? Is there a
  better/automated/reliable method?

  Aside from libgbm1, the base mesa-vdpau-drivers stayed installed even
  though I upgraded up to the vivid graphics stack---probably mesa-
  vdpau-drivers-lts-* was missing from the apt line because it is not
  necessary to have installed (not all systems can or want to do vdpau
  accel)?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa-lts-xenial/+bug/1620092/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1633935] Re: Inkscape freezes when selecting font

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1633935

and any other logs that are relevant for this particular issue.

** Changed in: inkscape
   Status: New => Incomplete

** Changed in: inkscape (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1633935

Title:
  Inkscape freezes when selecting font

Status in Inkscape:
  Incomplete
Status in inkscape package in Ubuntu:
  Incomplete

Bug description:
  If you perform the following steps, Inkscape freezes. It's a
  showstopper of using Inkscape at all with fonts.

  1. Launch Inkscape.
  2. On the new document, click the A on the left toolbar to create a new 
textbox.
  3. Drag a marquee in your document for the size of your textbox.
  4. Type the text "This is a test" and then choose Select All to select it all.
  5. Click the T in the top toolbar to open the Text and Font control panel.
  6. Choose DejaVu Sans.
  7. Put another window on top of the current window, such as switch to a web 
browser.
  8. Come back to Inkscape -- it won't repaint the window because it's frozen.

  Alternatively, you can also recreate the bug this way too:

  1. Launch Inkscape.
  2. On the new document, click the A on the left toolbar to create a new 
textbox.
  3. Drag a marquee in your document for the size of your textbox.
  4. Type the text "This is a test" and then choose Select All to select it all.
  5. Click the T in the top toolbar to open the Text and Font control panel.
  6. Choose DejaVu Sans.
  7. Set the font size to 48 from the Font Size: selector on that control 
panel. You'll notice that the dropdown occurs, when you select it, Inkscape 
freezes.

  Note that I'm running Inkscape 0.91 on Lubuntu Desktop 16.04 inside
  Oracle Virtualbox version 5.0.26 r108824 on a Mac Air 13" running OSX
  10.12 (Sierra) and have loaded the Virtualbox extensions. Note that I
  also tried the following things to see if they fixed the problem:

  - full apt-get update; apt-get upgrade; apt-get dist-upgrade, reboot,
  and tried that again

  - apt purge fonts-noto-cjk

  - tried briefly the latest stable PPA of Inkscape from Inkscape.org in
  my apt, and upgrade to the latest Inkscape -- that failed, so I did a
  purge remove of that version of inkscape, removed the PPA, redid my
  apt-get update, and installed the version that comes with Ubuntu 16.04
  (Inkscape 0.91).

  - unset GTK_IM_MODULE && inkscape

  All failed to show any fix.

  
  All failed to show any different result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1633935/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1266911] Re: Lightdm hangs when switching sessions

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1266911

and any other logs that are relevant for this particular issue.

** Changed in: lightdm (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1266911

Title:
  Lightdm hangs when switching sessions

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Lightdm hangs when attempting to select lx Games or Lubuntu Nexus 7
  sessions. This discovered for the Lubuntu 14.04 LTS testdrive via the
  virtual machine.

  Ubuntu Trusty Tahr (development branch)
  14.04

  lightdm:
     Installed: 1.9.5-0ubuntu1
     Candidate:  1.9.5-oubuntu1
     Version table:
   *** 1.9.5-0ubuntu1 0
     500   http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 
Packages
     100   /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1266911/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 997037] Re: Chromium freezes on play at youtube.com/xl on LXDE

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 997037

and any other logs that are relevant for this particular issue.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/997037

Title:
  Chromium freezes on play at youtube.com/xl on LXDE

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Start Chromium, open webpage http://www.youtube.com/xl and start any video.
  Chromium will freeze, start to behave strange on Lubuntu 12.04.

  Working normally on Ubuntu with Gnome Classic (Ubuntu 11.10 Gnome
  Classic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/997037/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1310392] Re: Hardware screen scaling problems since 14.04 upgrade with Nvidia legacy driver

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1310392

and any other logs that are relevant for this particular issue.

** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
https://bugs.launchpad.net/bugs/1310392

Title:
  Hardware screen scaling problems since 14.04 upgrade with Nvidia
  legacy driver

Status in nvidia-graphics-drivers-173 package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Just upgraded to Lubuntu 32-bit 14.04 from 13.10 on April 18th, 2014.

  - System is a P4, 2.8Ghz, 3GB RAM,
  - NVidia GeForce 5700LE AGP graphics card with proprietary legacy video 
drivers manually installed from Nvidia site (VERSION 173.14.39, RELEASE: 
2013.12.6 - the latest possible version available for my graphics card).
  - Motherboard is ASUS P4P800-E upgraded to the latest BIOS available.

  Prior to the upgrade, the arcade emulator MAME, the Commodore 64
  emulator VICE, and the Commodore Amiga emulator FS-UAE worked
  fantastically in full screen scaled mode. No delay, smooth
  performance. Reasonably low CPU usage for a processor of this vintage.

  After the upgrade to 14.04, all full screen modes (1080x1920) in these
  emulators bring the system to a crawl. Sound from the emulator is
  broken up, framerates are terrible (like two frames a second), CPU
  usage is near or past 100%. I suspect other OpenGL software using
  full-screen scaling would also be affected, but these are the only
  three pieces of software I have to test with.

  I've found that in MAME and VICE, I can work-around this problem but
  shutting off "hardware scaling". Essentially (I think), this takes my
  graphics card out of the loop and does the scaling in software/CPU.
  Scaling down the resolution of the emulation helps too. Frame-rates
  are better, CPU usage is lower by a factor of 30 to 40%. However,
  because of these "work around measure" the overall user experience of
  the emulators is severely impeded.

  I also ran glxgears as a test and resized the window from its original
  small size, a little bigger every five seconds, until it was the full
  height of the screen (1080 lines) and got the following results:

  Code:

  brent@Brent-Lubuntu:~$ glxgears
  552 frames in 5.0 seconds = 110.342 FPS
  593 frames in 5.0 seconds = 118.471 FPS
  416 frames in 5.0 seconds = 83.071 FPS
  315 frames in 5.0 seconds = 62.810 FPS
  287 frames in 5.0 seconds = 57.252 FPS
  197 frames in 5.0 seconds = 39.354 FPS
  165 frames in 5.0 seconds = 32.789 FPS
  130 frames in 5.0 seconds = 25.937 FPS
  124 frames in 5.0 seconds = 24.781 FPS
  117 frames in 5.0 seconds = 23.274 FPS
  XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 25689 requests (25666 known processed) with 0 events remaining.

  I had originally switched to the Nvidia proprietary driver from
  Nouveau because of slight artifacts and stuttering in the latter. The
  proprietary driver mentioned above worked like a dream in 13.10.

  MP4 videos played in VLC VideoLAN player still play well, with low CPU
  usage.

  Based on my limited knowledge, this seems to be a problem with the
  graphics card full-screen scaling to 1080x1920 (desktop & monitor
  screenmode) under 14.04. Might have to do something with OpenGL?

  The system works very well, other than when these emulators try to go
  into full screen mode.

  My Xorg.0.log file shows the following (notice the error lines):

  (II) LoadModule: "nvidia"
  (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
  (II) Module nvidia: vendor="NVIDIA Corporation"
  compiled for 4.0.2, module version = 1.0.0
  Module class: X.Org Video Driver
  (II) NVIDIA dlloader X Driver 173.14.39 Wed Nov 27 15:02:30 PST 2013
  (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs

  ...

  (**) NVIDIA(0): Enabling RENDER acceleration
  (EE) NVIDIA(0): Failed to initialize the GLX module; please check in
  your X
  (EE) NVIDIA(0): log file that the GLX module has been loaded in your X
  (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX
  module. If
  (EE) NVIDIA(0): you continue to encounter problems, Please try
  (EE) NVIDIA(0): reinstalling the NVIDIA driver.
  (II) NVIDIA(0): NVIDIA GPU GeForce FX 5700LE (NV36) at PCI:1:0:0 (GPU-0)
  (--) NVIDIA(0): Memory: 262144 kBytes
  (--) NVIDIA(0): VideoBIOS: 04.36.20.35.00
  (II) NVIDIA(0): 

[Desktop-packages] [Bug 282954] Re: Wish: Quiet installation option

2018-04-04 Thread Simon Quigley
I believe that Ubiquity is now quiet, and really doesn't emit any noise.

** Changed in: ubiquity (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/282954

Title:
  Wish: Quiet installation option

Status in pulseaudio package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: ubiquity

  I often test new systems (alphas, betas, mockups) when the house is
  asleep. Therefore, it is essential to me that the system not beep or
  be otherwise noisy. I propose an option in the Advanced dialog (at the
  end of the installation wizard) for disabling the PC Speaker and
  desktop (Gnome/KDE) sound theme. The advanced dialog contains only two
  options at the moment, so clutter is not a worry.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/282954/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1177267] Re: Inconsistency in passwords strength assessment

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1177267

and any other logs that are relevant for this particular issue.

** Changed in: ubuntu-gnome
   Status: New => Incomplete

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

** Changed in: ubiquity (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1177267

Title:
  Inconsistency in passwords strength assessment

Status in Ubuntu GNOME:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  The password strength assessment is inconsistent between Ubiquity and
  the Gnome "User Accounts" applet.

  For example, I use a pretty short but complicated password:
  - Ubiquity evaluates this password as "Good password" or "strong" (don't 
really remember)
  - Gnome "User Accounts" applet evaluates this same password as "weak".

  Ubuntu Gnome 13.04 + Gnome 3 PPA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1177267/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1187981] Re: symbol conflicts in libtimezonemap1

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1187981

and any other logs that are relevant for this particular issue.

** Changed in: gnome-control-center
   Status: Confirmed => Incomplete

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

** Changed in: libtimezonemap (Ubuntu)
   Status: New => Incomplete

** Changed in: ubiquity (Ubuntu)
   Status: New => Incomplete

** Changed in: unity-control-center (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1187981

Title:
  symbol conflicts in libtimezonemap1

Status in gnome-control-center:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in libtimezonemap package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete
Status in unity-control-center package in Ubuntu:
  Incomplete

Bug description:
  In gnome-control-center 3.8 all built in panels are statically linked.
  When the indicator-datetime panel loads it is picking up the symbols
  from the gnome datetime panel rather than the ones in libtimezonemap1,
  causing g-c-c to segfault.

  All public symbols in libtimezonemap1 need to renamed to avoid
  conflict. Likewise this might apply to any other g-c-c plugins that
  have code cut+paste from the built in gnome panels.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 12.10.3daily13.05.06.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Thu Jun  6 12:35:40 2013
  InstallationDate: Installed on 2012-09-23 (256 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1187981/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1066284] Re: Add keyboard layout button disabled in default live session

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1066284

and any other logs that are relevant for this particular issue.

** Changed in: gnome-control-center (Ubuntu)
   Status: Invalid => Incomplete

** Changed in: ubiquity (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1066284

Title:
  Add keyboard layout button disabled in default live session

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  When booting the quantal iso testing images and selecting Try Ubuntu
  without changing the language or keyboard layout, it is impossible to
  add keyboard layouts. In system settings -> keyboard layout there are
  only four English layouts listed and the + button that should add a
  layout is grayed out.

  When selecting a non-English layout by pressing F3 during boot the
  button is usable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1066284/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1256201] Re: Installation xubuntu crash

2018-04-04 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1256201

and any other logs that are relevant for this particular issue.

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

** Changed in: ubiquity (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1256201

Title:
  Installation xubuntu crash

Status in network-manager package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  Failed installation ... sistem installation crash

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ubiquity 2.15.26
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  Date: Fri Nov 29 06:29:12 2013
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=it 
keyboard-configuration/layoutcode?=it
  LiveMediaBuild: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=it_IT.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1256201/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1761313] Re: installer crashed

2018-04-04 Thread Simon Quigley
** Package changed: ubiquity (Ubuntu) => appstream (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1761313

Title:
  installer crashed

Status in appstream package in Ubuntu:
  New

Bug description:
  error copying files but cd check is ok

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity 2.21.63 [modified: 
lib/partman/automatically_partition/question]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  Date: Wed Apr  4 22:24:39 2018
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1761313/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1760998] Re: Libreoffice doesn't starts on kubuntu 18.04 32bit

2018-04-03 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1760998

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: libreoffice (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1760998

Title:
  Libreoffice doesn't starts on kubuntu 18.04 32bit

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Any time I try to run any libreoffice package I can see just the
  loader image, starts loading and than crash

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Tue Apr  3 23:43:48 2018
  InstallationDate: Installed on 2018-03-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1760998/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 986716] Re: Orca doesn't read the ubiquity promotional slides

2018-04-02 Thread Simon Quigley
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 986716

and any other logs that are relevant for this particular issue.

** Changed in: gnome-orca (Ubuntu)
   Status: New => Incomplete

** Changed in: ubiquity (Ubuntu)
   Status: New => Incomplete

** Changed in: ubiquity-slideshow-ubuntu (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-orca in Ubuntu.
https://bugs.launchpad.net/bugs/986716

Title:
  Orca doesn't read the ubiquity promotional slides

Status in gnome-orca package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Incomplete

Bug description:
  Release of Ubuntu: Ubuntu precise, 12.04
  Package Version: ubiquity 2.10.16, gnome-orca 3.4.0-0ubuntu2
  Expected Results: Orca should read the promotional slides while the 
installation is on progress
  Actual Results: Orca only keeps track of the percentage of the installation

  Probably the ubiquity slides are images, which explains why orca
  doesn't read them, it also doesn't explain in what step of the
  installation it's working, for example when copying file, it shouts
  the percentage, and when starts repartitioning, or installing others
  packages the percentage reading is reset and gives no clue about why
  it happened or in what part of the installation it is.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-orca/+bug/986716/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


  1   2   3   >