package: src:rhsrvany
version: 1.1-2
severity: serious
tag: patch
runsrvany64 and runpnpwait64 autopkgtests can fail on amd64 on
ci.debian.net because of foreign arch wine32 installability issues
[0]. This currently prevents wine from migrating to testing [1].
The attached patch solves the probl
+++ zlib-1.2.13.dfsg/debian/changelog 2023-08-02 01:30:53.0 +
@@ -1,3 +1,9 @@
+zlib (1:1.2.13.dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Build minizip packages.
+
+ -- Michael Gilbert Wed, 02 Aug 2023 01:30:53 +
+
zlib (1:1.2.13.dfsg-1) unstable; urgency=low
* New upstream rele
control: severity -1 normal
control: reassign -1 src:lutris
Bernhard Übelacker wrote:
> It looks like Lutris extracts the version
> from the path the wine executable was found.
Lutris parses version information from "wine --version" to conclude
whether features are supported [0]. The wine in deb
package: ftp.debian.org
severity: normal
user: ftp.debian@packages.debian.org
usertags: remove
Please remove src:jthread from bookworm and sid. It no longer has
reverse dependencies and is abandoned upstream.
It has release critical bug #1031253 that I plan to not fix.
Best wishes,
Mike
Günter Frenz wrote:
> version 6.18~repack-1 is the last working version. When comparing this
> to the current version 7.0, I noticed an error message in CombineZP
> saying "CreateCompatibleBitmap failed", maybe this helps too.
Bitmap handling was moved from dlls/gdi32 to dlls/win32u between 6.18
a
control: tag -1 moreinfo
Günter Frenz wrote:
> I'm using CombineZP (https://combinezp.software.informer.com/1.0/) with wine.
> Since the
> latest update the pictures are no longer displayed.
Are you saying it worked correctly with wine 6.0.3~repack-1?
If so, are you able to test the 6.x wine-de
package: ftp.debian.org
severity: normal
Please remove vkd3d binaries from s390x (testing only). s390x is not
yet a supported architecture upstream and autopkg tests currently fail
for that architecture. See #1010331.
Best wishes,
Mike
control: severity -1 minor
control: forwarded -1 http://crbug.com/1060925
Daniel Thompson wrote:
> 1. Install chromium
> 2. Navigate to https://chrome.google.com/webstore
> 3. Try to install an extension (I tested primarily with bitwarden
>but I also checked a couple of "random" ones from the
control: tag -1 moreinfo
control: severity -1 minor
Karl O. Pinc wrote:
> Package: chromium
> Version: 87.0.4280.88-0.4~deb10u1
> Severity: normal
>
> I find that trying to print to a postscript printer with chromium
> prints instead:
>
> ERROR NAME;
>undefined
> COMMAND;
>Invalid
> OPERAN
package: src:wine-development
severity: serious
This package is not intended to be released in a debian stable
release. This bug serves to prevent migration of the package to
testing.
Best wishes,
Mike
control: severity -1 minor
control: forwarded -1 http://crbug.com/1142228
control: retitle -1 chromium: APNGs flicker when built with system libpng
This is only a problem when chromium is built using the libpng shared
system library.
Best wishes,
Mike
On Sat, Feb 13, 2021 at 5:01 AM Andreas Henriksson wrote:
> > For systems where awk is not yet installed (chroots), installation of
> > dash will currently fail since it's postinst calls add-shell from
> > debianutils.
>
> Please share details about how to reproduce this situation!
>
> You say you
control: tag -1 -moreinfo
control: severity -1 minor
control: forwarded -1 https://bugs.winehq.org/show_bug.cgi?id=39439
On Mon, Jun 22, 2020 at 12:54 AM Gong S. wrote:
> 10538.908:000a:000b:exception c005 in PE entry point
> (proc=0x7b02d8c0,module=0x7b00,reason=PROCESS_ATTACH,res=0x32fb0
package: src:debianutils
severity: serious
version: 4.11.2
tag: patch
debianutil's add-shell script uses awk, but awk is not an
Essential:yes package. For systems where awk is not yet installed
(chroots), installation of dash will currently fail since it's
postinst calls add-shell from debianutil
control: severity -1 minor
On Sat, Feb 6, 2021 at 3:09 AM jim_p wrote:
> This means that sync and some other features will stop working from that day
> on
> and users that use them will complain and file bug reports.
None of this is relevant to running chromium as a web browser, which
is its int
On Fri, Sep 4, 2020 at 4:57 PM Rory Campbell-Lange wrote:
> Kernel: Linux 5.7.0-3-amd64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Chromium on tainted kernels is not supported.
Best wishes,
Mike
On Tue, Dec 22, 2020 at 3:45 AM Michel Le Bihan wrote:
> I my NMU 87.0.4280.88-0.2 has just been uploaded to unstable and I'm
> interested in joining and helping with the package. My work is in
> https://salsa.debian.org/mimi8/chromium/ . Please also see the
> discussion under
> https://bugs.de
On Fri, Jul 3, 2020 at 3:39 AM Alexis Huxley wrote:
> I've got Debian 10 and apply nightly updates as they become
> available. I was running chromium version 80.0.3987.162 but
> that was upgraded to 83.0.4103.116 a couple of nights ago. Since
> then CPU load at page load time is very high, the inte
On Mon, Jun 22, 2020 at 12:54 AM Gong S. wrote:
> The output is attached.
Based on the trace, one of the places wine finds kernelbase.dll on
your system is Z:\\usr\\home\\root\\kernelbase.dll. Could this be an
out of date version of the dll?
> I also used the root account with no ".wine" directo
On Sun, Apr 12, 2020 at 12:18 AM 積丹尼 Dan Jacobson wrote:
> I'm now seeing
>
> MESA-LOADER: failed to retrieve device information
> MESA-LOADER: failed to open i915 (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri) failed to load
> driver: i915
> MESA-LOADER: failed to op
control: tag -1 moreinfo
On Tue, Jun 23, 2020 at 10:27 AM 積丹尼 Dan Jacobson wrote:
> Received signal 11 SEGV_MAPERR 7f0168b7a277
> #0 0x55e2011c3bf9 (/usr/lib/chromium/chromium+0x52b3bf8)
> #1 0x55e201122e83 (/usr/lib/chromium/chromium+0x5212e82)
> #2 0x55e2011c3781 (/usr/lib/chromium/chromium+0x52
control: tag -1 moreinfo
control: severity -1 important
On Fri, Jun 19, 2020 at 11:09 PM Gong S. wrote:
> The current version of wine-development cannot launch any Windows programs,
> including built-in ones like "winecfg" and "wineconsole".
I am not able to reproduce this on i386. Is this on a
control: severity -1 minor
control: forwarded -1 http://crbug.com/1087707
control: retitle -1 print to pdf font subsetting issue
I am not able to reproduce this with 81.0.4044.92-1 following the
instructions in comment #13 from the upstream bug report. I get a
500K pdf file with only DejaVuSans,D
control: severity -1 important
On Thu, Jun 18, 2020 at 12:48 PM Harald Dunkel wrote:
> libva-x11-2 is version 2.7.1-1. nvidia-graphics-drivers is version 440.82-2.
> I cannot reproduce this using google-chrome 83.0.4103.106-1.
This is caused by ffmpeg 4.3, see #963035.
Best wishes,
Mike
control: tag -1 moreinfo
control: severity -1 minor
On Sat, Apr 18, 2020 at 9:30 AM jim_p wrote:
> I found it yesterday, when I made a new shortcut using the plus (+) icon
> there.
> I spelled something wrong and now I can not edit it nor remove it :D
I just tested this, and it works for me. I
control: tag -1 moreinfo
On Sun, Apr 12, 2020 at 12:18 AM Dan Jacobson wrote:
> MESA-LOADER: failed to retrieve device information
> MESA-LOADER: failed to open i915 (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri) failed to load
> driver: i915
Do you have the libgl1-
g
--- zlib-1.2.11.dfsg/debian/changelog 2020-02-24 16:07:12.0 -0500
+++ zlib-1.2.11.dfsg/debian/changelog 2020-04-07 21:50:15.0 -0400
@@ -1,3 +1,9 @@
+zlib (1:1.2.11.dfsg-2.1) UNRELEASED; urgency=medium
+
+ * Build minizip packages.
+
+ -- Michael Gilbert Wed, 08 Apr 2020 01:5
On Fri, Apr 3, 2020 at 5:28 PM Stephen Kitt wrote:
> Thanks for the report, the package is missing a build-dependency on
> gcc-mingw-w64-x86-64.
There is more to it than this. I am working on it now.
> Michael, I can take care of fixing this, doing a rebuild to make sure and
> uploading, if you
control: tag -1 help
On Thu, Apr 2, 2020 at 5:15 AM Bastian Germann wrote:
> This requires chromium to build with the ozone interface in the
> first place. Would it be possible to switch to using that (with the X11
> backend)? Would you take patches for it?
Yes.
Best wishes,
Mike
On Thu, Mar 19, 2020 at 8:28 AM Diafero wrote:
> Version 5.0-3 also seems affected.
Was the version that worked 4.21-1 or 4.21-2?
Best wishes,
Mike
control: tag -1 moreinfo
control: severity -1 minor
On Sun, Mar 15, 2020 at 7:21 AM Diafero wrote:
> But with recent versions (I tried 5.1 and 5.2)
Could you test whether wine 5.0-3 (not wine-development) works or not?
This will help determine which patches are most likely the problem.
Best wis
user debian-pyt...@lists.debian.org
usertags 942962 py2keep
usertags 942962 py3noport
thanks
control: tag -1 moreinfo
On Sat, Feb 22, 2020 at 9:57 PM Jean-Philippe MENGUAL wrote:
> 10 dependencies do not want to install: the install tries to replace
> the /usr/share/doc/package directory, to change the changelog.Debian.gz
> and, of course, refuses. I guess changelog.Debian.gz is different
control: retitle -1 wine: fails to build with clang 9 on arm64
On Mon, Feb 17, 2020 at 10:54 AM Gianfranco Costamagna wrote:
> Hello, looks like wine is still failing on Ubuntu arm64, probably because of
> new gcc or new glibc, or a combo of them both...
The difference is that clang 9 is ubuntu'
On Sat, Jan 18, 2020 at 11:05 PM Matti Hämäläinen wrote:
> > On Sat, Jan 18, 2020 at 3:35 PM Matti Hamalainen wrote:
> >> "virtual desktop" works, but is not a feasible option as on a 2560x1440
> >> screen
> >> a 640x480 resolution game will be minuscule.
> >
> > winecfg can be used to change dim
control: tag -1 moreinfo
control: severity -1 minor
On Sat, Jan 18, 2020 at 3:35 PM Matti Hamalainen wrote:
> "virtual desktop" works, but is not a feasible option as on a 2560x1440 screen
> a 640x480 resolution game will be minuscule.
winecfg can be used to change dimensions of the virtual deskt
control: tag -1 moreinfo
On Sat, Oct 26, 2019 at 10:48 AM Witold Baryluk wrote:
> Thread 20 "Chrome_InProcGp" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffaa7fc700 (LWP 32634)]
> 0x7fff770d9c37 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
> (gdb) bt
control: tag -1 moreinfo
> #4 0x58e64e4d in base::(anonymous
> namespace)::OnNoMemorySize(unsigned long) [clone .constprop.237] ()
> #5 0x58ef0c85 in calloc ()
> #6 0x7fffaa96c7e9 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
> #7 0x7fffaa45f4b9 in ?? () from
control: reopen -1
control: tag -1 - moreinfo
On Sat, Aug 31, 2019 at 9:57 AM Dan Jacobson wrote:
>
> MG> Could you try this again without packages from experimental? I assume
> MG> its caused by the update to libc6 2.29?
>
> Some other one. So now I use pure sid. Problem solved.
Can you figure
control: tag -1 moreinfo
On Sun, Aug 25, 2019 at 4:36 PM Dan Jacobson wrote:
> Versions of packages chromium depends on:
[...]
> ii libatk1.0-0 2.33.3+really2.33.3-1
[...]
> ii libc62.29-0experimental1
[...]
> ii libjpeg62-turbo 1:2.0.2-1~exp2
Could you try this a
On Wed, Jul 31, 2019 at 9:45 AM Sascha Wolke wrote:
> @mike: If any help to find the sources is required, just name them and i
> am going to find them.
The sourceless files are in third_party/catapult/tracing, which is now
stripped out of the debian source package.
Best wishes,
Mike
package: src:glib2.0
severity: serious
version: 2.60.5-1
The latest glib2.0 upload fails to build on i386 and mips [0].
On i386, the gmenumodel test timed out. On mips, the gvariant test timed out.
Best wishes,
Mike
[0] https://buildd.debian.org/status/package.php?p=glib2.0
package: src:kopano-webapp
severity: serious
version: 3.5.6+dfsg1-1
kopano-webapp currently has a failing autopkgtest [0]. This currently
blocks migration of chromium since it is listed as an autopkgtest
dependency for this package.
===
package: qa.debian.org
severity: normal
The blhc results on the build log scanner pages at qa.debian.org
indicate that most packages have missing pie flags now that gcc
injects it automatically on most archs.
Please use the new --debian flag, which was added to account for this [0].
Best wishes,
control: tag -1 moreinfo
On Thu, Jun 13, 2019 at 5:36 AM Guillem Jover wrote:
> [23609:23609:0613/102304.872428:FATAL:render_process_host_impl.cc(4060)]
> Check failed: render_process_host->InSameStoragePartition(
> BrowserContext::GetStoragePartition(browser_context, site_instance, false )).
On Tue, Jun 11, 2019 at 2:21 PM Riku Voipio wrote:
> I can make an upload if you prefer, or I can wait for you.
No reason to delay, please go ahead.
Best wishes,
Mike
package: src:chromium
severity: serious
version: 75.0.3770.80-1
The latest upload fails to build on armhf due to missing intrinsics [0].
Best wishes,
Mike
[0]https://buildd.debian.org/status/fetch.php?pkg=chromium&arch=armhf&ver=75.0.3770.80-1&stamp=1560141959&raw=0
package: src:chromium
severity: serious
version: 74.0.3729.108-1
The latest upload fails to build on arm64 due to errors in crc32 [0].
Best wishes,
Mike
[0]https://buildd.debian.org/status/fetch.php?pkg=chromium&arch=arm64&ver=74.0.3729.108-1&stamp=1556085401&raw=0
control: severity -1 wishlist
control: retitle -1 chromium: add "no-pings" flag
On Fri, Apr 26, 2019 at 7:09 PM ilf wrote:
> So either I am missing something here, or the Debian package
> default-flags should replace "disable-pings" with "no-pings".
The disable-pings flag has to do with the compo
control: tag -1 moreinfo, unreproducible
control: severity -1 minor
On Thu, Apr 25, 2019 at 6:33 PM Salvo Tomaselli wrote:
> middle clicking on a bookmark directory used to open all of the items in
> tabs. This no longer works.
>
> Also, right clicking and selecting "Open all" used to do the same.
control: forcemerge -1 926151
control: severity -1 minor
On Tue, Apr 2, 2019 at 5:21 AM wrote:
> However it is a short term solution. Why would we have to disable a feature
> like hardware acceleration and revert to a sluggish (and cpu hungry) software
> rendering in order to (barely) make thing
package: release.debian.org
user: release.debian@packages.debian.org
usertags: unblock
Please consider unblocking chromium. This is a large upstream release
with a bunch of security fixes. As has been done for the past few
stable releases, the plan is to push ongoing upstream security update
control: tag -1 pending
control: severity -1 minor
This should be fixed when chromium 73 is uploaded.
Best wishes,
Mike
On Sun, Mar 3, 2019 at 9:51 PM Gong S. wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Package: chromium
> Version: 72.0.3626.96-1~deb9u2
>
> When launched in
control: tag -1 pending
On Tue, Feb 26, 2019 at 4:39 AM Lee Garrett wrote:
> your issue is related to mixing stable and testing, which is not supported and
> causing your issue here.
This may not be common knowledge, but mixed suites have always been a
supported configuration. This is a legitima
control: severity -1 serious
Increasing severity since policy 10.7.3 is violated:
"Obsolete configuration files without local changes should be removed
by the package during upgrade."
The file in /etc/chromium.d is obsolete.
Best wishes,
Mike
control: notforwarded -1
control: reassign -1 chromium-ublock-origin
On Sat, Feb 23, 2019 at 8:31 PM W. Martin Borgert wrote:
> But the culprit was chromium-ublock-origin which was only
> uninstalled, but not purged. After purging
> chromium-ublock-origin, the message is gone.
chromium-ublock-ori
control: severity -1 minor
control: forwarded -1 http://crbug.com/835767
On Sat, Feb 23, 2019 at 4:21 AM W. Martin Borgert wrote:
> When I access a meet jitsi site, e.g.
> https://meet.jit.si/ChromiumFailsToAccessMyMicrophone
> Chromium asks whether I allow access to camera and microphone.
> When
On Sat, Feb 23, 2019 at 1:58 PM W. Martin Borgert wrote:
> Still, under chrome://extensions/, I see three extensions:
>
> - Chromium PDF Viewer
> - CryptoTokenExtension
> - GNOME Shell integration
It likely relates to the GNOME shell extension, though it may not. I
am not able to reproduce wit
control: severity -1 minor
control: forwarded -1 http://crbug.com/724826
On Fri, Feb 22, 2019 at 4:36 PM W. Martin Borgert wrote:
> When I start chromium as a newly added user (no chromium config
> is present in $HOME) I get a warning dialog:
>
> > Failed to load extension from: . Manifest file
>
control: tag -1 moreinfo
control: severity -1 minor
This sounds a lot like this upstream bug:
https://bugs.winehq.org/show_bug.cgi?id=23676
It is in a different app and only seen with mesa and ati drivers, not
nvidia. Which driver do you use?
Does AnyRail allow you to disable 3d rendering?
Bes
On Mon, Feb 4, 2019 at 3:03 AM Simon McVittie wrote:
> This was reduced from Depends to Recommends in 1.0.0.59-4. Michael:
> why this change?
Recommends are installed by default by apt, so most users will get it
installed automatically, but this also supports users that don't need
or want it. You
package: devscripts
severity: wishlist
It would be a nice improvement if the salsa script supported gitlab's
request_access, which allows a user to request membership to a team.
Best wishes,
Mike
control: tag -1 moreinfo, help
On Sat, Nov 11, 2017 at 4:05 PM Michael Gilbert wrote:
> I also noticed that a similar file is already in apparmor-profiles.
> Is that not sufficient?
It looks like apparmor will no longer provide a chromium profile with
buster. I'm not planning to loo
control: reassign -1 src:notification-daemon
On Sat, Jan 5, 2019 at 12:42 PM Dan Jacobson wrote:
> ERROR:object_proxy.cc(621)] Failed to call method:
> org.freedesktop.Notifications.GetCapabilities: object_path=
> /org/freedesktop/Notifications: org.freedesktop.DBus.Error.ServiceUnknown:
> The
control: severity -1 minor
control: forwarded -1 http://crbug.com/822418
On Sat, Jan 12, 2019 at 7:57 PM Dan Jacobson wrote:
> [5799:5799:0113/084128.701923:ERROR:context_group.cc(381)]
> ContextResult::kFatalFailure: too few texture image units supported (0,
> should be 8).
[...]
> Doesn't happ
package: src:wine-development
severity: serious
version: 3.12-2
This has been fixed in wine [0]. It also needs to be fixed in wine-development.
Best wishes,
Mike
[0] http://bugs.debian.org/918666
control: reopen -1
control: tag -1 - moreinfo
On Sat, Jan 26, 2019 at 3:21 PM Michael Gilbert wrote:
> From everything I can tell, this works correctly in current versions.
> Please feel free to reopen if it can be demonstrated otherwise.
This seems to be the same problem described i
On Fri, Jan 18, 2019 at 12:31 AM Michael Gilbert wrote:
> Two, Valve moves completely to XDG_DATA_HOME.
I intended to say that Valve completely follows the XDG base directory
specification, which is of course more than just XDG_DATA_HOME.
Best wishes,
Mike
control: tag -1 - patch pending
On Wed, Jan 16, 2019 at 6:33 AM Simon McVittie wrote:
> This is basically my earlier patch from #916303, except that the default
> is swapped: it will continue to use ~/.steam as the $STEAMDIR for new
> installations, and only use ~/.local/share/Steam (or any other
On Fri, Jan 11, 2019 at 1:03 PM Patrick Häcker wrote:
> I can confirm, that version 72.0.3626.7-6 is fixing the issue. Thanks a lot
> for
> pointing me to the unstable version.
>
> So as soon as this version enters testing, this bug report can be closed.
It can't be closed because the problem wil
control: tag -1 - moreinfo
On Sat, Jan 12, 2019 at 1:19 AM Michael Gilbert wrote:
> This is already the case. The current implementation automatically
> falls back to TMPDIR if /run/user/$UID does not exist. It also
> automatically handles creation of the wine subdirectory if it
control: tag -1 moreinfo
On Tue, Jan 8, 2019 at 4:21 AM Julian Andres Klode wrote:
> wine hardcodes the use of /run/user/$UID/wine if it can determine
> $UID (if getuid() exists) as the place to store server information.
>
> It's not clear to me who is responsible for creating those directories,
>
control: tag -1 moreinfo
On Sat, Dec 29, 2018 at 7:27 AM Minh Duc Vo wrote:
> Inputting a shortcut key combination while a text field is being focused will
> not trigger the desired action for that combination.
> For example, A Ctrl+T combination inputted while the cursor is placed in the
> Omnibo
control: tag -1 moreinfo
On Wed, Nov 28, 2018 at 4:09 AM Peter Gervai wrote:
> Anyway, Chromium SafeBrowsing seems not to work at all, despite that both
> "SafeBrowsing" and "Help improve SB" is on.
>
> Just go to this URL and see no warnings:
> https://www[.]xn--bbox-vw5a[.]com/login
> (It is a
control: severity -1 normal
On Mon, Dec 17, 2018 at 4:15 PM Sean Shapira wrote:
> Extensions which attempt to access Google (not chrome) bookmarks no longer
> function. This is a regression introducted since 69.0.3497.92-1~deb9u1.
enable_one_click_signin is set to false starting with version 70 t
control: tag -1 moreinfo
> The problem reproduces everytime during loading WorldOfWarcraft game.
[...]
> The game window is created but it is black and the terminal contains error
> message
>
>> 0009:err:seh:setup_exception stack overflow 1760 bytes in thread 0009
This sounds very similar to this
On Mon, Dec 17, 2018 at 4:40 AM Bastian Blank wrote:
> > Since this can be used in place of chromium's setuid binary, my
> > opinion is that the Depends relationship on chromium-sandbox is no
> > longer required.
>
> Nope, at least if the package is supposed to work without admin
> intervention.
D
On Fri, Nov 16, 2018 at 4:30 AM Bastian Blank wrote:
> Debian does not support unprivileged user namespaces, so chromium needs
> to depend on -sandbox to get a working package.
The debian version of the kernel package provides
kernel.unprivileged_userns_clone as a runtime selectable option for a
w
control: reassign -1 src:steam
control: retitle -1 steam: fails to load libGL.so.1
Make sure you have either libgl1-mesa-glx:i386 or your proprietary
driver's i386 glx package installed. See bug #718599.
Best wishes,
Mike
control: tag -1 moreinfo
There is a new upstream version uploaded now, 0.2.0+git20180917. Does
this fix the problem you're seeing?
For anyone that would like to help here, it would be helpful to figure
out which upstream commit fixed #898257, which is almost exactly the
same problem.
Best wishe
control: tag -1 upstream
control: severity -1 wishlist
On Nov 28, 2018 at 7:12 PM Vincent Lefevre wrote:
> 1. When X11 is not used like here, there is no reason to try to use
> DISPLAY (or at least, error messages should be deferred). Note that
> "env -u DISPLAY wine tversion.exe" doesn't output a
control: reassign -1 src:twm
On Sun, Nov 4, 2018 at 3:33 PM Mark Carroll wrote:
> I see the problem even in Chromium 69 with both twm and ctwm.
This seems like it should be considered a bug in twm. The chromium
upstream bug report includes a lightly tested patch to twm that fixes
it.
Best wishe
control: severity -1 important
control: fixed -1 70.0.3538.54-2
control: retitle -1 chromium: SEGV on startup in stretch on armhf
> the version in stable crashes after the security update on a Raspberry Pi
> on startup. The system ist mainly Debian stable with some Raspbian packages.
> I couldn't
I looked into this. It is caused by upstream's removal of the gtk2
window button implementation around version 64, which is why only
stretch is affected. It still uses gtk2. For anyone interested in
this, I am willing to accept a forward port of upstream's old
implementation. However, this isn'
control: severity -1 grave
control: reassign -1 libasound2-plugins
control: retitle -1 libasound2-plugins: broken symlinks in /etc/alsa/conf.d
control: found 1 1.1.7-1
This is caused by broken symlinks added to libasound2-plugins between
1.1.6-1 and 1.1.7-1.
Best wishes,
Mike
control: tag -1 moreinfo
> Negative, wine stable is not affected, at least for my use-case.
> According to the winehq bug, it all started from wine 3.8.
What about the latest uploads of wine-development, do they work for
you now? This should be fixed by upstream's DECLSPEC_HOTPATCH updates
as of
On Sat, Oct 13, 2018 at 12:39 PM Jens Reyer wrote:
> To avoid these issues I suggest to use
>
> wrap-and-sort --wrap-always --short-indent --trailing-comma
Hi Jens,
Welcome back!
Wrap and sort is itself the original source of the extra diff being
seen and will continue to be in the future. I
On Thu, Sep 6, 2018 at 8:49 PM Michael Gilbert wrote:
> This might be this upstream bug:
> https://bugs.winehq.org/show_bug.cgi?id=45199
>
> 3.13 was the first version built with gcc8. You could try rebuilding
> with either gcc7 or with -O1 instead of -O2.
The latest upload 3.16-
control: tag -1 confirmed
control: severity -1 important
On Sun, Sep 16, 2018 at 8:57 PM Jiri Palecek wrote:
> I think this bug is caused by the addition of the Diablo patch.
> Certainly, removing it fixed it.
I already knew as much since it was the only substantive change in
that upload. I agre
package: chromium
severity: minor
version: 68.0.3440.75-1~deb9u1
tag: upstream
This is a regression introduced upstream. Seen in this version and
possibly introduced earlier. It only affects the stretch package.
Best wishes,
Mike
control: tag -1 moreinfo
control: severity -1 minor
On Thu, Sep 6, 2018 at 11:03 AM Nicolas Rodriguez wrote:
> I use ArchLinux on my laptop with Chromium 68.0.3440.106 and it works
> very well.
>
> I suggest to update Chromium to 68.0.3440.106.
69.0.3497.81-1~deb9u1 has just been uploaded. Does
control: tag -1 upstream
control: severity -1 minor
This might be this upstream bug:
https://bugs.winehq.org/show_bug.cgi?id=45199
3.13 was the first version built with gcc8. You could try rebuilding
with either gcc7 or with -O1 instead of -O2.
Best wishes,
Mike
control: reopen -1
control: tag -1 confirmed, upstream
On Mon, Sep 3, 2018 at 9:27 AM Marius Mikucionis wrote:
> I have replaced the packages (see the new list below) with the Debian ones
> and the issue persists.
I tested as well now, it is reproducible with the latest upload.
> Is there a way
Should this be considered a bug in Qt since it fails to take into
account the return value from wTInfoT?
Also there was some refactoring upstream in 3.15 in wintab and winpos,
would you mind retesting with the latest upload?
Best wishes,
Mike
control: severity -1 minor
control: forwarded -1 http://crbug.com/473958
control: retitle -1 chromium: pdf and two factor extensions can't be removed
Upstream intentionally builds these extensions in by default. In fact
upstream hides them by default. If you don't want to see them in the
debian
On Wed, Aug 8, 2018 at 3:35 AM, Tim Connors wrote:
> Kernel: Linux 4.16.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
This may be totally unrelated, but I see that you're using a backports
kernel. Could you retry with an official stretch kernel? You might
also try updating to the latest bpo kernel, 4.17.
On Sun, Aug 12, 2018 at 8:04 PM, Michael Gilbert wrote:
>> Kernel: Linux 4.9.0-7-amd64 (SMP w/4 CPU cores)
>
> Your kernel is quite out of date. Could you try 4.9.110-1 or newer?
I read that wrong, you are up to date. There is a bug in xlib for
certain locales [0], from my understan
control: tag -1 moreinfo
> Chromium showing an anomalous behaviour after last debian stable update
> running under AMD graphical interface. A blue screen appears when the
> browser is loading.
Are you using the proprietary AMD driver?
> -- System Information:
> Debian Release: 9.5
> Architecture
control: tag -1 pending
On Tue, Aug 7, 2018 at 9:07 AM, Riku Voipio wrote:
> I didn't push this to main stretch branch, as the security upload commit
> is reconstructed rather the original from Michael. Changelog hasn't been
> updated either.
I had forgotten to push after the previous upload, don
On Sat, Aug 11, 2018 at 8:11 PM, Michael Gilbert wrote:
> As far as I can tell, this is upstream http://crbug.com/844377. It
> was introduced in chromium 66 just like you experienced and symptoms
> are nearly identical.
>
> I previously checked that their fix was applied in version
1 - 100 of 3327 matches
Mail list logo
