[Desktop-packages] [Bug 929067] Re: Crash during restore: "assert ropath.index == (), ropath.index"

2024-02-16 Thread Timothy Quinn
Just hit this bug on duplicity 0.8.23 on a modern FreeBSD PKG install.
Modern Debian apt package is 0.8.22 LOL. Now trying to get it installed
using python pip directly...

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

Title:
  Crash during restore: "assert ropath.index == (), ropath.index"

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

Bug description:
  Duplicity version: 0.6.15
  Python version: 2.7.2+
  OS: Ubuntu 11.10
  Target filesystem: Linux (Synology NAS, via sftp)

  I'm experiencing a repeatable crash which manifests itself on restore,
  when the initial backup is interrupted and resumed. The data I use
  doesn't seem to matter. Steps to reproduce:

  1. Create a directory of test data. Mine was around 125MiB
  2. duplicity --no-encryption TestDir ssh://user@target/backup/TestDir
  3. Wait until one or two tar files have been uploaded, then Ctrl-C to kill 
duplicity
  4. duplicity --no-encryption TestDir ssh://user@target/backup/TestDir 
(duplicity should resume the backup where it left off; allow it to complete 
this time)
  5. duplicity --no-encryption TestDir ssh://user@target/backup/TestDir (repeat 
the command a third time - note that duplicity reports a nonzero number of 
DeletedFiles even though the data has not changed.
  6. rm -r TestDir
  7. duplicity --no-encryption ssh://user@target/backup/TestDir TestDir 
(attempt to restore -> crash)

  The crash output is as follows:

  
  user@laptop:~$ duplicity --no-encryption ssh://user@target/backup/Test4 Test4
  Local and Remote metadata are synchronized, no sync needed.
  Last full backup date: Wed Feb  8 19:29:16 2012
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1359, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1342, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1276, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 591, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
Write_ROPaths
  ITR( ropath.index, ropath )
File "/usr/lib/python2.7/dist-packages/duplicity/lazy.py", line 320, in 
__call__
  self.process_w_branch(index, self.root_branch, args)
File "/usr/lib/python2.7/dist-packages/duplicity/lazy.py", line 293, in 
process_w_branch
  branch.start_process, args)
File "/usr/lib/python2.7/dist-packages/duplicity/robust.py", line 37, in 
check_common_error
  return function(*args)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 545, in 
start_process
  assert ropath.index == (), ropath.index
  AssertionError: somefile.dat

  
  I can provide more information, log output, test data (although the data 
doesn't seem to matter), or test with other versions of duplicity if requested.

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


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


[Desktop-packages] [Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available

2023-03-23 Thread Timothy Quinn
I've been having something similar with my 20.04 system. Every day,
whenever I leave my computer on but turn off displays, one of the three
monitors is locked at 640x480 when I power my monitors back on. It also
happened when power settings turned off displays automatically, which
I've subsequently disabled.

My GPU: Radeon RX6650 XT
Driver: xserver-xorg-video-amdgpu - 19.1.0-1ubuntu0.1

I've discovered a fix by going into Display Config and disable the bad
monitor. Once I re-enable.  I can the change its resolution to a proper
setting.

This is not an intermittent issue but happens like clockwork.

Should I open a different ticket for this?

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

Title:
  [amdgpu] Proper monitor resolution/refresh rate not available

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 
59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This 
problem appeared after plugging in my old monitor after 2 years again, it's a 
philips 272G5DYEB.  Things that I unsuccesfully tried to get a proper 
resolution:
  -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use 
different drivers: propritary and open source
  -Change resolution via xrandr addmode/newmode (leads to "no signal" from 
monitor)
  -Using "GRUB_GFXMODE" config in grub (no change)
  -Searching through logs, only useleful thing I found was in the Xorg log:
  [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0
  [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0
  [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9   25.18  640 656 752 800 
 480 490 492 525 -hsync -vsync (31.5 kHz e)
  -In Windows the resolution works fine
  -Both GPUs work fine with a different monitor
  I'm not sure how to proceed here nor do I know where the problem lies. I 
assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers 
lead to this problem making it unlikely to be a driver problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.4.0-050400-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 22:16:58 2020
  DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] [1002:0b36]
  InstallationDate: Installed on 2019-11-26 (173 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. MS-7A34
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic 
root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.LQ
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 PC MATE (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A34
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserv

[Desktop-packages] [Bug 1777925] [NEW] package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned

2018-06-20 Thread Timothy Quinn
Public bug reported:

installation error.

I'm new to linux so my knowledge of attaching additional information is
limited.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gnome-menus 3.13.3-11ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 20 14:03:44 2018
Dependencies:
 
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2018-06-10 (10 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: gnome-menus
Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-06-20 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  installation error.

  I'm new to linux so my knowledge of attaching additional information
  is limited.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-11ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Jun 20 14:03:44 2018
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-06-10 (10 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-06-20 (0 days ago)

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

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