[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#974768: marked as done (handbrake: Saving custom presets in custom category is broken)



Your message dated Mon, 5 Dec 2022 21:18:19 +0100
with message-id <Y45SC5TnUwrzJJEC@ramacher.at>
and subject line Re: Bug#974768: handbrake: Saving custom presets in custom category is broken
has caused the Debian Bug report #974768,
regarding handbrake: Saving custom presets in custom category is broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
974768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974768
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: handbrake
Version: 1.2.2+ds1-1
Severity: normal

Creating a custom preset category in the GUI is not possible. Saving a new preset with the option "new category" enabled fails silently.

Workaround:
- Save a new preset in a default category like "General"
- Close Handbrake
- Open ~/.config/ghb/presets.json
- There is a new second "General" category at the end of the file
- Change the name to your prefered new custom categories name

-- System Information:
Debian Release: 10.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-12-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages handbrake depends on:
ii  libass9                         1:0.14.0-2
ii  libavcodec58                    7:4.1.6-1~deb10u1
ii  libavfilter7                    7:4.1.6-1~deb10u1
ii  libavformat58                   7:4.1.6-1~deb10u1
ii  libavutil56                     7:4.1.6-1~deb10u1
ii  libbluray2                      1:1.1.0-1
ii  libc6                           2.28-10
ii  libcairo2                       1.16.0-4
ii  libdvdnav4                      6.0.0-1
ii  libdvdread4                     6.0.1-1
ii  libgdk-pixbuf2.0-0              2.38.1+dfsg-1
ii  libglib2.0-0                    2.58.3-2+deb10u2
ii  libgstreamer-plugins-base1.0-0  1.14.4-2
ii  libgstreamer1.0-0               1.14.4-1
ii  libgtk-3-0                      3.24.5-1
ii  libgudev-1.0-0                  232-2
ii  libjansson4                     2.12-1
ii  libpango-1.0-0                  1.42.4-8~deb10u1
ii  libsamplerate0                  0.1.9-2
ii  libswresample3                  7:4.1.6-1~deb10u1
ii  libswscale5                     7:4.1.6-1~deb10u1
ii  libtheora0                      1.1.1+dfsg.1-15
ii  libvorbis0a                     1.3.6-2
ii  libvorbisenc2                   1.3.6-2
ii  libx264-155                     2:0.155.2917+git0a84d98-2
ii  libx265-165                     2.9-4
ii  libxml2                         2.9.4+dfsg1-7+b3

Versions of packages handbrake recommends:
ii  gstreamer1.0-libav       1.15.0.1+git20180723+db823502-2
ii  gstreamer1.0-pulseaudio  1.14.4-1
ii  gstreamer1.0-x           1.14.4-2

handbrake suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.3.1+ds1-2

On 2022-12-05 20:58:00 +0100, Alban Browaeys wrote:
> You can close this bug report as I can reproduce when I installed
> stretch handbrake_1.2.2+ds1-1_amd64.deb with its required dependencies
> from strech (libdvdread4_6.0.1-1, libx265-165_2.9-4, libx264-
> 155_0.155.2917+git0a84d98-2).
> This even with bookworm libgtk-3-0 3.24.35-2 and all other dependencies
> untouched.
> 
> And with only change being upgrading handbrake 1.5.1+ds1-3
> (bookworm and sid) and handbrake 1.3.1+ds1-2+b3 (bullseye stable) the
> issue is fixed.

Thanks for checking. Done

Cheers
-- 
Sebastian Ramacher

--- End Message ---

Reply to: