from:"Mantas Kriaučiūnas"

** Summary changed:

- File-Roller should depend on 7zip package instead of p7zip-full since version 
43
+ File-Roller should depend on 7zip package instead of abandoned p7zip-full 
since version 43

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

Title:
  File-Roller should depend on 7zip package instead of abandoned p7zip-
  full since version 43

Status in file-roller package in Ubuntu:
  New

Bug description:
  File-Roller switched from p7zip to official 7zip utility since version
  43.alpha , see

  
https://gitlab.gnome.org/GNOME/file-roller/-/commit/b798bbd96d3777c20026f1dc2d3e15ecb5bc853d
  and 
https://gitlab.gnome.org/GNOME/file-roller/-/commit/a4359d11e05023605c4270c67ad703bc8a71f8fd

  but File-Roller Ubuntu/Debian package version 43-1 still depends on abandoned 
by upstream p7zip-full, while it should depend on 7zip package instead of 
p7zip-full 
  or maybe better to have "Depends: 7zip | p7zip-full" ?

  There are lots of bugs in p7zip, for example some large zip files cannot be 
extract on 16.02 but can on 9.20, see 
https://sourceforge.net/p/p7zip/discussion/383044/ and
  http://bugs.debian.org/src:p7zip also 
https://bugs.launchpad.net/ubuntu/+source/p7zip

  It seems Debian developers planing to replace p7zip-full with official
  7zip package, see https://bugs.debian.org/991428

  Also there is a related note in NEWS file:
   - Distros will want to adjust the `data/packages.match` file.

  Some archive managers in Ubuntu/Debian already depends on official
  7zip package instead of p7zip, see arqiver for example.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2028819/+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 2028819] [NEW] File-Roller should depend on 7zip package instead of p7zip-full since version 43

Public bug reported:

File-Roller switched from p7zip to official 7zip utility since version
43.alpha , see

https://gitlab.gnome.org/GNOME/file-roller/-/commit/b798bbd96d3777c20026f1dc2d3e15ecb5bc853d
and 
https://gitlab.gnome.org/GNOME/file-roller/-/commit/a4359d11e05023605c4270c67ad703bc8a71f8fd

but File-Roller Ubuntu/Debian package version 43-1 still depends on abandoned 
by upstream p7zip-full, while it should depend on 7zip package instead of 
p7zip-full 
or maybe better to have "Depends: 7zip | p7zip-full" ?

There are lots of bugs in p7zip, for example some large zip files cannot be 
extract on 16.02 but can on 9.20, see 
https://sourceforge.net/p/p7zip/discussion/383044/ and
http://bugs.debian.org/src:p7zip also 
https://bugs.launchpad.net/ubuntu/+source/p7zip

It seems Debian developers planing to replace p7zip-full with official
7zip package, see https://bugs.debian.org/991428

Also there is a related note in NEWS file:
 - Distros will want to adjust the `data/packages.match` file.

Some archive managers in Ubuntu/Debian already depends on official 7zip
package instead of p7zip, see arqiver for example.

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  File-Roller should depend on 7zip package instead of p7zip-full since
  version 43

Status in file-roller package in Ubuntu:
  New

Bug description:
  File-Roller switched from p7zip to official 7zip utility since version
  43.alpha , see

  
https://gitlab.gnome.org/GNOME/file-roller/-/commit/b798bbd96d3777c20026f1dc2d3e15ecb5bc853d
  and 
https://gitlab.gnome.org/GNOME/file-roller/-/commit/a4359d11e05023605c4270c67ad703bc8a71f8fd

  but File-Roller Ubuntu/Debian package version 43-1 still depends on abandoned 
by upstream p7zip-full, while it should depend on 7zip package instead of 
p7zip-full 
  or maybe better to have "Depends: 7zip | p7zip-full" ?

  There are lots of bugs in p7zip, for example some large zip files cannot be 
extract on 16.02 but can on 9.20, see 
https://sourceforge.net/p/p7zip/discussion/383044/ and
  http://bugs.debian.org/src:p7zip also 
https://bugs.launchpad.net/ubuntu/+source/p7zip

  It seems Debian developers planing to replace p7zip-full with official
  7zip package, see https://bugs.debian.org/991428

  Also there is a related note in NEWS file:
   - Distros will want to adjust the `data/packages.match` file.

  Some archive managers in Ubuntu/Debian already depends on official
  7zip package instead of p7zip, see arqiver for example.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2028819/+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 1859398] Re: Extracting .rar creates multi-GB file which fills up harddrive

Maybe this .rar archive extracting issue is fixed in latest File-Roller 43 
release? Look at  
https://gitlab.gnome.org/GNOME/file-roller/-/merge_requests/87

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

Title:
  Extracting .rar creates multi-GB file which fills up harddrive

Status in file-roller package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) Archive Manager 3.32.2-1
  3) Display a message if .rar is unsupported or display a message to install 
p7zip which can extract .rar files.
  4) Selecting the ProtectionId.690.December.2017.rar file and then right 
clicking "Extract Here", Archive Manager creates a multi-GB file named 
file_id.dz which fills up the harddrive. I was able to successfully extract the 
ProtectionId.690.December.2017.rar file with 7zip via WINE.

  https://protectionid.net/
  
https://web.archive.org/web/20181229235034/https://pid.wiretarget.com/?f=ProtectionId.690.December.2017.rar

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1859398/+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 1571806] Re: Backup files are silently ignored when using certain archive types

File-roller developers decided do not add files with a `~` on the end of
their names to new archive in version 2.23.4 , see
https://gitlab.gnome.org/GNOME/file-roller/-/blob/master/NEWS#L3858 :

New features and user visible changes:
[...]

* Do not add the backup files, that is files ending with ~, to
the archive.

It seems we should report this issue to the upstream:
https://gitlab.gnome.org/GNOME/file-roller/-/issues

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

Title:
  Backup files are silently ignored when using certain archive types

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  Depending on the kind of archive you create using file-roller, backup
  files (files with a `~` on the end of their names) are included or
  ignored. The user doesn't see any warning at all and will probably
  only discover this when they try to extract the archive.

  # How to reproduce the symptom.
  (I'm assuming you're using Nautilus with file-roller integration.)
  Create a folder `testFolder` (or any name but I'll use this one to refer to 
it) and create a file called `testFile~` in it. Then move to the parent folder 
of `testFolder`. Right-click test folder and choose "Compress".
  ## Correct behavior.
  Choose `.7z` as the archive format making it a 7zip archive and click 
"Create". The archive will contain the folder `testFolder` and in it the file 
`testFile~`.
  ## Incorrect behavior.
  Choose `.tar` as the archive format making it a tarball and click "Create". 
The tarball will contain the folder `testFolder` but it will be empty.

  Note that this isn't the fault of `tar`. If you create the tarball
  from the command line using the command `tar`, `testFile~` will be
  included.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1571806/+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 1873398] Re: gnome-disks won't do SMART on NVME drive

2023-04-23 Thread Mantas Kriaučiūnas

@Roman Martin (ubuntupsyx) this issue with NVME SSD still isn't fixed in 
upstream gnome-disk-utility project, so it wouldn't be fixed in Ubuntu until 
this bug isn't fixed:
https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/50

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

Title:
  gnome-disks won't do SMART on NVME drive

Status in GNOME Disks:
  New
Status in gnome-disk-utility package in Ubuntu:
  Triaged

Bug description:
  I'm running 20.04 beta amd64 Desktop from a USB stick of the live ISO.

  I opened Disks (gnome-disks) and it sees all my drives, but it won't
  show SMART stats on my NVME drive (Samsung SSD 970 EVO Plus 500GB).
  The SMART menu item is greyed out.  It works fine on other drives.

  The NVME has SMART support; it works fine with smartctl -a /dev/nvme0n1 for 
example.  (Though smartctl is not in this live ISO, I have apt-get installed it 
at another time and tried it; and
  it works fine in the Ubuntu 18.04 that is installed on this machine.)

  I've attached a screencast showing the failure.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-disk-utility 3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 17 07:32:43 2020
  ExecutablePath: /usr/bin/gnome-disks
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1873398/+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 1864215] Re: Please add webp loader to gdk-pixbuf

2023-04-11 Thread Mantas Kriaučiūnas

** Changed in: gdk-pixbuf (Baltix)
 Assignee: (unassigned) => Mantas Kriaučiūnas (mantas)

** Also affects: webp-pixbuf-loader (Baltix)
   Importance: Undecided
   Status: New

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

Title:
  Please add webp loader to gdk-pixbuf

Status in gdk-pixbuf:
  Fix Released
Status in webp-pixbuf-loader package in Ubuntu:
  Fix Released
Status in gdk-pixbuf package in Baltix:
  Triaged
Status in webp-pixbuf-loader package in Baltix:
  New
Status in webp-pixbuf-loader package in Debian:
  Fix Released

Bug description:
  Attempting to load a webp image -- for instance, 

https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp
  or

https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg
  -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file 
format" error.

  Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in
  libwebp, but isn't this really a gdk-pixbuf issue? If it really does
  belong to libwebp, my apologies, please dup this bug to 1407644 (I'm
  confident it doesn't belong to eog since I don't use that program; I
  have other programs that use libgdk-pixbuf).

  You can probably use eog to test this, or run
  /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i 
webp
  (I assume the loader would mention webp if there was a loader for it).

  I have these packages installed in addition to libgdk-pixbuf2.0-0:
  libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes
  the format:

  $ file /tmp/FKK78W.jpg.webp
  /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 
1200x533, Scaling: [none]x[none], YUV color, decoders should clamp

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  Date: Fri Feb 21 08:48:36 2020
  InstallationDate: Installed on 2019-10-10 (133 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1864215/+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 2009944] Re: [BPO] libreoffice 7.4.6 for bionic, focal and jammy

2023-04-03 Thread Mantas Kriaučiūnas

@ricotz, thanks, but I still don't understand why you use external graphite in 
Kinetic and Lunar and internal in Jammy and Bionic, 
when the same graphite2 1.3.14-1build2 released at 2022-03-28 is in Lunar, 
Kinetic and Jammy, also in Bionic is almost the same - 1.3.13-11build1 version, 
see

https://launchpad.net/ubuntu/+source/graphite2

> ricotz) wrote: @mantas: Libreoffice provides conditional paths to work
with older harfbuzz versions. Unfortunately this can lead to bugs like
[1] [2.

-- 
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/2009944

Title:
  [BPO] libreoffice 7.4.6 for bionic, focal and jammy

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice source package in Focal:
  Fix Released
Status in libreoffice source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release

   * This source packages matches the proposed SRU for kinetic handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2009354
     and its backport is currently provided by the LibreOffice Still PPA at
   
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages

   * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently
  released in bionic-/focal-backports

  [Scope]

   * Backport of
  https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.6-0ubuntu0.22.10.1

   * Backport targets are the Bionic/18.04, Focal/20.04 and Jammy/22.04
  LTS releases to provide an official build of a more recent upstream
  version of LibreOffice

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_74/1717/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests
  that were run and verified as passing.

     Bionic/18.04 build at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541804/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20230311_021721_5528d@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20230311_022133_e8482@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20230311_034543_5547f@/log.gz
  * [i386l] 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20230311_024716_6fc50@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20230311_013201_6dbb2@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20230311_013952_49140@/log.gz

     Focal/20.04 build at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541807/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/20230311_001616_c1e3a@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/20230310_164346_4ac1d@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/20230311_052748_8b7c3@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/20230310_151809_05c21@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20230310_190707_a5b67@/log.gz

     Jammy/22.04 build at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541810/+listing-archive-extra
  * [amd64]

[Desktop-packages] [Bug 2009944] Re: [BPO] libreoffice 7.4.6 for bionic, focal and jammy

2023-04-03 Thread Mantas Kriaučiūnas

@ricotz , I don't understand why you use internal graphite and harfbuzz
in jammy-backports, while the same graphite2 and harfbuzz version is in
Kinetic and Jammy? See

https://launchpad.net/ubuntu/+source/graphite2
https://launchpad.net/ubuntu/+source/harfbuzz

libreoffice (1:7.4.6-0ubuntu0.22.10.1~bpo22.04.1) jammy-backports;
urgency=medium

  * Backport from kinetic (LP: #2009944)
  * Use internal graphite and harfbuzz to meat upstream requirements

 -- Rico Tzschichholz   Thu, 09 Mar 2023 14:07:05
+0100

-- 
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/2009944

Title:
  [BPO] libreoffice 7.4.6 for bionic, focal and jammy

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice source package in Focal:
  Fix Released
Status in libreoffice source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release

   * This source packages matches the proposed SRU for kinetic handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2009354
     and its backport is currently provided by the LibreOffice Still PPA at
   
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages

   * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently
  released in bionic-/focal-backports

  [Scope]

   * Backport of
  https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.6-0ubuntu0.22.10.1

   * Backport targets are the Bionic/18.04, Focal/20.04 and Jammy/22.04
  LTS releases to provide an official build of a more recent upstream
  version of LibreOffice

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_74/1717/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests
  that were run and verified as passing.

     Bionic/18.04 build at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541804/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20230311_021721_5528d@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20230311_022133_e8482@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20230311_034543_5547f@/log.gz
  * [i386l] 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20230311_024716_6fc50@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20230311_013201_6dbb2@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20230311_013952_49140@/log.gz

     Focal/20.04 build at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541807/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/20230311_001616_c1e3a@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/20230310_164346_4ac1d@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/20230311_052748_8b7c3@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/20230310_151809_05c21@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20230310_190707_a5b67@/log.gz

     Jammy/22.04 build at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541810/+listing-archive-extra
  * [amd64]

[Desktop-packages] [Bug 2007755] [NEW] Tracker miners (eg. tracker-miner-fs-3) are started for GDM and other system users

2023-02-18 Thread Mantas Kriaučiūnas

Public bug reported:

Tracker miners (for example tracker-miner-fs-3) are started for GDM, lightdm, 
other system users, and waste RAM + SSD resources. I don't think tracker miners 
should be started for such users.
At https://bugs.debian.org/981089 I've found solution how to fix this important 
issue - I'm pasting with trivial change to work on Ubuntu 22.04 and newer:

The fix is to change one line in all tracker-miners systemd files:
/usr/lib/systemd/user/tracker-miner-fs-3.service
/usr/lib/systemd/user/tracker-miner-fs-control-3.service
/usr/lib/systemd/user/tracker-extract-3.service

From: ConditionUser=!root
To:   ConditionUser=!@system

On running system you can run simple sed command:

sed -i 's|ConditionUser=!root|ConditionUser=!@system|'
/usr/lib/systemd/user/tracker-{extract-3,miner-fs-*}.service

I can provide a debdiff if you can include this trivial patch into LTS
release.

** Affects: tracker-miners (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: tracker-miners (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: jammy patch

** Patch added: "disable tracker-miners for system-users - patch"
   
https://bugs.launchpad.net/bugs/2007755/+attachment/5648305/+files/disable_tracker-miners_for_system-users.patch

** Bug watch added: Debian Bug tracker #981089
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981089

** Also affects: tracker-miners (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981089
   Importance: Unknown
   Status: Unknown

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

Title:
  Tracker miners (eg. tracker-miner-fs-3) are started for GDM and other
  system users

Status in tracker-miners package in Ubuntu:
  New
Status in tracker-miners package in Debian:
  Unknown

Bug description:
  Tracker miners (for example tracker-miner-fs-3) are started for GDM, lightdm, 
other system users, and waste RAM + SSD resources. I don't think tracker miners 
should be started for such users.
  At https://bugs.debian.org/981089 I've found solution how to fix this 
important issue - I'm pasting with trivial change to work on Ubuntu 22.04 and 
newer:

  The fix is to change one line in all tracker-miners systemd files:
  /usr/lib/systemd/user/tracker-miner-fs-3.service
  /usr/lib/systemd/user/tracker-miner-fs-control-3.service
  /usr/lib/systemd/user/tracker-extract-3.service

  From: ConditionUser=!root
  To:   ConditionUser=!@system

  On running system you can run simple sed command:

  sed -i 's|ConditionUser=!root|ConditionUser=!@system|'
  /usr/lib/systemd/user/tracker-{extract-3,miner-fs-*}.service

  I can provide a debdiff if you can include this trivial patch into LTS
  release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/2007755/+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 2002941] Re: [BPO] libreoffice 7.4.4 for jammy

ricotz, please upload fixed 7.4.4 build with crash fix for 
https://bugs.documentfoundation.org/show_bug.cgi?id=153059 into 
ppa:libreoffice/ppa too, because Ubuntu 22.04 and 20.04 users now use buggy 
7.4.4.2 release :(
See issue LP:2003735

** Bug watch added: Document Foundation Bugzilla #153059
   https://bugs.documentfoundation.org/show_bug.cgi?id=153059

-- 
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/2002941

Title:
  [BPO] libreoffice 7.4.4 for jammy

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Jammy:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release

   * This source packages matches the proposed SRU for kinetic handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001911
     and its backport is currently provided by the LibreOffice Fresh PPA at
   https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages

   * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently
  released in jammy.

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Scope]

   * Backport of
  https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.1

   * Backport target is Jammy/22.04 LTS only to provide an official
  build of a more recent upstream version of LibreOffice

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_74/1542/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
 Tested build at 
https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+sourcepub/14441833/+listing-archive-extra

  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/amd64/libr/libreoffice/20230117_121308_55f21@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/arm64/libr/libreoffice/20230117_004531_c08ab@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/armhf/libr/libreoffice/20230117_192827_df4b4@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/ppc64el/libr/libreoffice/20230116_230929_28cc3@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/s390x/libr/libreoffice/20230117_034834_09f33@/log.gz

   * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented
  by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2002941/+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 1965105] Re: application crashes since update

amyekut, LibreOffice 7.2.x is already out of support, could you test if
your issue still appears on latest stable libreoffice release 7.4.4 from
https://launchpad.net/~libreoffice/+archive/ppa (ppa:libreoffice/ppa )

-- 
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/1965105

Title:
  application crashes since update

Status in libreoffice package in Ubuntu:
  New

Bug description:
  
  Since a few days ago the program LibreOffice Writer is broken.

  1) Does not launch, or launches after several clicks a long (> 2 min)
  dely.

  2) When open, the program often freezes and needs to be killed.

  My system:

  Operating System: Kubuntu 21.10
  KDE Plasma Version: 5.24.3
  KDE Frameworks Version: 5.91.0
  Qt Version: 5.15.2
  Kernel Version: 5.13.0-35-generic (64-bit)
  Graphics Platform: X11
  Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz
  Memory: 15.3 GiB of RAM
  Graphics Processor: Mesa Intel® Xe Graphics

  
  Using Hebrew.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libreoffice-writer 1:7.2.5-0ubuntu0.21.10.3
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Mar 16 11:19:12 2022
  InstallationDate: Installed on 2021-06-15 (273 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to impish on 2022-01-12 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1965105/+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 2001910] Re: Libreoffice Impress crashes when exiting presentation with high-dpi scaling in GNOME

peterfrank/zengmao, could you test if issue still appears on latest stable 
LibreOffice 7.4.4 from ppa:libreoffice/ppa ?
See https://launchpad.net/~libreoffice/+archive/ubuntu/ppa

-- 
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/2001910

Title:
  Libreoffice Impress crashes when exiting presentation with high-dpi
  scaling in GNOME

Status in libreoffice package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.04.01, LibreOffice Impress (version
  1:7.3.7-0ubuntu0.22.04.1) crashes when exiting the presentation mode,
  if I enable 200% scaling in GNOME settings on my high-dpi screen. The
  application window disappears silently instead of returning to the
  editing mode. The error message is (if Impress is started from a
  terminal):

  
  X-Error: BadDrawable (invalid Pixmap or Window parameter)
Major opcode: 62 (X_CopyArea)
Resource ID:  0x1202be7
Serial No:59699 (59699)
  These errors are reported asynchronously,
  set environment variable SAL_SYNCHRONIZE to 1 to help debugging
  Unspecified Application Error
  

  The crash occurs reliably every time. The crash does not happen if I
  do not use scaling in GNOME display settings, or if I turn off the
  "hardware acceleration" option in Impress --> Tools --> Options -->
  LibreOffice --> View --> Graphics Output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001910/+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 2003735] Re: [SRU] libreoffice 7.4.4 updates for kinetic

ricotz, please upload fixed 7.4.4 build with crash fix for
https://bugs.documentfoundation.org/show_bug.cgi?id=153059 into
ppa:libreoffice/ppa too, because Ubuntu 22.04 and 20.04 users now use
buggy 7.4.4.2 release :(

-- 
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/2003735

Title:
  [SRU] libreoffice 7.4.4 updates for kinetic

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Kinetic:
  Fix Committed
Status in libreoffice source package in Lunar:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 7.4.5.1 is a hotfix release of the 7.4 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.5_release
   https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1

   * It includes one crash fix for 
https://bugs.documentfoundation.org/show_bug.cgi?id=153059
   
https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1=ef02234e55c1ca0890b6882fb2d9a33328cbb88e

   * This SRU will cherry-pick this specific patch only.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_74/1604/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

* Test plan for this crash fix
  1. Open a new writer document
  2. Insert a page break
  3. Go to page 1 and click on the header
  4. Go to page 2 and click on the header button
  -> Crash

  [Regression Potential]

   * This is well defined and upstream tested patch to fix a specific
  crash.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/2003735/+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 1873398] Re: gnome-disks won't do SMART on NVME drive

2022-12-19 Thread Mantas Kriaučiūnas

** Tags removed: amd64
** Tags added: jammy

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

Title:
  gnome-disks won't do SMART on NVME drive

Status in GNOME Disks:
  New
Status in gnome-disk-utility package in Ubuntu:
  Triaged

Bug description:
  I'm running 20.04 beta amd64 Desktop from a USB stick of the live ISO.

  I opened Disks (gnome-disks) and it sees all my drives, but it won't
  show SMART stats on my NVME drive (Samsung SSD 970 EVO Plus 500GB).
  The SMART menu item is greyed out.  It works fine on other drives.

  The NVME has SMART support; it works fine with smartctl -a /dev/nvme0n1 for 
example.  (Though smartctl is not in this live ISO, I have apt-get installed it 
at another time and tried it; and
  it works fine in the Ubuntu 18.04 that is installed on this machine.)

  I've attached a screencast showing the failure.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-disk-utility 3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 17 07:32:43 2020
  ExecutablePath: /usr/bin/gnome-disks
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1873398/+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 1959747] Re: [upstream] Very high CPU and slow responsiveness in Thunderbird 91-102

2022-11-23 Thread Mantas Kriaučiūnas

** Summary changed:

- [upstream] Very high CPU and slow responsiveness in Thunderbird 91
+ [upstream] Very high CPU and slow responsiveness in Thunderbird 91-102

** Description changed:

- Very high CPU and slow responsiveness in Thunderbird 91.5.0. Just moving
- the mouse cursor over a message list results in 365% CPU for me.
+ Very high CPU and slow responsiveness in Thunderbird 91.5.0 and later.
+ Just moving the mouse cursor over a message list results in 365% CPU for
+ me.
  
  I had to set this in the config editor to fix it:
  
    gfx.webrender.force-disabled = TRUE
  
  Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423

-- 
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/1959747

Title:
  [upstream] Very high CPU and slow responsiveness in Thunderbird 91-102

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Very high CPU and slow responsiveness in Thunderbird 91.5.0 and later.
  Just moving the mouse cursor over a message list results in 365% CPU
  for me.

  I had to set this in the config editor to fix it:

    gfx.webrender.force-disabled = TRUE

  Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959747/+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 1559129] Re: Replace defaults.list by mimeapps.list

2022-04-26 Thread Mantas Kriaučiūnas

** Tags added: jammy

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

Title:
  Replace defaults.list by mimeapps.list

Status in desktop-file-utils package in Ubuntu:
  Confirmed

Bug description:
  That's something we forgot to do, maybe worth doing before the LTS?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1559129/+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 1970248] Re: .deb files open with Archive Manager by default

2022-04-26 Thread Mantas Kriaučiūnas

GNOME 40 and newer doesn't use /usr/share/applications/defaults.list
file, I think this is the main issue why deb files are opened by Archive
Manager, for more info look at

https://help.gnome.org/admin/system-admin-guide/stable/mime-types-
application.html.en

Quick fix could be to change the name of /usr/share/applications/defaults.list 
symlink to mimeapps.list , but I'm not 100% sure, because there is a line in 
/usr/share/applications/gnome-mimeapps.list
application/x-deb=org.gnome.FileRoller.desktop

The /usr/share/applications/mimeapps.list and
/usr/share/applications/gnome-mimeapps.list files specify which
application is registered to open specific MIME types by default. These
files are provided by the distribution.

To override the system defaults for all users on the system, you need to
create a /etc/xdg/mimeapps.list or /etc/xdg/gnome-mimeapps.list file
with a list of MIME types for which you want to override the default
registered application.

Files located in /etc/xdg/ take precedence over files found in
/usr/share/applications/. Additionally, /etc/xdg/gnome-mimeapps.list
takes precedence over /etc/xdg/mimeapps.list

Btw, there is a bug #1559129 (Replace defaults.list by mimeapps.list)
already reported few years ago by Ubuntu developer, but it seems someone
forgot to fix that :(

** Also affects: desktop-file-utils (Baltix)
   Importance: Undecided
   Status: New

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

Title:
  .deb files open with Archive Manager by default

Status in snap-store-desktop:
  Triaged
Status in desktop-file-utils package in Ubuntu:
  Triaged
Status in desktop-file-utils source package in Jammy:
  Triaged
Status in desktop-file-utils package in Baltix:
  New

Bug description:
  Impact
  --
  Someone who downloads a .deb file usually wants to install the .deb when they 
open it. Opening it with Archive Manager is really confusing.

  Test Case
  -
  Download a .deb
  Open your Downloads folder with the file manager.
  Double click on the .deb
  The Ubuntu Software app should open with a button that says Install.

  More Details
  
  desktop-file-utils provides /etc/gnome/defaults.list
  In that file, there is this line (and several other lines also referring to 
the same .desktop)

  application/vnd.debian.binary-package=snap-store_ubuntu-software-
  local-file.desktop

  But when I look at /snap/snap-store/575/usr/share/applications/
  there is gnome-software-local-file.desktop

  which is a different file name.

  I believe this issue can be fixed in either snap-store or with
  desktop-file-utils.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store-desktop/+bug/1970248/+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 1886271] Re: HEIF support should be installed by default

2021-11-13 Thread Mantas Kriaučiūnas

** Also affects: baltix-default-settings
   Importance: Undecided
   Status: New

** Changed in: baltix-default-settings
   Importance: Undecided => High

** Changed in: baltix-default-settings
 Assignee: (unassigned) => Mantas Kriaučiūnas (mantas)

** Changed in: baltix-default-settings
   Status: New => Triaged

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

Title:
  HEIF support should be installed by default

Status in Default settings and artwork for Baltix OS:
  Triaged
Status in eog package in Ubuntu:
  Confirmed

Bug description:
  The HEIF image file format [1] is getting quite popular, mainly
  because this is now the default image format for iOS [2].
  Unfortunately, this is not supported by default in Ubuntu (20.04). In
  practice, this means that if someone sends you a picture from an
  iPhone, you won't be able to look at it (and the error message in eog
  is just saying this "is not a image",  not hinting at all that
  installing a small package could solve it).

  Therefore, I'd recommend installing by default the following two extra 
packages. This is about 60kB: 
  heif-gdk-pixbuf
  heif-thumbnailer

  
  [1] https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format
  [2] https://www.imyfone.com/phone-data-transfer/what-is-iphone-heic/

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1886271/+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 1886271] Re: HEIF support should be installed by default

2021-11-13 Thread Mantas Kriaučiūnas

I think heif-gdk-pixbuf package should be recommended by ubuntu-desktop
or ubuntu-desktop-minimal metapackages, because HEIF (.HEIC ) pictures
are very popular in these days and not all people keep eog viewer
installed ;)

also we should patch org.gnome.eog.desktop file to add "image/heif;" to
MimeType=

** Tags added: focal impish jammy

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

Title:
  HEIF support should be installed by default

Status in eog package in Ubuntu:
  Confirmed

Bug description:
  The HEIF image file format [1] is getting quite popular, mainly
  because this is now the default image format for iOS [2].
  Unfortunately, this is not supported by default in Ubuntu (20.04). In
  practice, this means that if someone sends you a picture from an
  iPhone, you won't be able to look at it (and the error message in eog
  is just saying this "is not a image",  not hinting at all that
  installing a small package could solve it).

  Therefore, I'd recommend installing by default the following two extra 
packages. This is about 60kB: 
  heif-gdk-pixbuf
  heif-thumbnailer

  
  [1] https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format
  [2] https://www.imyfone.com/phone-data-transfer/what-is-iphone-heic/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1886271/+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 1896842] Re: Update simple-scan in Ubuntu 20.04 to 3.36.6 (fixes cannot scan a page using EPSON V39 scanner)

2020-11-24 Thread Mantas Kriaučiūnas

** Changed in: simple-scan (Ubuntu)
   Status: Fix Committed => Confirmed

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

Title:
  Update simple-scan in Ubuntu 20.04 to 3.36.6 (fixes cannot scan a page
  using EPSON V39 scanner)

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of simple-scan -
  fixes this and other issues, existing in older simple-scan 3.36.3,
  which is currently in Ubuntu 20.04 LTS (focal):

  Overview of changes in simple-scan 3.36.4

* Fix color scanning for Brother ADS 2200 and 2700 sane backend.
* Updated translations.

  Overview of changes in simple-scan 3.36.6

* Display error message if simple-scan is unable to open simple-scan.log
* Fix scanning on Epson devices, when Automatic Page Size is enabled.

  [ QA ]

  GNOME has a micro release exception that covers this package.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  So we don't need to verify the fixes explicitly.

   original bug report 
  ishabalov@black:~$ simple-scan --debug
  [+0.00s] DEBUG: simple-scan.vala:1720: Starting simple-scan 3.36.3, PID=38292
  [+0.00s] DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
  [+0.01s] DEBUG: _g_io_module_get_default: Found default implementation dconf 
(DConfSettingsBackend) for ‘gsettings-backend’
  [+0.09s] DEBUG: app-window.vala:1906: Loading state from 
/home/ishabalov/.cache/simple-scan/state
  [+0.09s] DEBUG: app-window.vala:1885: Restoring window to 1351x672 pixels
  [+0.17s] DEBUG: scanner.vala:1539: sane_init () -> SANE_STATUS_GOOD
  [+0.17s] DEBUG: scanner.vala:1545: SANE version 1.0.29
  [+0.17s] DEBUG: scanner.vala:1606: Requesting redetection of scan devices
  [+0.17s] DEBUG: scanner.vala:828: Processing request
  [+0.56s] DEBUG: app-window.vala:1981: Saving state to 
/home/ishabalov/.cache/simple-scan/state
  [+8.42s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
  [+8.42s] DEBUG: scanner.vala:353: Device: 
name="imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0"
 vendor="EPSON" model="Epson_Perfection_V39" type=""
  [+8.72s] DEBUG: app-window.vala:1981: Saving state to 
/home/ishabalov/.cache/simple-scan/state
  [+9.90s] DEBUG: simple-scan.vala:1536: Requesting scan at 300 dpi from device 
'imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0'
  [+9.90s] DEBUG: scanner.vala:1674: Scanner.scan 
("imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0",
 dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0, 
paper_height=0, brightness=26, contrast=46, delay=3000ms)
  [+9.90s] DEBUG: scanner.vala:828: Processing request
  [+10.17s] DEBUG: scanner.vala:889: sane_open 
("imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0")
 -> SANE_STATUS_GOOD
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (0)
  [+10.17s] DEBUG: scanner.vala:760: Option 0: type=int size=4 
cap=soft-detect,advanced
  [+10.17s] DEBUG: scanner.vala:763:   Description:
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (1)
  [+10.17s] DEBUG: scanner.vala:760: Option 1: name='device-02-general' 
title='General' type=group size=0 cap=inactive
  [+10.17s] DEBUG: scanner.vala:763:   Description: Basic options.
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (2)
  [+10.17s] DEBUG: scanner.vala:760: Option 2: name='source' title='Document 
Source' type=string size=15 values=["Document Table"] cap=soft-detect
  [+10.17s] DEBUG: scanner.vala:763:   Description: Document Source
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (3)
  [+10.17s] DEBUG: scanner.vala:760: Option 3: name='enable-resampling' 
title='Enable Resampling' type=bool size=4 cap=soft-detect,inactive,advanced
  [+10.17s] DEBUG: scanner.vala:763:   Description: This option provides the 
user with a wider range of supported resolutions.  Resolutions not supported by 
the hardware will be achieved through image processing methods.
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (4)
  [+10.17s] DEBUG: scanner.vala:760: Option 4: name='resolution' 
title='Resolution' type=int size=4 unit=dpi min=50, max=4800, quant=0 
cap=soft-select,soft-detect
  [+10.17s] DEBUG: scanner.vala:763:   Description: Resolution
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (5)
  [+10.17s] DEBUG: scanner.vala:760: Option 5: name='scan-area' title='Scan 
Area' type=string size=19 values=["Executive/Portrait", "ISO/A4/Portrait", 
"ISO/A5/Portrait", "ISO/A5/Landscape", "ISO/A6/Portrait", "ISO/A6/Landscape", 
"JIS/B5/Portrait", "JIS/B6/Portrait", "JIS/B6/Landscape", "Letter/Portrait", 
"Manual", "Maximum"]

[Desktop-packages] [Bug 1896842] Re: Update simple-scan in Ubuntu 20.04 to 3.36.6 (fixes cannot scan a page using EPSON V39 scanner)

2020-11-08 Thread Mantas Kriaučiūnas

** Summary changed:

- simple-scan cannot scan a page using EPSON V39 scanner
+ Update simple-scan in Ubuntu 20.04 to 3.36.6 (fixes cannot scan a page using 
EPSON V39 scanner)

** Tags added: focal

** Description changed:

+ [ Description ]
+ 
+ GNOME upstream have released a new stable version of simple-scan - fixes
+ this and other issues, existing in older simple-scan 3.36.3, which is
+ currently in Ubuntu 20.04 LTS (focal):
+ 
+ Overview of changes in simple-scan 3.36.4
+ 
+   * Fix color scanning for Brother ADS 2200 and 2700 sane backend.
+   * Updated translations.
+ 
+ Overview of changes in simple-scan 3.36.6
+ 
+   * Display error message if simple-scan is unable to open simple-scan.log
+   * Fix scanning on Epson devices, when Automatic Page Size is enabled.
+ 
+ [ QA ]
+ 
+ GNOME has a micro release exception that covers this package.
+ 
+ https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
+ 
+ So we don't need to verify the fixes explicitly.
+ 
+  original bug report 
  ishabalov@black:~$ simple-scan --debug
  [+0.00s] DEBUG: simple-scan.vala:1720: Starting simple-scan 3.36.3, PID=38292
  [+0.00s] DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
  [+0.01s] DEBUG: _g_io_module_get_default: Found default implementation dconf 
(DConfSettingsBackend) for ‘gsettings-backend’
  [+0.09s] DEBUG: app-window.vala:1906: Loading state from 
/home/ishabalov/.cache/simple-scan/state
  [+0.09s] DEBUG: app-window.vala:1885: Restoring window to 1351x672 pixels
  [+0.17s] DEBUG: scanner.vala:1539: sane_init () -> SANE_STATUS_GOOD
  [+0.17s] DEBUG: scanner.vala:1545: SANE version 1.0.29
  [+0.17s] DEBUG: scanner.vala:1606: Requesting redetection of scan devices
  [+0.17s] DEBUG: scanner.vala:828: Processing request
  [+0.56s] DEBUG: app-window.vala:1981: Saving state to 
/home/ishabalov/.cache/simple-scan/state
  [+8.42s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
  [+8.42s] DEBUG: scanner.vala:353: Device: 
name="imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0"
 vendor="EPSON" model="Epson_Perfection_V39" type=""
  [+8.72s] DEBUG: app-window.vala:1981: Saving state to 
/home/ishabalov/.cache/simple-scan/state
  [+9.90s] DEBUG: simple-scan.vala:1536: Requesting scan at 300 dpi from device 
'imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0'
  [+9.90s] DEBUG: scanner.vala:1674: Scanner.scan 
("imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0",
 dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0, 
paper_height=0, brightness=26, contrast=46, delay=3000ms)
  [+9.90s] DEBUG: scanner.vala:828: Processing request
  [+10.17s] DEBUG: scanner.vala:889: sane_open 
("imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0")
 -> SANE_STATUS_GOOD
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (0)
  [+10.17s] DEBUG: scanner.vala:760: Option 0: type=int size=4 
cap=soft-detect,advanced
- [+10.17s] DEBUG: scanner.vala:763:   Description: 
+ [+10.17s] DEBUG: scanner.vala:763:   Description:
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (1)
  [+10.17s] DEBUG: scanner.vala:760: Option 1: name='device-02-general' 
title='General' type=group size=0 cap=inactive
  [+10.17s] DEBUG: scanner.vala:763:   Description: Basic options.
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (2)
  [+10.17s] DEBUG: scanner.vala:760: Option 2: name='source' title='Document 
Source' type=string size=15 values=["Document Table"] cap=soft-detect
  [+10.17s] DEBUG: scanner.vala:763:   Description: Document Source
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (3)
  [+10.17s] DEBUG: scanner.vala:760: Option 3: name='enable-resampling' 
title='Enable Resampling' type=bool size=4 cap=soft-detect,inactive,advanced
  [+10.17s] DEBUG: scanner.vala:763:   Description: This option provides the 
user with a wider range of supported resolutions.  Resolutions not supported by 
the hardware will be achieved through image processing methods.
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (4)
  [+10.17s] DEBUG: scanner.vala:760: Option 4: name='resolution' 
title='Resolution' type=int size=4 unit=dpi min=50, max=4800, quant=0 
cap=soft-select,soft-detect
  [+10.17s] DEBUG: scanner.vala:763:   Description: Resolution
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (5)
  [+10.17s] DEBUG: scanner.vala:760: Option 5: name='scan-area' title='Scan 
Area' type=string size=19 values=["Executive/Portrait", "ISO/A4/Portrait", 
"ISO/A5/Portrait", "ISO/A5/Landscape", "ISO/A6/Portrait", "ISO/A6/Landscape", 
"JIS/B5/Portrait", "JIS/B6/Portrait", "JIS/B6/Landscape", "Letter/Portrait", 
"Manual", "Maximum"] cap=soft-select,soft-detect
  [+10.17s] DEBUG: scanner.vala:763:   Description: Scan Area
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (6)
  [+10.17s]

[Desktop-packages] [Bug 1881753] Re: Cannot scan in Photo mode with Brother MFC L3770 CDW

2020-11-08 Thread Mantas Kriaučiūnas

Could you test if this bug with  color scan in Photo mode isn't fixed in
simple-scan 3.36.4 or newer - I've found this in NEWS file:

Overview of changes in simple-scan 3.36.4
  * Fix color scanning for Brother ADS 2200 and 2700 sane backend.
  * Updated translations.


Overview of changes in simple-scan 3.37.3
  * Improve compression scale which appear during file saving, to be more
intuitive.
  * Fix color scanning for Brother ADS 2200 and 2700 sane backend.

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

Title:
  Cannot scan in Photo mode with Brother MFC L3770 CDW

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  Starting simple-scan 3.28.0-0ubuntu1 (Ubuntu 18.04.4), with a Brother
  MFC L3770 CDW and Brother br* packages installed and configured.

  - If the Photo mode is selected by default, a scan will be in color (no 
problem).
  - From step1, switching to text mode, the scan is monochrome (again no 
problem).
  - From step2, switching to Photo mode, all subsequent scans will be 
monochrome (ARGH ;-)).

  
  Looking at simple-scan git history, I found an interesting commit (I did not 
go with a full git bisect).
  
https://github.com/GNOME/simple-scan/commit/12e9c02a6cccf6b17aada9a26987007eb6d1360d

  I reproduced the problem on the sha1 preceeding this one.
  But on this sha1 (and on the current master), the problem is fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1881753/+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 1864215] Re: Please add webp loader to gdk-pixbuf

2020-07-14 Thread Mantas Kriaučiūnas

** Also affects: gdk-pixbuf (Baltix)
   Importance: Undecided
   Status: New

** Changed in: gdk-pixbuf (Baltix)
Milestone: None => baltix-18.04

** Changed in: gdk-pixbuf (Baltix)
   Importance: Undecided => Low

** Changed in: gdk-pixbuf (Baltix)
   Status: New => Triaged

** Bug watch added: gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues #103
   https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/103

** Also affects: gdk-pixbuf via
   https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/103
   Importance: Unknown
   Status: Unknown

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

Title:
  Please add webp loader to gdk-pixbuf

Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  Confirmed
Status in gdk-pixbuf package in Baltix:
  Triaged

Bug description:
  Attempting to load a webp image -- for instance, 

https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp
  or

https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg
  -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file 
format" error.

  Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in
  libwebp, but isn't this really a gdk-pixbuf issue? If it really does
  belong to libwebp, my apologies, please dup this bug to 1407644 (I'm
  confident it doesn't belong to eog since I don't use that program; I
  have other programs that use libgdk-pixbuf).

  You can probably use eog to test this, or run
  /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i 
webp
  (I assume the loader would mention webp if there was a loader for it).

  I have these packages installed in addition to libgdk-pixbuf2.0-0:
  libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes
  the format:

  $ file /tmp/FKK78W.jpg.webp
  /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 
1200x533, Scaling: [none]x[none], YUV color, decoders should clamp

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  Date: Fri Feb 21 08:48:36 2020
  InstallationDate: Installed on 2019-10-10 (133 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1864215/+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 1835220] Re: Please support /usr/lib64/sane

2020-07-14 Thread Mantas Kriaučiūnas

** Changed in: sane-backends (Baltix)
Milestone: None => baltix-18.04

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

Title:
  Please support /usr/lib64/sane

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Baltix:
  Confirmed
Status in sane-backends package in Debian:
  New

Bug description:
  The patch 0125-multiarch_dll_search_path.patch makes /usr/lib/sane be
  recognized as a directory for SANE backends. However, some .deb files
  with scanner drivers, typically provided by Brother, install files in
  /usr/lib64/sane. It would be great if that directory could be
  supported too.

  This issue has been discussed in bug #1728012, but was broken out from
  there to not block another more important change in bionic.

  If Debian accepts the proposal in ,
  the change is a SRU candidate to bionic at first hand.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1835220/+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 1746738] Re: резервное копирование не удалось

2020-07-05 Thread Mantas Kriaučiūnas

** Package changed: memtest86+ (Ubuntu) => ubuntu

** Package changed: ubuntu => deja-dup (Ubuntu)

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

Title:
  резервное копирование не удалось

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Создать резервную копию. Пишет: резервное копирование не удалось
  (неизвестная ошибка).   "The above configuration updates the
  package list, downloads, and installs available upgrades every day.
  The local download archive is cleaned every week. On servers upgraded
  to newer versions of Ubuntu, depending on your responses, the file
  listed above may not be there. In this case, creating a new file of
  this name should also work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1746738/+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 1835706] Re: Extensions don't load in gnome-shell 3.34/3.36 (Ubuntu 19.10-20.04)

2020-06-29 Thread Mantas Kriaučiūnas

Working latest version of gnome-shell-extension-weather packages are in main 
Baltix-Ubuntu operating system repositories - ppa:baltix, simply add this repo:
sudo add-apt-repository ppa:baltix/ppa

Look at https://code.launchpad.net/~baltix/+archive/ubuntu/ppa and
https://code.launchpad.net/~gnome-shell-extensions/+recipe/gnome-shell-
extension-openweather for more info.

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

Title:
  Extensions don't load in gnome-shell 3.34/3.36 (Ubuntu 19.10-20.04)

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-weather package in Ubuntu:
  Confirmed

Bug description:
  Some extensions don't load in gnome-shell 3.33/3.34

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+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 1835706] Re: Extensions don't load in gnome-shell 3.34/3.36 (Ubuntu 19.10-20.04)

2020-06-29 Thread Mantas Kriaučiūnas

** Summary changed:

- Extensions don't load in gnome-shell 3.33/3.34
+ Extensions don't load in gnome-shell 3.34/3.36 (Ubuntu 19.10-20.04)

** Tags added: focal

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

Title:
  Extensions don't load in gnome-shell 3.34/3.36 (Ubuntu 19.10-20.04)

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-weather package in Ubuntu:
  Confirmed

Bug description:
  Some extensions don't load in gnome-shell 3.33/3.34

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+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 1844808] Re: Can't delete file from desktop by clicking it and hitting delete key

2020-05-30 Thread Mantas Kriaučiūnas

** Also affects: gnome-shell-extension-desktop-icons (Baltix)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell-extension-desktop-icons (Baltix)
   Status: New => In Progress

** Changed in: gnome-shell-extension-desktop-icons (Baltix)
 Assignee: (unassigned) => Mantas Kriaučiūnas (mantas)

** Changed in: gnome-shell-extension-desktop-icons (Baltix)
Milestone: None => baltix-18.04

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

Title:
  Can't delete file from desktop by clicking it and hitting delete key

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Focal:
  Fix Committed
Status in gnome-shell-extension-desktop-icons package in Baltix:
  In Progress

Bug description:
  Just upgraded to 19.10 today. Previously, in 19.04, I could delete a
  file from the desktop by clicking on it and hitting the delete key.
  That no longer works.

  It's probably relevant that it doesn't appear to be possible to direct
  keyboard focus to the desktop itself any longer. When I click on an
  icon on the desktop and then hit the delete key, the keystroke is sent
  to the window that had focus before I clicked. This appears to be true
  regardless of what window focus mode I'm using (Click to Focus, Focus
  on Hover, or Secondary-Click). Note that the description of Secondary-
  Click, "Window is focused when hovered with the pointer. Hovering the
  desktop removes focus from the previous window," does not appear to be
  true. When I select that focus mode and hover my mouse over the
  desktop I remain focused on the previously focused window.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-desktop-icons 19.01.4-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 20 11:12:42 2019
  InstallationDate: Installed on 2019-09-12 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1844808/+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 1835220] Re: Please support /usr/lib64/sane

2020-05-14 Thread Mantas Kriaučiūnas

** Also affects: sane-backends (Baltix)
   Importance: Undecided
   Status: New

** Changed in: sane-backends (Baltix)
   Status: New => Confirmed

** Changed in: sane-backends (Baltix)
   Importance: Undecided => Medium

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

Title:
  Please support /usr/lib64/sane

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Baltix:
  Confirmed
Status in sane-backends package in Debian:
  New

Bug description:
  The patch 0125-multiarch_dll_search_path.patch makes /usr/lib/sane be
  recognized as a directory for SANE backends. However, some .deb files
  with scanner drivers, typically provided by Brother, install files in
  /usr/lib64/sane. It would be great if that directory could be
  supported too.

  This issue has been discussed in bug #1728012, but was broken out from
  there to not block another more important change in bionic.

  If Debian accepts the proposal in ,
  the change is a SRU candidate to bionic at first hand.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1835220/+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 1741977] Re: Scanning fails with many Samsung multifunctions (SCX-3200, SCX-3400, CLX-6260) after upgrading to Ubuntu 17.10/18.04 (SANE_USB_WORKAROUND=1 needed)

2020-05-14 Thread Mantas Kriaučiūnas

** Changed in: sane-backends (Baltix)
Milestone: None => baltix-18.04

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

Title:
  Scanning fails with many Samsung multifunctions (SCX-3200, SCX-3400,
  CLX-6260) after upgrading to Ubuntu 17.10/18.04 (SANE_USB_WORKAROUND=1
  needed)

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Baltix:
  Triaged
Status in sane-backends package in Fedora:
  Fix Released

Bug description:
  Upgraded from kubuntu 17.04 to 17.10. Before the upgrade I was able to
  use my printer/scanner Samsung SCX-3200 without problems, with 17.10 I
  can only use the printer part.

  sane-find-scanner finds the scanner

  $ sane-find-scanner -q
  [...]
  product=0x3441 [SCX-3200 Series]) at libusb:003:019
  [...]

  Scanning fails with many Samsung multifunctions (including SCX-3400,
  SCX-4624f, CLX-6260) after upgrading to Ubuntu 17.10/18.04

  It seems the best solution for now is to add SANE_USB_WORKAROUND=1
  line to /etc/environment:

  echo "SANE_USB_WORKAROUND=1" | sudo tee -a /etc/environment

  or to /etc/systemd/user.conf: echo
  "DefaultEnvironment=SANE_USB_WORKAROUND=1"|sudo tee -a
  /etc/systemd/user.conf

  For more info why SANE_USB_WORKAROUND=1 is needed look at 
http://www.sane-project.org release notes of 1.0.27: 
  Note 3: The Linux USB3 workaround which was added in version 1.0.25 is now 
disabled by default. If you have difficulty using a scanner which previously 
worked, or intermittent scanner availability, try setting the new environment 
variable SANE_USB_WORKAROUND=1 before starting frontend. 
  I found this info in comments of bug #1728012 and 
https://askubuntu.com/questions/966834/ubuntu-17-10-and-samsung-scx-4624f-scanner-not-working/966835

  When I start scanimage the first time, it can talk to the scanner just fine:
  $ export SANE_DEBUG_XEROX_MFP=255
  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffdf4d2e220, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x55d2e393c5d0
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] [70] a8 00 43 10 53 61 6d 73 75 6e 67 20 53 61 6d 73 75 6e 67 20 
53 43 58 2d 33 32 30 30 20 53 65 72 69 65 73 20 19 33 84 2b 00 00 27 d8 00 00 
36 d8 00 01 51 00 00 01 00 00 00 00 36 d8 00 00 36 d8 00 01 05 05 00...
  [xerox_mfp] dev_inquiry: found Samsung/Samsung SCX-3200 Series
  [xerox_mfp] usb_dev_close: closing dev 0x55d2e393c5d0
  device `xerox_mfp:libusb:003:018' is a Samsung Samsung SCX-3200 Series 
multi-function peripheral
  When I start scanimage a second time it cannot talk to the scanner anymore:

  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffe9ae18760, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x56138cfa1870
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] usb_dev_request: sanei_usb_read_bulk: Error during device I/O
  [xerox_mfp] dev_command: dev_request: Error during device I/O
  [xerox_mfp] usb_dev_close: closing dev 0x56138cfa1870
  [xerox_mfp] list_one_device: dev_inquiry(libusb:003:018): Error during device 
I/O

  Unplugging the usb cable and plugging it back in allows scanimage to
  talk to the scanner once. After that it fails again. The USB cable is
  not a problem, as it worked with 16.10.

  I downloaded VueScan and it has not problems to repeatedly scan pages
  using the same hw, which also indicates that this is a sw and not a hw
  problem. And just to mention it again, printing also works fine using
  the same cable. And yes, I tried multiple USB ports. All exhibit the
  same behaviour. When I execute scanimage -L once and start VueScan
  afterwards, then VueScan also doesn't see the scanner anymore. After
  unplugging and replugging the UBS cable and restarting VueScan, it's
  able to scan again.

  Looks to me like sane doesn't know how to talk to the scanner anymore.
  It seems that something get's messed up during the first usb command,
  which prevents subsequent usb commands from succeeding.

  I just downloaded 16.04.3 LTS and booted it from a USB stick. I can
  confirm that the scanner still works with 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: sane-utils 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jan  8 20:53:07 2018
  InstallationDate: Installed on 2016-04-03 (645 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily

[Desktop-packages] [Bug 1870102] Re: please sync gnome-user-docs 3.36.1-1 from Debian and add Lithuanian package

2020-04-03 Thread Mantas Kriaučiūnas

@gunnarhj maybe beta freeze is gone and you can update gnome-user-docs to 
3.36.1 today?
It would be nice for us to see current situation and finish Ubuntu-docs 
translation during weekend :)

-- 
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/1870102

Title:
  please sync gnome-user-docs 3.36.1-1 from Debian and add Lithuanian
  package

Status in gnome-user-docs package in Ubuntu:
  In Progress

Bug description:
  Please sync gnome-user-docs 3.36.1-1 from Debian and add gnome-user-docs-lt 
(Lithuanian) package - Lithuanian translation is missing in 3.36.0 and is added 
only in 3.36.1 release.
  I'm currently translating ubuntu-docs to Lithuanian language, so, it would be 
nice to have Ubuntu 20.04 release candidate with Lithuanian documentation :)

  Explanation of FeatureFreeze exception:
  3.36.1-1 contains newly added Lithuanian translation and updates of other 
languages:

  Upstream 3.36.1 NEWS:
   * Updates to GNOME Help (Rafael Fontenelle)
   * Updated translations:
     ca(Jordi Mas)
     es(Daniel Mustieles)
     fi(Jiri Grönroos)
     lt(Aurimas Černius)
     pl(Piotr Drąg)
     pt_BR (Rafael Fontenelle)
     sv(Anders Jonsson)

  debian/changelog since 3.36.0:

  gnome-user-docs (3.36.1-1) unstable; urgency=medium

    * New upstream release

   -- Jeremy Bicha   Sat, 28 Mar 2020 22:24:06 -0400

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1870102/+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 1870102] Re: [FFe] please sync gnome-user-docs 3.36.1-1 from Debian and add Lithuanian package

2020-04-01 Thread Mantas Kriaučiūnas

** Description changed:

- Please sync gnome-user-docs 3.36.1-1 from Debian and add gnome-user-
- docs-lt (Lithuanian) package - Lithuanian translation is missing in
- 3.36.0 and is added only in 3.36.1 release.
+ Please sync gnome-user-docs 3.36.1-1 from Debian and add gnome-user-docs-lt 
(Lithuanian) package - Lithuanian translation is missing in 3.36.0 and is added 
only in 3.36.1 release.
+ I'm currently translating ubuntu-docs to Lithuanian language, so, it would be 
nice to have Ubuntu 20.04 release candidate with Lithuanian documentation :)
  
  Explanation of FeatureFreeze exception:
  3.36.1-1 contains newly added Lithuanian translation and updates of other 
languages:
  
  Upstream 3.36.1 NEWS:
-  * Updates to GNOME Help (Rafael Fontenelle)
-  * Updated translations:
-ca(Jordi Mas)
-es(Daniel Mustieles)
-fi(Jiri Grönroos)
-lt(Aurimas Černius)
-pl(Piotr Drąg)
-pt_BR (Rafael Fontenelle)
-sv(Anders Jonsson)
+  * Updates to GNOME Help (Rafael Fontenelle)
+  * Updated translations:
+    ca(Jordi Mas)
+    es(Daniel Mustieles)
+    fi(Jiri Grönroos)
+    lt(Aurimas Černius)
+    pl(Piotr Drąg)
+    pt_BR (Rafael Fontenelle)
+    sv(Anders Jonsson)
  
  debian/changelog since 3.36.0:
  
  gnome-user-docs (3.36.1-1) unstable; urgency=medium
  
-   * New upstream release
+   * New upstream release
  
-  -- Jeremy Bicha   Sat, 28 Mar 2020 22:24:06 -0400
+  -- Jeremy Bicha   Sat, 28 Mar 2020 22:24:06 -0400

-- 
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/1870102

Title:
  [FFe] please sync gnome-user-docs 3.36.1-1 from Debian and add
  Lithuanian package

Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  Please sync gnome-user-docs 3.36.1-1 from Debian and add gnome-user-docs-lt 
(Lithuanian) package - Lithuanian translation is missing in 3.36.0 and is added 
only in 3.36.1 release.
  I'm currently translating ubuntu-docs to Lithuanian language, so, it would be 
nice to have Ubuntu 20.04 release candidate with Lithuanian documentation :)

  Explanation of FeatureFreeze exception:
  3.36.1-1 contains newly added Lithuanian translation and updates of other 
languages:

  Upstream 3.36.1 NEWS:
   * Updates to GNOME Help (Rafael Fontenelle)
   * Updated translations:
     ca(Jordi Mas)
     es(Daniel Mustieles)
     fi(Jiri Grönroos)
     lt(Aurimas Černius)
     pl(Piotr Drąg)
     pt_BR (Rafael Fontenelle)
     sv(Anders Jonsson)

  debian/changelog since 3.36.0:

  gnome-user-docs (3.36.1-1) unstable; urgency=medium

    * New upstream release

   -- Jeremy Bicha   Sat, 28 Mar 2020 22:24:06 -0400

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1870102/+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 1870102] [NEW] [FFe] please sync gnome-user-docs 3.36.1-1 from Debian and add Lithuanian package

2020-04-01 Thread Mantas Kriaučiūnas

Public bug reported:

Please sync gnome-user-docs 3.36.1-1 from Debian and add gnome-user-
docs-lt (Lithuanian) package - Lithuanian translation is missing in
3.36.0 and is added only in 3.36.1 release.

Explanation of FeatureFreeze exception:
3.36.1-1 contains newly added Lithuanian translation and updates of other 
languages:

Upstream 3.36.1 NEWS:
 * Updates to GNOME Help (Rafael Fontenelle)
 * Updated translations:
   ca(Jordi Mas)
   es(Daniel Mustieles)
   fi(Jiri Grönroos)
   lt(Aurimas Černius)
   pl(Piotr Drąg)
   pt_BR (Rafael Fontenelle)
   sv(Anders Jonsson)

debian/changelog since 3.36.0:

gnome-user-docs (3.36.1-1) unstable; urgency=medium

  * New upstream release

 -- Jeremy Bicha   Sat, 28 Mar 2020 22:24:06 -0400

** Affects: gnome-user-docs (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1870102

Title:
  [FFe] please sync gnome-user-docs 3.36.1-1 from Debian and add
  Lithuanian package

Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  Please sync gnome-user-docs 3.36.1-1 from Debian and add gnome-user-
  docs-lt (Lithuanian) package - Lithuanian translation is missing in
  3.36.0 and is added only in 3.36.1 release.

  Explanation of FeatureFreeze exception:
  3.36.1-1 contains newly added Lithuanian translation and updates of other 
languages:

  Upstream 3.36.1 NEWS:
   * Updates to GNOME Help (Rafael Fontenelle)
   * Updated translations:
 ca(Jordi Mas)
 es(Daniel Mustieles)
 fi(Jiri Grönroos)
 lt(Aurimas Černius)
 pl(Piotr Drąg)
 pt_BR (Rafael Fontenelle)
 sv(Anders Jonsson)

  debian/changelog since 3.36.0:

  gnome-user-docs (3.36.1-1) unstable; urgency=medium

* New upstream release

   -- Jeremy Bicha   Sat, 28 Mar 2020 22:24:06 -0400

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1870102/+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 1868216] Re: Please include updated Lithuanian, French and Polish translations from upstream

2020-03-20 Thread Mantas Kriaučiūnas

** Attachment added: "French translation from gnome-getting-started-docs 
upstream"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1868216/+attachment/5339238/+files/fr.po.gz

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

Title:
  Please include updated Lithuanian, French and Polish translations from
  upstream

Status in gnome-getting-started-docs package in Ubuntu:
  New

Bug description:
  Please include updated Lithuanian, French and Polish translations from
  upstream: https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/
  It is important to do ASAP because Ubuntu will be in Beta freeze very soon - 
Beta will be released at April 2nd.

  See https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/-/commits/master
  for more information.

  Also I'm attaching Lithuanian, French and Polish translations from GIT
  to this bugreport, please include :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1868216/+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 1868216] Re: Please include updated Lithuanian, French and Polish translations from upstream

2020-03-20 Thread Mantas Kriaučiūnas

** Attachment added: "Polish translation from gnome-getting-started-docs 
upstream"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1868216/+attachment/5339237/+files/pl.po.gz

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

Title:
  Please include updated Lithuanian, French and Polish translations from
  upstream

Status in gnome-getting-started-docs package in Ubuntu:
  New

Bug description:
  Please include updated Lithuanian, French and Polish translations from
  upstream: https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/
  It is important to do ASAP because Ubuntu will be in Beta freeze very soon - 
Beta will be released at April 2nd.

  See https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/-/commits/master
  for more information.

  Also I'm attaching Lithuanian, French and Polish translations from GIT
  to this bugreport, please include :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1868216/+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 1868216] [NEW] Please include updated Lithuanian, French and Polish translations from upstream

2020-03-20 Thread Mantas Kriaučiūnas

Public bug reported:

Please include updated Lithuanian, French and Polish translations from
upstream: https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/
It is important to do ASAP because Ubuntu will be in Beta freeze very soon - 
Beta will be released at April 2nd.

See https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/-/commits/master
for more information.

Also I'm attaching Lithuanian, French and Polish translations from GIT
to this bugreport, please include :)

** Affects: gnome-getting-started-docs (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: patch-accepted-upstream

** Attachment added: "Lithuanian translation from gnome-getting-started-docs 
upstream"
   https://bugs.launchpad.net/bugs/1868216/+attachment/5339236/+files/lt.po.gz

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

Title:
  Please include updated Lithuanian, French and Polish translations from
  upstream

Status in gnome-getting-started-docs package in Ubuntu:
  New

Bug description:
  Please include updated Lithuanian, French and Polish translations from
  upstream: https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/
  It is important to do ASAP because Ubuntu will be in Beta freeze very soon - 
Beta will be released at April 2nd.

  See https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/-/commits/master
  for more information.

  Also I'm attaching Lithuanian, French and Polish translations from GIT
  to this bugreport, please include :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1868216/+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 718693] Re: Can't type EURO symbol with AltGr+E using main lithuanian (lt) keymap

2020-02-12 Thread Mantas Kriaučiūnas

Current situation about this issue is described and fixed in bug
#1863001

** Changed in: baltix
   Status: New => Triaged

** Changed in: baltix
   Status: Triaged => In Progress

-- 
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/718693

Title:
  Can't type EURO symbol with AltGr+E using main lithuanian (lt) keymap

Status in xkeyboard-config package in Ubuntu:
  New
Status in Baltix:
  In Progress

Bug description:
  Binary package hint: xkeyboard-config

  Main lithuanian layout has no EURO symbol.

  Main lithuanian layout should have EURO symbol on key "e" (alt gr +
  e), like other layouts "Lithuanian US", "Lithuanian IBM", "Lihuanian
  Standard"  has it on key "e". Windows OS it is also on key "e".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/718693/+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 1664438] Re: updating device name in system settings doesn't update /etc/hosts

2020-02-12 Thread Mantas Kriaučiūnas

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  updating device name in system settings doesn't update /etc/hosts

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  probably a "paper cut" issue here. Issue exist on latest Ubuntu 19.10
  and older releases, like 18.04 and 16.04.

  Changed the hostname of a system recently by opening the system
  settings tool, into details, and typing a new device name.

  Noticed afterwards that running sudo commands in the terminal resulted
  in an 'unable to resolve hostname' message, although the commands ran
  successfully.

  Checked and it looked like changing the name updates /etc/hostname as
  expected, but it didn't update /etc/hosts for me - it still had:

  127.0.0.1 localhost
  127.0.1.1 (old hostname)

  Replacing the old hostname with the new one removed the message from
  the terminal when running sudo commands.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1664438/+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 1664438] Re: updating device name in system settings doesn't update /etc/hosts

2020-02-12 Thread Mantas Kriaučiūnas

** Tags added: eoan

** Description changed:

- probably a "paper cut" issue here. On 16.04.
+ probably a "paper cut" issue here. Issue exist on latest Ubuntu 19.10
+ and older releases, like 18.04 and 16.04.

Changed the hostname of a system recently by opening the system settings
tool, into details, and typing a new device name.

Noticed afterwards that running sudo commands in the terminal resulted
in an 'unable to resolve hostname' message, although the commands ran
successfully.

Checked and it looked like changing the name updates /etc/hostname as
expected, but it didn't update /etc/hosts for me - it still had:

127.0.0.1 localhost
127.0.1.1 (old hostname)

Replacing the old hostname with the new one removed the message from the
terminal when running sudo commands.

--
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/1664438

Title:
updating device name in system settings doesn't update /etc/hosts

Status in gnome-control-center package in Ubuntu:
Confirmed
Status in unity-control-center package in Ubuntu:
Confirmed

Bug description:
probably a "paper cut" issue here. Issue exist on latest Ubuntu 19.10
and older releases, like 18.04 and 16.04.

Changed the hostname of a system recently by opening the system
settings tool, into details, and typing a new device name.

Noticed afterwards that running sudo commands in the terminal resulted
in an 'unable to resolve hostname' message, although the commands ran
successfully.

Checked and it looked like changing the name updates /etc/hostname as
expected, but it didn't update /etc/hosts for me - it still had:

127.0.0.1 localhost
127.0.1.1 (old hostname)

Replacing the old hostname with the new one removed the message from
the terminal when running sudo commands.

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

[Desktop-packages] [Bug 1547127] Re: Guest account option - feature request

2020-01-11 Thread Mantas Kriaučiūnas

** Changed in: gdm3 (Baltix)
   Status: New => Triaged

** Changed in: gdm3 (Baltix)
   Importance: Undecided => Medium

** Tags added: focal

-- 
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/1547127

Title:
  Guest account option - feature request

Status in gdm:
  Expired
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gdm3 package in Baltix:
  Triaged

Bug description:
  Though I didn't have it enabled for security reasons when I was using
  Unity, I think that some may find it useful to have a 'guest account'
  option, though I think that it should be off by default and be
  reasonably easy to configure in the gnome-control-center.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1547127/+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 1811900] Re: SRU 3.28 latest git to bionic

2019-04-23 Thread Mantas Kriaučiūnas

Can you speed up publishing fixed gnome-shell to bionic-updates

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

Title:
  SRU 3.28 latest git to bionic

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in mutter source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Invalid

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+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 1798828] Re: gvfsd-trash fills up memory (uses about 1 GB) if Trash contains thousands of files

2018-10-19 Thread Mantas Kriaučiūnas

Bug #1558768 can be related, but that bug is abotu high CPU usage

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

Title:
  gvfsd-trash fills up memory (uses about 1 GB) if Trash contains
  thousands of files

Status in gvfs package in Ubuntu:
  New

Bug description:
  gvfsd-trash fills up memory (uses about 1 GB) if Trash contains
  thousands of files (I had ~8000)

  I noticed this on Ubuntu 16.04 64-bit with GNOME Shell installed:
  ~$ ps aux |grep -i trash
  uni0231910  6.2 20.0 1541900 789352 ?  Sl   12:53  10:11 
/usr/lib/gvfs/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_spaw/0

  Problem can be "solved" by emptying Trash bin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798828/+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 1558768] Re: gvfsd-trash causing high CPU-load when try to empty trash with thousands of files

2018-10-19 Thread Mantas Kriaučiūnas

I also noticed, that gvfsd-trash fills up memory (uses about 1 GB) if
Trash contains thousands of files, see bug #1798828

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

Title:
  gvfsd-trash causing high CPU-load when try to empty trash with
  thousands of files

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  - Ubuntu 16.04 (Xenial Xerus) Daily Build
  - AMD64
  - Unity

  Steps to reproduce:
  - a folder with thousands of files (here about 15000 files with a overall 
size of 1.5 GB)
  - delete files to trash
  - right-click at the trash icon
  - click empty trash

  A dialog "Dateioperationen" shows "vorbereiten" (it's German, I think
  in English the dialog has the title "file operations" and shows the
  text "prepare").

  This happens at this point:
  - the dialog remains unchanged
  - the process gvfsd-trash consumes up to 75% CPU, see output of top

  After 30 minutes of waiting for any reaction I killed the process. The
  trash still contains all the files.

  jan@janvm160464:~$ top

  top - 20:17:24 up 31 min,  1 user,  load average: 1,94, 1,97, 1,68
  Tasks: 244 gesamt,   5 laufend, 239 schlafend,   0 gestoppt,   0 Zombie
  %CPU(s): 85,1 be, 14,6 sy,  0,0 ni,  0,0 un,  0,0 wa,  0,0 hi,  0,3 si,  0,0 
st
  KiB Spch :  4037984 gesamt,  2142152 frei,   900784 belegt,   995048 
Puff/Cache
  KiB Swap:0 gesamt,0 frei,0 belegt.  3028940 verfü 
Spch 

PID USER  PR  NIVIRTRESSHR S %CPU %MEM ZEIT+ BEFEHL 
  
   1760 jan   20   0  454696  24448   7840 R 69,1  0,6  20:05.18 
gvfsd-trash  
   1690 jan   20   0  781012  71096  36440 S 12,0  1,8   6:13.42 nautilus   
  
   2649 jan   20   0  660088  41700  30328 S 10,3  1,0   0:04.29 gedit  
  
315 root  20   0   32236   2936   2500 R  3,3  0,1   1:06.21 
systemd-jou+ 
825 root  20   0  383184  77448  31492 S  1,3  1,9   0:15.84 Xorg   
  
   1543 jan   20   0 1254876 189468  65780 S  1,3  4,7   0:19.38 compiz 
  
641 syslog20   0  256380   3364   2684 S  1,0  0,1   0:16.81 rsyslogd   
  
   1521 jan   20   0  567508  32776  25756 S  0,7  0,8   0:01.16 
unity-panel+ 
   1448 jan   20   0   39728316 12 S  0,3  0,0   0:00.13 
upstart-dbu+ 
   2258 root  20   0   0  0  0 S  0,3  0,0   0:00.23 
kworker/u12+ 
   2695 jan   20   0   48912   3868   3136 R  0,3  0,1   0:00.01 top
  
  1 root  20   0  119720   5664   3780 S  0,0  0,1   0:02.72 systemd
  
  2 root  20   0   0  0  0 S  0,0  0,0   0:00.00 kthreadd   
  
  3 root  20   0   0  0  0 R  0,0  0,0   0:01.45 
ksoftirqd/0  
  5 root   0 -20   0  0  0 S  0,0  0,0   0:00.00 
kworker/0:0H 
  7 root  20   0   0  0  0 R  0,0  0,0   0:06.15 rcu_sched  
  
  8 root  20   0   0  0  0 S  0,0  0,0   0:00.00 rcu_bh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1558768/+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 1798828] [NEW] gvfsd-trash fills up memory (uses about 1 GB) if Trash contains thousands of files

2018-10-19 Thread Mantas Kriaučiūnas

Public bug reported:

gvfsd-trash fills up memory (uses about 1 GB) if Trash contains
thousands of files (I had ~8000)

I noticed this on Ubuntu 16.04 64-bit with GNOME Shell installed:
~$ ps aux |grep -i trash
uni0231910  6.2 20.0 1541900 789352 ?  Sl   12:53  10:11 
/usr/lib/gvfs/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_spaw/0

Problem can be "solved" by emptying Trash bin.

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

** Description changed:

  gvfsd-trash fills up memory (uses about 1 GB) if Trash contains
  thousands of files (I had ~8000)
  
- I noticed this on Ubuntu 16.04 64-bit with GNOME Shell installed.
+ I noticed this on Ubuntu 16.04 64-bit with GNOME Shell installed:
+ ~$ ps aux |grep -i trash
+ uni0231910  6.2 20.0 1541900 789352 ?  Sl   12:53  10:11 
/usr/lib/gvfs/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_spaw/0
  
  Problem can be "solved" by emptying Trash bin.

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

Title:
  gvfsd-trash fills up memory (uses about 1 GB) if Trash contains
  thousands of files

Status in gvfs package in Ubuntu:
  New

Bug description:
  gvfsd-trash fills up memory (uses about 1 GB) if Trash contains
  thousands of files (I had ~8000)

  I noticed this on Ubuntu 16.04 64-bit with GNOME Shell installed:
  ~$ ps aux |grep -i trash
  uni0231910  6.2 20.0 1541900 789352 ?  Sl   12:53  10:11 
/usr/lib/gvfs/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_spaw/0

  Problem can be "solved" by emptying Trash bin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798828/+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 1741977] Re: Scanning fails with many Samsung multifunctions (SCX-3200, SCX-3400, CLX-6260) after upgrading to Ubuntu 17.10/18.04 (SANE_USB_WORKAROUND=1 needed)

We could count aproximately how many scanners are broken NOW since SANE
1.0.27 by disabling Linux USB3 workaround by default vs how many
scanners could be broken by setting SANE_USB_WORKAROUND=1

Currently scanning with lots of mainstream SAMSUNG and XEROX multifunctional 
printers doesn't work in Ubuntu 18.04 LTS, but they works with Ubuntu 16.04 
LTS, so, this is a very important regression and this should be fixed ASAP.
If enabling SANE_USB_WORKAROUND=1 by default couses problems with few new 
scanners, which didn't work in Ubuntu 16.04 then this isn't such big problem 
like now - it's easier to write in Ubuntu 18.04 LTS Release Notes - new USB3 
scanners should add SANE_USB_WORKAROUND=0 to /etc/environment instead of 
cousing problems for users, who upgraded from 16.04 LTS

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

Title:
  Scanning fails with many Samsung multifunctions (SCX-3200, SCX-3400,
  CLX-6260) after upgrading to Ubuntu 17.10/18.04 (SANE_USB_WORKAROUND=1
  needed)

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Baltix:
  Triaged
Status in sane-backends package in Fedora:
  Fix Released

Bug description:
  Upgraded from kubuntu 17.04 to 17.10. Before the upgrade I was able to
  use my printer/scanner Samsung SCX-3200 without problems, with 17.10 I
  can only use the printer part.

  sane-find-scanner finds the scanner

  $ sane-find-scanner -q
  [...]
  product=0x3441 [SCX-3200 Series]) at libusb:003:019
  [...]

  Scanning fails with many Samsung multifunctions (including SCX-3400,
  SCX-4624f, CLX-6260) after upgrading to Ubuntu 17.10/18.04

  It seems the best solution for now is to add SANE_USB_WORKAROUND=1
  line to /etc/environment:

  echo "SANE_USB_WORKAROUND=1" | sudo tee -a /etc/environment

  or to /etc/systemd/user.conf: echo
  "DefaultEnvironment=SANE_USB_WORKAROUND=1"|sudo tee -a
  /etc/systemd/user.conf

  For more info why SANE_USB_WORKAROUND=1 is needed look at 
http://www.sane-project.org release notes of 1.0.27: 
  Note 3: The Linux USB3 workaround which was added in version 1.0.25 is now 
disabled by default. If you have difficulty using a scanner which previously 
worked, or intermittent scanner availability, try setting the new environment 
variable SANE_USB_WORKAROUND=1 before starting frontend. 
  I found this info in comments of bug #1728012 and 
https://askubuntu.com/questions/966834/ubuntu-17-10-and-samsung-scx-4624f-scanner-not-working/966835

  When I start scanimage the first time, it can talk to the scanner just fine:
  $ export SANE_DEBUG_XEROX_MFP=255
  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffdf4d2e220, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x55d2e393c5d0
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] [70] a8 00 43 10 53 61 6d 73 75 6e 67 20 53 61 6d 73 75 6e 67 20 
53 43 58 2d 33 32 30 30 20 53 65 72 69 65 73 20 19 33 84 2b 00 00 27 d8 00 00 
36 d8 00 01 51 00 00 01 00 00 00 00 36 d8 00 00 36 d8 00 01 05 05 00...
  [xerox_mfp] dev_inquiry: found Samsung/Samsung SCX-3200 Series
  [xerox_mfp] usb_dev_close: closing dev 0x55d2e393c5d0
  device `xerox_mfp:libusb:003:018' is a Samsung Samsung SCX-3200 Series 
multi-function peripheral
  When I start scanimage a second time it cannot talk to the scanner anymore:

  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffe9ae18760, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x56138cfa1870
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] usb_dev_request: sanei_usb_read_bulk: Error during device I/O
  [xerox_mfp] dev_command: dev_request: Error during device I/O
  [xerox_mfp] usb_dev_close: closing dev 0x56138cfa1870
  [xerox_mfp] list_one_device: dev_inquiry(libusb:003:018): Error during device 
I/O

  Unplugging the usb cable and plugging it back in allows scanimage to
  talk to the scanner once. After that it fails again. The USB cable is
  not a problem, as it worked with 16.10.

  I downloaded VueScan and it has not problems to repeatedly scan pages
  using the same hw, which also indicates that this is a sw and not a hw
  problem. And just to mention it again, printing also works fine using
  the same cable. And yes, I tried multiple USB ports. All exhibit the
  same behaviour. When I execute scanimage -L once and start VueScan
  afterwards, then VueScan also doesn't see the scanner anymore. After
  unplugging and replugging the UBS cable and restarting VueScan, it's
  able to scan again.

  Looks to me like sane doesn't

[Desktop-packages] [Bug 1741977] Re: Scanning fails with many Samsung multifunctions (SCX-3200, SCX-3400, CLX-6260) after upgrading to Ubuntu 17.10/18.04 (SANE_USB_WORKAROUND=1 needed)

I don't understand why Linux USB3 workaround which was added in version 1.0.25 
is disabled by default in SANE 1.0.27 :(
Maybe Ubuntu developers should patch SANE to enable SANE_USB_WORKAROUND=1 by 
default on all computers with USB 3.x ports?
Anyone knows if SANE_USB_WORKAROUND=1 variable could cause any problems? If 
not, then why don't set this by default?

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

Title:
  Scanning fails with many Samsung multifunctions (SCX-3200, SCX-3400,
  CLX-6260) after upgrading to Ubuntu 17.10/18.04 (SANE_USB_WORKAROUND=1
  needed)

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Baltix:
  Triaged
Status in sane-backends package in Fedora:
  Unknown

Bug description:
  Upgraded from kubuntu 17.04 to 17.10. Before the upgrade I was able to
  use my printer/scanner Samsung SCX-3200 without problems, with 17.10 I
  can only use the printer part.

  sane-find-scanner finds the scanner

  $ sane-find-scanner -q
  [...]
  product=0x3441 [SCX-3200 Series]) at libusb:003:019
  [...]

  Scanning fails with many Samsung multifunctions (including SCX-3400,
  SCX-4624f, CLX-6260) after upgrading to Ubuntu 17.10/18.04

  It seems the best solution for now is to add SANE_USB_WORKAROUND=1
  line to /etc/environment:

  echo "SANE_USB_WORKAROUND=1" | sudo tee -a /etc/environment

  or to /etc/systemd/user.conf: echo
  "DefaultEnvironment=SANE_USB_WORKAROUND=1"|sudo tee -a
  /etc/systemd/user.conf

  For more info why SANE_USB_WORKAROUND=1 is needed look at 
http://www.sane-project.org release notes of 1.0.27: 
  Note 3: The Linux USB3 workaround which was added in version 1.0.25 is now 
disabled by default. If you have difficulty using a scanner which previously 
worked, or intermittent scanner availability, try setting the new environment 
variable SANE_USB_WORKAROUND=1 before starting frontend. 
  I found this info in comments of bug #1728012 and 
https://askubuntu.com/questions/966834/ubuntu-17-10-and-samsung-scx-4624f-scanner-not-working/966835

  When I start scanimage the first time, it can talk to the scanner just fine:
  $ export SANE_DEBUG_XEROX_MFP=255
  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffdf4d2e220, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x55d2e393c5d0
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] [70] a8 00 43 10 53 61 6d 73 75 6e 67 20 53 61 6d 73 75 6e 67 20 
53 43 58 2d 33 32 30 30 20 53 65 72 69 65 73 20 19 33 84 2b 00 00 27 d8 00 00 
36 d8 00 01 51 00 00 01 00 00 00 00 36 d8 00 00 36 d8 00 01 05 05 00...
  [xerox_mfp] dev_inquiry: found Samsung/Samsung SCX-3200 Series
  [xerox_mfp] usb_dev_close: closing dev 0x55d2e393c5d0
  device `xerox_mfp:libusb:003:018' is a Samsung Samsung SCX-3200 Series 
multi-function peripheral
  When I start scanimage a second time it cannot talk to the scanner anymore:

  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffe9ae18760, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x56138cfa1870
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] usb_dev_request: sanei_usb_read_bulk: Error during device I/O
  [xerox_mfp] dev_command: dev_request: Error during device I/O
  [xerox_mfp] usb_dev_close: closing dev 0x56138cfa1870
  [xerox_mfp] list_one_device: dev_inquiry(libusb:003:018): Error during device 
I/O

  Unplugging the usb cable and plugging it back in allows scanimage to
  talk to the scanner once. After that it fails again. The USB cable is
  not a problem, as it worked with 16.10.

  I downloaded VueScan and it has not problems to repeatedly scan pages
  using the same hw, which also indicates that this is a sw and not a hw
  problem. And just to mention it again, printing also works fine using
  the same cable. And yes, I tried multiple USB ports. All exhibit the
  same behaviour. When I execute scanimage -L once and start VueScan
  afterwards, then VueScan also doesn't see the scanner anymore. After
  unplugging and replugging the UBS cable and restarting VueScan, it's
  able to scan again.

  Looks to me like sane doesn't know how to talk to the scanner anymore.
  It seems that something get's messed up during the first usb command,
  which prevents subsequent usb commands from succeeding.

  I just downloaded 16.04.3 LTS and booted it from a USB stick. I can
  confirm that the scanner still works with 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: sane-utils 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu

[Desktop-packages] [Bug 1741977] Re: Scanning fails with many Samsung multifunctions (SCX-3200, SCX-3400, CLX-6260) after upgrading to Ubuntu 17.10/18.04 (SANE_USB_WORKAROUND=1 needed)

** Bug watch added: Red Hat Bugzilla #1458903
   https://bugzilla.redhat.com/show_bug.cgi?id=1458903

** Also affects: sane-backends (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1458903
   Importance: Unknown
   Status: Unknown

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

Title:
  Scanning fails with many Samsung multifunctions (SCX-3200, SCX-3400,
  CLX-6260) after upgrading to Ubuntu 17.10/18.04 (SANE_USB_WORKAROUND=1
  needed)

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Baltix:
  Triaged
Status in sane-backends package in Fedora:
  Unknown

Bug description:
  Upgraded from kubuntu 17.04 to 17.10. Before the upgrade I was able to
  use my printer/scanner Samsung SCX-3200 without problems, with 17.10 I
  can only use the printer part.

  sane-find-scanner finds the scanner

  $ sane-find-scanner -q
  [...]
  product=0x3441 [SCX-3200 Series]) at libusb:003:019
  [...]

  Scanning fails with many Samsung multifunctions (including SCX-3400,
  SCX-4624f, CLX-6260) after upgrading to Ubuntu 17.10/18.04

  It seems the best solution for now is to add SANE_USB_WORKAROUND=1
  line to /etc/environment:

  echo "SANE_USB_WORKAROUND=1" | sudo tee -a /etc/environment

  or to /etc/systemd/user.conf: echo
  "DefaultEnvironment=SANE_USB_WORKAROUND=1"|sudo tee -a
  /etc/systemd/user.conf

  For more info why SANE_USB_WORKAROUND=1 is needed look at 
http://www.sane-project.org release notes of 1.0.27: 
  Note 3: The Linux USB3 workaround which was added in version 1.0.25 is now 
disabled by default. If you have difficulty using a scanner which previously 
worked, or intermittent scanner availability, try setting the new environment 
variable SANE_USB_WORKAROUND=1 before starting frontend. 
  I found this info in comments of bug #1728012 and 
https://askubuntu.com/questions/966834/ubuntu-17-10-and-samsung-scx-4624f-scanner-not-working/966835

  When I start scanimage the first time, it can talk to the scanner just fine:
  $ export SANE_DEBUG_XEROX_MFP=255
  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffdf4d2e220, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x55d2e393c5d0
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] [70] a8 00 43 10 53 61 6d 73 75 6e 67 20 53 61 6d 73 75 6e 67 20 
53 43 58 2d 33 32 30 30 20 53 65 72 69 65 73 20 19 33 84 2b 00 00 27 d8 00 00 
36 d8 00 01 51 00 00 01 00 00 00 00 36 d8 00 00 36 d8 00 01 05 05 00...
  [xerox_mfp] dev_inquiry: found Samsung/Samsung SCX-3200 Series
  [xerox_mfp] usb_dev_close: closing dev 0x55d2e393c5d0
  device `xerox_mfp:libusb:003:018' is a Samsung Samsung SCX-3200 Series 
multi-function peripheral
  When I start scanimage a second time it cannot talk to the scanner anymore:

  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffe9ae18760, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x56138cfa1870
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] usb_dev_request: sanei_usb_read_bulk: Error during device I/O
  [xerox_mfp] dev_command: dev_request: Error during device I/O
  [xerox_mfp] usb_dev_close: closing dev 0x56138cfa1870
  [xerox_mfp] list_one_device: dev_inquiry(libusb:003:018): Error during device 
I/O

  Unplugging the usb cable and plugging it back in allows scanimage to
  talk to the scanner once. After that it fails again. The USB cable is
  not a problem, as it worked with 16.10.

  I downloaded VueScan and it has not problems to repeatedly scan pages
  using the same hw, which also indicates that this is a sw and not a hw
  problem. And just to mention it again, printing also works fine using
  the same cable. And yes, I tried multiple USB ports. All exhibit the
  same behaviour. When I execute scanimage -L once and start VueScan
  afterwards, then VueScan also doesn't see the scanner anymore. After
  unplugging and replugging the UBS cable and restarting VueScan, it's
  able to scan again.

  Looks to me like sane doesn't know how to talk to the scanner anymore.
  It seems that something get's messed up during the first usb command,
  which prevents subsequent usb commands from succeeding.

  I just downloaded 16.04.3 LTS and booted it from a USB stick. I can
  confirm that the scanner still works with 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: sane-utils 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture:

[Desktop-packages] [Bug 1741977] Re: Scanning fails with many Samsung multifunctions (SCX-3200, SCX-3400, CLX-6260) after upgrading to Ubuntu 17.10/18.04 (SANE_USB_WORKAROUND=1 needed)

ionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jan  8 20:53:07 2018
  InstallationDate: Installed on 2016-04-03 (645 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: sane-backends
  UpgradeStatus: Upgraded to artful on 2018-01-05 (2 days ago)

** Changed in: sane-backends (Baltix)
   Status: New => Triaged

** Changed in: sane-backends (Baltix)
   Importance: Undecided => High

** Changed in: sane-backends (Baltix)
     Assignee: (unassigned) => Mantas Kriaučiūnas (mantas)

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

Title:
  Scanning fails with many Samsung multifunctions (SCX-3200, SCX-3400,
  CLX-6260) after upgrading to Ubuntu 17.10/18.04 (SANE_USB_WORKAROUND=1
  needed)

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Baltix:
  Triaged

Bug description:
  Upgraded from kubuntu 17.04 to 17.10. Before the upgrade I was able to
  use my printer/scanner Samsung SCX-3200 without problems, with 17.10 I
  can only use the printer part.

  sane-find-scanner finds the scanner

  $ sane-find-scanner -q
  [...]
  product=0x3441 [SCX-3200 Series]) at libusb:003:019
  [...]

  Scanning fails with many Samsung multifunctions (including SCX-3400,
  SCX-4624f, CLX-6260) after upgrading to Ubuntu 17.10/18.04

  It seems the best solution for now is to add SANE_USB_WORKAROUND=1
  line to /etc/environment:

  echo "SANE_USB_WORKAROUND=1" | sudo tee -a /etc/environment

  or to /etc/systemd/user.conf: echo
  "DefaultEnvironment=SANE_USB_WORKAROUND=1"|sudo tee -a
  /etc/systemd/user.conf

  For more info why SANE_USB_WORKAROUND=1 is needed look at 
http://www.sane-project.org release notes of 1.0.27: 
  Note 3: The Linux USB3 workaround which was added in version 1.0.25 is now 
disabled by default. If you have difficulty using a scanner which previously 
worked, or intermittent scanner availability, try setting the new environment 
variable SANE_USB_WORKAROUND=1 before starting frontend. 
  I found this info in comments of bug #1728012 and 
https://askubuntu.com/questions/966834/ubuntu-17-10-and-samsung-scx-4624f-scanner-not-working/966835

  When I start scanimage the first time, it can talk to the scanner just fine:
  $ export SANE_DEBUG_XEROX_MFP=255
  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffdf4d2e220, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x55d2e393c5d0
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] [70] a8 00 43 10 53 61 6d 73 75 6e 67 20 53 61 6d 73 75 6e 67 20 
53 43 58 2d 33 32 30 30 20 53 65 72 69 65 73 20 19 33 84 2b 00 00 27 d8 00 00 
36 d8 00 01 51 00 00 01 00 00 00 00 36 d8 00 00 36 d8 00 01 05 05 00...
  [xerox_mfp] dev_inquiry: found Samsung/Samsung SCX-3200 Series
  [xerox_mfp] usb_dev_close: closing dev 0x55d2e393c5d0
  device `xerox_mfp:libusb:003:018' is a Samsung Samsung SCX-3200 Series 
multi-function peripheral
  When I start scanimage a second time it cannot talk to the scanner anymore:

  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffe9ae18760, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x56138cfa1870
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] usb_dev_request: sanei_usb_read_bulk: Error during device I/O
  [xerox_mfp] dev_command: dev_request: Error during device I/O
  [xerox_mfp] usb_dev_close: closing dev 0x56138cfa1870
  [xerox_mfp] list_one_device: dev_inquiry(libusb:003:018): Error during device 
I/O

  Unplugging the usb cable and plugging it back in allows scanimage to
  talk to the scanner once. After that it fails again. The USB cable is
  not a problem, as it worked with 16.10.

  I downloaded VueScan and it has not problems to repeatedly scan pages
  using the same hw, which also indicates that this is a sw and not a hw
  problem. And just to mention it again, printing also works fine using
  the same cable. And yes, I tried multiple USB ports. All exhibit the
  same behaviour. When I execute scanimage -L once and start VueScan
  afterwards, then VueScan also doesn't see the scanner anymore. After
  unplugging and replugging the UBS cable and restarting VueScan, it's
  able to scan again.

  Looks to me like sane doesn't know how to talk to the scanner anymore.
  It seems that something get's messed up during the first usb command,
  which prevents subsequent usb

[Desktop-packages] [Bug 1741977] Re: Samsung SCX-3200, SCX-3400, CLX-6260 scanning fails after upgrading to Ubuntu 17.10/18.04

It seems the best solution for now is to add SANE_USB_WORKAROUND=1 line
to /etc/environment:

echo "SANE_USB_WORKAROUND=1" | sudo tee -a /etc/environment

(or to /etc/systemd/user.conf: echo
"DefaultEnvironment=SANE_USB_WORKAROUND=1"|sudo tee -a
/etc/systemd/user.conf )

For more info why SANE_USB_WORKAROUND=1 is needed look at 
http://www.sane-project.org release notes of 1.0.27:
Note 3: The Linux USB3 workaround which was added in version 1.0.25 is now 
disabled by default. If you have difficulty using a scanner which previously 
worked, or intermittent scanner availability, try setting the new environment 
variable SANE_USB_WORKAROUND=1 before starting frontend.
I found this info in comments of bug #1728012 and 
https://askubuntu.com/questions/966834/ubuntu-17-10-and-samsung-scx-4624f-scanner-not-working/966835

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

Title:
  Samsung SCX-3200, SCX-3400, CLX-6260 scanning fails after upgrading to
  Ubuntu 17.10/18.04

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Baltix:
  New

Bug description:
  A couple of days ago, I upgraded from kubuntu 16.10 to 17.04 and then
  to 17.10, including the required reboots. Before the upgrade I was
  able to use my printer/scanner SCX-3200 without problems, with 17.10 I
  can only use the printer part.

  sane-find-scanner finds the scanner

  $ sane-find-scanner -q
  [...]
  product=0x3441 [SCX-3200 Series]) at libusb:003:019
  [...]
  And when I start scanimage the first time, it can talk to the scanner just 
fine:

  $ export SANE_DEBUG_XEROX_MFP=255
  $ scanimage -L

   
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffdf4d2e220, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x55d2e393c5d0
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] [70] a8 00 43 10 53 61 6d 73 75 6e 67 20 53 61 6d 73 75 6e 67 20 
53 43 58 2d 33 32 30 30 20 53 65 72 69 65 73 20 19 33 84 2b 00 00 27 d8 00 00 
36 d8 00 01 51 00 00 01 00 00 00 00 36 d8 00 00 36 d8 00 01 05 05 00...
  [xerox_mfp] dev_inquiry: found Samsung/Samsung SCX-3200 Series
  [xerox_mfp] usb_dev_close: closing dev 0x55d2e393c5d0
  device `xerox_mfp:libusb:003:018' is a Samsung Samsung SCX-3200 Series 
multi-function peripheral
  When I start scanimage a second time it cannot talk to the scanner anymore:

  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffe9ae18760, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x56138cfa1870
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] usb_dev_request: sanei_usb_read_bulk: Error during device I/O
  [xerox_mfp] dev_command: dev_request: Error during device I/O
  [xerox_mfp] usb_dev_close: closing dev 0x56138cfa1870
  [xerox_mfp] list_one_device: dev_inquiry(libusb:003:018): Error during device 
I/O

  Unplugging the usb cable and plugging it back in allows scanimage to
  talk to the scanner once. After that it fails again. The USB cable is
  not a problem, as it worked with 16.10.

  I downloaded VueScan and it has not problems to repeatedly scan pages
  using the same hw, which also indicates that this is a sw and not a hw
  problem. And just to mention it again, printing also works fine using
  the same cable. And yes, I tried multiple USB ports. All exhibit the
  same behaviour. When I execute scanimage -L once and start VueScan
  afterwards, then VueScan also doesn't see the scanner anymore. After
  unplugging and replugging the UBS cable and restarting VueScan, it's
  able to scan again.

  Looks to me like sane doesn't know how to talk to the scanner anymore.
  It seems that something get's messed up during the first usb command,
  which prevents subsequent usb commands from succeeding.

  I just downloaded 16.04.3 LTS and booted it from a USB stick. I can
  confirm that the scanner still works with 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: sane-utils 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jan  8 20:53:07 2018
  InstallationDate: Installed on 2016-04-03 (645 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: sane-backends

[Desktop-packages] [Bug 1741977] Re: SCX-3200, scanning fails after migration to Kubuntu 17.10

2018-08-29 Thread Mantas Kriaučiūnas

** Also affects: sane-backends (Baltix)
   Importance: Undecided
   Status: New

** Summary changed:

- SCX-3200, scanning fails after migration to Kubuntu 17.10
+ Samsung SCX-3200, SCX-3400, CLX-6260 scanning fails after upgrading to Ubuntu 
17.10/18.04

** Tags removed: amd64
** Tags added: bionic regression

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

Title:
  Samsung SCX-3200, SCX-3400, CLX-6260 scanning fails after upgrading to
  Ubuntu 17.10/18.04

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Baltix:
  New

Bug description:
  A couple of days ago, I upgraded from kubuntu 16.10 to 17.04 and then
  to 17.10, including the required reboots. Before the upgrade I was
  able to use my printer/scanner SCX-3200 without problems, with 17.10 I
  can only use the printer part.

  sane-find-scanner finds the scanner

  $ sane-find-scanner -q
  [...]
  product=0x3441 [SCX-3200 Series]) at libusb:003:019
  [...]
  And when I start scanimage the first time, it can talk to the scanner just 
fine:

  $ export SANE_DEBUG_XEROX_MFP=255
  $ scanimage -L

   
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffdf4d2e220, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x55d2e393c5d0
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] [70] a8 00 43 10 53 61 6d 73 75 6e 67 20 53 61 6d 73 75 6e 67 20 
53 43 58 2d 33 32 30 30 20 53 65 72 69 65 73 20 19 33 84 2b 00 00 27 d8 00 00 
36 d8 00 01 51 00 00 01 00 00 00 00 36 d8 00 00 36 d8 00 01 05 05 00...
  [xerox_mfp] dev_inquiry: found Samsung/Samsung SCX-3200 Series
  [xerox_mfp] usb_dev_close: closing dev 0x55d2e393c5d0
  device `xerox_mfp:libusb:003:018' is a Samsung Samsung SCX-3200 Series 
multi-function peripheral
  When I start scanimage a second time it cannot talk to the scanner anymore:

  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffe9ae18760, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x56138cfa1870
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] usb_dev_request: sanei_usb_read_bulk: Error during device I/O
  [xerox_mfp] dev_command: dev_request: Error during device I/O
  [xerox_mfp] usb_dev_close: closing dev 0x56138cfa1870
  [xerox_mfp] list_one_device: dev_inquiry(libusb:003:018): Error during device 
I/O

  Unplugging the usb cable and plugging it back in allows scanimage to
  talk to the scanner once. After that it fails again. The USB cable is
  not a problem, as it worked with 16.10.

  I downloaded VueScan and it has not problems to repeatedly scan pages
  using the same hw, which also indicates that this is a sw and not a hw
  problem. And just to mention it again, printing also works fine using
  the same cable. And yes, I tried multiple USB ports. All exhibit the
  same behaviour. When I execute scanimage -L once and start VueScan
  afterwards, then VueScan also doesn't see the scanner anymore. After
  unplugging and replugging the UBS cable and restarting VueScan, it's
  able to scan again.

  Looks to me like sane doesn't know how to talk to the scanner anymore.
  It seems that something get's messed up during the first usb command,
  which prevents subsequent usb commands from succeeding.

  I just downloaded 16.04.3 LTS and booted it from a USB stick. I can
  confirm that the scanner still works with 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: sane-utils 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jan  8 20:53:07 2018
  InstallationDate: Installed on 2016-04-03 (645 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: sane-backends
  UpgradeStatus: Upgraded to artful on 2018-01-05 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1741977/+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 1789202] Re: 6.1.0.3 writer crashes when trying to insert more fields

2018-08-27 Thread Mantas Kriaučiūnas

** Also affects: libreoffice (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907397
   Importance: Unknown
   Status: Unknown

-- 
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/1789202

Title:
  6.1.0.3 writer crashes when trying to insert more fields

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice package in Debian:
  Unknown

Bug description:
  I'm testing libreoffice 6.1.0.3 on cosmic from ppa:osomon/lo-test.

  I have encountered the following regression, which I can reliably
  reproduce:

   1) Launch libreoffice writer
   2) Click on the "Insert" menu, then "Field" > "More Fields…"

  Expected result: a dialog to select the type and contents of the field is 
presented
  Current result: libreoffice crashes instantly

  This is the relevant backtrace:

  Thread 1 (Thread 0x7f82cbcead00 (LWP 4352)):
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
  #1  0x7f82d819c535 in __GI_abort () at abort.c:79
  #2  0x7f82d95b8a52 in SalUserEventList::DispatchUserEvents (
  this=0x55b01ede08b0, bHandleAllCurrentEvents=)
  at ./vcl/source/app/salusereventlist.cxx:115
  #3  0x7f82ca93b629 in call_userEventFn ()
  at ./vcl/unx/gtk3/gtk3gtkdata.cxx:784
  #4  0x7f82d6bbca78 in g_main_context_dispatch ()
 from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #5  0x7f82d6bbce68 in ?? () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #6  0x7f82d6bbcefc in g_main_context_iteration ()
 from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x7f82ca93c923 in GtkSalData::Yield(bool, bool) ()
  at ./vcl/unx/gtk3/gtk3gtkdata.cxx:459
  #8  0x7f82db20639e in ImplYield (i_bAllEvents=false, i_bWait=true)
  at ./vcl/source/app/svapp.cxx:470
  #9  Application::Yield () at ./vcl/source/app/svapp.cxx:535
  #10 0x7f82db207b15 in Application::Execute() ()
  at ./vcl/source/app/svapp.cxx:450
  #11 0x7f82da2d2e56 in desktop::Desktop::Main() ()
  at ./desktop/source/app/app.cxx:1634
  #12 0x7f82db20cc06 in ImplSVMain() () at ./vcl/source/app/svmain.cxx:200
  #13 0x7f82db20cd00 in SVMain () at ./vcl/source/app/svmain.cxx:238
  #14 0x7f82da2ef451 in soffice_main ()
  at ./desktop/source/app/sofficemain.cxx:170
  #15 0x55b01d0bb07b in sal_main () at ./desktop/source/app/main.c:48
  #16 main (argc=, argv=)
  at ./desktop/source/app/main.c:47

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1789202/+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 1770779] Re: language locales not compatible with firefox 60 update

line
intl.locale.requested=""
in /usr/lib/firefox/distribution/distribution.ini was added in 59.0+build5 
builds, for example:
https://launchpad.net/ubuntu/+source/firefox/59.0+build5-0ubuntu0.16.04.1

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

Title:
  language locales not compatible with firefox 60 update

Status in Default settings and artwork for Baltix OS:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu LTS 18.04, after the recent Firefox update to version
  60.0+build2, localization is deactivated presenting the browser only
  in english. In the languages section all language packs are
  deactivated citing incompatibilities with the present version.

  Performing a language support check in Ubuntu Settings do not resolve
  this issue.

  Summary:
  Ubuntu LTS 18.04 amd64
  firefox 60.0+build2
  Browser only shows in english; localization is deactivated due to 
incomptibilities with the installed language packs.
  Browser should be presented in my locale language (spanish).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 60.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   julian 1560 F...m pulseaudio
   /dev/snd/controlC1:  julian 1560 F pulseaudio
   /dev/snd/controlC0:  julian 1560 F pulseaudio
  BuildID: 20180509234620
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 11 20:24:31 2018
  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 2018-05-08 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.37 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_PE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=60.0/20180509234620 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.218
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.218:bd03/16/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1770779/+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 1755918] Re: Firefox 59 does not change UI language

Problem is, that some systems with ubuntu-defaults-it , ubuntu-defaults-zh-cn 
and ubuntu-defaults-baltix packages installed doesn't have line
intl.locale.requested=""
in /usr/lib/firefox/distribution/distribution.ini

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

Title:
  Firefox 59 does not change UI language

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Symptom: Since updating to Firefox 59, the Firefox UI items will be
  English only. E.g. all items under Peferences. Switching from en_US to
  de does no longer work.

  The Firefox packages firefox, firefox-locale-en, firefox-locale-de are
  installed. All 3 packages have been updated from 58.0.2 to 59.0 by the
  updater.

  When still on Firefox 58.0.2, the following settings existed and made sure my 
Firefox UI was localied to German (de)
  intl.locale.matchOS=true (boolean, default)
  general.useragent.locale=de (string, default)

  After the update to Firefox 59.0 the second parameter is no longer set. It is 
simply not present any longer in about:config.
  Adding it and restarting Firefox 59 does not have any effect.
  The UI will remain English only and the parameter is gone.

  This affects both Firefox packages:
  firefox 59.0+build5-0ubuntu0.16.04.1
  firefox 59.0+build5-0ubuntu0.14.04.1

  Ubuntu releases:
  Ubuntu 16.04.4 32-bit
  Ubuntu 14.04.5 32-bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1755918/+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 1770779] Re: language locales not compatible with firefox 60 update

Problem is, that some systems with ubuntu-defaults-it , ubuntu-defaults-zh-cn 
and ubuntu-defaults-baltix packages installed doesn't have line
intl.locale.requested=""
in /usr/lib/firefox/distribution/distribution.ini

See LP bug #1771272 and bug #1755918 for more info.

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

Title:
  language locales not compatible with firefox 60 update

Status in Default settings and artwork for Baltix OS:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu LTS 18.04, after the recent Firefox update to version
  60.0+build2, localization is deactivated presenting the browser only
  in english. In the languages section all language packs are
  deactivated citing incompatibilities with the present version.

  Performing a language support check in Ubuntu Settings do not resolve
  this issue.

  Summary:
  Ubuntu LTS 18.04 amd64
  firefox 60.0+build2
  Browser only shows in english; localization is deactivated due to 
incomptibilities with the installed language packs.
  Browser should be presented in my locale language (spanish).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 60.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   julian 1560 F...m pulseaudio
   /dev/snd/controlC1:  julian 1560 F pulseaudio
   /dev/snd/controlC0:  julian 1560 F pulseaudio
  BuildID: 20180509234620
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 11 20:24:31 2018
  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 2018-05-08 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.37 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_PE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=60.0/20180509234620 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.218
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.218:bd03/16/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1770779/+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 1770779] Re: language locales not compatible with firefox 60 update

** Also affects: baltix-default-settings
   Importance: Undecided
   Status: New

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

Title:
  language locales not compatible with firefox 60 update

Status in Default settings and artwork for Baltix OS:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu LTS 18.04, after the recent Firefox update to version
  60.0+build2, localization is deactivated presenting the browser only
  in english. In the languages section all language packs are
  deactivated citing incompatibilities with the present version.

  Performing a language support check in Ubuntu Settings do not resolve
  this issue.

  Summary:
  Ubuntu LTS 18.04 amd64
  firefox 60.0+build2
  Browser only shows in english; localization is deactivated due to 
incomptibilities with the installed language packs.
  Browser should be presented in my locale language (spanish).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 60.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   julian 1560 F...m pulseaudio
   /dev/snd/controlC1:  julian 1560 F pulseaudio
   /dev/snd/controlC0:  julian 1560 F pulseaudio
  BuildID: 20180509234620
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 11 20:24:31 2018
  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 2018-05-08 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.37 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_PE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=60.0/20180509234620 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.218
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.218:bd03/16/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1770779/+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 1748518] Re: [snap] bullets rendered incorrectly in docx files

2018-07-24 Thread Mantas Kriaučiūnas

Does this issue appear in LibreOffice 6.0.6 installed from 
ppa:libreoffice/libreoffice-prereleases ?
If yes, then please report this issue at https://bugs.documentfoundation.org 
and add link to bugreport here (click on +Also affects project)

-- 
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/1748518

Title:
  [snap] bullets rendered incorrectly in docx files

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/call-for-testing-
  libreoffice-6-0-0/3917/6)

  Steps to reproduce:

  1) create a text document with bullet points
  2) save it in the docx format
  3) close libreoffice, then re-open the document with writer

  Expected result: the bullets are rendered correctly as they were when
  the document was created and saved

  Actual result: bullets are rendered with another different glyph (that
  appears to vary from one setup to the other).

  I'm attaching a screenshot that demonstrates the issue (from the
  original forum post).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748518/+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 1768587] Re: [Regression] Reverse vnc protocol is missing in Remmina 1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic)

2018-05-30 Thread Mantas Kriaučiūnas

** Tags added: bionic

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

Title:
  [Regression] Reverse vnc protocol is missing in Remmina
  1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic)

Status in remmina package in Ubuntu:
  New

Bug description:
  [Regression] Reverse VNC (VNCI) protocol is missing in Remmina
  1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic), but is available in all
  older Ubuntu and official remmina-ppa-team PPA releases, including
  1.2.0-rcgit-27 and older versions from ppa:remmina-ppa-team/remmina-
  next

  AFAIK latest release with Reverse VNC (VNCI) protocol is remmina -
  1.2.0-rcgit-27-0~remmina201802142316.r566cdf6.dd516ac4~ubuntu16.04.1 ,
  see https://launchpad.net/~baltix-
  members/+archive/ubuntu/ppa/+packages?field.name_filter=remmina

  Steps to reproduce:

  1. Install remmina-plugin-vnc package and open Remmina app
  2. Press + button on the top left side
  3. Open "Protocol" dropdown list in newly appeared "Remote Desktop 
Preference" window
  4. Notice, that "Reverse VNC (VNCI)" is missing from "Protocol" dropdown list

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1768587/+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 1768587] [NEW] [Regression] Reverse vnc protocol is missing in Remmina 1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic)

2018-05-02 Thread Mantas Kriaučiūnas

Public bug reported:

[Regression] Reverse VNC (VNCI) protocol is missing in Remmina
1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic), but is available in all
older Ubuntu and official remmina-ppa-team PPA releases, including
1.2.0-rcgit-27 and older versions from ppa:remmina-ppa-team/remmina-next

AFAIK latest release with Reverse VNC (VNCI) protocol is remmina -
1.2.0-rcgit-27-0~remmina201802142316.r566cdf6.dd516ac4~ubuntu16.04.1 ,
see https://launchpad.net/~baltix-
members/+archive/ubuntu/ppa/+packages?field.name_filter=remmina

Steps to reproduce:

1. Install remmina-plugin-vnc package and open Remmina app
2. Press + button on the top left side
3. Open "Protocol" dropdown list in newly appeared "Remote Desktop Preference" 
window
4. Notice, that "Reverse VNC (VNCI)" is missing from "Protocol" dropdown list

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


** Tags: regression-release

** Attachment added: "Screenshot of Remmina  1.2.0-rcgit.29 - "Reverse VNC 
(VNCI)" missing from Protocol list"
   
https://bugs.launchpad.net/bugs/1768587/+attachment/5132235/+files/Remmina-new-connection-missing-VCNI-protocol.png

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

Title:
  [Regression] Reverse vnc protocol is missing in Remmina
  1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic)

Status in remmina package in Ubuntu:
  New

Bug description:
  [Regression] Reverse VNC (VNCI) protocol is missing in Remmina
  1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic), but is available in all
  older Ubuntu and official remmina-ppa-team PPA releases, including
  1.2.0-rcgit-27 and older versions from ppa:remmina-ppa-team/remmina-
  next

  AFAIK latest release with Reverse VNC (VNCI) protocol is remmina -
  1.2.0-rcgit-27-0~remmina201802142316.r566cdf6.dd516ac4~ubuntu16.04.1 ,
  see https://launchpad.net/~baltix-
  members/+archive/ubuntu/ppa/+packages?field.name_filter=remmina

  Steps to reproduce:

  1. Install remmina-plugin-vnc package and open Remmina app
  2. Press + button on the top left side
  3. Open "Protocol" dropdown list in newly appeared "Remote Desktop 
Preference" window
  4. Notice, that "Reverse VNC (VNCI)" is missing from "Protocol" dropdown list

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1768587/+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 1741977] Re: SCX-3200, scanning fails after migration to Kubuntu 17.10

2018-05-02 Thread Mantas Kriaučiūnas

Could you test if scanning works on your Samsung SCX-3200 multifunction
in Ubuntu 18.04 (Bionic) ?

I've meet with a similar issue - Samsung CLX 6260 Color Multifunction
Printer (Model CLX-6260FW) doesn't work with Ubuntu 18.04 (Bionic) but
works perfectly with Ubuntu 16.04 (xenial)

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

Title:
  SCX-3200, scanning fails after migration to Kubuntu 17.10

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  A couple of days ago, I upgraded from kubuntu 16.10 to 17.04 and then
  to 17.10, including the required reboots. Before the upgrade I was
  able to use my printer/scanner SCX-3200 without problems, with 17.10 I
  can only use the printer part.

  sane-find-scanner finds the scanner

  $ sane-find-scanner -q
  [...]
  product=0x3441 [SCX-3200 Series]) at libusb:003:019
  [...]
  And when I start scanimage the first time, it can talk to the scanner just 
fine:

  $ export SANE_DEBUG_XEROX_MFP=255
  $ scanimage -L

   
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffdf4d2e220, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x55d2e393c5d0
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] [70] a8 00 43 10 53 61 6d 73 75 6e 67 20 53 61 6d 73 75 6e 67 20 
53 43 58 2d 33 32 30 30 20 53 65 72 69 65 73 20 19 33 84 2b 00 00 27 d8 00 00 
36 d8 00 01 51 00 00 01 00 00 00 00 36 d8 00 00 36 d8 00 01 05 05 00...
  [xerox_mfp] dev_inquiry: found Samsung/Samsung SCX-3200 Series
  [xerox_mfp] usb_dev_close: closing dev 0x55d2e393c5d0
  device `xerox_mfp:libusb:003:018' is a Samsung Samsung SCX-3200 Series 
multi-function peripheral
  When I start scanimage a second time it cannot talk to the scanner anymore:

  $ scanimage -L
  [sanei_debug] Setting debug level of xerox_mfp to 255.
  [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize 
!= null
  [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffe9ae18760, 0
  [xerox_mfp] list_one_device: libusb:003:018
  [xerox_mfp] usb_dev_open: open 0x56138cfa1870
  [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
  [xerox_mfp] usb_dev_request: sanei_usb_read_bulk: Error during device I/O
  [xerox_mfp] dev_command: dev_request: Error during device I/O
  [xerox_mfp] usb_dev_close: closing dev 0x56138cfa1870
  [xerox_mfp] list_one_device: dev_inquiry(libusb:003:018): Error during device 
I/O

  Unplugging the usb cable and plugging it back in allows scanimage to
  talk to the scanner once. After that it fails again. The USB cable is
  not a problem, as it worked with 16.10.

  I downloaded VueScan and it has not problems to repeatedly scan pages
  using the same hw, which also indicates that this is a sw and not a hw
  problem. And just to mention it again, printing also works fine using
  the same cable. And yes, I tried multiple USB ports. All exhibit the
  same behaviour. When I execute scanimage -L once and start VueScan
  afterwards, then VueScan also doesn't see the scanner anymore. After
  unplugging and replugging the UBS cable and restarting VueScan, it's
  able to scan again.

  Looks to me like sane doesn't know how to talk to the scanner anymore.
  It seems that something get's messed up during the first usb command,
  which prevents subsequent usb commands from succeeding.

  I just downloaded 16.04.3 LTS and booted it from a USB stick. I can
  confirm that the scanner still works with 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: sane-utils 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jan  8 20:53:07 2018
  InstallationDate: Installed on 2016-04-03 (645 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: sane-backends
  UpgradeStatus: Upgraded to artful on 2018-01-05 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1741977/+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 1759625] Re: FFe: Sync gimp 2.10.0~RC2-1 (universe) from Debian experimental (main)

2018-04-28 Thread Mantas Kriaučiūnas

If you don't plan to include GIMP 2.10 into bionic then please set
status of this bug to Wontfix

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

Title:
  FFe: Sync gimp 2.10.0~RC2-1 (universe) from Debian experimental (main)

Status in MyPaint:
  New
Status in gimp package in Ubuntu:
  Fix Released

Bug description:
  Feature Freeze Justification
  
  gimp's last new stable series, 2.8, was released 6 years ago. The new series 
has years of work porting gimp to use gegl more completely, an integrated crash 
report tool, and many more improvements.

  The Gimp development team is so small that I do not expect there to be
  much support at all for gimp 2.8 any more.

  Future
  ==
  If the final gimp 2.10 is not released before Ubuntu 18.04 LTS is, then we 
should do an SRU to update it then.

  The Gimp developers have announced that they will add features to
  future 2.10 releases so that users won't have to wait several years
  like this again.

  Gimp 3.0 will switch to gtk3 (or gtk4).

  Affected Flavors
  
  Ubuntu Studio is the only flavor to include gimp by default.

  Changes
  ===
  This entire file!
  https://git.gnome.org/browse/gimp/tree/NEWS

  Features are described in several blog posts documenting the 2.9
  development releases at https://www.gimp.org/news/

  Changes in the new Debian version
  =
  Uploaded to experimental on request of the Debian maintainer Ari Pollack.

   gimp (2.10.0~RC1-1) experimental; urgency=medium
   .
     * New upstream release candidate (LP: #1759625)
   - Fixes screenshots in GNOME and KDE on Wayland (Closes: #880186)
     (LP: #1739684)
     * Bump dependencies per configure.ac
     * Add new Build-Depends: gegl, glib-networking, libgexiv2-dev,
   libmypaint-dev, libopenjp2-7-dev (Closes: #827083), libopenexr-dev,
   libwebp-dev, mypaint-brushes, python-cairo-dev
     * Depend on xdg-utils for email feature
     * Update debian/libgimp2.0.symbols
     * Drop all patches (except 01_hurd_ftbfs.patch) since they are obsolete
   with the new release

To manage notifications about this bug go to:
https://bugs.launchpad.net/mypaint/+bug/1759625/+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 1759625] Re: FFe: Sync gimp 2.10.0~RC2-1 (universe) from Debian experimental (main)

2018-04-27 Thread Mantas Kriaučiūnas

** Bug watch added: github.com/mypaint/mypaint/issues #918
   https://github.com/mypaint/mypaint/issues/918

** Also affects: gimp via
   https://github.com/mypaint/mypaint/issues/918
   Importance: Unknown
   Status: Unknown

** Project changed: gimp => mypaint

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

Title:
  FFe: Sync gimp 2.10.0~RC2-1 (universe) from Debian experimental (main)

Status in MyPaint:
  Unknown
Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  Feature Freeze Justification
  
  gimp's last new stable series, 2.8, was released 6 years ago. The new series 
has years of work porting gimp to use gegl more completely, an integrated crash 
report tool, and many more improvements.

  The Gimp development team is so small that I do not expect there to be
  much support at all for gimp 2.8 any more.

  Future
  ==
  If the final gimp 2.10 is not released before Ubuntu 18.04 LTS is, then we 
should do an SRU to update it then.

  The Gimp developers have announced that they will add features to
  future 2.10 releases so that users won't have to wait several years
  like this again.

  Gimp 3.0 will switch to gtk3 (or gtk4).

  Affected Flavors
  
  Ubuntu Studio is the only flavor to include gimp by default.

  Changes
  ===
  This entire file!
  https://git.gnome.org/browse/gimp/tree/NEWS

  Features are described in several blog posts documenting the 2.9
  development releases at https://www.gimp.org/news/

  Changes in the new Debian version
  =
  Uploaded to experimental on request of the Debian maintainer Ari Pollack.

   gimp (2.10.0~RC1-1) experimental; urgency=medium
   .
     * New upstream release candidate (LP: #1759625)
   - Fixes screenshots in GNOME and KDE on Wayland (Closes: #880186)
     (LP: #1739684)
     * Bump dependencies per configure.ac
     * Add new Build-Depends: gegl, glib-networking, libgexiv2-dev,
   libmypaint-dev, libopenjp2-7-dev (Closes: #827083), libopenexr-dev,
   libwebp-dev, mypaint-brushes, python-cairo-dev
     * Depend on xdg-utils for email feature
     * Update debian/libgimp2.0.symbols
     * Drop all patches (except 01_hurd_ftbfs.patch) since they are obsolete
   with the new release

To manage notifications about this bug go to:
https://bugs.launchpad.net/mypaint/+bug/1759625/+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 1759625] Re: FFe: Sync gimp 2.10.0~RC2-1 (universe) from Debian experimental (main)

2018-04-27 Thread Mantas Kriaučiūnas

** Summary changed:

- FFe: Sync gimp 2.10.0~RC1-1 (universe) from Debian experimental (main)
+ FFe: Sync gimp 2.10.0~RC2-1 (universe) from Debian experimental (main)

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

Title:
  FFe: Sync gimp 2.10.0~RC2-1 (universe) from Debian experimental (main)

Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  Feature Freeze Justification
  
  gimp's last new stable series, 2.8, was released 6 years ago. The new series 
has years of work porting gimp to use gegl more completely, an integrated crash 
report tool, and many more improvements.

  The Gimp development team is so small that I do not expect there to be
  much support at all for gimp 2.8 any more.

  Future
  ==
  If the final gimp 2.10 is not released before Ubuntu 18.04 LTS is, then we 
should do an SRU to update it then.

  The Gimp developers have announced that they will add features to
  future 2.10 releases so that users won't have to wait several years
  like this again.

  Gimp 3.0 will switch to gtk3 (or gtk4).

  Affected Flavors
  
  Ubuntu Studio is the only flavor to include gimp by default.

  Changes
  ===
  This entire file!
  https://git.gnome.org/browse/gimp/tree/NEWS

  Features are described in several blog posts documenting the 2.9
  development releases at https://www.gimp.org/news/

  Changes in the new Debian version
  =
  Uploaded to experimental on request of the Debian maintainer Ari Pollack.

   gimp (2.10.0~RC1-1) experimental; urgency=medium
   .
     * New upstream release candidate (LP: #1759625)
   - Fixes screenshots in GNOME and KDE on Wayland (Closes: #880186)
     (LP: #1739684)
     * Bump dependencies per configure.ac
     * Add new Build-Depends: gegl, glib-networking, libgexiv2-dev,
   libmypaint-dev, libopenjp2-7-dev (Closes: #827083), libopenexr-dev,
   libwebp-dev, mypaint-brushes, python-cairo-dev
     * Depend on xdg-utils for email feature
     * Update debian/libgimp2.0.symbols
     * Drop all patches (except 01_hurd_ftbfs.patch) since they are obsolete
   with the new release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1759625/+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 1760231] [NEW] gnome-software crashed with signal 5 in g_main_context_new()

2018-03-30 Thread Mantas Kriaučiūnas

Public bug reported:

Just installed latest bionic from cdimage.ubuntu.com/daily-live and
after installation installed aptitude and lots of other software with
aptitude from ppa:baltix-members ;)

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.0-0ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 31 00:40:16 2018
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2018-03-30 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180330)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.0-0ubuntu7
ProcCmdline: /usr/bin/gnome-software --gapplication-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=lt_LT.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-software
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
 snapd_client_get_interfaces_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
 gs_plugin_refine_app () from 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
Title: gnome-software crashed with signal 5 in g_main_context_new()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash bionic need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gnome-software crashed with signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Just installed latest bionic from cdimage.ubuntu.com/daily-live and
  after installation installed aptitude and lots of other software with
  aptitude from ppa:baltix-members ;)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 31 00:40:16 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180330)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_get_interfaces_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   gs_plugin_refine_app () from 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1760231/+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 1547127] Re: Guest account option - feature request

2018-03-30 Thread Mantas Kriaučiūnas

** Also affects: gdm3 (Baltix)
   Importance: Undecided
   Status: New

-- 
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/1547127

Title:
  Guest account option - feature request

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gdm3 package in Baltix:
  New

Bug description:
  Though I didn't have it enabled for security reasons when I was using
  Unity, I think that some may find it useful to have a 'guest account'
  option, though I think that it should be off by default and be
  reasonably easy to configure in the gnome-control-center.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1547127/+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 1547127] Re: Guest account option - feature request

2018-03-30 Thread Mantas Kriaučiūnas

** Tags added: artful bionic

-- 
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/1547127

Title:
  Guest account option - feature request

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gdm3 package in Baltix:
  New

Bug description:
  Though I didn't have it enabled for security reasons when I was using
  Unity, I think that some may find it useful to have a 'guest account'
  option, though I think that it should be off by default and be
  reasonably easy to configure in the gnome-control-center.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1547127/+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 1740792] Re: Automatic login still requires user password after suspend/hibernate

2018-03-27 Thread Mantas Kriaučiūnas

** Also affects: gdm3 (Baltix)
   Importance: Undecided
   Status: New

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

Title:
  Automatic login still requires user password after suspend/hibernate

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gdm3 package in Baltix:
  New

Bug description:
  Description:  Ubuntu 17.10
  Release:  17.10
  gnome-control-center 3.26.2

  When I set Ubuntu to automatically login a user the user still has to
  enter their password when resuming from a suspended session. The only
  option I can find to fix this is to disable the lock-screen
  completely, which I don't want to since I still want it to be an
  option to manually lock it. Setting Privacy > Screen Lock to off
  doesn't affect this behavior at all.

  The solution seems to be to use dconf-editor and change
  org.gnome.desktop.screensaver.ubuntu-lock-on-suspend to false. I got
  the solution after asking on askubuntu.com:
  https://askubuntu.com/questions/990056/turn-off-requesting-user-
  password-after-suspend-17-10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1740792/+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 1759017] [NEW] Can't play Audio CD in Ubuntu 18.04 - /usr/lib/gvfs/gvfsd-cdda always crashes

2018-03-26 Thread Mantas Kriaučiūnas

Public bug reported:

Audio CD doesn't open in Ubuntu 18.04 - /usr/lib/gvfs/gvfsd-cdda always
crashes when I insert Audio CD or try to play already inserted Audio CD
with Rhytmbox. I'm attachin crash report from /var/crash

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


** Tags: audiocd bionic crash

** Attachment added: "Crash report appears in /var/crash (after inserting 
AudioCD)"
   
https://bugs.launchpad.net/bugs/1759017/+attachment/5091517/+files/_usr_lib_gvfs_gvfsd-cdda.1000.crash

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

Title:
  Can't play Audio CD in Ubuntu 18.04 - /usr/lib/gvfs/gvfsd-cdda always
  crashes

Status in gvfs package in Ubuntu:
  New

Bug description:
  Audio CD doesn't open in Ubuntu 18.04 - /usr/lib/gvfs/gvfsd-cdda
  always crashes when I insert Audio CD or try to play already inserted
  Audio CD with Rhytmbox. I'm attachin crash report from /var/crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1759017/+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 1748889] Re: [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary files - SRU for Xenial

2018-02-21 Thread Mantas Kriaučiūnas

** Summary changed:

- [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary files
+ [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary files - 
SRU for Xenial

-- 
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/1748889

Title:
  [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary
  files - SRU for Xenial

Status in libreoffice package in Ubuntu:
  Fix Committed

Bug description:
  CVE: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6871
  LibreOffice through 6.0.1 allows remote attackers to read arbitrary files via 
=WEBSERVICE calls in a document, which use the COM.MICROSOFT.WEBSERVICE 
function.

  Current version 1:5.1.2-0ubuntu1 in Ubuntu 16.04.3 is confirmed to be
  affected

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Feb 12 14:19:03 2018
  InstallationDate: Installed on 2016-04-22 (661 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  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/1748889/+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 1748889] Re: [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary files

2018-02-21 Thread Mantas Kriaučiūnas

** This bug is no longer a duplicate of bug 1748999
   [SRU] libreoffice 5.4.5 for artful

-- 
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/1748889

Title:
  [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary
  files

Status in libreoffice package in Ubuntu:
  Fix Committed

Bug description:
  CVE: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6871
  LibreOffice through 6.0.1 allows remote attackers to read arbitrary files via 
=WEBSERVICE calls in a document, which use the COM.MICROSOFT.WEBSERVICE 
function.

  Current version 1:5.1.2-0ubuntu1 in Ubuntu 16.04.3 is confirmed to be
  affected

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Feb 12 14:19:03 2018
  InstallationDate: Installed on 2016-04-22 (661 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  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/1748889/+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 1746757] Re: [SRU] libreoffice 5.4.4 for artful

2018-02-17 Thread Mantas Kriaučiūnas

I think we should upload LibreOffice 5.4.5 to Ubuntu 17.10 repository,
because 5.4.4 has security issue CVE-2018-6871, see bug #1748999 [SRU]
libreoffice 5.4.5 for artful

 Libreoffice 5.4.5 fixes CVE-2018-6871 and ~70 other bugs, see:

https://wiki.documentfoundation.org/Releases/5.4.5/RC1#List_of_fixed_bugs


** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6871

-- 
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/1746757

Title:
  [SRU] libreoffice 5.4.4 for artful

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Artful:
  Fix Committed
Status in libreoffice-l10n source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 5.4.4 is the fourth bugfix release of the still 5.4 line. 
Version 5.4.2 is currently in 17.10.
     For a list of fixed bugs compared to 5.4.2 see the list of bugs fixed in 
the RC1 and RC2 for 5.4.3 and the RC1 and RC2 for 5.4.4:
   https://wiki.documentfoundation.org/Releases/5.4.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.3/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.4/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

   * Libreoffice 5.4.4 (RC2, which is effectively the final release) has
  been available for users to test since 2017-12-24 in the official
  "LibreOffice Fresh" PPA
  (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages),
  and it is in bionic-proposed since 2018-01-26.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release went through 2 release candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * Two new minor releases with a total of 134 bug fixes always carry
  the potential for introducing regressions, even though they are
  bugfix-only releases, meaning that no new features were added, and no
  existing features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1746757/+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 1724572] Re: vino-server crashed with SIGSEGV in _XSend()

2017-11-07 Thread Mantas Kriaučiūnas

** Bug watch added: Debian Bug tracker #856036
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856036

** Also affects: vino (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856036
   Importance: Unknown
   Status: Unknown

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

Title:
  vino-server crashed with SIGSEGV in _XSend()

Status in vino package in Ubuntu:
  Incomplete
Status in vino package in Debian:
  Unknown

Bug description:
  Following upgrade from 17.04 (Gnome) to 17.10.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: vino 3.8.1-0ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Oct 18 12:59:52 2017
  ExecutablePath: /usr/lib/vino/vino-server
  InstallationDate: Installed on 2017-04-17 (183 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/lib/vino/vino-server
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f2a587b63ce <_XSend+126>:   mov(%rax),%rdx
   PC (0x7f2a587b63ce) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: vino
  StacktraceTop:
   _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libXtst.so.6
   XTestQueryExtension () from /usr/lib/x86_64-linux-gnu/libXtst.so.6
   ?? ()
  Title: vino-server crashed with SIGSEGV in _XSend()
  UpgradeStatus: Upgraded to artful on 2017-10-18 (0 days ago)
  UserGroups: sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1724572/+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 1729970] Re: /usr/lib/vino/vino-server:11:_XSend:XQueryExtension:get_xinput_base:find_display:XTestQueryExtension

2017-11-07 Thread Mantas Kriaučiūnas

** Bug watch added: Debian Bug tracker #856036
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856036

** Also affects: vino (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856036
   Importance: Unknown
   Status: Unknown

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

Title:
  /usr/lib/vino/vino-
  
server:11:_XSend:XQueryExtension:get_xinput_base:find_display:XTestQueryExtension

Status in vino package in Ubuntu:
  New
Status in vino package in Debian:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
vino.  This problem was most recently seen with package version 
3.8.1-0ubuntu12, the problem page at 
https://errors.ubuntu.com/problem/46ce7f9e4cb9f9cf33885d094500e40aad2c4fe1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1729970/+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 1666681] Re: Restore interactive_search.patch (type-ahead search)

2017-10-24 Thread Mantas Kriaučiūnas

** Summary changed:

- Drop interactive_search.patch (type-ahead search)
+ Restore interactive_search.patch (type-ahead search)

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

Title:
Restore interactive_search.patch (type-ahead search)

Status in nautilus package in Ubuntu:
Confirmed

Bug description:
Nautilus dropped the popular type-ahead search feature years ago.
Ubuntu has been carrying a patch to revert that change. See bug
1164016 for the original LP bug and patch proposal.

Nautilus is now under very active development. During the 3.22 cycle,
that patch needed to be rebased. I tried to do it and what I came up
with caused a crash (it didn't really crash for me, but ricotz and
some others experienced it) and the first letter typed activated type-
ahead search but the first letter was dropped. In other words, you
would need to type "ddow" to activate the Downloads folder instead of
just "dow" like in previous releases. (LP: #1635988)

I did that rebase in October 2016 and no one has stepped up then to
improve the patch.

The Nautilus maintainer csoriano has said that the slots and views
changed significantly during 3.22 and will likely be refactored more
in the future.

If there's no one available to maintain the patch, unfortunately,
we'll eventually have to drop the patch to not be stuck on an ancient
version of Nautilus.

I am proposing that we do this at the start of the 17.10 development
cycle. This gives 6 months for a developer to step up and try to fix
the patch and 12 months before 18.04 LTS.

Other Items
===
- For better performance with the built-in search, we need to reconsider
avoiding tracker in Unity (LP: #176)

- There is an option in Preferences for users to disable searching in
subfolders. I don't think we want to do that by default but maybe it
can help some people.

The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with
this patch now disabled.

https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

[Desktop-packages] [Bug 1699670] Re: Gnome screensaver lock always responses "incorrect password" when last active window's language is not the language of the password

2017-10-23 Thread Mantas Kriaučiūnas

Gnome-screensaver shouldn't be running on GNOME Shell. It's 5 years old
software and is needed only for old GNOME flashback (fallback) session.

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

Title:
  Gnome screensaver lock always responses "incorrect password" when last
  active window's language is not the language of the password

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  OS - Ubuntu 16.04.2 LTS, DE - GNOME Shell 3.20.4, gnome-screensaver 3.6.1

  Prerequisites:
   - say, you have 2 language layouts installed
   - their layouts/character tables are completely different, so there is no 
chance you can type your password correctly using any language keyboard layout 
(e.g. you have en/ru, but not en/de etc.)

  Actual behavior:
  When the screen is being locked while your active window has the language 
which is not your password language set, you won't be able to log in back. Log 
in form shows that the language of the password is set (EN in my case) but it 
always returns 'Incorrect password' message in response to the correct input. 
Switching language layout using the keyboard shortcut or GUI doesn't help.
  'Switch user' trick allows you to log in back though, but it's a crutch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1699670/+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 1716278] Re: gnome-screensaver crashed with SIGSEGV in XForceScreenSaver()

2017-10-23 Thread Mantas Kriaučiūnas

Gnome-screensaver shouldn't be running on GNOME Shell. It's 5 years old
software and is needed only for old GNOME flashback (fallback) session.

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

Title:
  gnome-screensaver crashed with SIGSEGV in XForceScreenSaver()

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-screensaver 3.6.1-7ubuntu6
  Uname: Linux 4.13.0-041300rc1-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Sep 10 16:02:00 2017
  ExecutablePath: /usr/bin/gnome-screensaver
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'gnome'
   org.gnome.desktop.session idle-delay uint32 900
  InstallationDate: Installed on 2017-04-18 (145 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-screensaver --no-daemon
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
  Signal: 11
  SourcePackage: gnome-screensaver
  StacktraceTop:
   XForceScreenSaver () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XResetScreenSaver () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-screensaver crashed with SIGSEGV in XForceScreenSaver()
  UpgradeStatus: Upgraded to artful on 2017-04-29 (134 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1716278/+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 1719777] Re: Sync Pitivi 0.99-2 packages from Debian unstable - many bug fixes and performance improvements

** Summary changed:

- Update Pitivi packages to 0.99 (1.0rc) - many bug fixes and performance 
improvements
+ Sync Pitivi 0.99-2 packages from Debian unstable - many bug fixes and 
performance improvements

** Summary changed:

- Sync Pitivi 0.99-2 packages from Debian unstable - many bug fixes and 
performance improvements
+ Sync Pitivi ( universe) 0.99-2 from Debian unstable (main) - many bug fixes 
and performance improvements

** Description changed:

  First Pitivi 1.0 rc “Ocean Big Chair” (0.99) was released at September
- 22. This release has many bug fixes and performance improvements, test
- suite grew considerably, from 164 to 191 meaningful unit tests, see
- https://git.gnome.org/browse/pitivi/log/?h=1.0
+ 22 and is already packaged in Debian unstable - I'm pasting
+ debian/changelog since 0.98.1 version which is currently in Ubuntu
+ artful:
  
- Please update Pitivi packages to 0.99 (1.0 release candidate)
+ pitivi (0.99-2) unstable; urgency=medium
+ 
+   * debian/patches/0001-Don-t-require-gst-validate-to-be-available.patch:
+ + Don't require gst-validate to be available (Closes: #876607)
+ 
+  -- Sebastian Dröge   Sun, 24 Sep 2017 09:46:35 +0300
+ 
+ pitivi (0.99-1) unstable; urgency=medium
+ 
+   * New upstream release
+ 
+  -- Sebastian Dröge   Sat, 23 Sep 2017 14:28:52 +0300
+ 
+ Explanation of FeatureFreeze exception:
+ 0.99 release is just big bugfix, no new features, but many bug fixes and 
performance improvements, test suite grew considerably, from 164 to 191 
meaningful unit tests, see https://git.gnome.org/browse/pitivi/log/?h=1.0
+ 
+ Please sync Pitivi packages from Debian unstable before 17.10 release.
  
  For more info look at
  https://pitivi.wordpress.com/2017/09/22/pitivi-0-99-ocean-big-chair/

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

Title:
  Sync Pitivi ( universe) 0.99-2 from Debian unstable (main) - many bug
  fixes and performance improvements

Status in pitivi package in Ubuntu:
  New

Bug description:
  First Pitivi 1.0 rc “Ocean Big Chair” (0.99) was released at September
  22 and is already packaged in Debian unstable - I'm pasting
  debian/changelog since 0.98.1 version which is currently in Ubuntu
  artful:

  pitivi (0.99-2) unstable; urgency=medium

* debian/patches/0001-Don-t-require-gst-validate-to-be-available.patch:
  + Don't require gst-validate to be available (Closes: #876607)

   -- Sebastian Dröge   Sun, 24 Sep 2017 09:46:35
  +0300

  pitivi (0.99-1) unstable; urgency=medium

* New upstream release

   -- Sebastian Dröge   Sat, 23 Sep 2017 14:28:52
  +0300

  Explanation of FeatureFreeze exception:
  0.99 release is just big bugfix, no new features, but many bug fixes and 
performance improvements, test suite grew considerably, from 164 to 191 
meaningful unit tests, see https://git.gnome.org/browse/pitivi/log/?h=1.0

  Please sync Pitivi packages from Debian unstable before 17.10 release.

  For more info look at
  https://pitivi.wordpress.com/2017/09/22/pitivi-0-99-ocean-big-chair/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1719777/+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 1719777] [NEW] Sync Pitivi 0.99-2 packages from Debian unstable - many bug fixes and performance improvements

Public bug reported:

First Pitivi 1.0 rc “Ocean Big Chair” (0.99) was released at September
22. This release has many bug fixes and performance improvements, test
suite grew considerably, from 164 to 191 meaningful unit tests, see
https://git.gnome.org/browse/pitivi/log/?h=1.0

Please update Pitivi packages to 0.99 (1.0 release candidate)

For more info look at
https://pitivi.wordpress.com/2017/09/22/pitivi-0-99-ocean-big-chair/

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


** Tags: artful upgrade-software-version

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

Title:
  Sync Pitivi 0.99-2 packages from Debian unstable - many bug fixes and
  performance improvements

Status in pitivi package in Ubuntu:
  New

Bug description:
  First Pitivi 1.0 rc “Ocean Big Chair” (0.99) was released at September
  22. This release has many bug fixes and performance improvements, test
  suite grew considerably, from 164 to 191 meaningful unit tests, see
  https://git.gnome.org/browse/pitivi/log/?h=1.0

  Please update Pitivi packages to 0.99 (1.0 release candidate)

  For more info look at
  https://pitivi.wordpress.com/2017/09/22/pitivi-0-99-ocean-big-chair/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1719777/+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 1286578] Re: Standard (non-admin) users can't connect to new wireless networks on GNOME Shell

** Description changed:

- When you install Ubuntu 13.10 or 14.04, the first account is the admin
- account.  The admin account can connect to new wifi connections just
- fine without needing the admin password.  When the admin account creates
- a standard non-admin, that non-admin account when it tries to connect to
- new wifi connections, pops up a dialog box asking for the admin
- password.  Non-admin accounts can not connect to new wifi connections
- without the admin account.  Does this present a security flaw as the
- only solution is to make all accounts admin or having everyone know the
- admin password.  My sister is the admin account for the laptop and she
- can connect just fine.  I however is only just a non-admin account and
- everywhere I go I am asked for the admin account everytime I want to
- connect to wifi at Starbucks or any other place.
+ When you install Ubuntu-GNOME 14.04 or 16.04, the first account is the admin 
account. The admin account can connect to new wifi connections just fine 
without needing the admin password, but:
+ 1. Create a standard (non-admin) user, then log-in with non-admin account and 
try to connect to new Wi-Fi connection with non-admin account and a dialog pops 
up asking for the admin password :(
+ 2. Non-admin accounts can not connect to new wifi connections without the 
admin account :(
  
- I should note that wired ethernet connections work just fine, however it
- is annoying to find some business that has wired ports and some have
- none at all :(
+ This present a security flaw as the only solution is to add all users to
+ netdev group or make all accounts admin (or having everyone know the
+ admin password).
  
- This bug is present in 13.10 AND 14.04
+ Wired ethernet connections work just fine for non-admin users, however
+ it is annoying to find some public places that has wired ports and some
+ have none at all :(
  
- Tested on 14.04 as of Febuary 28, 2014
+ Tested on 14.04.4 and 16.04.3 with latest updates
  
  ProblemType: Bug
- DistroRelease: Ubuntu 13.10
- Package: network-manager-gnome 0.9.8.0-1ubuntu5.1
- ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
- Uname: Linux 3.11.0-15-generic x86_64
- NonfreeKernelModules: nvidia
- ApportVersion: 2.12.5-0ubuntu2.2
- Architecture: amd64
- Date: Sat Mar  1 09:52:27 2014
- ExecutablePath: /usr/bin/nm-applet
- IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
- InstallationDate: Installed on 2013-10-25 (127 days ago)
- InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
- IpRoute:
-  default via 69.145.136.1 dev eth0  proto static 
-  69.145.136.0/22 dev eth0  proto kernel  scope link  src 69.145.137.13  
metric 1
- IwConfig:
-  eth0  no wireless extensions.
-  
-  lono wireless extensions.
- MarkForUpload: True
- NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
-  WimaxEnabled=true
- ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
- SourcePackage: network-manager-applet
- UpgradeStatus: No upgrade log present (probably fresh install)
- nmcli-con:
-  NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
-  Wired connection 12e05c40f-3e1f-4b48-a4f3-2efbe1450403   
802-3-ethernet1393692735   Sat 01 Mar 2014 09:52:15 AM MSTyes   
no /org/freedesktop/NetworkManager/Settings/0
- nmcli-dev:
-  DEVICE TYPE  STATE DBUS-PATH 
 
-  eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
- nmcli-nm:
-  RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
-  running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled
+ DistroRelease: Ubuntu 16.04
+ Package: gnome-control-center 1:3.18.2-1ubuntu6

** Tags removed: amd64 apport-bug saucy
** Tags added: trusty xenial

-- 
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/1286578

Title:
  Standard (non-admin) users can't connect to new wireless networks on
  GNOME Shell

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  When you install Ubuntu-GNOME 14.04 or 16.04, the first account is the admin 
account. The admin account can connect to new wifi connections just fine 
without needing the admin password, but:
  1. Create a standard (non-admin) user, then log-in with non-admin account and

[Desktop-packages] [Bug 1286578] Re: Standard (non-admin) users can't connect to new wireless networks on GNOME Shell

** Summary changed:

- Non-admin users need admin access to connect to new wifi.  A problem on 
mobile devices with standard non admin accounts.  Present on 13.10 to 14.04
+ Standard (non-admin) users can't connect to new wireless networks on GNOME 
Shell

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1286578

Title:
  Standard (non-admin) users can't connect to new wireless networks on
  GNOME Shell

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  When you install Ubuntu 13.10 or 14.04, the first account is the admin
  account.  The admin account can connect to new wifi connections just
  fine without needing the admin password.  When the admin account
  creates a standard non-admin, that non-admin account when it tries to
  connect to new wifi connections, pops up a dialog box asking for the
  admin password.  Non-admin accounts can not connect to new wifi
  connections without the admin account.  Does this present a security
  flaw as the only solution is to make all accounts admin or having
  everyone know the admin password.  My sister is the admin account for
  the laptop and she can connect just fine.  I however is only just a
  non-admin account and everywhere I go I am asked for the admin account
  everytime I want to connect to wifi at Starbucks or any other place.

  I should note that wired ethernet connections work just fine, however
  it is annoying to find some business that has wired ports and some
  have none at all :(

  This bug is present in 13.10 AND 14.04

  Tested on 14.04 as of Febuary 28, 2014

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager-gnome 0.9.8.0-1ubuntu5.1
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Mar  1 09:52:27 2014
  ExecutablePath: /usr/bin/nm-applet
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-25 (127 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 69.145.136.1 dev eth0  proto static 
   69.145.136.0/22 dev eth0  proto kernel  scope link  src 69.145.137.13  
metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 12e05c40f-3e1f-4b48-a4f3-2efbe1450403   
802-3-ethernet1393692735   Sat 01 Mar 2014 09:52:15 AM MSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1286578/+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 1711851] Re: Disable MAC address randomization on Live system

** Summary changed:

- bad default setting
+ Disable MAC address randomization on Live system

-- 
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/1711851

Title:
  Disable MAC address randomization on Live system

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm using the pre-release version of artful 17.10 and network manager
  1.8.2-1ubuntu2 Much like in Debian Stretch, network-manager is set to
  use the random mac address feature of network manager, which doesn't
  allow certain wifi cards/ routers to work together. See Debian bug
  836351.  I think this feature should be disabled on a live cd, because
  it isn't fixable during an install and it might cause a user just to
  give up and not install Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Aug 19 14:00:17 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-08-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170818)
  IpRoute:
   default via 192.168.1.1 dev wlxec086b17f6d1 proto static metric 600 
   169.254.0.0/16 dev wlxec086b17f6d1 scope link metric 1000 
   192.168.1.0/24 dev wlxec086b17f6d1 proto kernel scope link src 192.168.1.4 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-08-19T13:51:03.103665
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH SLAVE 
   556F02  72b161b9-3dad-4583-ae59-1d3e0402b37e  802-11-wireless  
1503165502  Sat 19 Aug 2017 01:58:22 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlxec086b17f6d1  
activated  /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  1d860881-8bc6-3d0d-8455-2b15a87f1307  802-3-ethernet   
1503165498  Sat 19 Aug 2017 01:58:18 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --   
-- --  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   wlxec086b17f6d1  wifi  connected
/org/freedesktop/NetworkManager/Devices/3  556F02  
72b161b9-3dad-4583-ae59-1d3e0402b37e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eno1 ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1711851/+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 1661329] Re: Wifi password not taken into account if not entered rapidly

Maybe this bug is a duplicate of LP bug #1650835 (wifi association times
out while typing password)?

-- 
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/1661329

Title:
  Wifi password not taken into account if not entered rapidly

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  We install ubuntu/mint to numerous people and we got multiple
  reports that the wifi password was not taken into account. We managed
  to reproduce it by

  1 - Select your wifi network
  2 - Enter a fake password (Just to simulate a user error not entering well 
his wifi password)
  3 - Obviously here we cannot connect, so we wait
  4 - Password is asked a second time, and we enter it without error but we 
take our time to do so ( or wait some time after ). By taking our time we 
simulate people who are not fluent with their keyboard.
  5 - Wait to connect
  6 - Password is asked a third time.
  7 - Here if we go into the properties of the wifi (Applet > Modify > Modify) 
and check the password… the first fake password is still there

  Nice day

  It might be a double of this bug
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1219171

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1661329/+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 964705] Re: System policy prevents modification of network settings for all users

It seems Debian fix is simply to allow users from netdev (and sudo)
group add/change system-wide NetworkManager connections, this fix is
added in network-manager 0.9.4.0-7 and is merged in Ubuntu,

look at
/var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla

[Adding or changing system-wide NetworkManager connections]
Identity=unix-group:netdev;unix-group:sudo
Action=org.freedesktop.NetworkManager.settings.modify.system

So, main problem is that GNOME-Shell users aren't added to netdev group
by default?

Walter Lapchynski (wxl) wrote on 2015-06-29:#38
> Mathieu, it doesn't seem that the upstream fix in Debian ever got merged into 
> Ubuntu.
> Is there a reason for this?

-- 
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/964705

Title:
  System policy prevents modification of network settings for all users

Status in NetworkManager:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Debian:
  Fix Released
Status in network-manager package in openSUSE:
  Fix Released

Bug description:
  This seems like a regression? The screen shot is at
  http://thesii.org/Screenshot.jpg The nearest link I can find is from
  the forum area at http://ubuntuforums.org/showthread.php?p=1146

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sun Mar 25 19:36:45 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120323)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/964705/+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 1670343] Re: Usb_ModeSwitch package should become a part of HWE-stack

I've backported usb-modeswitch 2.4 and usb-modeswich-data 2017-01 from Ubuntu 
17.04 (Zesty) to 16.04 LTS (Xenial), you can update packages from 
ppa:baltix-members , see
https://launchpad.net/~baltix-members/+archive

Please reboot after installing usb-modeswitch 2.4 and usb-modeswich-data
2017-01 from ppa:baltix-members , test if your USB modem works correctly
with updated packages and write a comment here in any case (works or
not).

Thanks,
Mantas Kriaučiūnas
Developer of Baltix GNU/Linux Ubuntu derivative

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

Title:
  Usb_ModeSwitch package should become a part of HWE-stack

Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  For better support of newer modems usb-modeswitch package should be
  included in HWE-stack.

  Current situation: usb-modeswitch rules are seriously outdated on previous 
LTS editions.
  Proposed solution: usb-modeswitch may be recommend by HWE packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: usb-modeswitch 1.2.3+repack0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-123.166-generic 3.2.79
  Uname: Linux 3.2.0-123-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  Date: Mon Mar  6 15:37:31 2017
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MarkForUpload: True
  SourcePackage: usb-modeswitch
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1670343/+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 1569600] Re: usb_modeswitch crashed with SIGSEGV in libusb_exit()

I've backported usb-modeswitch 2.4 and usb-modeswich-data 2017-01 from Ubuntu 
17.04 (Zesty) to 16.04 LTS (Xenial), you can update packages from 
ppa:baltix-members , see
https://launchpad.net/~baltix-members/+archive

Please reboot after installing usb-modeswitch 2.4 and usb-modeswich-data
2017-01 from ppa:baltix-members , test if your USB modem works correctly
with updated packages and write a comment here in any case (works or
not).

Thanks,
Mantas Kriaučiūnas
Developer of Baltix GNU/Linux Ubuntu derivative

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

Title:
  usb_modeswitch crashed with SIGSEGV in libusb_exit()

Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b3b1 Chicony Electronics Co., Ltd 
  Bus 001 Device 007: ID 0930:0220 Toshiba Corp. 
  Bus 001 Device 012: ID 12d1:1c0b Huawei Technologies Co., Ltd. E173s 3G 
broadband stick (modem off)
  Bus 001 Device 003: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: usb-modeswitch 2.2.5+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Apr 12 23:40:19 2016
  ExecutablePath: /usr/sbin/usb_modeswitch
  InstallationDate: Installed on 2016-02-12 (60 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: usb_modeswitch -c /etc/usb_modeswitch.d/12d1:1c0b
  SegvAnalysis:
   Segfault happened at: 0x7effe96afdf6 <libusb_exit+134>:  mov
0x210(%rbx),%rdx
   PC (0x7effe96afdf6) ok
   source "0x210(%rbx)" (0x0210) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: usb-modeswitch
  StacktraceTop:
   libusb_exit () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? ()
   abort ()
   ?? ()
   ?? ()
  Title: usb_modeswitch crashed with SIGSEGV in libusb_exit()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1569600/+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 1606998] Re: HSUPA USB Modem MF195 not recognized in 16.04

I've backported usb-modeswitch 2.4 and usb-modeswich-data 2017-01 from Ubuntu 
17.04 (Zesty) to 16.04 LTS (Xenial), you can update packages from 
ppa:baltix-members , see
https://launchpad.net/~baltix-members/+archive

Please reboot after installing usb-modeswitch 2.4 and usb-modeswich-data
2017-01 from ppa:baltix-members , test if your USB modem works correctly
with updated packages and write a comment here in any case (works or
not).

Thanks,
Mantas Kriaučiūnas
Developer of Baltix GNU/Linux Ubuntu derivative

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

Title:
  HSUPA USB Modem MF195 not recognized in 16.04

Status in usb-modeswitch package in Ubuntu:
  New

Bug description:
  The USB Modem ZTE MF195 is still not recognized in Ubuntu 16.04:

  Jul 27 19:09:34 mbr mtp-probe: checking bus 3, device 16: 
"/sys/devices/pci:
  00/:00:14.0/usb3/3-1"
  Jul 27 19:09:34 mbr mtp-probe: bus: 3, device: 16 was not an MTP device
  Jul 27 19:09:34 mbr systemd[1]: Starting USB_ModeSwitch_3-1...
  Jul 27 19:09:34 mbr usb_modeswitch_dispatcher[26304]: Could not read 
attribute: 
  No such file or directory
  Jul 27 19:09:35 mbr kernel: [143996.698081] scsi 27:0:0:0: CD-ROM
ZTE
USB SCSI CD-ROM  0001 PQ: 0 ANSI: 0
  Jul 27 19:09:35 mbr kernel: [143996.698471] scsi 27:0:0:1: Direct-Access 
ZTE
Storage  0001 PQ: 0 ANSI: 0
  Jul 27 19:09:35 mbr kernel: [143996.699363] sr 27:0:0:0: [sr0] scsi3-mmc 
drive: 
  0x/0x caddy
  Jul 27 19:09:35 mbr kernel: [143996.699588] sr 27:0:0:0: Attached scsi CD-ROM 
sr
  0
  Jul 27 19:09:35 mbr kernel: [143996.699709] sr 27:0:0:0: Attached scsi 
generic s
  g1 type 5
  Jul 27 19:09:35 mbr kernel: [143996.699975] sd 27:0:0:1: Attached scsi 
generic s
  g2 type 0
  Jul 27 19:09:35 mbr kernel: [143996.701144] sd 27:0:0:1: [sdb] Attached SCSI 
rem
  ovable disk
  Jul 27 19:09:34 mbr usb_modeswitch_dispatcher[26304]: message repeated 2 
times: [ Could not read attribute: No such file or directory]
  Jul 27 19:09:35 mbr usb_modeswitch: switch device 19d2:1514 on 003/016
  Jul 27 19:09:35 mbr kernel: [143996.769268] scsi 27:0:0:0: rejecting I/O to 
offline device
  Jul 27 19:09:35 mbr kernel: [143996.769284] scsi 27:0:0:0: killing request
  Jul 27 19:09:36 mbr usb_modeswitch[26304]: usb_modeswitch: switched to 
19d2:1514 on 3/16
  Jul 27 19:09:37 mbr usb_modeswitch_dispatcher[26304]: Unable to open bind 
list file: No such file or directory
  Jul 27 19:09:37 mbr usb_modeswitch[26304]: usb_modeswitch: add device ID 
19d2:1514 to driver option
  Jul 27 19:09:37 mbr usb_modeswitch[26304]: usb_modeswitch: please report the 
device ID to the Linux USB developers!
  Jul 27 19:09:38 mbr gnome-session[16695]: (gnome-software:16875): Gs-WARNING 
**: failed to get updates: no results to show
  Jul 27 19:09:44 mbr systemd[1]: Started USB_ModeSwitch_3-1.

  Device ID: 19d2:1514

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: usb-modeswitch 2.2.5+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 27 19:14:31 2016
  InstallationDate: Installed on 2013-05-17 (1166 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac 
(20130424)
  SourcePackage: usb-modeswitch
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (95 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1606998/+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 1607001] Re: Huawei E122 USB Stick not recognized in Ubuntu 16.04

I've backported usb-modeswitch 2.4 and usb-modeswich-data 2017-01 from Ubuntu 
17.04 (Zesty) to 16.04 LTS (Xenial), you can update packages from 
ppa:baltix-members , see
https://launchpad.net/~baltix-members/+archive

Please reboot after installing usb-modeswitch 2.4 and usb-modeswich-data
2017-01 from ppa:baltix-members , test if your USB modem works correctly
with updated packages and write a comment here in any case (works or
not).

Thanks,
Mantas Kriaučiūnas
Developer of Baltix GNU/Linux Ubuntu derivative

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

Title:
  Huawei E122 USB Stick not recognized in Ubuntu 16.04

Status in One Hundred Papercuts:
  Confirmed
Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  The Huawei Mobile HSPA USB Modem E122 is does not connect and is not
  recognized in Ubuntu 16.04:

  Jul 27 19:18:48 mbr kernel: [144550.021251] usb 3-1: new high-speed USB 
device n
  umber 17 using xhci_hcd
  Jul 27 19:18:48 mbr kernel: [144550.149990] usb 3-1: New USB device found, 
idVen
  dor=12d1, idProduct=1446
  Jul 27 19:18:48 mbr kernel: [144550.150007] usb 3-1: New USB device strings: 
Mfr
  =1, Product=7, SerialNumber=0
  Jul 27 19:18:48 mbr kernel: [144550.150010] usb 3-1: Product: Huawei Mobile
  Jul 27 19:18:48 mbr kernel: [144550.150013] usb 3-1: Manufacturer: HUA WEI
  Jul 27 19:18:48 mbr kernel: [144550.150219] usb 3-1: ep 0x83 - rounding 
interval
   to 128 microframes, ep desc says 255 microframes
  Jul 27 19:18:48 mbr kernel: [144550.150228] usb 3-1: ep 0x3 - rounding 
interval 
  to 128 microframes, ep desc says 255 microframes
  Jul 27 19:18:48 mbr kernel: [144550.150235] usb 3-1: ep 0x82 - rounding 
interval
   to 128 microframes, ep desc says 255 microframes
  Jul 27 19:18:48 mbr kernel: [144550.150242] usb 3-1: ep 0x2 - rounding 
interval 
  to 128 microframes, ep desc says 255 microframes
  Jul 27 19:18:48 mbr kernel: [144550.150612] usb-storage 3-1:1.0: USB Mass 
Storage device detected
  Jul 27 19:18:48 mbr kernel: [144550.150895] scsi host28: usb-storage 3-1:1.0
  Jul 27 19:18:48 mbr kernel: [144550.151334] usb-storage 3-1:1.1: USB Mass 
Storage device detected
  Jul 27 19:18:48 mbr kernel: [144550.151578] scsi host29: usb-storage 3-1:1.1
  Jul 27 19:18:48 mbr mtp-probe: checking bus 3, device 17: 
"/sys/devices/pci:00/:00:14.0/usb3/3-1"
  Jul 27 19:18:48 mbr mtp-probe: bus: 3, device: 17 was not an MTP device
  Jul 27 19:18:48 mbr systemd[1]: Starting USB_ModeSwitch_3-1:1.0...
  Jul 27 19:18:48 mbr usb_modeswitch_dispatcher[27825]: Could not read 
attribute: No such file or directory
  Jul 27 19:18:49 mbr kernel: [144551.150218] scsi 28:0:0:0: CD-ROM
HUAWEI   Mass Storage 2.31 PQ: 0 ANSI: 2
  Jul 27 19:18:49 mbr kernel: [144551.150252] scsi 29:0:0:0: Direct-Access 
HUAWEI   SD Storage   2.31 PQ: 0 ANSI: 2
  Jul 27 19:18:49 mbr kernel: [144551.150978] sd 29:0:0:0: Attached scsi 
generic sg1 type 0
  Jul 27 19:18:49 mbr kernel: [144551.152045] sd 29:0:0:0: [sdb] Attached SCSI 
removable disk
  Jul 27 19:18:49 mbr kernel: [144551.152095] sr 28:0:0:0: [sr0] scsi-1 drive
  Jul 27 19:18:49 mbr kernel: [144551.152434] sr 28:0:0:0: Attached scsi CD-ROM 
sr0
  Jul 27 19:18:49 mbr kernel: [144551.152647] sr 28:0:0:0: Attached scsi 
generic sg2 type 5
  Jul 27 19:18:48 mbr usb_modeswitch_dispatcher[27825]: message repeated 3 
times: [ Could not read attribute: No such file or directory]
  Jul 27 19:18:49 mbr usb_modeswitch: switch device 12d1:1446 on 003/017
  Jul 27 19:18:50 mbr usb_modeswitch_dispatcher[27825]: Could not read 
attribute: No such file or directory
  Jul 27 19:18:50 mbr usb_modeswitch[27825]: usb_modeswitch: switched to 
12d1:1446 on 3/17
  Jul 27 19:18:51 mbr usb_modeswitch_dispatcher[27825]: Unable to open bind 
list file: No such file or directory
  Jul 27 19:18:51 mbr usb_modeswitch[27825]: usb_modeswitch: add device ID 
12d1:1446 to driver option
  Jul 27 19:18:51 mbr usb_modeswitch[27825]: usb_modeswitch: please report the 
device ID to the Linux USB developers!
  Jul 27 19:18:52 mbr gnome-session[16695]: (gnome-software:16875): Gs-WARNING 
**: failed to get updates: no results to show
  Jul 27 19:18:58 mbr systemd[1]: Started USB_ModeSwitch_3-1:1.0.

  Device ID 12d1:1446

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: usb-modeswitch 2.2.5+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 27 19:19:51 2016
  InstallationDate: Installed on 2013-05-17 (1166 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac 
(20130424)
  SourcePackage: usb-modeswitch
  UpgradeStatus: Upgraded to xenial on 201

[Desktop-packages] [Bug 1707810] Re: regression on udev rules for HUAWEI mobile broadband?

I've backported usb-modeswitch 2.4 and usb-modeswich-data 2017-01 from Ubuntu 
17.04 (Zesty) to 16.04 LTS (Xenial), you can update packages from 
ppa:baltix-members , see
https://launchpad.net/~baltix-members/+archive

Please reboot after installing usb-modeswitch 2.4 and usb-modeswich-data
2017-01 from ppa:baltix-members , test if your USB modem works correctly
with updated packages and write a comment here in any case (works or
not).

Thanks,
Mantas Kriaučiūnas
Developer of Baltix GNU/Linux Ubuntu derivative

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

Title:
  regression on udev rules for HUAWEI mobile broadband?

Status in linux package in Ubuntu:
  Incomplete
Status in usb-modeswitch-data package in Ubuntu:
  New

Bug description:
  I found several bug reports about mobile broadband USB sticks not
  working on Ubuntu 16.04. It seems that all the low level support is in
  place but the udev rules are incomplete, in what could be a regression
  from previous versions.

  --- 16.04 -

  
  ATTRS{idVendor}=="12d1", ATTRS{manufacturer}!="Android", 
ATTR{bInterfaceNumber}=="00", ATTR{bInterfaceClass}=="08", RUN+="usb_modeswitch 
'%b/%k'"
  ATTR{idVendor}=="12d1", ATTR{idProduct}=="1573", RUN+="usb_modeswitch '%b/%k'"

  
  --- 12.04 -

  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1003", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1009", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="101e", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1030", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1031", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1414", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1446", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1449", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14ad", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14b5", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14b7", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14c1", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14c4", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14c5", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14d1", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="14fe", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1505", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1520", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1521", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1523", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1553", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1557", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1c0b", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1d50", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1da1", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1f01", RUN+="usb_modeswitch 
'%b/%k'"
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="380b", RUN+="usb_modeswitch 
'%b/%k'"

  For example the HUAWEI device with vendor:product pair 12d1:1f01 (see
  #1527914 ) worked fine (plug and play) on Ubuntu 12.04 but appears as
  as mass storage device on Ubuntu 16.04.

  The missing rule is simply:

  ATTRS{idVendor}=="12d1", ATTR{idProduct}=="1f01", RUN+="usb_modeswitch
  '%b/%k'"

  References: #1431179 #1527914 #1514231

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707810/+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 1638991] Re: ZTE 3G USB dongles are recognized as storage devices instead of network device

I've backported usb-modeswitch 2.4 and usb-modeswich-data 2017-01 from Ubuntu 
17.04 (Zesty) to 16.04 LTS (Xenial), you can update packages from 
ppa:baltix-members , see
https://launchpad.net/~baltix-members/+archive

Please reboot after installing usb-modeswitch 2.4 and usb-modeswich-data
2017-01 from ppa:baltix-members , test if your USB modem works correctly
with updated packages and write a comment here in any case (works or
not).

Thanks,
Mantas Kriaučiūnas
Developer of Baltix GNU/Linux Ubuntu derivative

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

Title:
  ZTE 3G USB dongles are recognized as storage devices instead of
  network device

Status in usb-modeswitch package in Ubuntu:
  New

Bug description:
  ZTE 3G dongles (MTS Mblaze in India) are not recognized as network
  device, instead it is getting recognized as storage device. Also when
  an USB device is plugged in, it is not getting recognized
  automatically (hot plugging).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1638991/+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 1631667] Re: crash usb_modeswitch_dispaatcher

I've backported usb-modeswitch 2.4 and usb-modeswich-data 2017-01 from Ubuntu 
17.04 (Zesty) to 16.04 LTS (Xenial), you can update packages from 
ppa:baltix-members , see
https://launchpad.net/~baltix-members/+archive

Please reboot after installing usb-modeswitch 2.4 and usb-modeswich-data
2017-01 from ppa:baltix-members , test if your USB modem works correctly
with updated packages and write a comment here in any case (works or
not).

Thanks,
Mantas Kriaučiūnas
Developer of Baltix GNU/Linux Ubuntu derivative

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

Title:
  crash usb_modeswitch_dispaatcher

Status in usb-modeswitch package in Ubuntu:
  New

Bug description:
  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Oct  8 23:59:25 2016
  DistroRelease: Ubuntu 16.04
  ExecutablePath: /usr/sbin/usb_modeswitch_dispatcher
  ExecutableTimestamp: 1444057573
  ProcCmdline: /usr/sbin/usb_modeswitch_dispatcher --switch-systemd 1-1.4
  ProcCwd: /
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  ApportVersion: 2.20.1-0ubuntu2.1
  Dependencies:
   adduser 3.113+nmu3ubuntu4
   apt 1.2.12~ubuntu16.04.1
   apt-utils 1.2.12~ubuntu16.04.1
   coreutils 8.25-2ubuntu2
   debconf 1.5.58ubuntu1
   debconf-i18n 1.5.58ubuntu1
   debianutils 4.7
   dpkg 1.18.4ubuntu1.1
   e2fslibs 1.42.13-1ubuntu1
   e2fsprogs 1.42.13-1ubuntu1
   gcc-5-base 5.4.0-6ubuntu1~16.04.2
   gcc-6-base 6.0.1-0ubuntu1
   gnupg 1.4.20-1ubuntu3.1
   gpgv 1.4.20-1ubuntu3.1
   init-system-helpers 1.29ubuntu2
   initscripts 2.88dsf-59.3ubuntu2
   insserv 1.14.0-5ubuntu3
   libacl1 2.2.52-3
   libapt-inst2.0 1.2.12~ubuntu16.04.1
   libapt-pkg5.0 1.2.12~ubuntu16.04.1
   libattr1 1:2.4.47-2
   libaudit-common 1:2.4.5-1ubuntu2
   libaudit1 1:2.4.5-1ubuntu2
   libblkid1 2.27.1-6ubuntu3.1
   libbz2-1.0 1.0.6-8
   libc6 2.23-0ubuntu3
   libcomerr2 1.42.13-1ubuntu1
   libdb5.3 5.3.28-11
   libfdisk1 2.27.1-6ubuntu3.1
   libgcc1 1:6.0.1-0ubuntu1
   libgcrypt20 1.6.5-2ubuntu0.2
   libgpg-error0 1.21-2ubuntu1
   libgpm2 1.20.4-6.1
   libkmod2 22-1ubuntu4
   liblocale-gettext-perl 1.07-1build1
   liblz4-1 0.0~r131-2ubuntu2
   liblzma5 5.1.1alpha+20120614-2ubuntu2
   libmount1 2.27.1-6ubuntu3.1
   libncurses5 6.0+20160213-1ubuntu1
   libncursesw5 6.0+20160213-1ubuntu1
   libpam-modules 1.1.8-3.2ubuntu2
   libpam-modules-bin 1.1.8-3.2ubuntu2
   libpam0g 1.1.8-3.2ubuntu2
   libpcre3 2:8.38-3.1
   libpipeline1 1.4.1-2
   libprocps4 2:3.3.10-4ubuntu2
   libreadline6 6.3-8ubuntu2
   libselinux1 2.4-3build2
   libsemanage-common 2.3-1build3
   libsemanage1 2.3-1build3
   libsepol1 2.4-2
   libsmartcols1 2.27.1-6ubuntu3.1
   libss2 1.42.13-1ubuntu1
   libstdc++6 5.4.0-6ubuntu1~16.04.2
   libsystemd0 229-4ubuntu10
   libtext-charwidth-perl 0.04-7build5
   libtext-iconv-perl 1.7-5build4
   libtext-wrapi18n-perl 0.06-7.1
   libtinfo5 6.0+20160213-1ubuntu1
   libudev1 229-4ubuntu10
   libusb-0.1-4 2:0.1.12-28
   libusb-1.0-0 2:1.0.20-1
   libustr-1.0-1 1.0.4-5
   libuuid1 2.27.1-6ubuntu3.1
   lsb-base 9.20160110ubuntu0.2
   mount 2.27.1-6ubuntu3.1
   multiarch-support 2.23-0ubuntu3
   passwd 1:4.2-3.1ubuntu5
   perl-base 5.22.1-9
   procps 2:3.3.10-4ubuntu2
   psmisc 22.21-2.1build1
   readline-common 6.3-8ubuntu2
   sensible-utils 0.0.9
   sysv-rc 2.88dsf-59.3ubuntu2
   sysvinit-utils 2.88dsf-59.3ubuntu2
   tar 1.28-2.1
   ubuntu-keyring 2012.05.19
   udev 229-4ubuntu10
   usb-modeswitch 2.2.5+repack0-1ubuntu1
   usb-modeswitch-data 20151101-1
   util-linux 2.27.1-6ubuntu3.1
   uuid-runtime 2.27.1-6ubuntu3.1
   zlib1g 1:1.2.8.dfsg-2ubuntu4

  Title: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1631667/+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 1654090] Re: [Backport-lts] Modem 03f0:931d not switched