[Desktop-packages] [Bug 1972991] [NEW] 22.04 Totem crashes on launch (segmentation fault)

[Aaron Whitehouse]

Public bug reported:

Hello,

Since upgrading (fresh reinstall) to 22.04, I have had issues with Totem
crashing.

I have not been able to pin down when it works and when it doesn't, as
playing the same videos seems to work sometimes and not work others.
After it crashes, trying to open it again normally does not work and
trying to launch totem from the commandline gives a segmentation fault.

Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Segmentation fault (core dumped)

$ totem
Segmentation fault (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 11 13:10:48 2022
InstallationDate: Installed on 2022-04-24 (16 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  22.04 Totem crashes on launch (segmentation fault)

Status in totem package in Ubuntu:
  New

Bug description:
  Hello,

  Since upgrading (fresh reinstall) to 22.04, I have had issues with
  Totem crashing.

  I have not been able to pin down when it works and when it doesn't, as
  playing the same videos seems to work sometimes and not work others.
  After it crashes, trying to open it again normally does not work and
  trying to launch totem from the commandline gives a segmentation
  fault.

  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  

[Desktop-packages] [Bug 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)

[Aaron Whitehouse]

(And Firefox gave me a notification about hitting version 100, so it
presumably did update)

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

Title:
  Ubuntu Dock does not show indicator for open Firefox (after snap
  refresh?)

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I am using the Firefox Snap on a fresh install of 22.04 (using
  defaults, as far as I know).

  Normally, Firefox shows an indicator in the Dock showing that it is
  running (the orange dot) and gives the ability to choose between open
  windows.

  At the moment, I have Firefox windows open, but nothing is shown in
  the Dock (as if it is closed).

  My suspicion is that the snap was refreshed while running and this
  confused Gnome Shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 13:31:40 2022
  InstallationDate: Installed on 2022-04-24 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+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 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)

[Aaron Whitehouse]

** Attachment added: "As expected, closing and reopening Firefox makes it work 
as expected"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587903/+files/Screenshot%20from%202022-05-09%2013-44-45.png

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

Title:
  Ubuntu Dock does not show indicator for open Firefox (after snap
  refresh?)

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I am using the Firefox Snap on a fresh install of 22.04 (using
  defaults, as far as I know).

  Normally, Firefox shows an indicator in the Dock showing that it is
  running (the orange dot) and gives the ability to choose between open
  windows.

  At the moment, I have Firefox windows open, but nothing is shown in
  the Dock (as if it is closed).

  My suspicion is that the snap was refreshed while running and this
  confused Gnome Shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 13:31:40 2022
  InstallationDate: Installed on 2022-04-24 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+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 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)

[Aaron Whitehouse]

** Attachment added: "Screenshot of the dock"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587901/+files/Screenshot%20from%202022-05-09%2013-32-20.png

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

Title:
  Ubuntu Dock does not show indicator for open Firefox (after snap
  refresh?)

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I am using the Firefox Snap on a fresh install of 22.04 (using
  defaults, as far as I know).

  Normally, Firefox shows an indicator in the Dock showing that it is
  running (the orange dot) and gives the ability to choose between open
  windows.

  At the moment, I have Firefox windows open, but nothing is shown in
  the Dock (as if it is closed).

  My suspicion is that the snap was refreshed while running and this
  confused Gnome Shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 13:31:40 2022
  InstallationDate: Installed on 2022-04-24 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+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 1972545] [NEW] Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)

[Aaron Whitehouse]

Public bug reported:

I am using the Firefox Snap on a fresh install of 22.04 (using defaults,
as far as I know).

Normally, Firefox shows an indicator in the Dock showing that it is
running (the orange dot) and gives the ability to choose between open
windows.

At the moment, I have Firefox windows open, but nothing is shown in the
Dock (as if it is closed).

My suspicion is that the snap was refreshed while running and this
confused Gnome Shell.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May  9 13:31:40 2022
InstallationDate: Installed on 2022-04-24 (14 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "journalctl -b 0 > log"
   https://bugs.launchpad.net/bugs/1972545/+attachment/5587897/+files/log

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

Title:
  Ubuntu Dock does not show indicator for open Firefox (after snap
  refresh?)

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I am using the Firefox Snap on a fresh install of 22.04 (using
  defaults, as far as I know).

  Normally, Firefox shows an indicator in the Dock showing that it is
  running (the orange dot) and gives the ability to choose between open
  windows.

  At the moment, I have Firefox windows open, but nothing is shown in
  the Dock (as if it is closed).

  My suspicion is that the snap was refreshed while running and this
  confused Gnome Shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 13:31:40 2022
  InstallationDate: Installed on 2022-04-24 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+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 1970185] Re: 20.04 does not remember preferred bluetooth headset microphone

[Aaron Whitehouse]

** Attachment added: "Headset back on, output has gone back to the headset but 
microphone has not"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583423/+files/Screenshot%20from%202022-04-25%2009-43-46.png

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

Title:
  20.04 does not remember preferred bluetooth headset microphone

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

Bug description:
  In Gnome's sound settings, it takes a sensible approach for my Bluetooth 
headset speaker:
  1) I set it as my preferred audio Output Device
  2) I turn the headset off and it disappears, reverting to the built in 
speakers
  3) I turn the headset on again and it switches back to using the Bluetooth 
headset speaker

  This sensible approach is not taken for the microphone. The same flow for the 
microphone is:
  1) Set the headset microphone as the default
  2) Turn the headset off and it reverts to the internal microphone
  3) Turn the headset back on and it stays as the internal microphone

  I have attached screenshots in case they help explain.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 09:44:42 2022
  InstallationDate: Installed on 2022-04-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+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 1970185] Re: 20.04 does not remember preferred bluetooth headset microphone

[Aaron Whitehouse]

** Attachment added: "Headset turned off, input and output revert to internal 
ones"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583422/+files/Screenshot%20from%202022-04-25%2009-43-27.png

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

Title:
  20.04 does not remember preferred bluetooth headset microphone

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

Bug description:
  In Gnome's sound settings, it takes a sensible approach for my Bluetooth 
headset speaker:
  1) I set it as my preferred audio Output Device
  2) I turn the headset off and it disappears, reverting to the built in 
speakers
  3) I turn the headset on again and it switches back to using the Bluetooth 
headset speaker

  This sensible approach is not taken for the microphone. The same flow for the 
microphone is:
  1) Set the headset microphone as the default
  2) Turn the headset off and it reverts to the internal microphone
  3) Turn the headset back on and it stays as the internal microphone

  I have attached screenshots in case they help explain.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 09:44:42 2022
  InstallationDate: Installed on 2022-04-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+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 1970185] [NEW] 20.04 does not remember preferred bluetooth headset microphone

[Aaron Whitehouse]

Public bug reported:

In Gnome's sound settings, it takes a sensible approach for my Bluetooth 
headset speaker:
1) I set it as my preferred audio Output Device
2) I turn the headset off and it disappears, reverting to the built in speakers
3) I turn the headset on again and it switches back to using the Bluetooth 
headset speaker

This sensible approach is not taken for the microphone. The same flow for the 
microphone is:
1) Set the headset microphone as the default
2) Turn the headset off and it reverts to the internal microphone
3) Turn the headset back on and it stays as the internal microphone

I have attached screenshots in case they help explain.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.4-1ubuntu12
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 25 09:44:42 2022
InstallationDate: Installed on 2022-04-24 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "Headset on, headset mic and speaker set as input and 
output devices"
   
https://bugs.launchpad.net/bugs/1970185/+attachment/5583417/+files/Screenshot%20from%202022-04-25%2009-42-41.png

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

Title:
  20.04 does not remember preferred bluetooth headset microphone

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

Bug description:
  In Gnome's sound settings, it takes a sensible approach for my Bluetooth 
headset speaker:
  1) I set it as my preferred audio Output Device
  2) I turn the headset off and it disappears, reverting to the built in 
speakers
  3) I turn the headset on again and it switches back to using the Bluetooth 
headset speaker

  This sensible approach is not taken for the microphone. The same flow for the 
microphone is:
  1) Set the headset microphone as the default
  2) Turn the headset off and it reverts to the internal microphone
  3) Turn the headset back on and it stays as the internal microphone

  I have attached screenshots in case they help explain.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 09:44:42 2022
  InstallationDate: Installed on 2022-04-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+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 1938867] Re: Logitech K400R keyboard not entering text into input fields on Raspberry Pi 4

[Aaron Whitehouse]

Ah interesting, thanks Daniel. I did not realise Raspberry Pis were
doing Wayland by default.

Yes, it works as expected in xorg, but not in Wayland.

It's a Raspberry Pi 4 Model B - 8GB, in case that was not clear from my
logs.

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

Title:
  Logitech K400R keyboard not entering text into input fields on
  Raspberry Pi 4

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I am running Hirsuite on a Raspberry Pi 4. My main keyboard for this
  (TV) machine is a wireless Logitech K400r combined keyboard/trackpad.

  When I first installed, I do not think there were any issues with the
  keyboard. When I did updates, my keyboard half-stopped working. It is
  very odd -- the keyboard is obviously working, as I can enter in my
  password on the lock screen or press Ctrl+Alt t for a terminal, but
  then I cannot enter anything into the terminal, Firefox input fields
  or anything else. Even more strangely, when I attach a second USB
  keyboard, both that new keyboard and my K400r work perfectly.When I
  unplug the USB keyboard, it stops working again.

  I'm not sure where this problem is, but:
  $ apt policy xserver-xorg-input-all
  xserver-xorg-input-all:
Installed: 1:7.7+22ubuntu1

  Please let me know if I can provide anything further to help diagnose
  this.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg-input-all 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-1015.16-raspi 5.11.22
  Uname: Linux 5.11.0-1015-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  4 08:46:44 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20210421
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
video=HDMI-A-1:1280x720M@60 smsc95xx.macaddr=E4:5F:01:48:E1:03 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1938867/+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 1938867] [NEW] Keyboard not entering text into input fields

[Aaron Whitehouse]

Public bug reported:

I am running Hirsuite on a Raspberry Pi 4. My main keyboard for this
(TV) machine is a wireless Logitech K400r combined keyboard/trackpad.

When I first installed, I do not think there were any issues with the
keyboard. When I did updates, my keyboard half-stopped working. It is
very odd -- the keyboard is obviously working, as I can enter in my
password on the lock screen or press Ctrl+Alt t for a terminal, but then
I cannot enter anything into the terminal, Firefox input fields or
anything else. Even more strangely, when I attach a second USB keyboard,
both that new keyboard and my K400r work perfectly.When I unplug the USB
keyboard, it stops working again.

I'm not sure where this problem is, but:
$ apt policy xserver-xorg-input-all
xserver-xorg-input-all:
  Installed: 1:7.7+22ubuntu1

Please let me know if I can provide anything further to help diagnose
this.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xserver-xorg-input-all 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-1015.16-raspi 5.11.22
Uname: Linux 5.11.0-1015-raspi aarch64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: arm64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug  4 08:46:44 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 
ImageMediaBuild: 20210421
Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 3.0 
Host Controller
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
video=HDMI-A-1:1280x720M@60 smsc95xx.macaddr=E4:5F:01:48:E1:03 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
 
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: apport-bug arm64 arm64-image hirsute raspi-image ubuntu wayland-session

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

Title:
  Keyboard not entering text into input fields

Status in xorg package in Ubuntu:
  New

Bug description:
  I am running Hirsuite on a Raspberry Pi 4. My main keyboard for this
  (TV) machine is a wireless Logitech K400r combined keyboard/trackpad.

  When I first installed, I do not think there were any issues with the
  keyboard. When I did updates, my keyboard half-stopped working. It is
  very odd -- the keyboard is obviously working, as I can enter in my
  password on the lock screen or press Ctrl+Alt t for a terminal, but
  then I cannot enter anything into the terminal, Firefox input fields
  or anything else. Even more strangely, when I attach a second USB
  keyboard, both that new keyboard and my K400r work perfectly.When I
  unplug the USB keyboard, it stops working again.

  I'm not sure where this problem is, but:
  $ apt policy xserver-xorg-input-all
  xserver-xorg-input-all:
Installed: 1:7.7+22ubuntu1

  Please let me know if I can provide anything further to help diagnose
  this.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg-input-all 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-1015.16-raspi 5.11.22
  Uname: Linux 5.11.0-1015-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  4 08:46:44 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20210421
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
video=HDMI-A-1:1280x720M@60 smsc95xx.macaddr=E4:5F:01:48:E1:03 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
 

[Desktop-packages] [Bug 1892379] Re: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling

[Aaron Whitehouse]

** Attachment added: "Playback on 200% screen"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403153/+files/Screenshot%20from%202020-08-20%2015-54-40.png

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

Title:
  Totem plays video scaled down on HiDPI screen on Wayland with multiple
  monitors at different fractional scaling

Status in totem package in Ubuntu:
  New

Bug description:
  I am using Ubuntu Focal Fossa with Wayland and two screens. 
  Display 1 is a 3840 x 2160 screen at 200% scaling
  Display 2 is a 1920x1200 at 100% scaling

  Fractional Scaling is on. Display 2 is my Primary Display.

  When I play a video on Display 2, everything works as expected. When I
  play a video on Display 1 (whether I drag it there or it is there all
  along) then it plays taking up only the top-left corner of the window.

  May be related to:
  https://bugzilla.redhat.com/show_bug.cgi?id=1529008
  https://gitlab.gnome.org/GNOME/totem/-/issues/271
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/252

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:45:13 2020
  InstallationDate: Installed on 2020-05-03 (108 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+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 1892379] Re: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling

[Aaron Whitehouse]

** Attachment added: "Display Settings screenshot 2"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403155/+files/Screenshot%20from%202020-08-20%2015-56-01.png

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

Title:
  Totem plays video scaled down on HiDPI screen on Wayland with multiple
  monitors at different fractional scaling

Status in totem package in Ubuntu:
  New

Bug description:
  I am using Ubuntu Focal Fossa with Wayland and two screens. 
  Display 1 is a 3840 x 2160 screen at 200% scaling
  Display 2 is a 1920x1200 at 100% scaling

  Fractional Scaling is on. Display 2 is my Primary Display.

  When I play a video on Display 2, everything works as expected. When I
  play a video on Display 1 (whether I drag it there or it is there all
  along) then it plays taking up only the top-left corner of the window.

  May be related to:
  https://bugzilla.redhat.com/show_bug.cgi?id=1529008
  https://gitlab.gnome.org/GNOME/totem/-/issues/271
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/252

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:45:13 2020
  InstallationDate: Installed on 2020-05-03 (108 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+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 1892379] Re: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling

[Aaron Whitehouse]

** Attachment added: "Display Settings screenshot 1"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403154/+files/Screenshot%20from%202020-08-20%2015-55-54.png

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

Title:
  Totem plays video scaled down on HiDPI screen on Wayland with multiple
  monitors at different fractional scaling

Status in totem package in Ubuntu:
  New

Bug description:
  I am using Ubuntu Focal Fossa with Wayland and two screens. 
  Display 1 is a 3840 x 2160 screen at 200% scaling
  Display 2 is a 1920x1200 at 100% scaling

  Fractional Scaling is on. Display 2 is my Primary Display.

  When I play a video on Display 2, everything works as expected. When I
  play a video on Display 1 (whether I drag it there or it is there all
  along) then it plays taking up only the top-left corner of the window.

  May be related to:
  https://bugzilla.redhat.com/show_bug.cgi?id=1529008
  https://gitlab.gnome.org/GNOME/totem/-/issues/271
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/252

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:45:13 2020
  InstallationDate: Installed on 2020-05-03 (108 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+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 1892379] [NEW] Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling

[Aaron Whitehouse]

Public bug reported:

I am using Ubuntu Focal Fossa with Wayland and two screens. 
Display 1 is a 3840 x 2160 screen at 200% scaling
Display 2 is a 1920x1200 at 100% scaling

Fractional Scaling is on. Display 2 is my Primary Display.

When I play a video on Display 2, everything works as expected. When I
play a video on Display 1 (whether I drag it there or it is there all
along) then it plays taking up only the top-left corner of the window.

May be related to:
https://bugzilla.redhat.com/show_bug.cgi?id=1529008
https://gitlab.gnome.org/GNOME/totem/-/issues/271
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/252

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: totem 3.34.1-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 20 15:45:13 2020
InstallationDate: Installed on 2020-05-03 (108 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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


** Tags: amd64 apport-bug focal wayland-session

** Attachment added: "Video playback on 100% screen"
   
https://bugs.launchpad.net/bugs/1892379/+attachment/5403147/+files/Screenshot%20from%202020-08-20%2015-54-27.png

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

Title:
  Totem plays video scaled down on HiDPI screen on Wayland with multiple
  monitors at different fractional scaling

Status in totem package in Ubuntu:
  New

Bug description:
  I am using Ubuntu Focal Fossa with Wayland and two screens. 
  Display 1 is a 3840 x 2160 screen at 200% scaling
  Display 2 is a 1920x1200 at 100% scaling

  Fractional Scaling is on. Display 2 is my Primary Display.

  When I play a video on Display 2, everything works as expected. When I
  play a video on Display 1 (whether I drag it there or it is there all
  along) then it plays taking up only the top-left corner of the window.

  May be related to:
  https://bugzilla.redhat.com/show_bug.cgi?id=1529008
  https://gitlab.gnome.org/GNOME/totem/-/issues/271
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/252

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 15:45:13 2020
  InstallationDate: Installed on 2020-05-03 (108 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+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 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function

[Aaron Whitehouse]

Hello all,

Apologies, I missed these recent messages.

For background, the error UnicodeDecodeError just means that a non-ASCII
character is hitting a piece of code that was not designed to handle it.
That is not surprising -- prior to the 0.8 series, very little of the
code was designed for non-ASCII characters. What that means is that you
may be seeing a UnicodeDecodeError even though this bug is fixed,
because somewhere else in the code needs fixing.

Victor Douglas (jhngalt): This is an interesting error and thank you very much 
for following our instructions on testing the snap and giving the relevant 
details. Can you please test with the latest stable duplicity snap and, if you 
still have a problem, report the bug in our new tracker 
(https://gitlab.com/duplicity/duplicity/-/issues )? Note that "snap run 
duplicity" does not actually do anything without arguments (even working 
correctly it gives:
Command line error: Expected 2 args, got 0
Enter 'duplicity --help' for help screen.), but it still should not be giving 
an error like that. It looks as though the error was related to non-ASCII in 
your temporary directory name not being handled correctly.

Martin Theiner (mathesubu1) and BlueT - Matthew Lien - 練喆明 (bluet) --
you are both using an old (pre 0.8 series) version of duplicity/deja
dup. Please uninstall the system version (e.g. "sudo apt-get purge
duplicity") and install the stable snap (e.g. "sudo snap install
duplicity —classic") and test again.

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

Title:
  Duplicity fails with UnicodeDecodeError in uexc function

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+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 1879742] [NEW] When using Google Meet on Firefox, delay sending sound from microphone

[Aaron Whitehouse]

Public bug reported:

When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for
the first 5-10 seconds of the meeting, nobody can hear anything that I
am saying. After that, I have no issues. I also have no issues joining
with Chromium.

The sound indicator on my end (the little green bars that flash when you
are talking) start immediately, but nobody on the call hears anything
from me.

The only info I could find from Googling was somebody else talking about a 
similar problem:
https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 76.0.1+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  aaron-work   1813 F pulseaudio
BuildID: 20200507114007
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Wed May 20 17:05:20 2020
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2020-05-03 (16 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
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.14 metric 600
Locales: extensions.sqlite corrupt or missing
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:738
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/11/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.1
dmi.board.name: 0F6P3V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  When using Google Meet on Firefox, delay sending sound from microphone

Status in firefox package in Ubuntu:
  New

Bug description:
  When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for
  the first 5-10 seconds of the meeting, nobody can hear anything that I
  am saying. After that, I have no issues. I also have no issues joining
  with Chromium.

  The sound indicator on my end (the little green bars that flash when
  you are talking) start immediately, but nobody on the call hears
  anything from me.

  The only info I could find from Googling was somebody else talking about a 
similar problem:
  
https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 76.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   1813 F pulseaudio
  BuildID: 20200507114007
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 17:05:20 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-05-03 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:738
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Desktop-packages] [Bug 1877038] Re: Firefox seems to lack FIDO2 support with Yubikeys

[Aaron Whitehouse]

Is this related to: https://bugzilla.mozilla.org/show_bug.cgi?id=1530370
? If so, in the duplicate bug
(https://bugzilla.mozilla.org/show_bug.cgi?id=1619850 ) somebody said
"This is a 2020 goal."

** Package changed: evolution (Ubuntu) => firefox (Ubuntu)

** Bug watch added: Mozilla Bugzilla #1530370
   https://bugzilla.mozilla.org/show_bug.cgi?id=1530370

** Bug watch added: Mozilla Bugzilla #1619850
   https://bugzilla.mozilla.org/show_bug.cgi?id=1619850

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

Title:
  Firefox seems to lack FIDO2 support with Yubikeys

Status in firefox package in Ubuntu:
  New

Bug description:
  Ubuntu LTS versions affected.

  "Passwordless" authentications with Yubikeys using Firefox don't work
  with FIDO2.

  Tested both with the yubikey software packages from the
  bionic/universe repo and those from the vendor https://www.yubico.com/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1877038/+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 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function

[Aaron Whitehouse]

All,

This should be fixed in 0.8.00, which has now been released. This is the
first 0.8-series release, so expect issues and test it out on data you
can afford to lose (if it comes to that).

I have now packaged up this version as a snap. You can install it by typing:
snap install duplicity --classic --beta
Please uninstall your current version of duplicity to ensure you are using the 
snap instead of one from apt etc.
(This will work out of the box on nearly all versions of Ubuntu. If you use a 
different distro and have never installed snaps before, visit this page:
https://docs.snapcraft.io/installing-snapd )

This includes the latest duplicity and all dependencies wrapped up in a
self-contained bundle. You should not need to install anything else for
this to work (including for all backends).

If you do test this, it would be very helpful if you could please
comment here, even if the only feedback is that all worked as expected.

If you are giving any feedback, please also give the output of:
which duplicity
and
snap list | grep duplicity
and let me know which backends you used.

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

Title:
  Duplicity fails with UnicodeDecodeError in uexc function

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+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 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function

[Aaron Whitehouse]

All, to clarify the current position, this is fixed in the 0.8 series,
but I set out the steps to test the fix in comment #15 and was waiting
on testing feedback before merging the patch back into the 0.7 series.
Nobody gave me any testing feedback. It is therefore not yet fixed in
the 0.7 series.

It looks as though Ubuntu has separately patched this in Disco only
(comment #19).

So it will not work in Bionic or Xenial.

We are now so close to a 0.8 release that I am inclined to wait for that
and encourage affected users to move straight to that, rather than risk
breaking people who are sticking to the 0.7 series.

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

Title:
  Duplicity fails with UnicodeDecodeError in uexc function

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+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 1440372] Re: please port duplicity to Python3

[Aaron Whitehouse]

@Sebastian, Kenneth is planning to release a 0.8 version very soon.

Note that I have wound the Python 3 blueprint completion back a step, as
I have realised that there are some backend dependencies (e.g. pyrax)
that do not work on Python 3. I believe deja dup only uses a subset of
the backends anyway, so what has already been done may be sufficient
once a 0.8-series release is out the door.

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

Title:
  please port duplicity to Python3

Status in Duplicity:
  Fix Committed
Status in duplicity package in Ubuntu:
  In Progress
Status in duplicity source package in Eoan:
  In Progress

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. deja-dup should be ported to Python3.

  There seems to be some progress upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1440372/+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 1826550] Re: Fractional scaling options do not appear with multiple monitors

[Aaron Whitehouse]

** Attachment added: "Screenshot with external monitor connected. Only whole 
number scaling available."
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+attachment/5259303/+files/Screenshot%20from%202019-04-26%2014-32-06.png

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

Title:
  Fractional scaling options do not appear with multiple monitors

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

Bug description:
  Using 19.04 disco with Wayland.

  I have a HiDPI laptop screen (XPS13) and a normal DPI external
  monitor.

  I have enabled the experimental fractional scaling support.

  When no external monitor is connected, the fractional scaling options
  are displayed as expected. When the external monitor is connected,
  only the old whole number scaling options are displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 14:32:55 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-04 (234 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+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 1826550] [NEW] Fractional scaling options do not appear with multiple monitors

[Aaron Whitehouse]

Public bug reported:

Using 19.04 disco with Wayland.

I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.

I have enabled the experimental fractional scaling support.

When no external monitor is connected, the fractional scaling options
are displayed as expected. When the external monitor is connected, only
the old whole number scaling options are displayed.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.1-1ubuntu4
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 26 14:32:55 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-09-04 (234 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)

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


** Tags: amd64 apport-bug disco third-party-packages wayland-session

** Attachment added: "With no external monitor. Fractional scaling options 
shown."
   
https://bugs.launchpad.net/bugs/1826550/+attachment/5259299/+files/Screenshot%20from%202019-04-26%2014-32-37.png

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

Title:
  Fractional scaling options do not appear with multiple monitors

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

Bug description:
  Using 19.04 disco with Wayland.

  I have a HiDPI laptop screen (XPS13) and a normal DPI external
  monitor.

  I have enabled the experimental fractional scaling support.

  When no external monitor is connected, the fractional scaling options
  are displayed as expected. When the external monitor is connected,
  only the old whole number scaling options are displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 14:32:55 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-04 (234 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+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 1826547] [NEW] [Wayland] Display change "Revert Settings" window uses primary screen scaling factor

[Aaron Whitehouse]

Public bug reported:

Using 19.04 disco with Wayland.

I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have the laptop screen set to 200% and the external screen set to
100%.

If I set the primary display to the built-in display but have the
display settings window open on the external screen, then when I change
the scaling factor of the built-in display to e.g. 300% and click Apply,
the "Do you want to keep these settings" confirmation window appears on
the external screen, scaled by 300%. If the external monitor is the
primary display, it is always scaled normally at 100%.

Conversely, if the external monitor is set as the primary display, but
the settings window is on the built-in display, then when I change the
scaling factor of the external monitor to 100%, then this "Do you want
to keep these settings" dialog appears incorrectly scaled at 100%
instead of 200%.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.1-1ubuntu4
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 26 14:16:23 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-09-04 (234 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)

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


** Tags: amd64 apport-bug disco third-party-packages wayland-session

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

Title:
  [Wayland] Display change "Revert Settings" window uses primary screen
  scaling factor

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

Bug description:
  Using 19.04 disco with Wayland.

  I have a HiDPI laptop screen (XPS13) and a normal DPI external
  monitor. I have the laptop screen set to 200% and the external screen
  set to 100%.

  If I set the primary display to the built-in display but have the
  display settings window open on the external screen, then when I
  change the scaling factor of the built-in display to e.g. 300% and
  click Apply, the "Do you want to keep these settings" confirmation
  window appears on the external screen, scaled by 300%. If the external
  monitor is the primary display, it is always scaled normally at 100%.

  Conversely, if the external monitor is set as the primary display, but
  the settings window is on the built-in display, then when I change the
  scaling factor of the external monitor to 100%, then this "Do you want
  to keep these settings" dialog appears incorrectly scaled at 100%
  instead of 200%.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 14:16:23 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-04 (234 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826547/+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 1826543] [NEW] [Wayland] Support multiple monitors with different scaling factors

[Aaron Whitehouse]

Public bug reported:

Running 19.04 Disco with Wayland
Version 64ubuntu7

I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have the laptop screen set to 200% and the external screen set to
100%.

When running the display solely on my built-in monitor, the dock is
correctly scaled to 200%. When running the display is running solely on
the external monitor, the dock is scaled to 100%.

When running both monitors at the same time, the scaling factor used for
the docks on both monitors is the scaling factor of the primary monitor:
so if that is the external screen is primary then the laptop screen
version of the dock is tiny; and if the built-in screen is primary then
the external monitor dock is huge.

I would expect the dock scaling factor to always match the scaling
factor of the screen that the dock is displayed on.

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- [Wayland] Scale the dock based on the scaling factor for that monitor
+ [Wayland] Support multiple monitors with different scaling factors

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

Title:
  [Wayland] Support multiple monitors with different scaling factors

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Running 19.04 Disco with Wayland
  Version 64ubuntu7

  I have a HiDPI laptop screen (XPS13) and a normal DPI external
  monitor. I have the laptop screen set to 200% and the external screen
  set to 100%.

  When running the display solely on my built-in monitor, the dock is
  correctly scaled to 200%. When running the display is running solely
  on the external monitor, the dock is scaled to 100%.

  When running both monitors at the same time, the scaling factor used
  for the docks on both monitors is the scaling factor of the primary
  monitor: so if that is the external screen is primary then the laptop
  screen version of the dock is tiny; and if the built-in screen is
  primary then the external monitor dock is huge.

  I would expect the dock scaling factor to always match the scaling
  factor of the screen that the dock is displayed on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1826543/+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 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function

[Aaron Whitehouse]

The 0.8-series was affected by this (as I mentioned above, fixing the
underlying problem avoids this error and a number of these have been
fixed, so it is harder to trigger).

I have just proposed a fix for it be merged into the 0.8-series:
https://code.launchpad.net/~aaron-whitehouse/duplicity/08-uexc-fix

I would still appreciate any feedback on the 0.7-series branch above. I
am more nervous about making changes in our stable branch without
feedback.

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

Title:
  Duplicity fails with UnicodeDecodeError in uexc function

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+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 1440372] Re: please port duplicity to Python3

[Aaron Whitehouse]

Marking this as Fix Committed, as we have Python 3 compatible code in
0.8-series with all tests also being run against this environment. We
have not yet put out a 0.8 release, though.

See https://blueprints.launchpad.net/duplicity/+spec/python3


** Changed in: duplicity
   Importance: Undecided => High

** Changed in: duplicity
   Status: New => Fix Committed

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

Title:
  please port duplicity to Python3

Status in Duplicity:
  Fix Committed
Status in duplicity package in Ubuntu:
  Triaged

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. deja-dup should be ported to Python3.

  There seems to be some progress upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1440372/+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 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function

[Aaron Whitehouse]

Thank you everybody for your bug reports and comments.

I believe that this bug is already fixed in the 0.8-series, but we have
not yet released a package for this.

The code triggering this is used when there is an exception/error
message containing a non-ASCII character (for example a filename), so
this is sometimes 'fixed' by fixing the underlying problem. This is why
some commenters say the problem went away when they resolved permissions
issues. I do not know what has changed that is causing this to break for
people it did not break for previously.

The reality is that version 0.7 and below were never actually written to
accommodate non-ASCII characters and the fact it worked at all was
largely luck. The 0.8 series does add proper support for non-ASCII, with
the internals converted to Unicode and Python 3 support.

Many thanks to Pete Zaitcev (zaitcev) in Bug #1797928 for proposing a
patch for this, which I had overlooked.

I have applied this in the branch here: lp:~aaron-
whitehouse/duplicity/07-uexc-fix

It would be helpful if you can please test to see if this fixes your problem as 
follows:
1. Create a new destination directory to test with.
2. Test that duplicity fails as you have reported when using this destination.
3. Pull down a copy of the branch with the fix:
bzr branch lp:~aaron-whitehouse/duplicity/07-uexc-fix dup_patched
4. cd dup_patched/duplicity 
5. run ./compilec.py
6. change directory back to wherever you were running duplicity from before
5. Test with the patched duplicity:
PYTHONPATH=[full path/]dup_patched [full path/]dup_patched/bin/duplicity [all 
of your options/arguments]

Please let me know how you get on.

== Simple illustration of failure ==
A simple example triggering this bug is to create a couple of empty 
directories, say "source1" and "dest".

Then try:
duplicity --exclude=bänana source1/ file://dest/

This should give a FilePrefixError (hideous in version 0.7 and much more 
informative in 0.8), but instead says:
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1611, in 
if "Forced assertion for testing" in util.uexc(e):
  File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 1: ordinal 
not in range(128)

** Branch linked: lp:~aaron-whitehouse/duplicity/07-uexc-fix

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

Title:
  Duplicity fails with UnicodeDecodeError in uexc function

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh inst

[Desktop-packages] [Bug 1770929] Re: backup fails with UnicodeDecodeError in uexc function

[Aaron Whitehouse]

** Summary changed:

- backup fails with UnicodeDecodeError
+ backup fails with UnicodeDecodeError in uexc function

** Summary changed:

- backup fails with UnicodeDecodeError in uexc function
+ Duplicity fails with UnicodeDecodeError in uexc function

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

Title:
  Duplicity fails with UnicodeDecodeError in uexc function

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+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 1731341] Re: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)"

[Aaron Whitehouse]

** Also affects: gphoto2 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the
  camera: Unspecified error (-1)"

Status in gphoto2 package in Ubuntu:
  Confirmed
Status in shotwell package in Ubuntu:
  Confirmed

Bug description:
  I have a Fujifilm X-T10. This worked perfectly in Shotwell in 17.04. Since 
upgrading to 17.10, I receive an error whenever I try to import photos:
  Unable to fetch previews from the camera: Unspecified error (-1)

  lsusb gives:

  Bus 001 Device 010: ID 04cb:02c8 Fuji Photo Film Co., Ltd

  dmesg gives:

  [  585.129167] usb 1-2: new high-speed USB device number 10 using xhci_hcd
  [  585.269979] usb 1-2: New USB device found, idVendor=04cb, 
idProduct=02c8
  [  585.269980] usb 1-2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [  585.269981] usb 1-2: Product: USB PTP Camera
  [  585.269981] usb 1-2: SerialNumber: 59353130303416092266F93011BFE6

  This looks like the same issue reported in Ask Ubuntu (with no answer) here:
  
https://askubuntu.com/questions/972613/usb-ptp-camera-no-longer-working-after-upgrade-to-17-10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: shotwell 0.26.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 21:36:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-03 (494 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: shotwell
  UpgradeStatus: Upgraded to artful on 2017-10-29 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1731341/+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 1731341] [NEW] Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)"

[Aaron Whitehouse]

Public bug reported:

I have a Fujifilm X-T10. This worked perfectly in Shotwell in 17.04. Since 
upgrading to 17.10, I receive an error whenever I try to import photos:
Unable to fetch previews from the camera: Unspecified error (-1)

lsusb gives:

Bus 001 Device 010: ID 04cb:02c8 Fuji Photo Film Co., Ltd

dmesg gives:

[  585.129167] usb 1-2: new high-speed USB device number 10 using xhci_hcd
[  585.269979] usb 1-2: New USB device found, idVendor=04cb, idProduct=02c8
[  585.269980] usb 1-2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
[  585.269981] usb 1-2: Product: USB PTP Camera
[  585.269981] usb 1-2: SerialNumber: 59353130303416092266F93011BFE6

This looks like the same issue reported in Ask Ubuntu (with no answer) here:
https://askubuntu.com/questions/972613/usb-ptp-camera-no-longer-working-after-upgrade-to-17-10

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: shotwell 0.26.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  9 21:36:30 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-03 (494 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: shotwell
UpgradeStatus: Upgraded to artful on 2017-10-29 (11 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the
  camera: Unspecified error (-1)"

Status in shotwell package in Ubuntu:
  New

Bug description:
  I have a Fujifilm X-T10. This worked perfectly in Shotwell in 17.04. Since 
upgrading to 17.10, I receive an error whenever I try to import photos:
  Unable to fetch previews from the camera: Unspecified error (-1)

  lsusb gives:

  Bus 001 Device 010: ID 04cb:02c8 Fuji Photo Film Co., Ltd

  dmesg gives:

  [  585.129167] usb 1-2: new high-speed USB device number 10 using xhci_hcd
  [  585.269979] usb 1-2: New USB device found, idVendor=04cb, 
idProduct=02c8
  [  585.269980] usb 1-2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [  585.269981] usb 1-2: Product: USB PTP Camera
  [  585.269981] usb 1-2: SerialNumber: 59353130303416092266F93011BFE6

  This looks like the same issue reported in Ask Ubuntu (with no answer) here:
  
https://askubuntu.com/questions/972613/usb-ptp-camera-no-longer-working-after-upgrade-to-17-10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: shotwell 0.26.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 21:36:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-03 (494 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: shotwell
  UpgradeStatus: Upgraded to artful on 2017-10-29 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1731341/+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 1651396] Re: Backup fails every time after one incremental file is possibly corrupted

[Aaron Whitehouse]

Have you tried to verify your backup or do a new full backup?

> Can someone recommend a better backup software for personal use?
http://lmgtfy.com/?q=personal+backup+software+linux

There is a reason, though, that Deja Dup (which you are already using)
is the default in Ubuntu -- it is a pretty good balance of ease of use
and reliability.

Kind regards,

Aaron

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

Title:
  Backup fails every time after one incremental file is possibly
  corrupted

Status in deja-dup package in Ubuntu:
  New

Bug description:
  The backup location is on a NAS mounted with NFS. I get this message
  every time I try to make a new backup:

  Backup Failed

  Invalid data - SHA1 hash mismatch for file:
   duplicity-inc.20161219T001458Z.to.20161220T001456Z.vol1.difftar.gpg
   Calculated hash: 3dde403f81e36268ce9b7f53478d9dd8301a439c
   Manifest hash: b46782fb799c7c5a543ac88d9bfb7cc1df25d38c


  Can someone recommend a better backup software for personal use?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 20 12:36:15 2016
  InstallationDate: Installed on 2014-05-16 (949 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (139 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1651396/+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 1308105] Re: Xfce resets TV mode to NULL when power cycled

[Aaron Whitehouse]

Jonathan,

Given the latest version of xfce-settings (4.12.1) was easy to install
and fixed all of my issues (see comment #130 above), it would be
interesting to know whether this also fixed your problem.

Kind regards,

Aaron

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

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu:
  Confirmed
Status in xfce4-settings:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode "NULL"

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello 

  OUTPUT="HDMI-0"
  BAD_MODE="1280x720"
  GOOD_MODE="1920x1080"

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+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 1308105] Re: Xfce resets TV mode to NULL when power cycled

[Aaron Whitehouse]

I have an ASUS Z170M-Plus Mobo with an Intel Core i3-6100T, Intel HD 530
graphics and a Samsung TV connected through HDMI, running Mythbuntu
16.04.

I had the issue that when I turned the TV off and then back on again, the TV 
would say "No Signal" and I would have to run 
$ sudo service lightdm restart
to get it to work again.

Based on Alexandre's comment #128, I installed xfce-settings 4.12.1 from here:
https://packages.debian.org/stretch/amd64/xfce4-settings/download
http://ftp.uk.debian.org/debian/pool/main/x/xfce4-settings/xfce4-settings_4.12.1-1_amd64.deb
and installed it on my Mythbuntu 16.04 installation. To my surprise, I didn't 
have any dependency issues, it all applied without problems and now the problem 
seems fixed! I can turn the TV off and on again and the picture comes back as 
expected.

Great work all in getting this sorted.

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

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu:
  Confirmed
Status in xfce4-settings:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode "NULL"

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello 

  OUTPUT="HDMI-0"
  BAD_MODE="1280x720"
  GOOD_MODE="1920x1080"

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+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 1329133] Re: Error message about .dbus directory shows up after backup even though the directory is excluded.

[Aaron Whitehouse]

*** This bug is a duplicate of bug 1313034 ***
https://bugs.launchpad.net/bugs/1313034

** This bug has been marked a duplicate of bug 1313034
   Deja-dup reports it couldn't backup ~/.cache/dconf and ~/.gvfs even though 
it's not supposed to try to (also, ~/.dbus)

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

Title:
  Error message about .dbus directory shows up after backup even though
  the directory is excluded.

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Please check the attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 12 04:11:35 2014
  InstallationDate: Installed on 2014-05-16 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1329133/+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 1245013] [NEW] [Regression] Vertical/Horizontal scroll along edge of touchpad not working in 13.10 (Dell 14z)

[Aaron Whitehouse]

Public bug reported:

I use a Dell Inspiron 14z with 13.10.  I'm pretty sure that at least
vertical scrolling (by moving my finger along the right edge of the
touchpad) used to work, but neither work for me now in 13.10.

My hardware details should be attached.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Sat Oct 26 17:38:37 2013
DistUpgraded: 2013-10-05 21:00:51,454 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-04-26 (183 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MachineType: Dell Inc. Inspiron 5423
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic 
root=UUID=e429a76e-75c0-44b9-90d4-a75ee21d98a2 ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: Upgraded to saucy on 2013-10-05 (20 days ago)
dmi.bios.date: 08/03/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0RMVR3
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/03/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0RMVR3:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 5423
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Sat Oct 26 18:06:28 2013
xserver.configfile: default
xserver.errors:
 RADEON(G0): [drm] Failed to open DRM device for pci::02:00.0: No such file 
or directory
 RADEON(G0): Kernel modesetting setup failed
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id9020 
 vendor AUO
xserver.version: 2:1.14.3-3ubuntu1

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug saucy ubuntu

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

Title:
  [Regression] Vertical/Horizontal scroll along edge of touchpad not
  working in 13.10 (Dell 14z)

Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  New

Bug description:
  I use a Dell Inspiron 14z with 13.10.  I'm pretty sure that at least
  vertical scrolling (by moving my finger along the right edge of the
  touchpad) used to work, but neither work for me now in 13.10.

  My hardware details should be attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sat Oct 26 17:38:37 2013
  DistUpgraded: 2013-10-05 21:00:51,454 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-26 (183 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Dell Inc. Inspiron 5423
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic 
root=UUID=e429a76e-75c0-44b9-90d4-a75ee21d98a2 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: Upgraded to saucy on 2013-10-05 (20 days ago)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0RMVR3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/03/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0RMVR3:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: 

[Desktop-packages] [Bug 1088187] Re: Scan doesn't give a preview and only saves in jpeg format

[Aaron Whitehouse]

We have recently updated (new clean install) to 13.04 Raring Ringtail
and this appears to have been fixed. I now have a preview when scanning
and have no problems saving PDFs. Thanks!

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

Title:
  Scan doesn't give a preview and only saves in jpeg format

Status in Simple Scan:
  Confirmed
Status in “simple-scan” package in Ubuntu:
  Confirmed

Bug description:
  I have used Simple Scan a lot on other machines etc.

  On my new laptop running 12.10, it doesn't really work.

  1) When I scan a page, the white blank page disappears so that there is only 
a blank grey area there. If I let it scan, nothing changes and only the grey 
background shows. It must have scanned correctly, however, as if I save as a 
JPEG, it works and the file looks okay.
  2) However, if I save instead as a PDF, only a blank white document is saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: simple-scan 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sun Dec  9 14:23:31 2012
  DriverPackageVersions:
   libsane 1.0.23-0ubuntu1
   libsane-extras N/A
   hplip 3.12.6-3ubuntu4
   hpoj N/A
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-30 (69 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120926)
  MachineType: Dell Inc. Inspiron 5423
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic 
root=UUID=e8fd1b8e-1837-4efd-8466-e6a803e2f1eb ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0RMVR3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/03/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0RMVR3:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1088187/+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 1088187] Re: Scan doesn't give a preview and only saves in jpeg format

[Aaron Whitehouse]

Sorry, I meant to say, it would be interesting to know if updating also
solves your problem, Pierre - you may be able to try from a live DVD of
13.04?

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

Title:
  Scan doesn't give a preview and only saves in jpeg format

Status in Simple Scan:
  Confirmed
Status in “simple-scan” package in Ubuntu:
  Confirmed

Bug description:
  I have used Simple Scan a lot on other machines etc.

  On my new laptop running 12.10, it doesn't really work.

  1) When I scan a page, the white blank page disappears so that there is only 
a blank grey area there. If I let it scan, nothing changes and only the grey 
background shows. It must have scanned correctly, however, as if I save as a 
JPEG, it works and the file looks okay.
  2) However, if I save instead as a PDF, only a blank white document is saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: simple-scan 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sun Dec  9 14:23:31 2012
  DriverPackageVersions:
   libsane 1.0.23-0ubuntu1
   libsane-extras N/A
   hplip 3.12.6-3ubuntu4
   hpoj N/A
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-30 (69 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120926)
  MachineType: Dell Inc. Inspiron 5423
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic 
root=UUID=e8fd1b8e-1837-4efd-8466-e6a803e2f1eb ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0RMVR3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/03/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0RMVR3:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1088187/+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 1088244] Re: No Full-Disk Encryption unlock screen on some boots

[Aaron Whitehouse]

I just did a clean install of 13.04 Raring Ringtail and this still
occurs (on my first boot, unfortunately!)

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

Title:
  No Full-Disk Encryption unlock screen on some boots

Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  I use Full-Disk Encryption on 12.10. All seems to work fine sometimes
  - the pretty screen asks for my disk unlock password and then takes me
  to the login screen when I enter it correctly.

  Other times, it shows a completely blank black screen. I can type the
  password in the dark and hit enter and it goes to the login screen,
  but it obviously isn't very good from a usability point of view.

  Let me know how I can help.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: lightdm 1.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sun Dec  9 20:15:36 2012
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-12-09 (0 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1088244/+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 1173393] [NEW] Both my IGD Intel 4000HD and discrete ATi Radeon are powered on by default

[Aaron Whitehouse]

Public bug reported:

I have a Dell Insprion 14z (Inspiron 5423) and I'm running 13.04. The
machine has an Intel 4000 HD and Radeon 7550M/7570M/7650M

By default, both graphics cards are powered up, even though only the integrated 
Intel is used:
$ sudo cat /sys/kernel/debug/vgaswitcheroo/switch
0:DIS: :Pwr::02:00.0
1:IGD:+:Pwr::00:02.0

The same was the case in 12.10. By default, the machine heats up
terribly and the fan blasts full-tilt, with battery life affected.

Each time that I reinstall Ubuntu, I have to manually edit /etc/rc.local to add 
the following above the exit 0:
echo IGD  /sys/kernel/debug/vgaswitcheroo/switch
echo OFF  /sys/kernel/debug/vgaswitcheroo/switch

As far as I can tell, this makes no difference to performance, as by
default the ATi/AMD card isn't doing anything anyway.

I appreciate that, long term, the problem will hopefully be solved by
powering up the discrete card as-needed and switching to that, but until
we reach hybrid graphics Nirvana, perhaps the sensible option is to just
turn off the discrete cards by default. I assume that it takes some
jiggery-pokery to make the discrete card do anything, so adding another
step to that seems less important than making sure that machines in the
default setup don't overheat and have poor battery life. With the new
Intel chips/drivers, they are actually a pretty good option anyway - I'm
driving a 1900x1200 external monitor off mine, along with the 720p
laptop monitor.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Apr 26 22:34:26 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:057f]
 Advanced Micro Devices [AMD] nee ATI Thames [Radeon 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
InstallationDate: Installed on 2013-04-26 (0 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MachineType: Dell Inc. Inspiron 5423
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic 
root=UUID=e429a76e-75c0-44b9-90d4-a75ee21d98a2 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0RMVR3
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/03/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0RMVR3:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 5423
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.43-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1

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


** Tags: amd64 apport-bug compiz-0.9 raring ubuntu

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

Title:
  Both my IGD Intel 4000HD and discrete ATi Radeon are powered on by
  default

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I have a Dell Insprion 14z (Inspiron 5423) and I'm running 13.04. The
  machine has an Intel 4000 HD and Radeon 7550M/7570M/7650M

  By default, both graphics cards are powered up, even though only the 
integrated Intel is used:
  $ sudo cat /sys/kernel/debug/vgaswitcheroo/switch
  0:DIS: :Pwr::02:00.0
  1:IGD:+:Pwr::00:02.0

  The same was the case in 12.10. By default, the machine heats up
  terribly and the fan blasts full-tilt, with battery life affected.

  Each time that I reinstall Ubuntu, I have to manually edit /etc/rc.local to 
add the following above the exit 0:
  echo IGD  /sys/kernel/debug/vgaswitcheroo/switch
  

[Desktop-packages] [Bug 1088187] Re: Scan doesn't give a preview and only saves in jpeg format

[Aaron Whitehouse]

$ simple-scan --debug
[+0.00s] DEBUG: simple-scan.vala:582: Starting Simple Scan 3.6.0, PID=11198
[+0.00s] DEBUG: Connecting to session manager
[+0.03s] DEBUG: ui.vala:1404: Restoring window to 600x400 pixels
[+0.06s] DEBUG: scanner.vala:1378: sane_init () - SANE_STATUS_GOOD
[+0.06s] DEBUG: scanner.vala:1384: SANE version 1.0.23
[+0.06s] DEBUG: scanner.vala:1445: Requesting redetection of scan devices
[+0.06s] DEBUG: scanner.vala:753: Processing request
[+2.61s] DEBUG: scanner.vala:334: sane_get_devices () - SANE_STATUS_GOOD
[+2.61s] DEBUG: scanner.vala:346: Device: 
name=hpaio:/usb/Photosmart_C6300_series?serial=MY8C97712D0544 
vendor=Hewlett-Packard model=Photosmart_C6300_series type=all-in-one
[+11.32s] DEBUG: simple-scan.vala:310: Requesting scan at 300 dpi from device 
'hpaio:/usb/Photosmart_C6300_series?serial=MY8C97712D0544'
[+11.32s] DEBUG: scanner.vala:1491: Scanner.scan 
(hpaio:/usb/Photosmart_C6300_series?serial=MY8C97712D0544, dpi=300, 
scan_mode=ScanMode.COLOR, depth=8, type=ScanType.SINGLE, paper_width=0, 
paper_height=0)
[+11.32s] DEBUG: scanner.vala:753: Processing request
[+13.37s] DEBUG: scanner.vala:814: sane_open 
(hpaio:/usb/Photosmart_C6300_series?serial=MY8C97712D0544) - SANE_STATUS_GOOD
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (0)
[+13.37s] DEBUG: scanner.vala:685: Option 0: title='Number of options' type=int 
size=4 cap=,soft-detect
[+13.37s] DEBUG: scanner.vala:688:   Description: Read-only option that 
specifies how many options a specific devices supports.
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (1)
[+13.37s] DEBUG: scanner.vala:685: Option 1: name='(null)' title='Scan mode' 
type=group size=0
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (2)
[+13.37s] DEBUG: scanner.vala:685: Option 2: name='mode' title='Scan mode' 
type=string size=20 values=[Lineart, Gray, Color] 
cap=,soft-select,soft-detect
[+13.37s] DEBUG: scanner.vala:688:   Description: Selects the scan mode (e.g., 
lineart, monochrome, or color).
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (3)
[+13.37s] DEBUG: scanner.vala:685: Option 3: name='resolution' title='Scan 
resolution' type=int size=4 unit=dpi values=[75, 100, 150, 200, 300, 600, 1200, 
2400, 4800] cap=,soft-select,soft-detect
[+13.37s] DEBUG: scanner.vala:688:   Description: Sets the resolution of the 
scanned image.
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (4)
[+13.37s] DEBUG: scanner.vala:685: Option 4: name='(null)' title='Advanced' 
type=group size=0 cap=,advanced
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (5)
[+13.37s] DEBUG: scanner.vala:685: Option 5: name='contrast' title='Contrast' 
type=int size=4 min=0, max=100, quant=0 
cap=,soft-select,soft-detect,inactive,advanced
[+13.37s] DEBUG: scanner.vala:688:   Description: Controls the contrast of the 
acquired image.
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (6)
[+13.37s] DEBUG: scanner.vala:685: Option 6: name='compression' 
title='Compression' type=string size=20 values=[None, JPEG] 
cap=,soft-select,soft-detect,advanced
[+13.37s] DEBUG: scanner.vala:688:   Description: Selects the scanner 
compression method for faster scans, possibly at the expense of image quality.
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (7)
[+13.37s] DEBUG: scanner.vala:685: Option 7: name='jpeg-quality' title='JPEG 
compression factor' type=int size=4 min=0, max=100, quant=0 
cap=,soft-select,soft-detect,advanced
[+13.37s] DEBUG: scanner.vala:688:   Description: Sets the scanner JPEG 
compression factor. Larger numbers mean better compression, and smaller numbers 
mean better image quality.
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (8)
[+13.37s] DEBUG: scanner.vala:685: Option 8: name='batch-scan' title='Batch 
scan' type=bool size=4 cap=,soft-select,soft-detect,advanced
[+13.37s] DEBUG: scanner.vala:688:   Description: Enables continuous scanning 
with automatic document feeder (ADF).
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (9)
[+13.37s] DEBUG: scanner.vala:685: Option 9: name='source' title='Scan source' 
type=string size=20 values=[] cap=,soft-select,soft-detect,advanced
[+13.37s] DEBUG: scanner.vala:688:   Description: Selects the scan source (such 
as a document-feeder).
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (10)
[+13.37s] DEBUG: scanner.vala:685: Option 10: name='duplex' title='Duplex' 
type=bool size=4 cap=,soft-select,soft-detect,inactive,advanced
[+13.37s] DEBUG: scanner.vala:688:   Description: Enables scanning on both 
sides of the page.
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (11)
[+13.37s] DEBUG: scanner.vala:685: Option 11: name='(null)' title='Geometry' 
type=group size=0 cap=,advanced
[+13.37s] DEBUG: scanner.vala:835: sane_get_option_descriptor (12)
[+13.37s] DEBUG: scanner.vala:685: Option 12: name='length-measurement' 
title='Length measurement' type=string size=20 

[Desktop-packages] [Bug 1088187] Re: Scan doesn't give a preview and only saves in jpeg format

[Aaron Whitehouse]

** Attachment added: Screenshot after page scanned
   
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1088187/+attachment/3473143/+files/JPEG%20Screenshot%20from%202013-01-03%2009%3A25%3A29.png

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

Title:
  Scan doesn't give a preview and only saves in jpeg format

Status in “simple-scan” package in Ubuntu:
  Incomplete

Bug description:
  I have used Simple Scan a lot on other machines etc.

  On my new laptop running 12.10, it doesn't really work.

  1) When I scan a page, the white blank page disappears so that there is only 
a blank grey area there. If I let it scan, nothing changes and only the grey 
background shows. It must have scanned correctly, however, as if I save as a 
JPEG, it works and the file looks okay.
  2) However, if I save instead as a PDF, only a blank white document is saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: simple-scan 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sun Dec  9 14:23:31 2012
  DriverPackageVersions:
   libsane 1.0.23-0ubuntu1
   libsane-extras N/A
   hplip 3.12.6-3ubuntu4
   hpoj N/A
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-30 (69 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120926)
  MachineType: Dell Inc. Inspiron 5423
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic 
root=UUID=e8fd1b8e-1837-4efd-8466-e6a803e2f1eb ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0RMVR3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/03/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0RMVR3:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1088187/+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 1088187] Re: Scan doesn't give a preview and only saves in jpeg format

[Aaron Whitehouse]

From scanning to a PDF:
$ simple-scan --debug
[+0.00s] DEBUG: simple-scan.vala:582: Starting Simple Scan 3.6.0, PID=11751
[+0.00s] DEBUG: Connecting to session manager
[+0.04s] DEBUG: ui.vala:1404: Restoring window to 600x400 pixels
[+0.04s] DEBUG: ui.vala:1409: Restoring window to maximized
[+0.07s] DEBUG: scanner.vala:1378: sane_init () - SANE_STATUS_GOOD
[+0.07s] DEBUG: scanner.vala:1384: SANE version 1.0.23
[+0.07s] DEBUG: scanner.vala:1445: Requesting redetection of scan devices
[+0.07s] DEBUG: scanner.vala:753: Processing request
[+2.22s] DEBUG: simple-scan.vala:310: Requesting scan at 300 dpi from device 
'(null)'
[+2.22s] DEBUG: scanner.vala:1491: Scanner.scan ((null), dpi=300, 
scan_mode=ScanMode.COLOR, depth=8, type=ScanType.SINGLE, paper_width=0, 
paper_height=0)
[+2.50s] DEBUG: scanner.vala:334: sane_get_devices () - SANE_STATUS_GOOD
[+2.50s] DEBUG: scanner.vala:346: Device: 
name=hpaio:/usb/Photosmart_C6300_series?serial=MY8C97712D0544 
vendor=Hewlett-Packard model=Photosmart_C6300_series type=all-in-one
[+2.50s] DEBUG: scanner.vala:753: Processing request
[+4.55s] DEBUG: scanner.vala:814: sane_open 
(hpaio:/usb/Photosmart_C6300_series?serial=MY8C97712D0544) - SANE_STATUS_GOOD
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (0)
[+4.55s] DEBUG: scanner.vala:685: Option 0: title='Number of options' type=int 
size=4 cap=,soft-detect
[+4.55s] DEBUG: scanner.vala:688:   Description: Read-only option that 
specifies how many options a specific devices supports.
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (1)
[+4.55s] DEBUG: scanner.vala:685: Option 1: name='(null)' title='Scan mode' 
type=group size=0
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (2)
[+4.55s] DEBUG: scanner.vala:685: Option 2: name='mode' title='Scan mode' 
type=string size=20 values=[Lineart, Gray, Color] 
cap=,soft-select,soft-detect
[+4.55s] DEBUG: scanner.vala:688:   Description: Selects the scan mode (e.g., 
lineart, monochrome, or color).
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (3)
[+4.55s] DEBUG: scanner.vala:685: Option 3: name='resolution' title='Scan 
resolution' type=int size=4 unit=dpi values=[75, 100, 150, 200, 300, 600, 1200, 
2400, 4800] cap=,soft-select,soft-detect
[+4.55s] DEBUG: scanner.vala:688:   Description: Sets the resolution of the 
scanned image.
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (4)
[+4.55s] DEBUG: scanner.vala:685: Option 4: name='(null)' title='Advanced' 
type=group size=0 cap=,advanced
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (5)
[+4.55s] DEBUG: scanner.vala:685: Option 5: name='contrast' title='Contrast' 
type=int size=4 min=0, max=100, quant=0 
cap=,soft-select,soft-detect,inactive,advanced
[+4.55s] DEBUG: scanner.vala:688:   Description: Controls the contrast of the 
acquired image.
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (6)
[+4.55s] DEBUG: scanner.vala:685: Option 6: name='compression' 
title='Compression' type=string size=20 values=[None, JPEG] 
cap=,soft-select,soft-detect,advanced
[+4.55s] DEBUG: scanner.vala:688:   Description: Selects the scanner 
compression method for faster scans, possibly at the expense of image quality.
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (7)
[+4.55s] DEBUG: scanner.vala:685: Option 7: name='jpeg-quality' title='JPEG 
compression factor' type=int size=4 min=0, max=100, quant=0 
cap=,soft-select,soft-detect,advanced
[+4.55s] DEBUG: scanner.vala:688:   Description: Sets the scanner JPEG 
compression factor. Larger numbers mean better compression, and smaller numbers 
mean better image quality.
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (8)
[+4.55s] DEBUG: scanner.vala:685: Option 8: name='batch-scan' title='Batch 
scan' type=bool size=4 cap=,soft-select,soft-detect,advanced
[+4.55s] DEBUG: scanner.vala:688:   Description: Enables continuous scanning 
with automatic document feeder (ADF).
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (9)
[+4.55s] DEBUG: scanner.vala:685: Option 9: name='source' title='Scan source' 
type=string size=20 values=[] cap=,soft-select,soft-detect,advanced
[+4.55s] DEBUG: scanner.vala:688:   Description: Selects the scan source (such 
as a document-feeder).
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (10)
[+4.55s] DEBUG: scanner.vala:685: Option 10: name='duplex' title='Duplex' 
type=bool size=4 cap=,soft-select,soft-detect,inactive,advanced
[+4.55s] DEBUG: scanner.vala:688:   Description: Enables scanning on both sides 
of the page.
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (11)
[+4.55s] DEBUG: scanner.vala:685: Option 11: name='(null)' title='Geometry' 
type=group size=0 cap=,advanced
[+4.55s] DEBUG: scanner.vala:835: sane_get_option_descriptor (12)
[+4.55s] DEBUG: scanner.vala:685: Option 12: name='length-measurement' 
title='Length measurement' type=string size=20 values=[Unknown, 
Approximate, Padded] 

[Desktop-packages] [Bug 1088187] Re: Scan doesn't give a preview and only saves in jpeg format

[Aaron Whitehouse]

For completeness, a screenshot from after scanning to PDF, though this
matches the screenshot above.

** Attachment added: PDF Screenshot from 2013-01-03 09:29:20.png
   
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1088187/+attachment/3473145/+files/PDF%20Screenshot%20from%202013-01-03%2009%3A29%3A20.png

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

Title:
  Scan doesn't give a preview and only saves in jpeg format

Status in “simple-scan” package in Ubuntu:
  Incomplete

Bug description:
  I have used Simple Scan a lot on other machines etc.

  On my new laptop running 12.10, it doesn't really work.

  1) When I scan a page, the white blank page disappears so that there is only 
a blank grey area there. If I let it scan, nothing changes and only the grey 
background shows. It must have scanned correctly, however, as if I save as a 
JPEG, it works and the file looks okay.
  2) However, if I save instead as a PDF, only a blank white document is saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: simple-scan 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sun Dec  9 14:23:31 2012
  DriverPackageVersions:
   libsane 1.0.23-0ubuntu1
   libsane-extras N/A
   hplip 3.12.6-3ubuntu4
   hpoj N/A
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-30 (69 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120926)
  MachineType: Dell Inc. Inspiron 5423
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic 
root=UUID=e8fd1b8e-1837-4efd-8466-e6a803e2f1eb ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0RMVR3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/03/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0RMVR3:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1088187/+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 1088187] [NEW] Scan doesn't give a preview and only saves in jpeg format

[Aaron Whitehouse]

Public bug reported:

I have used Simple Scan a lot on other machines etc.

On my new laptop running 12.10, it doesn't really work.

1) When I scan a page, the white blank page disappears so that there is only a 
blank grey area there. If I let it scan, nothing changes and only the grey 
background shows. It must have scanned correctly, however, as if I save as a 
JPEG, it works and the file looks okay.
2) However, if I save instead as a PDF, only a blank white document is saved.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: simple-scan 3.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Sun Dec  9 14:23:31 2012
DriverPackageVersions:
 libsane 1.0.23-0ubuntu1
 libsane-extras N/A
 hplip 3.12.6-3ubuntu4
 hpoj N/A
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-09-30 (69 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120926)
MachineType: Dell Inc. Inspiron 5423
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic 
root=UUID=e8fd1b8e-1837-4efd-8466-e6a803e2f1eb ro quiet splash vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0RMVR3
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/03/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0RMVR3:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 5423
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug quantal running-unity

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

Title:
  Scan doesn't give a preview and only saves in jpeg format

Status in “simple-scan” package in Ubuntu:
  New

Bug description:
  I have used Simple Scan a lot on other machines etc.

  On my new laptop running 12.10, it doesn't really work.

  1) When I scan a page, the white blank page disappears so that there is only 
a blank grey area there. If I let it scan, nothing changes and only the grey 
background shows. It must have scanned correctly, however, as if I save as a 
JPEG, it works and the file looks okay.
  2) However, if I save instead as a PDF, only a blank white document is saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: simple-scan 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sun Dec  9 14:23:31 2012
  DriverPackageVersions:
   libsane 1.0.23-0ubuntu1
   libsane-extras N/A
   hplip 3.12.6-3ubuntu4
   hpoj N/A
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-30 (69 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120926)
  MachineType: Dell Inc. Inspiron 5423
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic 
root=UUID=e8fd1b8e-1837-4efd-8466-e6a803e2f1eb ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0RMVR3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/03/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0RMVR3:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1088187/+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 1088244] [NEW] No Full-Disk Encryption unlock screen from reboot

[Aaron Whitehouse]

Public bug reported:

I use Full-Disk Encryption on 12.10. All seems to work fine if I power
the machine on from a full power off - the pretty screen asks for my
disk unlock password and then takes me to the login screen when I enter
it correctly.

If I reboot the computer instead, it shows a completely blank black
screen. I can type the password in the dark and hit enter and it goes
to the login screen, but it obviously isn't very good from a useability
point of view.

Let me know how I can help.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: lightdm 1.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Sun Dec  9 20:15:36 2012
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-12-09 (0 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
MarkForUpload: True
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug quantal running-unity

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

Title:
  No Full-Disk Encryption unlock screen from reboot

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  I use Full-Disk Encryption on 12.10. All seems to work fine if I power
  the machine on from a full power off - the pretty screen asks for my
  disk unlock password and then takes me to the login screen when I
  enter it correctly.

  If I reboot the computer instead, it shows a completely blank black
  screen. I can type the password in the dark and hit enter and it
  goes to the login screen, but it obviously isn't very good from a
  useability point of view.

  Let me know how I can help.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: lightdm 1.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sun Dec  9 20:15:36 2012
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-12-09 (0 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1088244/+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 1088244] Re: No Full-Disk Encryption unlock screen from reboot

[Aaron Whitehouse]

Okay, I just had this happen to me after shutting down, so it seems to
just be random whether it works or not.

** Summary changed:

- No Full-Disk Encryption unlock screen from reboot
+ No Full-Disk Encryption unlock screen on some boots

** Description changed:

- I use Full-Disk Encryption on 12.10. All seems to work fine if I power
- the machine on from a full power off - the pretty screen asks for my
- disk unlock password and then takes me to the login screen when I enter
- it correctly.
+ I use Full-Disk Encryption on 12.10. All seems to work fine sometimes -
+ the pretty screen asks for my disk unlock password and then takes me to
+ the login screen when I enter it correctly.
  
- If I reboot the computer instead, it shows a completely blank black
- screen. I can type the password in the dark and hit enter and it goes
- to the login screen, but it obviously isn't very good from a useability
- point of view.
+ Other times, it shows a completely blank black screen. I can type the
+ password in the dark and hit enter and it goes to the login screen,
+ but it obviously isn't very good from a usability point of view.
  
  Let me know how I can help.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: lightdm 1.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sun Dec  9 20:15:36 2012
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-12-09 (0 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  No Full-Disk Encryption unlock screen on some boots

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  I use Full-Disk Encryption on 12.10. All seems to work fine sometimes
  - the pretty screen asks for my disk unlock password and then takes me
  to the login screen when I enter it correctly.

  Other times, it shows a completely blank black screen. I can type the
  password in the dark and hit enter and it goes to the login screen,
  but it obviously isn't very good from a usability point of view.

  Let me know how I can help.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: lightdm 1.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sun Dec  9 20:15:36 2012
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-12-09 (0 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1088244/+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 1088244] Re: No Full-Disk Encryption unlock screen on some boots

[Aaron Whitehouse]

Description changed so that it no longer says this happens on reboot and
not on a cold start.

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

Title:
  No Full-Disk Encryption unlock screen on some boots

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  I use Full-Disk Encryption on 12.10. All seems to work fine sometimes
  - the pretty screen asks for my disk unlock password and then takes me
  to the login screen when I enter it correctly.

  Other times, it shows a completely blank black screen. I can type the
  password in the dark and hit enter and it goes to the login screen,
  but it obviously isn't very good from a usability point of view.

  Let me know how I can help.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: lightdm 1.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sun Dec  9 20:15:36 2012
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-12-09 (0 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1088244/+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