[Desktop-packages] [Bug 1975385] [NEW] connection editor does not preserve ignore-auto-dns=true flag

[Václav Haisman]

Public bug reported:

I want to avoid using the DHCP server provided DNS. To achieve this, I
tried using ignore-auto-dns=true flag in NM configuration. However,
subsequent editing of the network configuration through the applet
remove the flag. At the same time the applet does not allow me to
specify this flag in any way.

The applet should either preserve flags it does not understand or it
should know about this flag and let me edit it in the applet.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: network-manager-gnome 1.24.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-41.46-lowlatency 5.13.19
Uname: Linux 5.13.0-41-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu71.2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Sat May 21 19:55:35 2022
ExecutablePath: /usr/bin/nm-connection-editor
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2011-11-13 (3842 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IpRoute:
 default via 192.168.0.1 dev enp6s0 proto dhcp metric 100 
 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
 192.168.0.0/24 dev enp6s0 proto kernel scope link src 192.168.0.71 metric 100 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager-applet
UpgradeStatus: Upgraded to impish on 2021-10-15 (218 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2019-03-27T00:07:10.128435
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.32.12  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

** Attachment removed: "XsessionErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591842/+files/XsessionErrors.txt

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591827/+files/CRDA.txt

** Attachment removed: "IpAddr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591829/+files/IpAddr.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591841/+files/WifiSyslog.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591840/+files/ProcStatus.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591839/+files/ProcMaps.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591838/+files/ProcEnviron.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591837/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "PciNetwork.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591836/+files/PciNetwork.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591830/+files/IwConfig.txt

** Attachment removed: "NetDevice.virbr0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591834/+files/NetDevice.virbr0.txt

** Attachment removed: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591833/+files/NetDevice.lo.txt

** Attachment removed: "NetDevice.docker0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+attachment/5591831/+files/NetDevice.docker0.txt

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

Title:
  connection editor does not preserve ignore-auto-dns=true flag

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  I want to avoid using the DHCP server provided DNS. To achieve this, I
  tried using ignore-auto-dns=true flag in NM configuration. However,
  subsequent editing of the network configuration through the applet
  remove the flag. At the same time the applet does not allow me to
  specify this flag in any way.

  The applet should either preserve flags it does not understand or it
  should know about this flag and let me edit it in the applet.

  ProblemType: Bug
  

[Desktop-packages] [Bug 1778638] Re: duplicity stuck in splice() call on Bionic

[Václav Haisman]

For what it is worth, Duplicity 0.8.11.1612-1 on Ubuntu 20.10 works
fine.

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

Title:
  duplicity stuck in splice() call on Bionic

Status in Duplicity:
  Incomplete
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I am using Duplicity through Deja-Dup through its deja-dup-monitor
  process. After update to Bionic, it has basically stopped doing
  backups. Version is duplicity 0.7.17+bzr1357, Python version is
  2.7.15rc1, Xubuntu Bionic.

  It seems to be stuck in pipes related call. When I try to strace the
  process I get this:

  strace: Process 28490 attached
  splice(9, [359], 16, NULL, 1048576, SPLICE_F_MORE

  From handle 9 to 16. The handle 9 is a file on my CIFS mount to where
  I do backups. If I go to the directory and do ls it works fine:

  duplicity 28490 USER9r  REG   0,52  359
  67128742 /var/backups/USER/backup.HOST/duplicity-
  inc.20180611T014226Z.to.20180612T014125Z.manifest.gpg

  Handle 16 is a pipe:

  duplicity 28490 USER   16w FIFO   0,12  0t0
  1415081 pipe

  Its other end is handle 13, I think:

  duplicity 28490 USER   13r FIFO   0,12  0t0
  1415081 pipe

  But I do not see anyone reading from it. That sounds like the issue.

  It seems to be stuck in GIO file handling code:

  (gdb) bt
  #0  0x7f0e78588dda in splice (fd_in=9, off_in=0x7ffe5e958388, fd_out=16, 
off_out=0x0, len=1048576, flags=4) at ../sysdeps/unix/sysv/linux/splice.c:26
  #1  0x7f0e6ee2672e in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #2  0x7f0e6ee2d827 in g_file_copy () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #3  0x7f0e76ccfdae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #4  0x7f0e76ccf71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #5  0x7f0e6fb8ecfa in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #6  0x7f0e6fb908e8 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #7  0x7f0e6fb84c39 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #8  0x5560917a1f60 in PyEval_EvalFrameEx ()

  I have already tried to restart it and it got stuck like this again
  the next backup cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1778638/+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 1693709] Re: Wrong substitution for TimesNewRomanPSMT in evince / postscriptname not used

[Václav Haisman]

I am seeing this even on 20.10.

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

Title:
  Wrong substitution for TimesNewRomanPSMT in evince / postscriptname
  not used

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  A PDF I got referenced the not embedded font TimesNewRomanPSMT. Document 
viewer evince by fontconfig used DejaVu Sans to display it.
  But „TimesNewRomanPSMT“ is the postscriptname of Times New Roman, so it looks 
like fontconfig is not looking for the postscript names.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1693709/+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 1865536] [NEW] OBS consumes all memory, fixed in upstream Mesa

[Václav Haisman]

Public bug reported:

There is an issue where due to a Mesa bug OBS consumes all memory
eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426.
Unfortunately, this issue is in all recent Ubuntu versions.

** Affects: mesa
 Importance: Unknown
 Status: Unknown

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


** Tags: eoan

** Package changed: mesa (Ubuntu) => mesa

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #1426
   https://gitlab.freedesktop.org/mesa/mesa/issues/1426

** Changed in: mesa
   Importance: Undecided => Unknown

** Changed in: mesa
   Status: New => Unknown

** Changed in: mesa
 Remote watch: None => gitlab.freedesktop.org/mesa/mesa/issues #1426

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

** Description changed:

  There is an issue where due to a Mesa bug OBS consumes all memory
  eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426.
- Unfortunately, this issue is in all released Ubuntu versions.
+ Unfortunately, this issue is in all recent Ubuntu versions.

** Tags added: eoan

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

Title:
  OBS consumes all memory, fixed in upstream Mesa

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  New

Bug description:
  There is an issue where due to a Mesa bug OBS consumes all memory
  eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426.
  Unfortunately, this issue is in all recent Ubuntu versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1865536/+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 1736222] Re: speech-dispatcher distorts all sound

[Václav Haisman]

Yup. I have just diagnosed this as well on Cosmic. Suddenly, it started
while I was watching film on Netflix in browser. I looked around and
noticed three new speech-dispatcher processes connected to pulseaudio. I
kept the film running and issued `killall speech-dispatcher` and the
distortion stopped immediately.

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

Title:
  speech-dispatcher distorts all sound

Status in speech-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  So, a brand new computer running Ubuntu 16.04.3 LTS.
  In hardinfo summary, my audio adapters are
  • HDA-Intel - HDA Intel HDMI
  • HDA-Intel - HDA Intel PCH
  • HDA-Intel - HDA NVidia
  In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller (rev 06)
  Memory 16kb (non-prefetchable), snd_hda_intel

  As soon as I load a website in Firefox that utilizes speech-dispatcher
  (fimfiction.net) all sounds get distorted, whether I click a paragraph
  for TTS reading or not. The problem seems to go away if I don't use
  the site after a while. When I close down Firefox the problem still
  lingers a bit, but maybe not as long. One thing I did which seemed
  faster was close down everything, then load what I wanted to listen to
  (Skype, Discord), and if it still persisted I would go into "Sound
  Settings" and after a few blinks in that window the sound is normal
  again.

  While the site is open, according to "Sound Settings" (from the
  speaker icon menu) and Pulse Audio Volume Controller (pavu) there are
  4 copies of this package. Muting them did not help the problem, but
  moving one of them, and a very specific one, from the "Built-in Audio
  Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be
  a workaround.

  Just so you know, I do not use the HDMI cable for sound, but instead
  use the "headphones" jack. If you need any more details, I'll try to
  provide them.

  /Edward

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+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 1803815] Re: Evince stuck with "Loading..." and empty page for ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf file specifically

[Václav Haisman]

I have reported the bug to Poppler project:
https://gitlab.freedesktop.org/poppler/poppler/issues/673

** Package changed: evince (Ubuntu) => poppler (Ubuntu)

** Also affects: poppler
   Importance: Undecided
   Status: New

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

Title:
  Evince stuck with "Loading..." and empty page for
  ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf file specifically

Status in Poppler:
  New
Status in poppler package in Ubuntu:
  New

Bug description:
  I was viewing
  https://www.ecfr.eu/page/ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf
  in Firefox which works fine and fast, and then I decided to download
  it and view it alter with Evince. However, in Evince, the viewing pane
  never shows anything but "Loading..." in upper right corner. I can
  view any other PDF with Evince just fine. Only this specific PDF from
  ECFR.EU page shows this behaviour. The Evince GUI is not stuck. I can
  see bookmarks and I can click on them but the viewing pane is never
  filled with any content.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.1-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov 17 11:53:57 2018
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2011-11-13 (2560 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1803815/+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 1803815] Re: Evince stuck with "Loading..." and empty page for ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf file specifically

[Václav Haisman]

** Tags added: performance

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

Title:
  Evince stuck with "Loading..." and empty page for
  ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf file specifically

Status in evince package in Ubuntu:
  New

Bug description:
  I was viewing
  https://www.ecfr.eu/page/ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf
  in Firefox which works fine and fast, and then I decided to download
  it and view it alter with Evince. However, in Evince, the viewing pane
  never shows anything but "Loading..." in upper right corner. I can
  view any other PDF with Evince just fine. Only this specific PDF from
  ECFR.EU page shows this behaviour. The Evince GUI is not stuck. I can
  see bookmarks and I can click on them but the viewing pane is never
  filled with any content.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.1-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov 17 11:53:57 2018
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2011-11-13 (2560 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1803815/+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 1803815] Re: Evince stuck with "Loading..." and empty page for ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf file specifically

[Václav Haisman]

Alright, it took many minutes but it eventually did load the PDF and now
I can view it. So I guess this is more like performance issue that
Firefox's PDF viewer can do better on this file than Evince.

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

Title:
  Evince stuck with "Loading..." and empty page for
  ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf file specifically

Status in evince package in Ubuntu:
  New

Bug description:
  I was viewing
  https://www.ecfr.eu/page/ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf
  in Firefox which works fine and fast, and then I decided to download
  it and view it alter with Evince. However, in Evince, the viewing pane
  never shows anything but "Loading..." in upper right corner. I can
  view any other PDF with Evince just fine. Only this specific PDF from
  ECFR.EU page shows this behaviour. The Evince GUI is not stuck. I can
  see bookmarks and I can click on them but the viewing pane is never
  filled with any content.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.1-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov 17 11:53:57 2018
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2011-11-13 (2560 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1803815/+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 1803815] [NEW] Evince stuck with "Loading..." and empty page for ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf file specifically

[Václav Haisman]

Public bug reported:

I was viewing
https://www.ecfr.eu/page/ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf in
Firefox which works fine and fast, and then I decided to download it and
view it alter with Evince. However, in Evince, the viewing pane never
shows anything but "Loading..." in upper right corner. I can view any
other PDF with Evince just fine. Only this specific PDF from ECFR.EU
page shows this behaviour. The Evince GUI is not stuck. I can see
bookmarks and I can click on them but the viewing pane is never filled
with any content.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: evince 3.30.1-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Nov 17 11:53:57 2018
ExecutablePath: /usr/bin/evince
InstallationDate: Installed on 2011-11-13 (2560 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: evince
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (28 days ago)

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


** Tags: amd64 apparmor apport-bug cosmic

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

Title:
  Evince stuck with "Loading..." and empty page for
  ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf file specifically

Status in evince package in Ubuntu:
  New

Bug description:
  I was viewing
  https://www.ecfr.eu/page/ECFR269_EU_COALITION_EXPLORER_2018_V1.10.pdf
  in Firefox which works fine and fast, and then I decided to download
  it and view it alter with Evince. However, in Evince, the viewing pane
  never shows anything but "Loading..." in upper right corner. I can
  view any other PDF with Evince just fine. Only this specific PDF from
  ECFR.EU page shows this behaviour. The Evince GUI is not stuck. I can
  see bookmarks and I can click on them but the viewing pane is never
  filled with any content.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.1-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov 17 11:53:57 2018
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2011-11-13 (2560 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1803815/+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 1778638] Re: duplicity stuck in splice() call on Bionic

[Václav Haisman]

It looks like this is not just me who is having this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1582654

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

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

Title:
  duplicity stuck in splice() call on Bionic

Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  New

Bug description:
  I am using Duplicity through Deja-Dup through its deja-dup-monitor
  process. After update to Bionic, it has basically stopped doing
  backups. Version is duplicity 0.7.17+bzr1357, Python version is
  2.7.15rc1, Xubuntu Bionic.

  It seems to be stuck in pipes related call. When I try to strace the
  process I get this:

  strace: Process 28490 attached
  splice(9, [359], 16, NULL, 1048576, SPLICE_F_MORE

  From handle 9 to 16. The handle 9 is a file on my CIFS mount to where
  I do backups. If I go to the directory and do ls it works fine:

  duplicity 28490 USER9r  REG   0,52  359
  67128742 /var/backups/USER/backup.HOST/duplicity-
  inc.20180611T014226Z.to.20180612T014125Z.manifest.gpg

  Handle 16 is a pipe:

  duplicity 28490 USER   16w FIFO   0,12  0t0
  1415081 pipe

  Its other end is handle 13, I think:

  duplicity 28490 USER   13r FIFO   0,12  0t0
  1415081 pipe

  But I do not see anyone reading from it. That sounds like the issue.

  It seems to be stuck in GIO file handling code:

  (gdb) bt
  #0  0x7f0e78588dda in splice (fd_in=9, off_in=0x7ffe5e958388, fd_out=16, 
off_out=0x0, len=1048576, flags=4) at ../sysdeps/unix/sysv/linux/splice.c:26
  #1  0x7f0e6ee2672e in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #2  0x7f0e6ee2d827 in g_file_copy () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #3  0x7f0e76ccfdae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #4  0x7f0e76ccf71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #5  0x7f0e6fb8ecfa in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #6  0x7f0e6fb908e8 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #7  0x7f0e6fb84c39 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #8  0x5560917a1f60 in PyEval_EvalFrameEx ()

  I have already tried to restart it and it got stuck like this again
  the next backup cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1778638/+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 1778638] Re: duplicity stuck in splice() call on Bionic

[Václav Haisman]

Further debugging with `strace` shows it literally creates the pipe
right before it tries to write into it:

write(1, "Registering (mktemp) temporary f"..., 82) = 82
write(13, "DEBUG 1\n. Registering (mktemp) t"..., 93) = 93
lstat("/tmp/duplicity-iMtvLG-tempdir/mktemp-Z8PNlG-2", 0x7ffd210b6cc0) = -1 
ENOENT (No such file or directory)
futex(0x7f4cce376f38, FUTEX_WAKE_PRIVATE, 2147483647) = 0
lstat("/var/backups/wilx/backup.amber2/duplicity-inc.20180824T154037Z.to.20180825T014020Z.manifest",
 {st_mode=S_IFREG|0755, st_size=214, ...}) = 0
openat(AT_FDCWD, 
"/var/backups/wilx/backup.amber2/duplicity-inc.20180824T154037Z.to.20180825T014020Z.manifest",
 O_RDONLY) = 9
fstat(9, {st_mode=S_IFREG|0755, st_size=214, ...}) = 0
futex(0x7f4cce376f38, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f4cce376f38, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f4cce376f38, FUTEX_WAKE_PRIVATE, 2147483647) = 0
fstat(9, {st_mode=S_IFREG|0755, st_size=214, ...}) = 0
flistxattr(9, NULL, 0)  = -1 ENODATA (No data available)
openat(AT_FDCWD, "/tmp/duplicity-iMtvLG-tempdir/mktemp-Z8PNlG-2", 
O_WRONLY|O_CREAT|O_EXCL, 0755) = 10
futex(0x7f4cce376f38, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f4cce376f38, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(10, BTRFS_IOC_CLONE or FICLONE, 9) = -1 EXDEV (Invalid cross-device link)

It creates the pipe descriptor pair here:

pipe2([19, 20], O_CLOEXEC)  = 0
fcntl(20, F_SETPIPE_SZ, 1048576)= 1048576
fstat(9, {st_mode=S_IFREG|0755, st_size=214, ...}) = 0

And immediately tries to write into it. Who is supposed to be reading
the other end?

splice(9, [0], 20, NULL, 1048576, SPLICE_F_MORE) = 214
splice(19, NULL, 10, [0], 214, SPLICE_F_MORE) = 214
splice(9, [214], 20, NULL, 1048576, SPLICE_F_MORE

The two commented chunks above are adjacent in the `strace` log. I have
not left out anything. These are literally the last 6 lines of the
`strace` log of the stuck process.

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

Title:
  duplicity stuck in splice() call on Bionic

Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  New

Bug description:
  I am using Duplicity through Deja-Dup through its deja-dup-monitor
  process. After update to Bionic, it has basically stopped doing
  backups. Version is duplicity 0.7.17+bzr1357, Python version is
  2.7.15rc1, Xubuntu Bionic.

  It seems to be stuck in pipes related call. When I try to strace the
  process I get this:

  strace: Process 28490 attached
  splice(9, [359], 16, NULL, 1048576, SPLICE_F_MORE

  From handle 9 to 16. The handle 9 is a file on my CIFS mount to where
  I do backups. If I go to the directory and do ls it works fine:

  duplicity 28490 USER9r  REG   0,52  359
  67128742 /var/backups/USER/backup.HOST/duplicity-
  inc.20180611T014226Z.to.20180612T014125Z.manifest.gpg

  Handle 16 is a pipe:

  duplicity 28490 USER   16w FIFO   0,12  0t0
  1415081 pipe

  Its other end is handle 13, I think:

  duplicity 28490 USER   13r FIFO   0,12  0t0
  1415081 pipe

  But I do not see anyone reading from it. That sounds like the issue.

  It seems to be stuck in GIO file handling code:

  (gdb) bt
  #0  0x7f0e78588dda in splice (fd_in=9, off_in=0x7ffe5e958388, fd_out=16, 
off_out=0x0, len=1048576, flags=4) at ../sysdeps/unix/sysv/linux/splice.c:26
  #1  0x7f0e6ee2672e in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #2  0x7f0e6ee2d827 in g_file_copy () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #3  0x7f0e76ccfdae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #4  0x7f0e76ccf71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #5  0x7f0e6fb8ecfa in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #6  0x7f0e6fb908e8 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #7  0x7f0e6fb84c39 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #8  0x5560917a1f60 in PyEval_EvalFrameEx ()

  I have already tried to restart it and it got stuck like this again
  the next backup cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1778638/+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 1778638] Re: duplicity stuck in splice() call on Bionic

[Václav Haisman]

I have even tried without encryption. The `--no-use-agent` option is
there even:

DUPLICITY: . Args: /usr/bin/duplicity
--exclude=/var/backups/wilx/backup.amber2
--exclude=/home/wilx/snap/*/*/.cache --include=/home/wilx/.cache/deja-
dup/metadata --exclude=/home/wilx/Private
--exclude=/home/wilx/.local/share/Trash --exclude=/home/wilx/.xsession-
errors --exclude=/home/wilx/.thumbnails --exclude=/home/wilx/.steam/root
--exclude=/home/wilx/.adobe/Flash_Player/AssetCache
--exclude=/home/wilx/.cache/deja-dup --exclude=/home/wilx/.cache
--exclude=/home/wilx/.steam --include=/home/wilx --exclude=/sys
--exclude=/run --exclude=/proc --exclude=/var/tmp --exclude=/tmp
--exclude=** --dry-run --volsize=50 /
gio+file:///var/backups/wilx/backup.amber2 --no-encryption --verbosity=9
--gpg-options=--no-use-agent --archive-dir=/home/wilx/.cache/deja-dup
--tempdir=/tmp --log-fd=13

It still gets stuck in the `splice()` call.

#0  0x7f4b979efdda in splice (fd_in=9, off_in=0x7ffd5ff098f8,
fd_out=15, off_out=0x0, len=1048576, flags=4) at
../sysdeps/unix/sysv/linux/splice.c:26

Nobody is reading from the pipe:

duplicity 1328 wilx9r  REG   0,52  214
45574945 /var/backups/wilx/backup.amber2/duplicity-
inc.20180824T154037Z.to.20180825T014020Z.manifest

duplicity 1328 wilx   14r FIFO   0,12  0t0   28167742 pipe
duplicity 1328 wilx   15w FIFO   0,12  0t0   28167742 pipe


** Changed in: duplicity
   Status: Incomplete => New

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

Title:
  duplicity stuck in splice() call on Bionic

Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  New

Bug description:
  I am using Duplicity through Deja-Dup through its deja-dup-monitor
  process. After update to Bionic, it has basically stopped doing
  backups. Version is duplicity 0.7.17+bzr1357, Python version is
  2.7.15rc1, Xubuntu Bionic.

  It seems to be stuck in pipes related call. When I try to strace the
  process I get this:

  strace: Process 28490 attached
  splice(9, [359], 16, NULL, 1048576, SPLICE_F_MORE

  From handle 9 to 16. The handle 9 is a file on my CIFS mount to where
  I do backups. If I go to the directory and do ls it works fine:

  duplicity 28490 USER9r  REG   0,52  359
  67128742 /var/backups/USER/backup.HOST/duplicity-
  inc.20180611T014226Z.to.20180612T014125Z.manifest.gpg

  Handle 16 is a pipe:

  duplicity 28490 USER   16w FIFO   0,12  0t0
  1415081 pipe

  Its other end is handle 13, I think:

  duplicity 28490 USER   13r FIFO   0,12  0t0
  1415081 pipe

  But I do not see anyone reading from it. That sounds like the issue.

  It seems to be stuck in GIO file handling code:

  (gdb) bt
  #0  0x7f0e78588dda in splice (fd_in=9, off_in=0x7ffe5e958388, fd_out=16, 
off_out=0x0, len=1048576, flags=4) at ../sysdeps/unix/sysv/linux/splice.c:26
  #1  0x7f0e6ee2672e in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #2  0x7f0e6ee2d827 in g_file_copy () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #3  0x7f0e76ccfdae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #4  0x7f0e76ccf71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #5  0x7f0e6fb8ecfa in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #6  0x7f0e6fb908e8 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #7  0x7f0e6fb84c39 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #8  0x5560917a1f60 in PyEval_EvalFrameEx ()

  I have already tried to restart it and it got stuck like this again
  the next backup cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1778638/+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 1778638] Re: duplicity stuck in splice() call on Bionic

[Václav Haisman]

Is that true? Haven't I set up the pass phrase during initial backup in
Deja Dup? It does not make sense for automatic backup to as for
passhrase each time it runs. Is this Deja Dup issue then?

** Also affects: deja-dup (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  duplicity stuck in splice() call on Bionic

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  New

Bug description:
  I am using Duplicity through Deja-Dup through its deja-dup-monitor
  process. After update to Bionic, it has basically stopped doing
  backups. Version is duplicity 0.7.17+bzr1357, Python version is
  2.7.15rc1, Xubuntu Bionic.

  It seems to be stuck in pipes related call. When I try to strace the
  process I get this:

  strace: Process 28490 attached
  splice(9, [359], 16, NULL, 1048576, SPLICE_F_MORE

  From handle 9 to 16. The handle 9 is a file on my CIFS mount to where
  I do backups. If I go to the directory and do ls it works fine:

  duplicity 28490 USER9r  REG   0,52  359
  67128742 /var/backups/USER/backup.HOST/duplicity-
  inc.20180611T014226Z.to.20180612T014125Z.manifest.gpg

  Handle 16 is a pipe:

  duplicity 28490 USER   16w FIFO   0,12  0t0
  1415081 pipe

  Its other end is handle 13, I think:

  duplicity 28490 USER   13r FIFO   0,12  0t0
  1415081 pipe

  But I do not see anyone reading from it. That sounds like the issue.

  It seems to be stuck in GIO file handling code:

  (gdb) bt
  #0  0x7f0e78588dda in splice (fd_in=9, off_in=0x7ffe5e958388, fd_out=16, 
off_out=0x0, len=1048576, flags=4) at ../sysdeps/unix/sysv/linux/splice.c:26
  #1  0x7f0e6ee2672e in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #2  0x7f0e6ee2d827 in g_file_copy () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #3  0x7f0e76ccfdae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #4  0x7f0e76ccf71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #5  0x7f0e6fb8ecfa in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #6  0x7f0e6fb908e8 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #7  0x7f0e6fb84c39 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
  #8  0x5560917a1f60 in PyEval_EvalFrameEx ()

  I have already tried to restart it and it got stuck like this again
  the next backup cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1778638/+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 498933] Re: Crash when restoring data KeyError

[Václav Haisman]

> The file list coming back from the remote is truncated [...]

You are absolutely right. I have WD My Cloud Mirror Gen 2 device and I
used FTP to store the backups there. It turns out the Pro-FTPd that it
uses only returns 1 lines for directory listing command and my
backups have grown beyond that point. I have ended up switching to CIFS
mount to work around this.

This could alleviated if Deja-dup/Duplicity was using larger files for
storage. Also, diagnosing this directory listing truncation instead of
outright exception stack trace would be nice.

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

Title:
  Crash when restoring data KeyError

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: deja-dup

  1) Ubuntu 9.10
  2) Deja Dup 10.2-0ubuntu1.1
  3) I expected my backup to be restored
  4) Deja Dup crashed instead.

  I just tried to restore the backup I made, and it crashes repeatedly
  when trying to restore.

  I have it setup to backup my home directory, and tried restoring to
  both the original location as well as a completely different folder.
  Both lead to the same error message.

  
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 825, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 818, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 775, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 436, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 521, in 
Write_ROPaths
  ITR(ropath.index, ropath)
File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 336, in 
__call__
  last_branch.fast_process, args)
File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 38, in 
check_common_error
  return function(*args)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 574, in 
fast_process
  ropath.copy(self.base_path.new_index(index))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 412, in copy
  other.writefileobj(self.open("rb"))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 574, in 
writefileobj
  buf = fin.read(_copy_blocksize)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 199, in 
read
  if not self.addtobuffer():
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 224, in 
addtobuffer
  self.tarinfo_list[0] = self.tar_iter.next()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 331, in 
next
  self.set_tarfile()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 320, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 472, in get_fileobj_iter
  backup_set.volume_name_dict[vol_num],
  KeyError: 15

  ProblemType: Bug
  Architecture: i386
  Date: Sun Dec 20 19:59:06 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: deja-dup 10.2-0ubuntu1.1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: deja-dup
  Uname: Linux 2.6.31-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/498933/+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 498933] Re: Crash when restoring data KeyError

[Václav Haisman]

Here is the result of `grep -C 10 "vol43\." deja-dup.log`. It is
compressed because it is otherwise 5 MiB.

** Attachment added: "result of `grep -C 10 "vol43\." deja-dup.log`"
   
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/498933/+attachment/5098011/+files/vol43.txt.xz

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

Title:
  Crash when restoring data KeyError

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: deja-dup

  1) Ubuntu 9.10
  2) Deja Dup 10.2-0ubuntu1.1
  3) I expected my backup to be restored
  4) Deja Dup crashed instead.

  I just tried to restore the backup I made, and it crashes repeatedly
  when trying to restore.

  I have it setup to backup my home directory, and tried restoring to
  both the original location as well as a completely different folder.
  Both lead to the same error message.

  
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 825, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 818, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 775, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 436, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 521, in 
Write_ROPaths
  ITR(ropath.index, ropath)
File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 336, in 
__call__
  last_branch.fast_process, args)
File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 38, in 
check_common_error
  return function(*args)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 574, in 
fast_process
  ropath.copy(self.base_path.new_index(index))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 412, in copy
  other.writefileobj(self.open("rb"))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 574, in 
writefileobj
  buf = fin.read(_copy_blocksize)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 199, in 
read
  if not self.addtobuffer():
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 224, in 
addtobuffer
  self.tarinfo_list[0] = self.tar_iter.next()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 331, in 
next
  self.set_tarfile()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 320, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 472, in get_fileobj_iter
  backup_set.volume_name_dict[vol_num],
  KeyError: 15

  ProblemType: Bug
  Architecture: i386
  Date: Sun Dec 20 19:59:06 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: deja-dup 10.2-0ubuntu1.1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: deja-dup
  Uname: Linux 2.6.31-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/498933/+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 498933] Re: Crash when restoring data KeyError

[Václav Haisman]

Log head.

** Attachment added: "Log head."
   
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/498933/+attachment/5097883/+files/deja-dup-log.head.txt

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

Title:
  Crash when restoring data KeyError

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: deja-dup

  1) Ubuntu 9.10
  2) Deja Dup 10.2-0ubuntu1.1
  3) I expected my backup to be restored
  4) Deja Dup crashed instead.

  I just tried to restore the backup I made, and it crashes repeatedly
  when trying to restore.

  I have it setup to backup my home directory, and tried restoring to
  both the original location as well as a completely different folder.
  Both lead to the same error message.

  
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 825, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 818, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 775, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 436, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 521, in 
Write_ROPaths
  ITR(ropath.index, ropath)
File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 336, in 
__call__
  last_branch.fast_process, args)
File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 38, in 
check_common_error
  return function(*args)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 574, in 
fast_process
  ropath.copy(self.base_path.new_index(index))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 412, in copy
  other.writefileobj(self.open("rb"))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 574, in 
writefileobj
  buf = fin.read(_copy_blocksize)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 199, in 
read
  if not self.addtobuffer():
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 224, in 
addtobuffer
  self.tarinfo_list[0] = self.tar_iter.next()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 331, in 
next
  self.set_tarfile()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 320, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 472, in get_fileobj_iter
  backup_set.volume_name_dict[vol_num],
  KeyError: 15

  ProblemType: Bug
  Architecture: i386
  Date: Sun Dec 20 19:59:06 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: deja-dup 10.2-0ubuntu1.1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: deja-dup
  Uname: Linux 2.6.31-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/498933/+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 498933] Re: Crash when restoring data KeyError

[Václav Haisman]

Log head.

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

Title:
  Crash when restoring data KeyError

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: deja-dup

  1) Ubuntu 9.10
  2) Deja Dup 10.2-0ubuntu1.1
  3) I expected my backup to be restored
  4) Deja Dup crashed instead.

  I just tried to restore the backup I made, and it crashes repeatedly
  when trying to restore.

  I have it setup to backup my home directory, and tried restoring to
  both the original location as well as a completely different folder.
  Both lead to the same error message.

  
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 825, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 818, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 775, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 436, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 521, in 
Write_ROPaths
  ITR(ropath.index, ropath)
File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 336, in 
__call__
  last_branch.fast_process, args)
File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 38, in 
check_common_error
  return function(*args)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 574, in 
fast_process
  ropath.copy(self.base_path.new_index(index))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 412, in copy
  other.writefileobj(self.open("rb"))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 574, in 
writefileobj
  buf = fin.read(_copy_blocksize)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 199, in 
read
  if not self.addtobuffer():
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 224, in 
addtobuffer
  self.tarinfo_list[0] = self.tar_iter.next()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 331, in 
next
  self.set_tarfile()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 320, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 472, in get_fileobj_iter
  backup_set.volume_name_dict[vol_num],
  KeyError: 15

  ProblemType: Bug
  Architecture: i386
  Date: Sun Dec 20 19:59:06 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: deja-dup 10.2-0ubuntu1.1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: deja-dup
  Uname: Linux 2.6.31-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/498933/+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 498933] Re: Crash when restoring data KeyError

[Václav Haisman]

This is a tail of log:

DUPLICITY: DEBUG 1
DUPLICITY: . Found manifest volume 7529

DUPLICITY: DEBUG 1
DUPLICITY: . Found manifest volume 7530

DUPLICITY: DEBUG 1
DUPLICITY: . Found manifest volume 7531

DUPLICITY: INFO 1
DUPLICITY: . Found 7531 volumes in manifest

DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile 
/home/user1/.cache/deja-dup/85893b547e8951c12699b18a9f26d2da/lockfile

DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-LM6LdM-tempdir/mkstemp-slQNlf-1

DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile 
/home/user1/.cache/deja-dup/85893b547e8951c12699b18a9f26d2da/lockfile

DUPLICITY: ERROR 30 KeyError
DUPLICITY: . Traceback (innermost last):
DUPLICITY: .   File "/usr/bin/duplicity", line 1555, in 
DUPLICITY: . with_tempdir(main)
DUPLICITY: .   File "/usr/bin/duplicity", line 1541, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: .   File "/usr/bin/duplicity", line 1393, in main
DUPLICITY: . do_backup(action)
DUPLICITY: .   File "/usr/bin/duplicity", line 1472, in do_backup
DUPLICITY: . restore(col_stats)
DUPLICITY: .   File "/usr/bin/duplicity", line 728, in restore
DUPLICITY: . restore_get_patched_rop_iter(col_stats)):
DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", 
line 558, in Write_ROPaths
DUPLICITY: . for ropath in rop_iter:
DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", 
line 521, in integrate_patch_iters
DUPLICITY: . for patch_seq in collated:
DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", 
line 389, in yield_tuples
DUPLICITY: . setrorps(overflow, elems)
DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", 
line 378, in setrorps
DUPLICITY: . elems[i] = iter_list[i].next()
DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", 
line 107, in filter_path_iter
DUPLICITY: . for path in path_iter:
DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", 
line 121, in difftar2path_iter
DUPLICITY: . tarinfo_list = [tar_iter.next()]
DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", 
line 339, in next
DUPLICITY: . self.set_tarfile()
DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", 
line 333, in set_tarfile
DUPLICITY: . self.current_fp = self.fileobj_iter.next()
DUPLICITY: .   File "/usr/bin/duplicity", line 764, in get_fileobj_iter
DUPLICITY: . backup_set.volume_name_dict[vol_num],
DUPLICITY: .  KeyError: 43
DUPLICITY: . 

DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile 
/home/user1/.cache/deja-dup/85893b547e8951c12699b18a9f26d2da/lockfile

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

Title:
  Crash when restoring data KeyError

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: deja-dup

  1) Ubuntu 9.10
  2) Deja Dup 10.2-0ubuntu1.1
  3) I expected my backup to be restored
  4) Deja Dup crashed instead.

  I just tried to restore the backup I made, and it crashes repeatedly
  when trying to restore.

  I have it setup to backup my home directory, and tried restoring to
  both the original location as well as a completely different folder.
  Both lead to the same error message.

  
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 825, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 818, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 775, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 436, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 521, in 
Write_ROPaths
  ITR(ropath.index, ropath)
File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 336, in 
__call__
  last_branch.fast_process, args)
File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 38, in 
check_common_error
  return function(*args)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 574, in 
fast_process
  ropath.copy(self.base_path.new_index(index))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 412, in copy
  other.writefileobj(self.open("rb"))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 574, in 
writefileobj
  buf = fin.read(_copy_blocksize)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 199, in 
read
  if not self.addtobuffer():
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 224, in 
addtobuffer
  self.tarinfo_list[0] = self.tar_iter.next()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 331, in 
next
  self.set_tarfile()
File 

[Desktop-packages] [Bug 498933] Re: Crash when restoring data KeyError

[Václav Haisman]

I am seeing this too. It happened first time after I started backups
from scratch after several weeks. It keeps occurring every day now.

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 1472, in do_backup
restore(col_stats)
  File "/usr/bin/duplicity", line 728, in restore
restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in 
Write_ROPaths
for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in 
integrate_patch_iters
for patch_seq in collated:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
setrorps(overflow, elems)
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
elems[i] = iter_list[i].next()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
for path in path_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
tarinfo_list = [tar_iter.next()]
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
self.set_tarfile()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
self.current_fp = self.fileobj_iter.next()
  File "/usr/bin/duplicity", line 764, in get_fileobj_iter
backup_set.volume_name_dict[vol_num],
 KeyError: 43

This is with duplicity 0.7.17+bzr1353 and deja-dup 36.3 on Ubuntu 17.10.

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

Title:
  Crash when restoring data KeyError

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: deja-dup

  1) Ubuntu 9.10
  2) Deja Dup 10.2-0ubuntu1.1
  3) I expected my backup to be restored
  4) Deja Dup crashed instead.

  I just tried to restore the backup I made, and it crashes repeatedly
  when trying to restore.

  I have it setup to backup my home directory, and tried restoring to
  both the original location as well as a completely different folder.
  Both lead to the same error message.

  
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 825, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 818, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 775, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 436, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 521, in 
Write_ROPaths
  ITR(ropath.index, ropath)
File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 336, in 
__call__
  last_branch.fast_process, args)
File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 38, in 
check_common_error
  return function(*args)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 574, in 
fast_process
  ropath.copy(self.base_path.new_index(index))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 412, in copy
  other.writefileobj(self.open("rb"))
File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 574, in 
writefileobj
  buf = fin.read(_copy_blocksize)
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 199, in 
read
  if not self.addtobuffer():
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 224, in 
addtobuffer
  self.tarinfo_list[0] = self.tar_iter.next()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 331, in 
next
  self.set_tarfile()
File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 320, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 472, in get_fileobj_iter
  backup_set.volume_name_dict[vol_num],
  KeyError: 15

  ProblemType: Bug
  Architecture: i386
  Date: Sun Dec 20 19:59:06 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: deja-dup 10.2-0ubuntu1.1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: deja-dup
  Uname: Linux 2.6.31-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/498933/+subscriptions

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

Re: [Desktop-packages] [Bug 1727653] Re: error: can't start new thread

[Václav Haisman]

On 26 January 2018 at 11:59, Wolf Rogner wrote:
> I cannot confirm that ulimit -s 16384 will heal the issue (suggested in
> #30). I have inserted ulimit -s 16384 to no avail.
>
> Exec=sh -c "ulimit -v 100; ulimit -s 16384; ulimit -n 4096; exec
> /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor"

Can you try without the ulimit -v 100?

Have you killed the existing deja-dup-monitor process first?

What's your ulimit -a output?

>
> -> still causes the issue.
>
> Trying to check my file count I realized that Nautilus interupts file
> count and restarts regularly. This behaviour might be triggered by
> several symlinks.
>
> Can it be that duplicity tries to follow a directory structure and gets
> confused if circular references via symlinks exist?
>
> If so, I have to draw a link tree for further analysis.
>

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Confirmed
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

[Václav Haisman]

@Kenneth: The -v limit was suggested in comment #19.

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Confirmed
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1727653] Re: error: can't start new thread

[Václav Haisman]

So, I have been experimenting. I have removed ulimit -v 100...0 out of
the command line because I have unlimited limit by default. What I have
added though is ulimit -s 16384 which doubles stack limit and I have
also ulimit -n 2048 to double file limit. Todays backup passed without
the usual exception.

I suggest others do the same. Find out file handle limits and stack size
limits and try again with doubled values. And remove the VM limit if it
actually sets a limit from unlimited.

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Confirmed
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1727653] Re: error: can't start new thread

[Václav Haisman]

@Kenneth: The call stack is clearly different. Also, it does not explain
the hanging threads in Duplicity and processes of GPG waiting on pipe
write to return. Also, I have been running the PPA version last few
months.

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Confirmed
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1727653] Re: error: can't start new thread

[Václav Haisman]

Debugging the Python process of Duplicity shows no polling or reading
from appropriate number of pipes:

* 1Thread 0x7f7f510d0740 (LWP 19797) 0x7f7f50ce9f96 in 
futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, 
futex_word=0x559f3d5e48f0)
at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  2Thread 0x7f7f4d9b0700 (LWP 19801) 0x7f7f50a01951 in __GI___poll 
(fds=0x559f3d517d30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  3Thread 0x7f7f469fd700 (LWP 19802) 0x7f7f50a01951 in __GI___poll 
(fds=0x559f3d5290a0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  4Thread 0x7f7f461fc700 (LWP 19960) 0x7f7f50ceba4a in __waitpid 
(pid=19959, stat_loc=0x7f7f461fb534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  5Thread 0x7f7f3700 (LWP 19962) 0x7f7f50ceba4a in __waitpid 
(pid=19961, stat_loc=0x7f7f3fffe534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  6Thread 0x7f7f3f7fe700 (LWP 19965) 0x7f7f50ceba4a in __waitpid 
(pid=19964, stat_loc=0x7f7f3f7fd534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  7Thread 0x7f7f3effd700 (LWP 19967) 0x7f7f50ceba4a in __waitpid 
(pid=19966, stat_loc=0x7f7f3effc534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  8Thread 0x7f7f3e7fc700 (LWP 19969) 0x7f7f50ceba4a in __waitpid 
(pid=19968, stat_loc=0x7f7f3e7fb534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  9Thread 0x7f7f3dffb700 (LWP 19971) 0x7f7f50ceba4a in __waitpid 
(pid=19970, stat_loc=0x7f7f3dffa534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  10   Thread 0x7f7f3d7fa700 (LWP 19973) 0x7f7f50ceba4a in __waitpid 
(pid=19972, stat_loc=0x7f7f3d7f9534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  11   Thread 0x7f7f3cff9700 (LWP 19975) 0x7f7f50ceba4a in __waitpid 
(pid=19974, stat_loc=0x7f7f3cff8534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  12   Thread 0x7f7f2bfff700 (LWP 19977) 0x7f7f50ceba4a in __waitpid 
(pid=19976, stat_loc=0x7f7f2bffe534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  13   Thread 0x7f7f2b7fe700 (LWP 19979) 0x7f7f50ceba4a in __waitpid 
(pid=19978, stat_loc=0x7f7f2b7fd534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  14   Thread 0x7f7f2affd700 (LWP 19981) 0x7f7f50ceba4a in __waitpid 
(pid=19980, stat_loc=0x7f7f2affc534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  15   Thread 0x7f7f2a7fc700 (LWP 19983) 0x7f7f50ceba4a in __waitpid 
(pid=19982, stat_loc=0x7f7f2a7fb534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  16   Thread 0x7f7f29ffb700 (LWP 19985) 0x7f7f50ceba4a in __waitpid 
(pid=19984, stat_loc=0x7f7f29ffa534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  17   Thread 0x7f7f297fa700 (LWP 19988) 0x7f7f50ceba4a in __waitpid 
(pid=19987, stat_loc=0x7f7f297f9534, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Confirmed
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File 

[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

[Václav Haisman]

So I have several (over 5) processes in the previously mentioned state:
Duplicity with a dozen or so gpg processes under it, hanging, duplicity
is being run as `usr/bin/duplicity restore`.

I have attached generated a core dump, downloaded symbols and analysed
the core dump with GDB. This is the stack trace:

#0  0x7f6a2a3130c4 in __GI___libc_write (fd=1, 
buf=buf@entry=0x55af21404900, nbytes=nbytes@entry=4096) at 
../sysdeps/unix/sysv/linux/write.c:26
#1  0x7f6a2a291ba7 in _IO_new_file_write (f=0x7f6a2a5ea720 
<_IO_2_1_stdout_>, data=0x55af21404900, n=4096) at fileops.c:1255
#2  0x7f6a2a293782 in new_do_write (to_do=4096, 
data=0x55af21404900 "**REDACTED**", fp=0x7f6a2a5ea720 <_IO_2_1_stdout_>) at 
fileops.c:510
#3  _IO_new_do_write (fp=0x7f6a2a5ea720 <_IO_2_1_stdout_>, 
data=0x55af21404900 "**REDACTED**", to_do=4096) at fileops.c:486
#4  0x7f6a2a2923bd in _IO_new_file_xsputn (f=0x7f6a2a5ea720 
<_IO_2_1_stdout_>, data=, n=8192) at fileops.c:1323
#5  0x7f6a2a28651b in __GI__IO_fwrite (buf=buf@entry=0x55af213d57b0, 
size=size@entry=1, count=count@entry=8192, fp=0x7f6a2a5ea720 <_IO_2_1_stdout_>) 
at iofwrite.c:39
#6  0x7f6a2a5f31ec in func_fp_write (cookie=0x55af213d5730, 
buffer=0x55af213d57b0, size=8192) at ../../src/estream.c:1523
#7  0x7f6a2a5f2b18 in flush_stream (stream=stream@entry=0x55af213d5750) at 
../../src/estream.c:1965
#8  0x7f6a2a5f3108 in es_write_fbf (stream=stream@entry=0x55af213d5750, 
buffer=buffer@entry=0x55af213fc8f0 "**REDACTED**", 
bytes_to_write=bytes_to_write@entry=32768, 
bytes_written=bytes_written@entry=0x7fffb74c6d30) at ../../src/estream.c:2711
#9  0x7f6a2a5f4313 in es_writen (stream=stream@entry=0x55af213d5750, 
buffer=buffer@entry=0x55af213fc8f0, bytes_to_write=32768, 
bytes_written=bytes_written@entry=0x7fffb74c6da0)
at ../../src/estream.c:2813
#10 0x7f6a2a5f5fac in _gpgrt_fwrite (ptr=ptr@entry=0x55af213fc8f0, 
size=size@entry=1, nitems=nitems@entry=32768, stream=0x55af213d5750) at 
../../src/estream.c:4221
#11 0x7f6a2a5fae35 in gpgrt_fwrite (ptr=ptr@entry=0x55af213fc8f0, 
size=size@entry=1, nitems=nitems@entry=32768, stream=) at 
../../src/visibility.c:466
#12 0x55af1f4b53a2 in handle_plaintext (pt=pt@entry=0x55af213dbbb0, 
mfx=mfx@entry=0x55af213efcd0, nooutput=, 
clearsig=clearsig@entry=0) at ../../g10/plaintext.c:426
#13 0x55af1f4a0ddc in proc_plaintext (c=c@entry=0x55af213efcb0, 
pkt=pkt@entry=0x55af213efd60) at ../../g10/mainproc.c:760
#14 0x55af1f4a3d7b in do_proc_packets (ctrl=0x55af213dbb30, 
c=0x55af213efcb0, a=0x55af213e72a0) at ../../g10/mainproc.c:1412
#15 0x55af1f4a3f0a in proc_packets (ctrl=ctrl@entry=0x55af213dbb30, 
anchor=anchor@entry=0x55af213edaf0, a=0x55af213e72a0) at 
../../g10/mainproc.c:1181
#16 0x55af1f492aaf in handle_compressed (ctrl=0x55af213dbb30, 
procctx=procctx@entry=0x55af213edaf0, cd=0x55af213edba0, 
callback=callback@entry=0x0, passthru=passthru@entry=0x0)
at ../../g10/compress.c:324
#17 0x55af1f4a1070 in proc_compressed (c=c@entry=0x55af213edaf0, 
pkt=pkt@entry=0x55af213dcd90) at ../../g10/mainproc.c:819
#18 0x55af1f4a3c9b in do_proc_packets (ctrl=0x55af213dbb30, 
c=0x55af213edaf0, a=0x55af213e72a0) at ../../g10/mainproc.c:1413
#19 0x55af1f4a3f0a in proc_packets (ctrl=ctrl@entry=0x55af213dbb30, 
anchor=anchor@entry=0x55af213e9340, a=0x55af213e72a0) at 
../../g10/mainproc.c:1181
#20 0x55af1f4c355d in decrypt_data (ctrl=0x55af213dbb30, 
procctx=procctx@entry=0x55af213e9340, ed=0x55af213dcdd0, dek=0x7f6a2b8bb118) at 
../../g10/decrypt-data.c:253
#21 0x55af1f4a07f8 in proc_encrypted (c=c@entry=0x55af213e9340, 
pkt=pkt@entry=0x55af213dce10) at ../../g10/mainproc.c:603
#22 0x55af1f4a3d0b in do_proc_packets (ctrl=0x55af213dbb30, 
c=0x55af213e9340, a=0x55af213e72a0) at ../../g10/mainproc.c:1411
#23 0x55af1f4a4181 in proc_encryption_packets 
(ctrl=ctrl@entry=0x55af213dbb30, anchor=anchor@entry=0x0, 
a=a@entry=0x55af213e72a0) at ../../g10/mainproc.c:1280
#24 0x55af1f4c21bb in decrypt_message (ctrl=0x55af213dbb30, 
filename=) at ../../g10/decrypt.c:88
#25 0x55af1f4810d0 in main (argc=, argv=) at 
../../g10/gpg.c:4045


I have redacted the write buffer contents but it is clear, IMHO, that it has 
deciphered some file and is trying to write it into the communication pipe 
Duplicity has established. I can't find it in the code **is it possible that 
Duplicity is not consuming the GPG output thus GPG never exits this threads 
waiting to `pthread_join()` after `wait()` are stuck thus no more threads can 
be started at some point?**

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Confirmed
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 

[Desktop-packages] [Bug 1731631] Re: KeyError: 56

[Václav Haisman]

** Tags added: artful

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

Title:
   KeyError: 56

Status in duplicity package in Ubuntu:
  New

Bug description:
  Last run of Deja-dup has ended up with the following error:

  Traceback (innermost last):
File "/usr/bin/duplicity", line 1559, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1545, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1394, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1473, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 729, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 765, in get_fileobj_iter
  backup_set.volume_name_dict[vol_num],
   KeyError: 56

  This is with 0.7.14+bzr1336-0ubuntu3~ubuntu17.10.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1731631/+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 1731631] [NEW] KeyError: 56

[Václav Haisman]

Public bug reported:

Last run of Deja-dup has ended up with the following error:

Traceback (innermost last):
  File "/usr/bin/duplicity", line 1559, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1545, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1394, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1473, in do_backup
restore(col_stats)
  File "/usr/bin/duplicity", line 729, in restore
restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in 
Write_ROPaths
for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in 
integrate_patch_iters
for patch_seq in collated:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
setrorps(overflow, elems)
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
elems[i] = iter_list[i].next()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
for path in path_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
tarinfo_list = [tar_iter.next()]
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
self.set_tarfile()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
self.current_fp = self.fileobj_iter.next()
  File "/usr/bin/duplicity", line 765, in get_fileobj_iter
backup_set.volume_name_dict[vol_num],
 KeyError: 56

This is with 0.7.14+bzr1336-0ubuntu3~ubuntu17.10.1.

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


** Tags: artful

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

Title:
   KeyError: 56

Status in duplicity package in Ubuntu:
  New

Bug description:
  Last run of Deja-dup has ended up with the following error:

  Traceback (innermost last):
File "/usr/bin/duplicity", line 1559, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1545, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1394, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1473, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 729, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 765, in get_fileobj_iter
  backup_set.volume_name_dict[vol_num],
   KeyError: 56

  This is with 0.7.14+bzr1336-0ubuntu3~ubuntu17.10.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1731631/+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 1694329] Re: oversized "characters" when Noto Color Emoji font is used on a page

[Václav Haisman]

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1694329/+attachment/4885854/+files/JournalErrors.txt

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

Title:
  oversized "characters" when Noto Color Emoji font is used on a page

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  I am seeing oversized emoji characters. See a duck in attached
  screenshot. This duck is from Noto Color Emoji font. In previous
  releases of Firefox it worked fine. It also works fine on Firefox for
  Windows. You can test it yourself if you have the font by visiting
  this URL:
  http://chat.stackexchange.com/transcript/message/37722474#37722474

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-lowlatency 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
  Uname: Linux 4.10.0-21-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon May 29 22:07:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf2fd7df-da6e-4e8b-876e-c91fa967ae41
  InstallationDate: Installed on 2011-11-13 (2024 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-790XTA-UD4
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-lowlatency 
root=UUID=503b3cdd-770e-4354-bf3d-c917a2ebe292 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw elevator=cfq nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-lowlatency N/A
   linux-backports-modules-4.10.0-21-lowlatency  N/A
   linux-firmware1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (43 days ago)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-790XTA-UD4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XTA-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XTA-UD4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-790XTA-UD4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1694329/+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 1727653] Re: error: can't start new thread

[Václav Haisman]

I have bumped the file limit to 8k from 4k for last night's backup and
still got the same error.

I am not sure how to run this in verbose mode. I am using it through
deja-dup and its plugin that runs the backup every night.

What confuses me are the hanging gpg processes that I have reported
about in
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1728720. Why
would that be happening?

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

Title:
  error: can't start new thread

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

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1727653] Re: error: can't start new thread

[Václav Haisman]

I have tested with 0.7.14+bzr1335-0ubuntu3~ubuntu17.10.1 and it still
fails the same.

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

Title:
  error: can't start new thread

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

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1727653] Re: error: can't start new thread

[Václav Haisman]

Re #8: Is there a PPA for that?

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

Title:
  error: can't start new thread

Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1727653/+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 1728720] Re: error: can't start new thread

[Václav Haisman]

The process seems to be stuck at this state for some time:

23574 ?SLl   35:08 deja-dup --backup --auto
24687 ?Ssl4:30  \_ /usr/bin/python /usr/bin/duplicity restore --gio 
--file-to-restore=home/wilx/.cache/deja-dup/metadata --force 
ftp://wilx@10.0.0.3/wilx/backup.amber2 /home/wilx/.cache/deja-dup/metadata 
--verbosity=9 --gpg-options=--no-use-agent 
--archive-dir=/home/wilx/.cache/deja-dup --tempdir=/tmp --log-fd=19
24998 ?SL 0:00  \_ gpg --status-fd 11 --passphrase-fd 20 
--logger-fd 9 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback 
--no-use-agent --decrypt
25001 ?SL 0:00  \_ gpg --status-fd 20 --passphrase-fd 24 
--logger-fd 12 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback 
--no-use-agent --decrypt
25004 ?SL 0:01  \_ gpg --status-fd 24 --passphrase-fd 28 
--logger-fd 21 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback 
--no-use-agent --decrypt
25007 ?SL 0:00  \_ gpg --status-fd 28 --passphrase-fd 32 
--logger-fd 25 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback 
--no-use-agent --decrypt
25010 ?SL 0:00  \_ gpg --status-fd 32 --passphrase-fd 36 
--logger-fd 29 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback 
--no-use-agent --decrypt
25013 ?SL 0:01  \_ gpg --status-fd 36 --passphrase-fd 40 
--logger-fd 33 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback 
--no-use-agent --decrypt
25016 ?SL 0:00  \_ gpg --status-fd 40 --passphrase-fd 44 
--logger-fd 37 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback 
--no-use-agent --decrypt
25019 ?SL 0:00  \_ gpg --status-fd 44 --passphrase-fd 48 
--logger-fd 41 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback 
--no-use-agent --decrypt
25021 ?SL 0:00  \_ gpg --status-fd 48 --passphrase-fd 52 
--logger-fd 45 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback 
--no-use-agent --decrypt

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

Title:
  error: can't start new thread

Status in Déjà Dup:
  New
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Deja-dup ends up with the following error (possibly a duplicity
  issue?):

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  

[Desktop-packages] [Bug 1728720] [NEW] error: can't start new thread

[Václav Haisman]

Public bug reported:

Deja-dup ends up with the following error (possibly a duplicity issue?):

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1546, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
  File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
for patch_seq in collated:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
setrorps(overflow, elems)
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
elems[i] = iter_list[i].next()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
for path in path_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
tarinfo_list = [tar_iter.next()]
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
self.set_tarfile()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
self.current_fp = self.fileobj_iter.next()
  File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
  File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
  File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
  File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
  File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
'logger': self.logger_fp})
  File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 374, 
in run
create_fhs, attach_fhs)
  File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 420, 
in _attach_fork_exec
process.thread.start()
  File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: deja-dup 36.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Oct 30 22:16:00 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/deja-dup
InstallationDate: Installed on 2011-11-13 (2178 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to artful on 2017-10-28 (2 days ago)

** Affects: deja-dup
 Importance: Undecided
 Status: New

** Affects: duplicity
 Importance: Undecided
 Status: New

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug artful

** Also affects: deja-dup
   Importance: Undecided
   Status: New

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

** Also affects: duplicity
   Importance: Undecided
   Status: New

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/duplicity/+bug/1728720/+attachment/5000437/+files/JournalErrors.txt

** Attachment removed: "XsessionErrors.txt"
   
https://bugs.launchpad.net/duplicity/+bug/1728720/+attachment/5000442/+files/XsessionErrors.txt

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

Title:
  error: can't start new thread

Status in Déjà Dup:
  New
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Deja-dup ends up with the following error (possibly a duplicity
  issue?):

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, 

[Desktop-packages] [Bug 1660353] Re: thumbnails disappear when scrolling in thumbnails pane

[Václav Haisman]

I still see this with Evince 3.24.0 on Zesty.

** Tags added: zesty

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

Title:
  thumbnails disappear when scrolling in thumbnails pane

Status in Evince:
  Fix Released
Status in evince package in Ubuntu:
  Triaged

Bug description:
  1. open a many-page (at least 15 pages) document
  2. open the thumbnails pane
  3. click on a thumbnail
  4. scroll up and down until the thumbnails (including outlines disappear)

  Obviously, we expect for the thumbnails to stay visible.  To make then
  visible again, move the pointer to the main document window, and then
  back to the thumbnails. Each one will reappear as you move the pointer
  over it.

  This is not the same as bug 1369028 as evince does not hang.
  This is not the same as bug 1629633, as there is still a thumbnail border for 
that document, and under no circumstances will the thumbnail appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: evince 3.22.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 30 15:36:40 2017
  InstallationDate: Installed on 2014-10-13 (840 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  SourcePackage: evince
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (108 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1660353/+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 1694329] Re: oversized "characters" when Noto Color Emoji font is used on a page

[Václav Haisman]

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1694329/+attachment/4885851/+files/CRDA.txt

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

Title:
  oversized "characters" when Noto Color Emoji font is used on a page

Status in firefox package in Ubuntu:
  New

Bug description:
  I am seeing oversized emoji characters. See a duck in attached
  screenshot. This duck is from Noto Color Emoji font. In previous
  releases of Firefox it worked fine. It also works fine on Firefox for
  Windows. You can test it yourself if you have the font by visiting
  this URL:
  http://chat.stackexchange.com/transcript/message/37722474#37722474

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-lowlatency 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
  Uname: Linux 4.10.0-21-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon May 29 22:07:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf2fd7df-da6e-4e8b-876e-c91fa967ae41
  InstallationDate: Installed on 2011-11-13 (2024 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-790XTA-UD4
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-lowlatency 
root=UUID=503b3cdd-770e-4354-bf3d-c917a2ebe292 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw elevator=cfq nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-lowlatency N/A
   linux-backports-modules-4.10.0-21-lowlatency  N/A
   linux-firmware1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (43 days ago)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-790XTA-UD4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XTA-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XTA-UD4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-790XTA-UD4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1694329/+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 1694329] [NEW] oversized "characters" when Noto Color Emoji font is used on a page

[Václav Haisman]

Public bug reported:

I am seeing oversized emoji characters. See a duck in attached
screenshot. This duck is from Noto Color Emoji font. In previous
releases of Firefox it worked fine. It also works fine on Firefox for
Windows. You can test it yourself if you have the font by visiting this
URL: http://chat.stackexchange.com/transcript/message/37722474#37722474

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-21-lowlatency 4.10.0-21.23
ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
Uname: Linux 4.10.0-21-lowlatency x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Mon May 29 22:07:30 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=cf2fd7df-da6e-4e8b-876e-c91fa967ae41
InstallationDate: Installed on 2011-11-13 (2024 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-790XTA-UD4
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-lowlatency 
root=UUID=503b3cdd-770e-4354-bf3d-c917a2ebe292 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw elevator=cfq nomdmonddf nomdmonisw nomdmonddf nomdmonisw
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-21-lowlatency N/A
 linux-backports-modules-4.10.0-21-lowlatency  N/A
 linux-firmware1.164.1
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-16 (43 days ago)
dmi.bios.date: 12/03/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-790XTA-UD4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XTA-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XTA-UD4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-790XTA-UD4
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug zesty

** Attachment added: "screenshot of oversized emoji"
   
https://bugs.launchpad.net/bugs/1694329/+attachment/4885848/+files/Screenshot_2017-05-29_22-14-13.png

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

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1694329/+attachment/4885862/+files/WifiSyslog.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1694329/+attachment/4885861/+files/UdevDb.txt

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1694329/+attachment/4885849/+files/AlsaInfo.txt

** Attachment removed: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1694329/+attachment/4885850/+files/AudioDevicesInUse.txt

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

Title:
  oversized "characters" when Noto Color Emoji font is used on a page

Status in firefox package in Ubuntu:
  New

Bug description:
  I am seeing oversized emoji characters. See a duck in attached
  screenshot. This duck is from Noto Color Emoji font. In previous
  releases of Firefox it worked fine. It also works fine on Firefox for
  Windows. You can test it yourself if you have the font by visiting
  this URL:
  http://chat.stackexchange.com/transcript/message/37722474#37722474

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-lowlatency 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
  Uname: Linux 4.10.0-21-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon May 29 22:07:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf2fd7df-da6e-4e8b-876e-c91fa967ae41
  InstallationDate: Installed on 2011-11-13 (2024 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-790XTA-UD4
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-lowlatency 
root=UUID=503b3cdd-770e-4354-bf3d-c917a2ebe292 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw elevator=cfq nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   

[Desktop-packages] [Bug 1590580] Re: Noto CJK font issue with LuaLaTeX

[Václav Haisman]

** Project changed: luatex => texlive-base (Ubuntu)

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

Title:
  Noto CJK font issue with LuaLaTeX

Status in texlive-base package in Ubuntu:
  New

Bug description:
  I am seeing an issue with NotoSansCJK-Regular.ttc when I try to use it
  in LuaLaTeX:

  https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1590580/+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 1590580] Re: Noto CJK font issue with LuaLaTeX

[Václav Haisman]

** No longer affects: fonts-noto-cjk (Ubuntu)

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

Title:
  Noto CJK font issue with LuaLaTeX

Status in luatex:
  New

Bug description:
  I am seeing an issue with NotoSansCJK-Regular.ttc when I try to use it
  in LuaLaTeX:

  https://bugs.launchpad.net/luatex/+bug/1590580/+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 1590580] Re: Noto CJK font issue with LuaLaTeX

[Václav Haisman]

** Also affects: luatex
   Importance: Undecided
   Status: New

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

Title:
  Noto CJK font issue with LuaLaTeX

Status in luatex:
  New
Status in fonts-noto-cjk package in Ubuntu:
  Incomplete

Bug description:
  I am seeing an issue with NotoSansCJK-Regular.ttc when I try to use it
  in LuaLaTeX:

  https://bugs.launchpad.net/luatex/+bug/1590580/+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 1590580] Re: Noto CJK font issue with LuaLaTeX

[Václav Haisman]

@gunnarhj: This is the LuaLaTeX I am using:

This is LuaTeX, Version beta-0.80.0 (TeX Live 2015/Debian) (rev 5238)

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

Title:
  Noto CJK font issue with LuaLaTeX

Status in luatex:
  New
Status in fonts-noto-cjk package in Ubuntu:
  Incomplete

Bug description:
  I am seeing an issue with NotoSansCJK-Regular.ttc when I try to use it
  in LuaLaTeX:

  https://bugs.launchpad.net/luatex/+bug/1590580/+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 1590580] [NEW] Noto CJK font issue with LuaLaTeX

[Václav Haisman]

Public bug reported:

I am seeing an issue with NotoSansCJK-Regular.ttc when I try to use it
in LuaLaTeX:

https://bugs.launchpad.net/bugs/1590580

Title:
  Noto CJK font issue with LuaLaTeX

Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  I am seeing an issue with NotoSansCJK-Regular.ttc when I try to use it
  in LuaLaTeX:

  https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1590580/+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 1553562] [NEW] Chromium gets stuck after some time of inattention.

[Václav Haisman]

Public bug reported:

It gets stuck or hangs. Its windows stop refreshing GUI or rendering
pages. All of the processes are still there.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: chromium-browser 48.0.2564.116-0ubuntu0.15.10.1.1221
ProcVersionSignature: Ubuntu 4.2.0-23.28-lowlatency 4.2.6
Uname: Linux 4.2.0-23-lowlatency x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
DRM.card0.HDMI.A.1:
 edid-base64: 
AP///wAmzS5WKwkAAC8ZAQOAMh14KgZVpVVRoSgPUFSla4BxAIFAgYCpQLMAlQDRwAEBAjqAGHE4LUBYLEUA8CQRAAAe/wAxMTMyNDU0NzIyMzQ3/QA3TB5TEQAKICAgICAg/ABQTDIyODNICiAgICAgAT0CAyLxT5AFBAMCARESExQGBxUWHyMJBwGDAQAAZQMMABAAAjqAGHE4LUBYLEUAEyshAAAfAR2A0HIcFiAQLCWAEyshAACeAR0AvFLQHiC4KFVAEyshAAAejArQkCBAMSAMQFUAEyshAAAYAjqA0HI4LUAQLEWAEyshAAAe0A==
 dpms: On
 modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 
1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1152x864 1280x720 
1280x720 1280x720 1152x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400
 enabled: enabled
 status: connected
DRM.card0.VGA.1:
 edid-base64: 
 dpms: Off
 modes: 
 enabled: disabled
 status: disconnected
Date: Sat Mar  5 18:42:05 2016
Desktop-Session:
 'None'
 'None'
 'None'
DetectedPlugins:
 
EcryptfsInUse: Yes
Env:
 'None'
 'None'
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2011-11-13 (1574 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Load-Avg-1min: 1.71
Load-Processes-Running-Percent:   0.1%
MachineType: Gigabyte Technology Co., Ltd. GA-790XTA-UD4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-lowlatency 
root=UUID=503b3cdd-770e-4354-bf3d-c917a2ebe292 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw elevator=cfq nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to wily on 2015-10-24 (133 days ago)
dmi.bios.date: 12/03/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-790XTA-UD4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XTA-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XTA-UD4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-790XTA-UD4
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2014-10-25T05:36:44

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


** Tags: amd64 apport-bug wily

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

Title:
  Chromium gets stuck after some time of inattention.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  It gets stuck or hangs. Its windows stop refreshing GUI or rendering
  pages. All of the processes are still there.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: chromium-browser 48.0.2564.116-0ubuntu0.15.10.1.1221
  ProcVersionSignature: Ubuntu 4.2.0-23.28-lowlatency 4.2.6
  Uname: Linux 4.2.0-23-lowlatency x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0.HDMI.A.1:
   edid-base64: 
AP///wAmzS5WKwkAAC8ZAQOAMh14KgZVpVVRoSgPUFSla4BxAIFAgYCpQLMAlQDRwAEBAjqAGHE4LUBYLEUA8CQRAAAe/wAxMTMyNDU0NzIyMzQ3/QA3TB5TEQAKICAgICAg/ABQTDIyODNICiAgICAgAT0CAyLxT5AFBAMCARESExQGBxUWHyMJBwGDAQAAZQMMABAAAjqAGHE4LUBYLEUAEyshAAAfAR2A0HIcFiAQLCWAEyshAACeAR0AvFLQHiC4KFVAEyshAAAejArQkCBAMSAMQFUAEyshAAAYAjqA0HI4LUAQLEWAEyshAAAe0A==
   dpms: On
   modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 
1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1152x864 1280x720 
1280x720 1280x720 1152x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0.VGA.1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  Date: Sat Mar  5 18:42:05 2016
  Desktop-Session:
   'None'
   'None'
   'None'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
 

[Desktop-packages] [Bug 1520435] [NEW] Unwanted super thick borders in Xubuntu 15.10

[Václav Haisman]

Public bug reported:

I am seeing very thick borders around dialogue windows of Gtk+
applications. This started with upgrade to Wily. I do not have any local
themes installed - i.e. no themes in `~/.themes`.

Description:Ubuntu 15.10
Release:15.10

libgtk-3-0:
  Installed: 3.16.7-0ubuntu3

Cf. http://askubuntu.com/questions/697386/unwanted-super-thick-borders-
in-xubuntu-15-10

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "screenshot showing the issue"
   
https://bugs.launchpad.net/bugs/1520435/+attachment/4526171/+files/Screenshot_2015-11-05_22-08-49.png

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

Title:
  Unwanted super thick borders in Xubuntu 15.10

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I am seeing very thick borders around dialogue windows of Gtk+
  applications. This started with upgrade to Wily. I do not have any
  local themes installed - i.e. no themes in `~/.themes`.

  Description:  Ubuntu 15.10
  Release:  15.10

  libgtk-3-0:
Installed: 3.16.7-0ubuntu3

  Cf. http://askubuntu.com/questions/697386/unwanted-super-thick-
  borders-in-xubuntu-15-10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1520435/+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 1512056] Re: Firefox continuously crashes when scrolling FaceBook pages

[Václav Haisman]

I am seeing this on Wily as well. Additionally, this might be unrelated,
sometimes, on youtube, video is black (sound works) when it switches to
_HD_, fullscreen or windowed.

** Tags added: wily

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

Title:
  Firefox continuously crashes when scrolling FaceBook pages

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Sir,
  Firefox crashes either in standard or in Safe Mode when I browse FaceBook 
pages.

  This happens since some weeks back updates, and it has not been fixed
  yet.

  I'm running Ubuntu 14.04.3 LTS Trusty 64 bit with GNOME Fallback GUI
  on AMD Athlon 64 X2 Dual Core 5000+ CPU with 4GB Ram.

  Many thanks for your feedback.
  Regards
  Mauro

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 41.0.2+build2-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marenzi1869 F pulseaudio
  BuildID: 20151015172900
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun Nov  1 06:44:21 2015
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-17 (562 days ago)
  InstallationMedia:
   
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.106  metric 
1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MostRecentCrashID: bp-ea0ab317-e8ba-4bf0-8508-140852150824
  PciNetwork:
   
  PrefSources:
   prefs.js
   
[Profile]/extensions/FasterFox_Lite@BigRedBrent/defaults/preferences/fasterfoxlite.js
   
[Profile]/extensions/{EF522540-89F5-46b9-B6FE-1829E2B572C6}/defaults/preferences/prefs.js
  Profiles: Profile0 (Default) - LastVersion=41.0.2/20151015172900 (In use)
  RelatedPackageVersions:
   totem-mozilla 3.10.1-1ubuntu4
   rhythmbox-mozilla 3.0.2-0ubuntu2
   gnome-shell   3.10.4-0ubuntu5.2
   google-talkplugin 5.41.0.0-1
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd03/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1512056/+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 1405380] Re: evince crashed with SIGSEGV in INT_cairo_surface_set_device_scale()

[Václav Haisman]

** Tags added: wily

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

Title:
  evince crashed with SIGSEGV in INT_cairo_surface_set_device_scale()

Status in Evince:
  Unknown
Status in evince package in Ubuntu:
  Triaged

Bug description:
  Evince crashed after about 10 minutes printing to file PDF with the
  attached. The next time I printed it took 2 hours so it is
  intermittenly reproducible.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: evince 3.14.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 24 01:00:32 2014
  ExecutablePath: /usr/bin/evince
  ExecutableTimestamp: 1413470384
  InstallationDate: Installed on 2014-12-14 (10 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141213)
  ProcCmdline: evince /home/name/Desktop/grammar4.ps
  ProcCwd: /home/name
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f8734828a08 : 
mov0x1c(%rdi),%r9d
   PC (0x7f8734828a08) ok
   source "0x1c(%rdi)" (0x001c) not located in a known VMA region (needed 
readable region)!
   destination "%r9d" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evince
  StacktraceTop:
   INT_cairo_surface_set_device_scale (surface=0x0, sx=1, sy=1) at 
/build/buildd/cairo-1.13.0~20140204/src/cairo-surface.c:1676
   set_device_scale_on_surface (device_scale=, 
surface=) at 
/build/buildd/evince-3.14.1/./libview/ev-pixbuf-cache.c:273
   copy_job_to_job_info (job_render=job_render@entry=0x1a27010, 
job_info=job_info@entry=0x154df00, pixbuf_cache=pixbuf_cache@entry=0x1427340) 
at /build/buildd/evince-3.14.1/./libview/ev-pixbuf-cache.c:288
   job_finished_cb (job=, pixbuf_cache=0x1427340) at 
/build/buildd/evince-3.14.1/./libview/ev-pixbuf-cache.c:340
   _g_closure_invoke_va (closure=0x0, closure@entry=0x19187d0, 
return_value=return_value@entry=0x0, instance=0x0, instance@entry=0x1a27010, 
args=0x7f8714021c30, args@entry=0x7fff7e9903d0, n_params=0, 
param_types=0x7f8714021760) at 
/build/buildd/glib2.0-2.43.2/./gobject/gclosure.c:831
  Title: evince crashed with SIGSEGV in INT_cairo_surface_set_device_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1405380/+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 586528] Re: keyboard doesn't work after screensaver shuts down the monitor

[Václav Haisman]

@Lysenko: FFS, there was somebody else commenting on this issues this
month. The bug is still the same, there is nothing else to add to this.
The reproduction scenario is still the same.

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

Title:
  keyboard doesn't work after screensaver shuts down the monitor

Status in gnome-screensaver package in Ubuntu:
  Confirmed
Status in xscreensaver package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  The keyboard doesn't work when I return to work on the computer after
  a few minutes, long enough for the screen to go blank.

  To reproduce: 
  Don't touch the keyboard nor mouse for a while.
  After the first 5 minutes, the screensaver kicks in (matrix).
  On minute 10, the screen goes blank.
  Wait a few more minutes.
  Move the mouse or press a key to keep working.

  Just type something in the window you have already opened you'll
  notice that the active window does not receive any keyboard input, and
  you can't even press alt-tab to switch to another window.

  Of course, i expect the keyboard to work as usual but it does not.

  Here, when the keyboard doesn't work, you can switch to another window
  using the mouse and the keyboard will return to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-screensaver 2.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu May 27 14:47:06 2010
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_PE.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  WindowManager: gnome-wm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528/+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 586528] Re: keyboard doesn't work after screensaver shuts down the monitor

[Václav Haisman]

I am on 15.04. That it does not happen to you does not mean it does not
happen to others.

** Changed in: gnome-screensaver (Ubuntu)
   Status: Invalid => Confirmed

** Changed in: xscreensaver (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  keyboard doesn't work after screensaver shuts down the monitor

Status in gnome-screensaver package in Ubuntu:
  Confirmed
Status in xscreensaver package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  The keyboard doesn't work when I return to work on the computer after
  a few minutes, long enough for the screen to go blank.

  To reproduce: 
  Don't touch the keyboard nor mouse for a while.
  After the first 5 minutes, the screensaver kicks in (matrix).
  On minute 10, the screen goes blank.
  Wait a few more minutes.
  Move the mouse or press a key to keep working.

  Just type something in the window you have already opened you'll
  notice that the active window does not receive any keyboard input, and
  you can't even press alt-tab to switch to another window.

  Of course, i expect the keyboard to work as usual but it does not.

  Here, when the keyboard doesn't work, you can switch to another window
  using the mouse and the keyboard will return to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-screensaver 2.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu May 27 14:47:06 2010
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_PE.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  WindowManager: gnome-wm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528/+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 586528] Re: keyboard doesn't work after screensaver shuts down the monitor

[Václav Haisman]

@Lysenko: 22 people confirmed this. There are 2 duplicates attached to
this bug report and then there is  #1483868 that I was requested to fill
separately. Yet, you want to close this bug. Are you for real? I have
nothing more to say, except expletives.

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

Title:
  keyboard doesn't work after screensaver shuts down the monitor

Status in gnome-screensaver package in Ubuntu:
  Confirmed
Status in xscreensaver package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  The keyboard doesn't work when I return to work on the computer after
  a few minutes, long enough for the screen to go blank.

  To reproduce: 
  Don't touch the keyboard nor mouse for a while.
  After the first 5 minutes, the screensaver kicks in (matrix).
  On minute 10, the screen goes blank.
  Wait a few more minutes.
  Move the mouse or press a key to keep working.

  Just type something in the window you have already opened you'll
  notice that the active window does not receive any keyboard input, and
  you can't even press alt-tab to switch to another window.

  Of course, i expect the keyboard to work as usual but it does not.

  Here, when the keyboard doesn't work, you can switch to another window
  using the mouse and the keyboard will return to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-screensaver 2.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu May 27 14:47:06 2010
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_PE.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  WindowManager: gnome-wm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528/+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 586528] Re: keyboard doesn't work after screensaver shuts down the monitor

[Václav Haisman]

I have one more bit of information to add. I have just logged in and
clicked into and Emacs X11 window. The cursor in Emacs moved to the
place I have clicked onto but it stayed unfilled which means the Emacs
X11 window does not have focus. So, it seems like this whole issue has
something to do with focus.

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

Title:
  keyboard doesn't work after screensaver shuts down the monitor

Status in gnome-screensaver package in Ubuntu:
  Incomplete
Status in xscreensaver package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: gnome-screensaver

  The keyboard doesn't work when I return to work on the computer after
  a few minutes, long enough for the screen to go blank.

  To reproduce: 
  Don't touch the keyboard nor mouse for a while.
  After the first 5 minutes, the screensaver kicks in (matrix).
  On minute 10, the screen goes blank.
  Wait a few more minutes.
  Move the mouse or press a key to keep working.

  Just type something in the window you have already opened you'll
  notice that the active window does not receive any keyboard input, and
  you can't even press alt-tab to switch to another window.

  Of course, i expect the keyboard to work as usual but it does not.

  Here, when the keyboard doesn't work, you can switch to another window
  using the mouse and the keyboard will return to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-screensaver 2.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu May 27 14:47:06 2010
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_PE.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  WindowManager: gnome-wm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528/+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 1483868] Re: keyboard doesn't work after xscreensaver shuts down the monitor

[Václav Haisman]

I have one more bit of information to add. I have just logged in and
clicked into and Emacs X11 window. The cursor in Emacs moved to the
place I have clicked onto but it stayed unfilled which means the Emacs
X11 window does not have focus. So, it seems like this whole issue has
something to do with focus.

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

Title:
  keyboard doesn't work after xscreensaver shuts down the monitor

Status in xscreensaver package in Ubuntu:
  New

Bug description:
  I am experiencing the same symptoms as described in
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  screensaver/+bug/586528. This bug report is new on request.

  I run Xubuntu with XFCE, xscreensaver and Light Locker. Recently,
  whenever I log back (twice, once through locker and once through
  xscreensaver), the X11 applications are not accepting keyboard input.
  I can switch desktops using keyboard shortcuts, though. What fixes the
  issue for me is switching into a Terminal window. Then the keyboard
  input start working.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xscreensaver 5.30-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-lowlatency 3.19.8-ckt2
  Uname: Linux 3.19.0-25-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Aug 11 21:23:04 2015
  InstallationDate: Installed on 2011-11-13 (1367 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: xscreensaver
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (108 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1483868/+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 586528] Re: keyboard doesn't work after screensaver shuts down the monitor

[Václav Haisman]

For cross reference:  #1483868.

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

Title:
  keyboard doesn't work after screensaver shuts down the monitor

Status in gnome-screensaver package in Ubuntu:
  Incomplete
Status in xscreensaver package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: gnome-screensaver

  The keyboard doesn't work when I return to work on the computer after
  a few minutes, long enough for the screen to go blank.

  To reproduce: 
  Don't touch the keyboard nor mouse for a while.
  After the first 5 minutes, the screensaver kicks in (matrix).
  On minute 10, the screen goes blank.
  Wait a few more minutes.
  Move the mouse or press a key to keep working.

  Just type something in the window you have already opened you'll
  notice that the active window does not receive any keyboard input, and
  you can't even press alt-tab to switch to another window.

  Of course, i expect the keyboard to work as usual but it does not.

  Here, when the keyboard doesn't work, you can switch to another window
  using the mouse and the keyboard will return to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-screensaver 2.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu May 27 14:47:06 2010
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_PE.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  WindowManager: gnome-wm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528/+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 1483868] [NEW] keyboard doesn't work after xscreensaver shuts down the monitor

[Václav Haisman]

Public bug reported:

I am experiencing the same symptoms as described in
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528.
This bug report is new on request.

I run Xubuntu with XFCE, xscreensaver and Light Locker. Recently,
whenever I log back (twice, once through locker and once through
xscreensaver), the X11 applications are not accepting keyboard input. I
can switch desktops using keyboard shortcuts, though. What fixes the
issue for me is switching into a Terminal window. Then the keyboard
input start working.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xscreensaver 5.30-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-25.26-lowlatency 3.19.8-ckt2
Uname: Linux 3.19.0-25-lowlatency x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Aug 11 21:23:04 2015
InstallationDate: Installed on 2011-11-13 (1367 days ago)
InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
SourcePackage: xscreensaver
UpgradeStatus: Upgraded to vivid on 2015-04-25 (108 days ago)

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


** Tags: amd64 apport-bug vivid

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

Title:
  keyboard doesn't work after xscreensaver shuts down the monitor

Status in xscreensaver package in Ubuntu:
  New

Bug description:
  I am experiencing the same symptoms as described in
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  screensaver/+bug/586528. This bug report is new on request.

  I run Xubuntu with XFCE, xscreensaver and Light Locker. Recently,
  whenever I log back (twice, once through locker and once through
  xscreensaver), the X11 applications are not accepting keyboard input.
  I can switch desktops using keyboard shortcuts, though. What fixes the
  issue for me is switching into a Terminal window. Then the keyboard
  input start working.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xscreensaver 5.30-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-lowlatency 3.19.8-ckt2
  Uname: Linux 3.19.0-25-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Aug 11 21:23:04 2015
  InstallationDate: Installed on 2011-11-13 (1367 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: xscreensaver
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (108 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1483868/+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 586528] Re: keyboard doesn't work after screensaver shuts down the monitor

[Václav Haisman]

I am experiencing this in 15.04 Vivid. I use XFCE and xscreensaver and
xflock4.

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

** Tags added: vivid

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

Title:
  keyboard doesn't work after screensaver shuts down the monitor

Status in gnome-screensaver package in Ubuntu:
  Confirmed
Status in xscreensaver package in Ubuntu:
  New

Bug description:
  Binary package hint: gnome-screensaver

  The keyboard doesn't work when I return to work on the computer after
  a few minutes, long enough for the screen to go blank.

  To reproduce: 
  Don't touch the keyboard nor mouse for a while.
  After the first 5 minutes, the screensaver kicks in (matrix).
  On minute 10, the screen goes blank.
  Wait a few more minutes.
  Move the mouse or press a key to keep working.

  Just type something in the window you have already opened you'll
  notice that the active window does not receive any keyboard input, and
  you can't even press alt-tab to switch to another window.

  Of course, i expect the keyboard to work as usual but it does not.

  Here, when the keyboard doesn't work, you can switch to another window
  using the mouse and the keyboard will return to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-screensaver 2.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu May 27 14:47:06 2010
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_PE.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  WindowManager: gnome-wm

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