[Desktop-packages] [Bug 1959508] Re: enable BMFF support in exiv2

[Damon Lynch]

I can confirm CR3 support is not enabled in exiv2 0.27.5-1. It very much
appears the steps outlined by Robin Mills (aka clanmills) have not been
undertaken by the Debian packager.

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

Title:
  enable BMFF support in exiv2

Status in exiv2 package in Ubuntu:
  Incomplete
Status in exiv2 package in Debian:
  Fix Released

Bug description:
  On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that
  Ubuntu 22.04 currently includes exiv2 0.27.3

  Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3
  file format has been the Canon camera-raw file format since mid 2018,
  and is probably one of the most common raw image file formats today.
  Applications such as darktable, amongst others, use exiv2 to extract
  image metadata, thumbnails and previews, and can only open CR3 files
  when linked with exiv2 0.27.5 or later.

  Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On
  to enable *.CR3 support.

  Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled
  included in Ubuntu 22.04?

  Note that a similar request exists for Debian in
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788

  References
  https://github.com/exiv2/exiv2#2-19
  https://github.com/Exiv2/exiv2/issues/1229
  https://github.com/darktable-org/darktable/pull/10332
  https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918
  https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+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 1762222] Re: will not mount or read card in camera

[Damon Lynch]

You are using a version that is years old. Update to the newest version.
You can do that by either installing it from
http://damonlynch.net/rapid/download.html , or waiting until 18.04 is
released and installing the version found in that in release.

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

Title:
  will not mount or read card in camera

Status in rapid-photo-downloader package in Ubuntu:
  New

Bug description:
  james@james-desktop-ubuntu:~$ rapid-photo-downloader --debug
  [INFO/MainProcess] Rapid Photo Downloader 0.4.11
  [INFO/MainProcess] Using pyexiv2 0.3.2
  [INFO/MainProcess] Using exiv2 0.25.0
  [INFO/MainProcess] Using exiftool 10.10
  [INFO/MainProcess] Using hachoir 1.3.3
  [INFO/MainProcess] No downloads have occurred so far today
  [INFO/MainProcess] allocating a new mmap of length 4096
  [DEBUG/MainProcess] created semlock with handle 140253754241024
  [DEBUG/MainProcess] created semlock with handle 140253754208256
  [DEBUG/MainProcess] created semlock with handle 140253754175488
  [DEBUG/MainProcess] created semlock with handle 140253754142720
  [DEBUG/MainProcess] created semlock with handle 140253754109952
  [DEBUG/MainProcess] created semlock with handle 140253753290752
  [DEBUG/MainProcess] created semlock with handle 140253753257984
  [DEBUG/MainProcess] created semlock with handle 140253753225216
  [DEBUG/MainProcess] _set_from_toolbar_state
  [INFO/GetPreviewImage-1] child process calling self.run()
  [DEBUG/MainProcess] Start of day is set to 3:0
  [DEBUG/MainProcess] SubfolderFile PID: 23464
  [INFO/MainProcess] Using manually specified path /media/james/PMHOME
  [INFO/MainProcess] # photo backup devices: 0; # video backup devices: 0
  [INFO/SubfolderFile-2] child process calling self.run()
  [DEBUG/MainProcess] Working with 1 devices
  [DEBUG/MainProcess] Starting a device scan for device /media/james/PMHOME
  [DEBUG/MainProcess] created semlock with handle 140253432197120
  [DEBUG/MainProcess] created semlock with handle 140253432164352
  [DEBUG/MainProcess] created semlock with handle 140253432131584
  [DEBUG/MainProcess] Queue._after_fork()
  [DEBUG/MainProcess] created semlock with handle 140253347196928
  [DEBUG/MainProcess] created semlock with handle 140253347164160
  [DEBUG/MainProcess] created semlock with handle 140253347131392
  [DEBUG/MainProcess] created semlock with handle 140253347098624
  [DEBUG/MainProcess] created semlock with handle 140253347065856
  [DEBUG/Scan-3] Queue._after_fork()
  [DEBUG/MainProcess] TaskManager PID: 23465
  [INFO/Scan-3] child process calling self.run()
  [INFO/Scan-3] process shutting down
  [DEBUG/Scan-3] running all "atexit" finalizers with priority >= 0
  [DEBUG/Scan-3] running the remaining "atexit" finalizers
  [INFO/Scan-3] process exiting with exitcode 0
  [INFO/MainProcess] Found 0 photos or videos
  [INFO/MainProcess] Files total 
  [DEBUG/MainProcess] Turning on display of thumbnails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rapid-photo-downloader/+bug/176/+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 1702579] [NEW] nautilus crashed with SIGSEGV in g_type_check_instance_is_a()

[Damon Lynch]

Public bug reported:

As nautilus was thumbnailing photos and videos on a Nexus 5X connected
via PTP, I right clicked in the file browser close or possibly on a file
name of one of files that did not yet have a thumbnail generated. It was
at that point that nautilus crashed.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.24.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Wed Jul  5 17:40:09 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-05-16 (50 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170511)
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f934721a811 :  testb  
$0x4,0x16(%rax)
 PC (0x7f934721a811) ok
 source "$0x4" ok
 destination "0x16(%rax)" (0x3a3a737365636376) not located in a known VMA 
region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_is_a () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 gnome_desktop_thumbnail_factory_generate_thumbnail () at 
/usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12
 ()
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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


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

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV in g_type_check_instance_is_a()

Status in nautilus package in Ubuntu:
  New

Bug description:
  As nautilus was thumbnailing photos and videos on a Nexus 5X connected
  via PTP, I right clicked in the file browser close or possibly on a
  file name of one of files that did not yet have a thumbnail generated.
  It was at that point that nautilus crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Jul  5 17:40:09 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-05-16 (50 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170511)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f934721a811 :
testb  $0x4,0x16(%rax)
   PC (0x7f934721a811) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x3a3a737365636376) not located in a known VMA 
region (needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   g_type_check_instance_is_a () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gnome_desktop_thumbnail_factory_generate_thumbnail () at 
/usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12
   ()
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1702579/+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 1653323] Re: Severe screen flicker on Unity when terminal maximized

[Damon Lynch]

Appears to be fixed as of 4.10.0-19-generic. I'm relieved!

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

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

Title:
  Severe screen flicker on Unity  when terminal maximized

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  The screen experiences severe flicker when using Nvidia 375.26 on a
  GTX 1070 in 16.10, Unity Desktop -- but only when the terminal is in
  the top left of the screen or maximized, and is full of text.

  I made a video illustrating the problem: http://damonlynch.net/share
  /Ubuntu1610screen-flicker.mp4

  Driver is from the "graphics-drivers" PPA.

  At this point I don't know if it's a hardware problem or software
  problem -- I've never seen anything like it before. I've ruled out the
  DisplayPort cable as a problem, because it exhibits the same problem
  with two different cables.

  The LCD is a Dell UP3017.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.26  Thu Dec  8 18:36:43 
PST 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 340580/915712 files, 2047147/3661865 blocks
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Dec 30 23:05:25 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-30-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2016-10-09 (82 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=b2cca22d-b1af-498e-84e2-4f06fd41880d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd03/01/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  

[Desktop-packages] [Bug 1653323] Re: Severe screen flicker on Unity when terminal maximized

[Damon Lynch]

I just tried the nouveau driver in 4.9.0-11-generic. Now while it didn't
flicker, what it did do was exhibit the very start of the problem, which
manifests as subtle vertical bars in the top panel's dark brown bar. So
it may not be an Nvidia problem, but a kernel problem, that may have
been fixed in 4.10.

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

Title:
  Severe screen flicker on Unity  when terminal maximized

Status in xorg package in Ubuntu:
  New

Bug description:
  The screen experiences severe flicker when using Nvidia 375.26 on a
  GTX 1070 in 16.10, Unity Desktop -- but only when the terminal is in
  the top left of the screen or maximized, and is full of text.

  I made a video illustrating the problem: http://damonlynch.net/share
  /Ubuntu1610screen-flicker.mp4

  Driver is from the "graphics-drivers" PPA.

  At this point I don't know if it's a hardware problem or software
  problem -- I've never seen anything like it before. I've ruled out the
  DisplayPort cable as a problem, because it exhibits the same problem
  with two different cables.

  The LCD is a Dell UP3017.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.26  Thu Dec  8 18:36:43 
PST 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 340580/915712 files, 2047147/3661865 blocks
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Dec 30 23:05:25 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-30-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2016-10-09 (82 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=b2cca22d-b1af-498e-84e2-4f06fd41880d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd03/01/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 

[Desktop-packages] [Bug 1653323] Re: Severe screen flicker on Unity when terminal maximized

[Damon Lynch]

Running the mainline kernel 4.10-rc2 and the nouveau driver on 17.04
means the bug does not appear; it does appear with the Nvidia 375 driver
in the regular 17.04 kernel. The 4.10-rc2 kernel is significant because
in the 4.9 and earlier kernels, the mouse cursor does not move from the
top left corner of the screen.

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

Title:
  Severe screen flicker on Unity  when terminal maximized

Status in xorg package in Ubuntu:
  New

Bug description:
  The screen experiences severe flicker when using Nvidia 375.26 on a
  GTX 1070 in 16.10, Unity Desktop -- but only when the terminal is in
  the top left of the screen or maximized, and is full of text.

  I made a video illustrating the problem: http://damonlynch.net/share
  /Ubuntu1610screen-flicker.mp4

  Driver is from the "graphics-drivers" PPA.

  At this point I don't know if it's a hardware problem or software
  problem -- I've never seen anything like it before. I've ruled out the
  DisplayPort cable as a problem, because it exhibits the same problem
  with two different cables.

  The LCD is a Dell UP3017.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.26  Thu Dec  8 18:36:43 
PST 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 340580/915712 files, 2047147/3661865 blocks
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Dec 30 23:05:25 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-30-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2016-10-09 (82 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=b2cca22d-b1af-498e-84e2-4f06fd41880d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd03/01/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: 

[Desktop-packages] [Bug 1653323] Re: Severe screen flicker on Unity when terminal maximized

[Damon Lynch]

Taking a full-screen screenshot of the problematic view (i.e. with a
maximized terminal window full of text), and then viewing the screenshot
at full screen, is displayed fine.

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

Title:
  Severe screen flicker on Unity  when terminal maximized

Status in xorg package in Ubuntu:
  New

Bug description:
  The screen experiences severe flicker when using Nvidia 375.26 on a
  GTX 1070 in 16.10, Unity Desktop -- but only when the terminal is in
  the top left of the screen or maximized, and is full of text.

  I made a video illustrating the problem: http://damonlynch.net/share
  /Ubuntu1610screen-flicker.mp4

  Driver is from the "graphics-drivers" PPA.

  At this point I don't know if it's a hardware problem or software
  problem -- I've never seen anything like it before. I've ruled out the
  DisplayPort cable as a problem, because it exhibits the same problem
  with two different cables.

  The LCD is a Dell UP3017.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.26  Thu Dec  8 18:36:43 
PST 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 340580/915712 files, 2047147/3661865 blocks
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Dec 30 23:05:25 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-30-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2016-10-09 (82 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=b2cca22d-b1af-498e-84e2-4f06fd41880d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd03/01/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  

[Desktop-packages] [Bug 1653323] [NEW] Severe screen flicker on Unity when terminal maximized

[Damon Lynch]

Public bug reported:

The screen experiences severe flicker when using Nvidia 375.26 on a GTX
1070 in 16.10, Unity Desktop -- but only when the terminal is in the top
left of the screen or maximized, and is full of text.

I made a video illustrating the problem: http://damonlynch.net/share
/Ubuntu1610screen-flicker.mp4

Driver is from the "graphics-drivers" PPA.

At this point I don't know if it's a hardware problem or software
problem -- I've never seen anything like it before. I've ruled out the
DisplayPort cable as a problem, because it exhibits the same problem
with two different cables.

The LCD is a Dell UP3017.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.26  Thu Dec  8 18:36:43 
PST 2016
 GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
BootLog: /dev/sda6: clean, 340580/915712 files, 2047147/3661865 blocks
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Dec 30 23:05:25 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
 bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
 nvidia-375, 375.26, 4.8.0-30-generic, x86_64: installed
 nvidia-375, 375.26, 4.8.0-32-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
 NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701]
InstallationDate: Installed on 2016-10-09 (82 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
MachineType: Gigabyte Technology Co., Ltd. Z170X-UD3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=b2cca22d-b1af-498e-84e2-4f06fd41880d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/01/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170X-UD3-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd03/01/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z170X-UD3
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Fri Dec 30 18:46:35 2016
xserver.configfile: default
xserver.errors:
 modeset(G0): eglInitialize() failed
 modeset(G0): glamor initialization failed
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-1ubuntu6.1

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


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

-- 
You received 

[Desktop-packages] [Bug 1630013] [NEW] glxinfo infinite loop, no live image desktop login

[Damon Lynch]

Public bug reported:

On today's Yakkety Yak daily image I'm running into an infinite loop
with glxinfo such that no desktop shows on login. The desktop is black
(no cursor) and logging in via a console shows glxinfo running at 100%.

Package version info according to packages.ubuntu.com is 1:1.0.12-2.

My apologies but this bug report has been submitted manually because I
could not install Yakkety Yak due to this bug. I'm running an encrypted
/home and must be able to install from the live image desktop with /home
already mounted.

Hardware: Quadro 1000M (Fermi) on a Lenovo W520 (Sandy Bridge quad
core).

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: iso-testing yakkety

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

Title:
  glxinfo infinite loop, no live image desktop login

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  On today's Yakkety Yak daily image I'm running into an infinite loop
  with glxinfo such that no desktop shows on login. The desktop is black
  (no cursor) and logging in via a console shows glxinfo running at
  100%.

  Package version info according to packages.ubuntu.com is 1:1.0.12-2.

  My apologies but this bug report has been submitted manually because I
  could not install Yakkety Yak due to this bug. I'm running an
  encrypted /home and must be able to install from the live image
  desktop with /home already mounted.

  Hardware: Quadro 1000M (Fermi) on a Lenovo W520 (Sandy Bridge quad
  core).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1630013/+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 1074028] Re: Port all pyexiv2 apps to GExiv2

[Damon Lynch]

** Changed in: rapid/pyqt
Milestone: None => 0.9.0a1

** Changed in: rapid/pyqt
   Status: Fix Committed => Fix Released

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

Title:
  Port all pyexiv2 apps to GExiv2

Status in Gramps:
  Fix Released
Status in Nautilus Image Manipulator:
  Fix Released
Status in pyexiv2:
  Fix Committed
Status in Rapid Photo Downloader:
  Fix Released
Status in Rapid Photo Downloader pyqt series:
  Fix Released
Status in SmartShine Photo:
  Fix Committed
Status in creepy package in Ubuntu:
  Fix Released
Status in flickrbackup package in Ubuntu:
  Fix Committed
Status in gexiv2 package in Ubuntu:
  Fix Released
Status in gramps package in Ubuntu:
  Fix Released
Status in lazygal package in Ubuntu:
  Fix Released
Status in phatch package in Ubuntu:
  Triaged
Status in videoporama package in Ubuntu:
  Won't Fix

Bug description:
  I have spoken directly with the maintainer of pyexiv2 and we have
  agreed that pyexiv2 is an abandoned project that will never support
  Python3. Therefore, anything that depends on pyexiv2 is going to be
  stuck on Python 2 until they port to GExiv2. GExiv2 is a clear winner
  in terms of simplicity, and maintainability.

  Packages marked as affected by this bug were designated so because
  they have a dependency on the pyexiv2 package. They will need to be
  ported to GExiv2 before they can be ported to Python 3. Here is the
  popcon data for these packages, which may hopefully allow us to
  prioritize this work by installation popularity:

  #rank nameinst  vote   old recent no-files
  6692  gramps 41836   534 41095   198 9
  8296  phatch-cli 26266   734 25209   30914
  13025 videoporama 8766   120  860239 5
  16897 rapid-photo-downloader  4683   174  440397 9
  19941 nautilus-image-manipulator  3054   164  281673 1
  35392 creepy   59111   56317 0
  36572 lazygal  53411   522 1 0
  65688 smartshine60 522 627
  78375 flickrbackup  26 125 0 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gramps/+bug/1074028/+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 1074028] Re: Port all pyexiv2 apps to GExiv2

[Damon Lynch]

** Also affects: rapid/pyqt
   Importance: High
 Assignee: Damon Lynch (dlynch3)
   Status: Fix Committed

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

Title:
  Port all pyexiv2 apps to GExiv2

Status in Gramps:
  Fix Released
Status in Nautilus Image Manipulator:
  Fix Released
Status in pyexiv2:
  Fix Committed
Status in Rapid Photo Downloader:
  Fix Committed
Status in Rapid Photo Downloader pyqt series:
  Fix Committed
Status in SmartShine Photo:
  Fix Committed
Status in creepy package in Ubuntu:
  Fix Released
Status in flickrbackup package in Ubuntu:
  Fix Committed
Status in gexiv2 package in Ubuntu:
  Fix Released
Status in gramps package in Ubuntu:
  Fix Released
Status in lazygal package in Ubuntu:
  Fix Released
Status in phatch package in Ubuntu:
  Triaged
Status in videoporama package in Ubuntu:
  Won't Fix

Bug description:
  I have spoken directly with the maintainer of pyexiv2 and we have
  agreed that pyexiv2 is an abandoned project that will never support
  Python3. Therefore, anything that depends on pyexiv2 is going to be
  stuck on Python 2 until they port to GExiv2. GExiv2 is a clear winner
  in terms of simplicity, and maintainability.

  Packages marked as affected by this bug were designated so because
  they have a dependency on the pyexiv2 package. They will need to be
  ported to GExiv2 before they can be ported to Python 3. Here is the
  popcon data for these packages, which may hopefully allow us to
  prioritize this work by installation popularity:

  #rank nameinst  vote   old recent no-files
  6692  gramps 41836   534 41095   198 9
  8296  phatch-cli 26266   734 25209   30914
  13025 videoporama 8766   120  860239 5
  16897 rapid-photo-downloader  4683   174  440397 9
  19941 nautilus-image-manipulator  3054   164  281673 1
  35392 creepy   59111   56317 0
  36572 lazygal  53411   522 1 0
  65688 smartshine60 522 627
  78375 flickrbackup  26 125 0 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gramps/+bug/1074028/+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 1074028] Re: Port all pyexiv2 apps to GExiv2

[Damon Lynch]

** Branch linked: lp:rapid

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

Title:
  Port all pyexiv2 apps to GExiv2

Status in Gramps:
  Fix Released
Status in Nautilus Image Manipulator:
  Fix Released
Status in pyexiv2:
  Fix Committed
Status in Rapid Photo Downloader:
  Fix Committed
Status in SmartShine Photo:
  Fix Committed
Status in creepy package in Ubuntu:
  Fix Released
Status in flickrbackup package in Ubuntu:
  Fix Committed
Status in gexiv2 package in Ubuntu:
  Fix Released
Status in gramps package in Ubuntu:
  Fix Released
Status in lazygal package in Ubuntu:
  Fix Released
Status in phatch package in Ubuntu:
  Triaged
Status in videoporama package in Ubuntu:
  Won't Fix

Bug description:
  I have spoken directly with the maintainer of pyexiv2 and we have
  agreed that pyexiv2 is an abandoned project that will never support
  Python3. Therefore, anything that depends on pyexiv2 is going to be
  stuck on Python 2 until they port to GExiv2. GExiv2 is a clear winner
  in terms of simplicity, and maintainability.

  Packages marked as affected by this bug were designated so because
  they have a dependency on the pyexiv2 package. They will need to be
  ported to GExiv2 before they can be ported to Python 3. Here is the
  popcon data for these packages, which may hopefully allow us to
  prioritize this work by installation popularity:

  #rank nameinst  vote   old recent no-files
  6692  gramps 41836   534 41095   198 9
  8296  phatch-cli 26266   734 25209   30914
  13025 videoporama 8766   120  860239 5
  16897 rapid-photo-downloader  4683   174  440397 9
  19941 nautilus-image-manipulator  3054   164  281673 1
  35392 creepy   59111   56317 0
  36572 lazygal  53411   522 1 0
  65688 smartshine60 522 627
  78375 flickrbackup  26 125 0 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gramps/+bug/1074028/+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 1524746] Re: Rapid-Photo-Downloader stalled

[Damon Lynch]

Hi, I'm the developer of Rapid Photo Downloader. You're better off
reporting your bug here:

https://bugs.launchpad.net/rapid

Furthermore, to make the bug report more useful, do this:

1. open a terminal window
2.  run this: rapid-photo-downloader --debug
3. copy and paste the terminal output into your bug report

Thanks
Damon

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

Title:
  Rapid-Photo-Downloader stalled

Status in rapid-photo-downloader package in Ubuntu:
  New

Bug description:
  After download, RPD remains with the "pause" buton, and a message 3sec
  remainings, but it never ends.

  3 zombies

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: rapid-photo-downloader 0.4.10-3
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Dec 10 12:33:38 2015
  InstallationDate: Installed on 2015-05-29 (195 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  PackageArchitecture: all
  SourcePackage: rapid-photo-downloader
  UpgradeStatus: Upgraded to wily on 2015-11-21 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rapid-photo-downloader/+bug/1524746/+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 1074028] Re: Port all pyexiv2 apps to GExiv2

[Damon Lynch]

** Changed in: rapid
   Status: In Progress = Fix Committed

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

Title:
  Port all pyexiv2 apps to GExiv2

Status in Gramps:
  Fix Released
Status in Nautilus Image Manipulator:
  Fix Released
Status in pyexiv2:
  Fix Committed
Status in Rapid Photo Downloader:
  Fix Committed
Status in SmartShine Photo:
  Fix Committed
Status in creepy package in Ubuntu:
  Fix Released
Status in flickrbackup package in Ubuntu:
  Fix Committed
Status in gexiv2 package in Ubuntu:
  Fix Released
Status in gramps package in Ubuntu:
  Fix Released
Status in lazygal package in Ubuntu:
  Fix Released
Status in phatch package in Ubuntu:
  Triaged
Status in videoporama package in Ubuntu:
  Won't Fix

Bug description:
  I have spoken directly with the maintainer of pyexiv2 and we have
  agreed that pyexiv2 is an abandoned project that will never support
  Python3. Therefore, anything that depends on pyexiv2 is going to be
  stuck on Python 2 until they port to GExiv2. GExiv2 is a clear winner
  in terms of simplicity, and maintainability.

  Packages marked as affected by this bug were designated so because
  they have a dependency on the pyexiv2 package. They will need to be
  ported to GExiv2 before they can be ported to Python 3. Here is the
  popcon data for these packages, which may hopefully allow us to
  prioritize this work by installation popularity:

  #rank nameinst  vote   old recent no-files
  6692  gramps 41836   534 41095   198 9
  8296  phatch-cli 26266   734 25209   30914
  13025 videoporama 8766   120  860239 5
  16897 rapid-photo-downloader  4683   174  440397 9
  19941 nautilus-image-manipulator  3054   164  281673 1
  35392 creepy   59111   56317 0
  36572 lazygal  53411   522 1 0
  65688 smartshine60 522 627
  78375 flickrbackup  26 125 0 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gramps/+bug/1074028/+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 1074028] Re: Port all pyexiv2 apps to GExiv2

[Damon Lynch]

** Changed in: rapid
   Importance: Undecided = High

** Changed in: rapid
   Status: Confirmed = In Progress

** Changed in: rapid
 Assignee: (unassigned) = Damon Lynch (dlynch3)

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

Title:
  Port all pyexiv2 apps to GExiv2

Status in Genealogical Research and Analysis Management Programming System:
  Fix Released
Status in Nautilus Image Manipulator:
  Fix Released
Status in pyexiv2, a python binding to exiv2:
  Fix Committed
Status in Rapid Photo Downloader:
  In Progress
Status in SmartShine - automation for the photographers:
  Fix Committed
Status in creepy package in Ubuntu:
  Fix Released
Status in flickrbackup package in Ubuntu:
  Fix Committed
Status in gexiv2 package in Ubuntu:
  Fix Released
Status in gramps package in Ubuntu:
  Fix Released
Status in lazygal package in Ubuntu:
  Fix Released
Status in phatch package in Ubuntu:
  Triaged
Status in videoporama package in Ubuntu:
  Won't Fix

Bug description:
  I have spoken directly with the maintainer of pyexiv2 and we have
  agreed that pyexiv2 is an abandoned project that will never support
  Python3. Therefore, anything that depends on pyexiv2 is going to be
  stuck on Python 2 until they port to GExiv2. GExiv2 is a clear winner
  in terms of simplicity, and maintainability.

  Packages marked as affected by this bug were designated so because
  they have a dependency on the pyexiv2 package. They will need to be
  ported to GExiv2 before they can be ported to Python 3. Here is the
  popcon data for these packages, which may hopefully allow us to
  prioritize this work by installation popularity:

  #rank nameinst  vote   old recent no-files
  6692  gramps 41836   534 41095   198 9
  8296  phatch-cli 26266   734 25209   30914
  13025 videoporama 8766   120  860239 5
  16897 rapid-photo-downloader  4683   174  440397 9
  19941 nautilus-image-manipulator  3054   164  281673 1
  35392 creepy   59111   56317 0
  36572 lazygal  53411   522 1 0
  65688 smartshine60 522 627
  78375 flickrbackup  26 125 0 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gramps/+bug/1074028/+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 1431179] Re: USB 4G modem detected as USB mass storage

[Damon Lynch]

$ systemctl status -l usb_modeswitch@-3-1.2:1.0.service
● usb_modeswitch@-3-1.2:1.0.service - USB_ModeSwitch
   Loaded: loaded (/lib/systemd/system/usb_modeswitch@.service; static; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Thu 2015-03-12 12:34:56 TJT; 1min 
5s ago
  Process: 892 ExecStart=/usr/sbin/usb_modeswitch_dispatcher --switch-systemd 
%I (code=exited, status=1/FAILURE)
 Main PID: 892 (code=exited, status=1/FAILURE)

Mar 12 12:34:56 damon-W520 systemd[1]: Starting USB_ModeSwitch...
Mar 12 12:34:56 damon-W520 systemd[1]: usb_modeswitch@-3-1.2:1.0.service: main 
process exited, code=exited, status=1/FAILURE
Mar 12 12:34:56 damon-W520 systemd[1]: Failed to start USB_ModeSwitch.
Mar 12 12:34:56 damon-W520 systemd[1]: Unit usb_modeswitch@-3-1.2:1.0.service 
entered failed state.
Mar 12 12:34:56 damon-W520 systemd[1]: usb_modeswitch@-3-1.2:1.0.service failed.


** Attachment added: Requested udev output before manual modem start
   
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1431179/+attachment/4342361/+files/udev.txt

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

Title:
  USB 4G modem detected as USB mass storage

Status in usb-modeswitch package in Ubuntu:
  Incomplete

Bug description:
  I lack the technical knowledge to know if this is a bug in udev,
  systemd or another component.

  After the switch to systemd, my 4G Huawei USB modem  no longer
  functions as a modem unless I run usb_modeswitch to flip its state
  from USB mass storage. The command I issue and its output is below,
  which also show the Vendor and Product ID.

  Strangely, it does not do this every time. Yesterday when I updated
  using apt-get dist-upgrade upon reboot the modem worked as expected.
  But from a cold boot this morning it did not.

  $ sudo usb_modeswitch -v 0x12d1 -p 0x1f01 -J
  [sudo] password for damon: 
  Look for default devices ...
 product ID matched
   Found devices in default mode (1)
  Access device 003 on bus 003
  Current configuration number is 1
  Use interface number 0
  Use endpoints 0x01 (out) and 0x81 (in)

  USB description data (for identification)
  -
  Manufacturer: HUAWEI Technology
   Product: HUAWEI Mobile
Serial No.: 
  -
  Using standard Huawei switching message
  Looking for active driver ...
   OK, driver detached
  Set up interface 0
  Use endpoint 0x01 for message sending ...
  Trying to send message 1 to endpoint 0x01 ...
   OK, message successfully sent
  Reset response endpoint 0x81
   Could not reset endpoint (probably harmless): -99
  Reset message endpoint 0x01
   Could not reset endpoint (probably harmless): -99
   Device is gone, skip any further commands
  - Run lsusb to note any changes. Bye!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 219-4ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Thu Mar 12 11:37:06 2015
  InstallationDate: Installed on 2015-02-05 (34 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20150205)
  MachineType: LENOVO 427637U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic 
root=UUID=eb18ef51-a2d0-4372-8eb9-ae009a05d4f6 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8BET62WW (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 427637U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8BET62WW(1.42):bd07/26/2013:svnLENOVO:pn427637U:pvrThinkPadW520:rvnLENOVO:rn427637U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 427637U
  dmi.product.version: ThinkPad W520
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1431179/+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 1431179] Re: usb_modeswitch@.service fails sometimes

[Damon Lynch]

@pitti command output as requested

** Attachment added: usb_modeswitch_output.txt
   
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1431179/+attachment/4342405/+files/usb_modeswitch_output.txt

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

Title:
  usb_modeswitch@.service fails sometimes

Status in usb-modeswitch package in Ubuntu:
  Incomplete

Bug description:
  I lack the technical knowledge to know if this is a bug in udev,
  systemd or another component.

  After the switch to systemd, my 4G Huawei USB modem  no longer
  functions as a modem unless I run usb_modeswitch to flip its state
  from USB mass storage. The command I issue and its output is below,
  which also show the Vendor and Product ID.

  Strangely, it does not do this every time. Yesterday when I updated
  using apt-get dist-upgrade upon reboot the modem worked as expected.
  But from a cold boot this morning it did not.

  $ sudo usb_modeswitch -v 0x12d1 -p 0x1f01 -J
  [sudo] password for damon: 
  Look for default devices ...
 product ID matched
   Found devices in default mode (1)
  Access device 003 on bus 003
  Current configuration number is 1
  Use interface number 0
  Use endpoints 0x01 (out) and 0x81 (in)

  USB description data (for identification)
  -
  Manufacturer: HUAWEI Technology
   Product: HUAWEI Mobile
Serial No.: 
  -
  Using standard Huawei switching message
  Looking for active driver ...
   OK, driver detached
  Set up interface 0
  Use endpoint 0x01 for message sending ...
  Trying to send message 1 to endpoint 0x01 ...
   OK, message successfully sent
  Reset response endpoint 0x81
   Could not reset endpoint (probably harmless): -99
  Reset message endpoint 0x01
   Could not reset endpoint (probably harmless): -99
   Device is gone, skip any further commands
  - Run lsusb to note any changes. Bye!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 219-4ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Thu Mar 12 11:37:06 2015
  InstallationDate: Installed on 2015-02-05 (34 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20150205)
  MachineType: LENOVO 427637U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic 
root=UUID=eb18ef51-a2d0-4372-8eb9-ae009a05d4f6 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8BET62WW (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 427637U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8BET62WW(1.42):bd07/26/2013:svnLENOVO:pn427637U:pvrThinkPadW520:rvnLENOVO:rn427637U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 427637U
  dmi.product.version: ThinkPad W520
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1431179/+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 1066265] Re: crashes when downloading photos (ubuntu 12.10)

[Damon Lynch]

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

** This bug has been marked a duplicate of bug 1025908
   Application freezes under Ubuntu 12.10, Fedora 18 and other recent releases

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

Title:
  crashes when downloading photos (ubuntu 12.10)

Status in “rapid-photo-downloader” package in Ubuntu:
  Confirmed

Bug description:
  gui turns grey and freezes, running from terminal yields no
  interesting information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rapid-photo-downloader/+bug/1066265/+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 1289975] [NEW] Sync package request from Debian with critical bug fix

[Damon Lynch]

Public bug reported:

Debian Unstable has been updated to the latest upstream version.
Compared to the version in Universe, the updated package contains a
critical bug fix for bug #1025908, as well as other bug fixes,
translation updates and a minor new feature.

https://packages.debian.org/source/unstable/rapid-photo-downloader

The upstream Changelog diff compared to the version in Universe:

Version 0.4.10
--

2014-02-23

Updated Catalan and Portuguese translations.

Fixed bug in translations for term Back up.


Version 0.4.9
-

2014-01-21

Updated Catalan and Spanish translations.

Fixed occasional incorrect use of term backup.


Version 0.4.9 Beta 3


2014-01-20

Fixed packaging bug.


Version 0.4.9 Beta 2


2014-01-20

Added file verification of downloaded and backed up files.

Updated Dutch, Hungarian, Italian, Polish, Serbian, Spanish and Swedish 
translations. Added Catalan translation.


Version 0.4.9 Beta 1


2014-01-16

Fixed bugs #1025908 and #1186955: Finalize fix for severe performance problems 
and crashes that arose from the combination of Gnome's GIO file functionality 
and python's multiprocessing. The solution was to remove GIO and replace it with
regular python file processing. A nice side effect is that the program now runs
faster than ever before.

Fixed bug #1268291: Handle cases where filesystem metadata (e.g. file 
permissions) could not be copied when writing to certain file systems such as
NTFS. The program will now consider a file is copied succesfully even if the
filesystem metadata could not be updated.

Fixed bug #1269032: When Sync RAW + JPEG sequence numbers is enabled, the 
program fails to properly deal with photos with corrupt EXIF metadata.

Fixed bug #1269079: Download failure when folder exists for only one of photo or
video on auto detected back devices. 

Updated Norwegian and Serbian translations.


Version 0.4.8
-

2013-12-31

Fixed bug #1263237: Added support for MPO files (3D images). Thanks to Jan 
Kaluza for reporting it.

Fixed bug #1263483: Some terms in the user interface are not being translated.
Thanks to Jose Luis Tirado for alerting me to the problem, which has probably 
existed for some time.

Updated Dutch, French Italian, Polish and Spanish translations.

** Affects: rapid-photo-downloader (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Sync package request from Debian with critical bug fix

Status in “rapid-photo-downloader” package in Ubuntu:
  New

Bug description:
  Debian Unstable has been updated to the latest upstream version.
  Compared to the version in Universe, the updated package contains a
  critical bug fix for bug #1025908, as well as other bug fixes,
  translation updates and a minor new feature.

  https://packages.debian.org/source/unstable/rapid-photo-downloader

  The upstream Changelog diff compared to the version in Universe:

  Version 0.4.10
  --

  2014-02-23

  Updated Catalan and Portuguese translations.

  Fixed bug in translations for term Back up.

  
  Version 0.4.9
  -

  2014-01-21

  Updated Catalan and Spanish translations.

  Fixed occasional incorrect use of term backup.

  
  Version 0.4.9 Beta 3
  

  2014-01-20

  Fixed packaging bug.

  
  Version 0.4.9 Beta 2
  

  2014-01-20

  Added file verification of downloaded and backed up files.

  Updated Dutch, Hungarian, Italian, Polish, Serbian, Spanish and Swedish 
  translations. Added Catalan translation.

  
  Version 0.4.9 Beta 1
  

  2014-01-16

  Fixed bugs #1025908 and #1186955: Finalize fix for severe performance 
problems 
  and crashes that arose from the combination of Gnome's GIO file functionality 
  and python's multiprocessing. The solution was to remove GIO and replace it 
with
  regular python file processing. A nice side effect is that the program now 
runs
  faster than ever before.

  Fixed bug #1268291: Handle cases where filesystem metadata (e.g. file 
  permissions) could not be copied when writing to certain file systems such as
  NTFS. The program will now consider a file is copied succesfully even if the
  filesystem metadata could not be updated.

  Fixed bug #1269032: When Sync RAW + JPEG sequence numbers is enabled, the 
  program fails to properly deal with photos with corrupt EXIF metadata.

  Fixed bug #1269079: Download failure when folder exists for only one of photo 
or
  video on auto detected back devices. 

  Updated Norwegian and Serbian translations.

  
  Version 0.4.8
  -

  2013-12-31

  Fixed bug #1263237: Added support for MPO files (3D images). Thanks to Jan 
  Kaluza for reporting it.

  Fixed bug #1263483: Some terms in the 

[Desktop-packages] [Bug 1268119] Re: ICC color profile application lost during login

[Damon Lynch]

Via a BIOS setting my laptop can switch between integrated (intel) and
nvidia graphics. The bug only occurs when running nvidia. I have not
installed the nvidia binary driver.

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

Title:
  ICC color profile application lost during login

Status in “colord” package in Ubuntu:
  Triaged

Bug description:
  I assume colord is the correct package to report this bug against, but
  to be honest I really don't know!

  Symptoms:
  I have an ICC color profile which is not being applied at login. Upon logging 
in, the system (Unity) appears to use it for a second or so, but then something 
happens which results in it being unloaded.  This never happened in Ubuntu 
13.10.

  Workaround:
  Go to system settings, color. Note the correct profile is selected (your 
custom profile). Choose the default (system) profile (i.e. not your custom 
profile), and then again choose the profile that is meant to be used. The 
correct color profile will now be used until logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: colord 1.0.2-1
  ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
  Uname: Linux 3.13.0-1-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Sat Jan 11 17:44:19 2014
  ExecutablePath: /usr/lib/colord/colord
  InstallationDate: Installed on 2014-01-10 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140103)
  ProcEnviron:
   
  SourcePackage: colord
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1268119/+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 1268119] [NEW] ICC color profile application lost during login

[Damon Lynch]

Public bug reported:

I assume colord is the correct package to report this bug against, but
to be honest I really don't know!

Symptoms:
I have an ICC color profile which is not being applied at login. Upon logging 
in, the system (Unity) appears to use it for a second or so, but then something 
happens which results in it being unloaded.  This never happened in Ubuntu 
13.10.

Workaround:
Go to system settings, color. Note the correct profile is selected (your custom 
profile). Choose the default (system) profile (i.e. not your custom profile), 
and then again choose the profile that is meant to be used. The correct color 
profile will now be used until logout.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: colord 1.0.2-1
ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
Uname: Linux 3.13.0-1-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Sat Jan 11 17:44:19 2014
ExecutablePath: /usr/lib/colord/colord
InstallationDate: Installed on 2014-01-10 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140103)
ProcEnviron:
 
SourcePackage: colord
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  ICC color profile application lost during login

Status in “colord” package in Ubuntu:
  New

Bug description:
  I assume colord is the correct package to report this bug against, but
  to be honest I really don't know!

  Symptoms:
  I have an ICC color profile which is not being applied at login. Upon logging 
in, the system (Unity) appears to use it for a second or so, but then something 
happens which results in it being unloaded.  This never happened in Ubuntu 
13.10.

  Workaround:
  Go to system settings, color. Note the correct profile is selected (your 
custom profile). Choose the default (system) profile (i.e. not your custom 
profile), and then again choose the profile that is meant to be used. The 
correct color profile will now be used until logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: colord 1.0.2-1
  ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
  Uname: Linux 3.13.0-1-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Sat Jan 11 17:44:19 2014
  ExecutablePath: /usr/lib/colord/colord
  InstallationDate: Installed on 2014-01-10 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140103)
  ProcEnviron:
   
  SourcePackage: colord
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Desktop-packages] [Bug 1074028] Re: Port all pyexiv2 apps to GExiv2

[Damon Lynch]

I understand for all practical purposes, the introspection bindings depend
on python 3 and GTK 3. Rapid Photo Downloader currently depends on PIL,
which is not yet ported to Python 3. Ripping out PIL, converting to GTK3 +
introspection + python3 seems like a massive undertaking! And all this with
no actual practical end benefit for the user. On the other hand, if gphoto2
has an introspection binding, that would be a benefit, because finally the
user might be able to download from a camera without the nightmare of the
buggy gphoto2/gvfs bindings.


On Tue, Jan 1, 2013 at 4:02 PM, Robert Bruce Park robert.p...@canonical.com
 wrote:

 Porting of Rapid Photo Downloader is blocked because this app is still
 using all the old static gtk/gobject bindings, which conflict with the
 gobject introspection magic that is necessary to import GExiv2. The code
 that implements GExiv2 for rapid photo downloader is largely done, but
 it won't actually run correctly until the rest of rpd gets ported to the
 new introspection bindings.

 ** Changed in: rapid
Status: In Progress = Confirmed

 --
 You received this bug notification because you are subscribed to Rapid
 Photo Downloader.
 https://bugs.launchpad.net/bugs/1074028

 Title:
   Port all pyexiv2 apps to GExiv2

 Status in Nautilus Image Manipulator:
   Fix Committed
 Status in pyexiv2, a python binding to exiv2:
   Triaged
 Status in Rapid Photo Downloader:
   Confirmed
 Status in SmartShine - automation for the photographers:
   Fix Committed
 Status in “creepy” package in Ubuntu:
   Fix Committed
 Status in “flickrbackup” package in Ubuntu:
   Fix Committed
 Status in “gexiv2” package in Ubuntu:
   Triaged
 Status in “gramps” package in Ubuntu:
   Triaged
 Status in “lazygal” package in Ubuntu:
   Fix Committed
 Status in “phatch” package in Ubuntu:
   Triaged
 Status in “pyexiv2” package in Ubuntu:
   Triaged
 Status in “videoporama” package in Ubuntu:
   Triaged

 Bug description:
   I have spoken directly with the maintainer of pyexiv2 and we have
   agreed that pyexiv2 is an abandoned project that will never support
   Python3. Therefore, anything that depends on pyexiv2 is going to be
   stuck on Python 2 until they port to GExiv2. GExiv2 is a clear winner
   in terms of simplicity, and maintainability.

   Packages marked as affected by this bug were designated so because
   they have a dependency on the pyexiv2 package. They will need to be
   ported to GExiv2 before they can be ported to Python 3. Here is the
   popcon data for these packages, which may hopefully allow us to
   prioritize this work by installation popularity:

   #rank nameinst  vote   old recent no-files
   6692  gramps 41836   534 41095   198 9
   8296  phatch-cli 26266   734 25209   30914
   13025 videoporama 8766   120  860239 5
   16897 rapid-photo-downloader  4683   174  440397 9
   19941 nautilus-image-manipulator  3054   164  281673 1
   35392 creepy   59111   56317 0
   36572 lazygal  53411   522 1 0
   65688 smartshine60 522 627
   78375 flickrbackup  26 125 0 0

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/nautilus-image-manipulator/+bug/1074028/+subscriptions



-- 
http://www.damonlynch.net

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

Title:
  Port all pyexiv2 apps to GExiv2

Status in Nautilus Image Manipulator:
  Fix Committed
Status in pyexiv2, a python binding to exiv2:
  Triaged
Status in Rapid Photo Downloader:
  Confirmed
Status in SmartShine - automation for the photographers:
  Fix Committed
Status in “creepy” package in Ubuntu:
  Fix Committed
Status in “flickrbackup” package in Ubuntu:
  Fix Committed
Status in “gexiv2” package in Ubuntu:
  Triaged
Status in “gramps” package in Ubuntu:
  Triaged
Status in “lazygal” package in Ubuntu:
  Fix Committed
Status in “phatch” package in Ubuntu:
  Triaged
Status in “pyexiv2” package in Ubuntu:
  Triaged
Status in “videoporama” package in Ubuntu:
  Triaged

Bug description:
  I have spoken directly with the maintainer of pyexiv2 and we have
  agreed that pyexiv2 is an abandoned project that will never support
  Python3. Therefore, anything that depends on pyexiv2 is going to be
  stuck on Python 2 until they port to GExiv2. GExiv2 is a clear winner
  in terms of simplicity, and maintainability.

  Packages marked as affected by this bug were designated so because
  they have a dependency on the pyexiv2 package. They will need to be
  ported to GExiv2 before they can be ported to Python 3. Here is the
  popcon data for these packages, which may hopefully allow us to
  prioritize this work by 

Re: [Desktop-packages] [Bug 1074028] Re: Port all pyexiv2 apps to GExiv2

[Damon Lynch]

Not having to also move to python 3 does make it easier. I understand that
I would need to completely redo the glade files to move to GTK3 - is that
correct? Based on other projects, the time the transition would take in
hours would be how much? Am I looking at one week of full time work, or
more like 2 weeks, or 4 weeks or more?

I've checked the gphoto2 page, and as yet there are no introspection
bindings for it. The gvfs/libgphoto2 code has been broken since it was
first developed - it works with some cameras, and not at all with others.
It seems the Gnome developers simply do not have access to a sufficient
range of cameras, so any bugs reported are apparently not fixed. Users of
Rapid Photo Downloader blame my program, of course! There is no python
binding to libgphoto2. I guess the Shotwell developers wrote their own
wrapper code for vala.


On Tue, Jan 1, 2013 at 4:46 PM, Robert Bruce Park robert.p...@canonical.com
 wrote:

 No, the introspection code has been carefully constructed to work
 excellently with both python 2 and python 3. The static bindings only
 support python 2, so sticking with the static bindings is holding you
 back. Porting to introspection doesn't force you to also port to python
 3 immediately, what it does is *allows* you to port to Python 3 at your
 leisure.

 The benefit to your users is that your application will continue to
 exist. Python 2 and GTK 2 are going away. Sure, it might be years before
 they're truly gone, but it will happen eventually. Imagine for a moment
 if your application only ran with Python 1 and GTK 1. Nobody would even
 be able to run it because nobody packages those old versions anymore.
 They're unsupported, unmaintained, and if you found a bug in the APIs,
 it would simply never get fixed. Python 2 and GTK 2 are slowly moving in
 that direction and if you don't port away from them, users will
 eventually lose the ability to run your program as distros stop shipping
 those versions.

 I am not familiar with gphoto2 specifically, but yes, the introspection
 bindings are well maintained and if you find bugs in them, you can
 reasonably expect to report those and get them fixed. So yes, you'll be
 able to get away from the 'nightmare' of unmaintained, buggy bindings.

 --
 You received this bug notification because you are subscribed to Rapid
 Photo Downloader.
 https://bugs.launchpad.net/bugs/1074028

 Title:
   Port all pyexiv2 apps to GExiv2

 Status in Nautilus Image Manipulator:
   Fix Committed
 Status in pyexiv2, a python binding to exiv2:
   Triaged
 Status in Rapid Photo Downloader:
   Confirmed
 Status in SmartShine - automation for the photographers:
   Fix Committed
 Status in “creepy” package in Ubuntu:
   Fix Committed
 Status in “flickrbackup” package in Ubuntu:
   Fix Committed
 Status in “gexiv2” package in Ubuntu:
   Triaged
 Status in “gramps” package in Ubuntu:
   Triaged
 Status in “lazygal” package in Ubuntu:
   Fix Committed
 Status in “phatch” package in Ubuntu:
   Triaged
 Status in “pyexiv2” package in Ubuntu:
   Triaged
 Status in “videoporama” package in Ubuntu:
   Triaged

 Bug description:
   I have spoken directly with the maintainer of pyexiv2 and we have
   agreed that pyexiv2 is an abandoned project that will never support
   Python3. Therefore, anything that depends on pyexiv2 is going to be
   stuck on Python 2 until they port to GExiv2. GExiv2 is a clear winner
   in terms of simplicity, and maintainability.

   Packages marked as affected by this bug were designated so because
   they have a dependency on the pyexiv2 package. They will need to be
   ported to GExiv2 before they can be ported to Python 3. Here is the
   popcon data for these packages, which may hopefully allow us to
   prioritize this work by installation popularity:

   #rank nameinst  vote   old recent no-files
   6692  gramps 41836   534 41095   198 9
   8296  phatch-cli 26266   734 25209   30914
   13025 videoporama 8766   120  860239 5
   16897 rapid-photo-downloader  4683   174  440397 9
   19941 nautilus-image-manipulator  3054   164  281673 1
   35392 creepy   59111   56317 0
   36572 lazygal  53411   522 1 0
   65688 smartshine60 522 627
   78375 flickrbackup  26 125 0 0

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/nautilus-image-manipulator/+bug/1074028/+subscriptions



-- 
http://www.damonlynch.net

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

Title:
  Port all pyexiv2 apps to GExiv2

Status in Nautilus Image Manipulator:
  Fix Committed
Status in pyexiv2, a python binding to exiv2:
  Triaged
Status in Rapid 

[Desktop-packages] [Bug 914400] Re: gnome-control-center crashed with signal 7 in g_closure_invoke()

[Damon Lynch]

** Visibility changed to: Public

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

Title:
  gnome-control-center crashed with signal 7 in g_closure_invoke()

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

Bug description:
  This bug may have been triggered by me opening the lid on my laptop.
  When I am using an external display, the laptop lid is closed.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.2.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0
  Uname: Linux 3.2.0-8-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  Date: Tue Jan 10 11:51:45 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(2029.1)
  ProcCmdline: gnome-control-center --overview
  Signal: 7
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/control-center-1/panels/libcolor.so
   ?? () from /usr/lib/control-center-1/panels/libcolor.so
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with signal 7 in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   deja-dup   21.2-0ubuntu2
   gnome-bluetooth3.2.1-1ubuntu3
   indicator-datetime 0.3.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/914400/+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 550054] Re: External Monitor not Sleeping with Laptop Lid Closed

[Damon Lynch]

Good news: I had the bug in  versions up to and including 11.04, but it
appears to be fixed in 11.10. Can someone else confirm it works for
them?

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

Title:
  External Monitor not Sleeping with Laptop Lid Closed

Status in Gnome Powermanager:
  New
Status in “gnome-power-manager” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-power-manager

  In Ubuntu 10.04, the gnome-power-manager seems to have no effect on my
  laptop. I am running my Toshiba laptop with an external monitor and
  the laptop LCD disabled. I've set the gnome-power manager to turn the
  screen off after 10 minutes (the time is actually irrelevant), but the
  screen will never turn off. It doesn't matter if I have the
  screensaver set to activate or not. It also doesn't matter how much
  time I tell the manager to wait before powering down the monitor. The
  monitor stays on no matter what.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-power-manager 2.29.91-0ubuntu9
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-17-generic i686
  Architecture: i386
  Date: Sun Mar 28 00:18:29 2010
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318)
  MachineType: TOSHIBA Satellite M105
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic 
root=UUID=188be98a-11ff-4e0a-a433-bfecef18c900 ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  dmi.bios.date: 09/13/2007
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V2.90
  dmi.board.name: HAQAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Null
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV2.90:bd09/13/2007:svnTOSHIBA:pnSatelliteM105:pvrPSMA0U-0F201T:rvnTOSHIBA:rnHAQAA:rvrNull:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite M105
  dmi.product.version: PSMA0U-0F201T
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-power/+bug/550054/+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