Bug#976189: Bug 9761189 - How to fix
Hello Maintainer:
Came across this as well and did some digging to find the cause. Found that
Python 3.9 removed the getiterator attribute and replaced it with iter.
To fix, in file "/usr/lib/python3/dist-packages/catfish_lib/Builder.py" at
line 87 changed this line:
ele_widgets = tree.getiterator("object")
to
ele_widgets = tree.iter("object")
Also found one more line in the file needed to be changed (as I scanned to
see if "getiterator" was mentioned anywhere else in the file) and it's this
code at line 112:
ele_signals = tree.getiterator("signal")
Changed it to show:
ele_signals = tree.iter("signal")
Saved the original with .orig extension then saved changed file as
Builder.py.
Tested catfish again from terminal and it started right up and functioned
normally as I tested several searches. As I never did a patch diff before,
if anyone can create a patch from my notes here feel free to do so.
Cheers!
-R
Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work
Hi.
I have also been bitten by this bug, resolved by downgrading back to
chromium 66.0.3359.181-1 and then watching Youtube videos or using web
video chat applications worked again.
Hoping for a resolution soon enough.
Thanks,
R
On Thu, 31 May 2018 18:34:46 -0400 "Justin P." wrote:
> Package: chromium
> Version: 67.0.3396.62-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where
appropriate ***
>
> * What led up to the situation?
>
> Can't use video on youtube. Gif's no longer work. And I cannot get
media to play. This started after upgrading from 66.0.3359.181-1 to
67.0.3396.62-1
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> Reverting the package was the only solution I could find. It appears
the app build may be missing some flags in the build. I found this that
had similar errors to my situation
https://groups.google.com/a/chromium.org/forum/?nomobile=true#!msg/android-webview-dev/oVjyFhhxOQ8/ns8q9uPrCAAJ
>
> * What was the outcome of this action?
>
> chromium 66.0.3359.181-1 was reinstalled, video is working again.
>
> * What outcome did you expect instead?
>
> chromium 67.0.3396.62-1 video should work after install.
>
> Chromium Log while trying to play files
> [129:160:0531/181749.318090:ERROR:render_media_log.cc(30)]
MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context
failed"}
> [129:129:0531/181749.320645:ERROR:render_media_log.cc(30)]
MediaEvent: PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
> [129:160:0531/181749.352209:ERROR:render_media_log.cc(30)]
MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context
failed"}
> [129:129:0531/181749.354280:ERROR:render_media_log.cc(30)]
MediaEvent: PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
> [129:160:0531/181749.551754:ERROR:render_media_log.cc(30)]
MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization
failed"}
> [129:129:0531/181749.559473:ERROR:render_media_log.cc(30)]
MediaEvent: PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
> [129:160:0531/181750.431299:ERROR:render_media_log.cc(30)]
MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization
failed"}
> [129:129:0531/181750.433293:ERROR:render_media_log.cc(30)]
MediaEvent: PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
> libpng warning: iCCP: known incorrect sRGB profile
>
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages chromium depends on:
> ii chromium-common 67.0.3396.62-1
> ii libasound2 1.1.6-1
> ii libatk-bridge2.0-0 2.26.2-1
> ii libatk1.0-0 2.28.1-1
> ii libavcodec57 7:3.4.2-2+b1
> ii libavformat57 7:3.4.2-2+b1
> ii libavutil55 7:3.4.2-2+b1
> ii libc6 2.27-3
Bug#634051: wicd-daemon: Fails to install/upgrade if existing user is removed - bug still exists
With a recent dist-upgrade the problem still exists as noted below. I have purged all the wicd* packages and tried afresh but still fails to preconfigure wicd-daemon: ~$ sudo apt-get install wicd [sudo] password for ruser: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libxcb-render-util0 libtorrent13 libwebkit-1.0-2 libdirectfb-extra libthunar-vfs-1-common libnl1 libffmpegthumbnailer4 libgnome-desktop-2-17 fonts-droid libwebkit-1.0-common libthunar-vfs-1-2 Use 'apt-get autoremove' to remove them. The following extra packages will be installed: python-wicd wicd-daemon wicd-gtk The following NEW packages will be installed: python-wicd wicd wicd-daemon wicd-gtk 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 543 kB of archives. After this operation, 2,432 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://ftp.us.debian.org/debian/ unstable/main python-wicd all 1.7.0+ds1-7 [78.2 kB] Get:2 http://ftp.us.debian.org/debian/ unstable/main wicd-daemon all 1.7.0+ds1-7 [280 kB] Get:3 http://ftp.us.debian.org/debian/ unstable/main wicd-gtk all 1.7.0+ds1-7 [143 kB] Get:4 http://ftp.us.debian.org/debian/ unstable/main wicd all 1.7.0+ds1-7 [41.8 kB] Fetched 543 kB in 0s (599 kB/s) Preconfiguring packages ... wicd-daemon failed to preconfigure, with exit status 1 Selecting previously unselected package python-wicd. (Reading database ... 113161 files and directories currently installed.) Unpacking python-wicd (from .../python-wicd_1.7.0+ds1-7_all.deb) ... Selecting previously unselected package wicd-daemon. Unpacking wicd-daemon (from .../wicd-daemon_1.7.0+ds1-7_all.deb) ... Selecting previously unselected package wicd-gtk. Unpacking wicd-gtk (from .../wicd-gtk_1.7.0+ds1-7_all.deb) ... Selecting previously unselected package wicd. Unpacking wicd (from .../wicd_1.7.0+ds1-7_all.deb) ... Processing triggers for man-db ... Processing triggers for hicolor-icon-theme ... Processing triggers for menu ... Processing triggers for desktop-file-utils ... Setting up python-wicd (1.7.0+ds1-7) ... Setting up wicd-daemon (1.7.0+ds1-7) ... dpkg: error processing wicd-daemon (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of wicd-gtk:configured to not write apport reports wicd-gtk depends on wicd-daemon (= 1.7.0+ds1-7); however: Package wicd-daemon is not configured yet. dpkg: error processing wicd-gtk (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of wicd:configured to not write apport reports wicd depends on wicd-daemon (= 1.7.0+ds1-7); however: Package wicd-daemon is not configured yet. wicd depends on wicd-gtk (= 1.7.0+ds1-7) | wicd-curses (= 1.7.0+ds1-7) | wicd-cli (= 1.7.0+ds1-7) | wicd-client; however: Package wicd-gtk is not configured yet. Package wicd-curses is not installed. Package wicd-cli is not installed. Package wicd-client is not installed. Package wicd-gtk which provides wicd-client is not configured yet. dpkg: error processing wicd (--configure): dependency problems - leaving unconfigured Processing triggers for python-support ...configured to not write apport reports Errors were encountered while processing: wicd-daemon wicd-gtk wicd E: Sub-process /usr/bin/dpkg returned an error code (1) Per a user suggestion on the AntiX forum I created a user called demo and then was able to get the daemon to install. As this was a live-cd user it gets removed after an install of distro AntiX and the previous install of wicd had had this user. Thought purging the packages removed all references to users but I guess its stored somewhere else. Is there a real need to remember users in these packages? Removed user profiles should be ignored IMHO in configuring this package thus this bug should be reopened and investigated further.
