I got this behavior with "session":{"restore_on_startup":1} in
~/.config/chromium/{profile}/Preferences.
I only get this on my laptop, for some reason, not my desktop.
I can set that to 0 instead of 1 and everything is OK, except my saved tabs of
course which are not restored.
Also, I've notic
Processing commands for cont...@bugs.debian.org:
> retitle 930587 www.debian.org: release notes fail to build for jessie and
> stretch
Bug #930587 [www.debian.org] www.debian.org: release notes fail to build for
jessie and
Changed Bug title to 'www.debian.org: release notes fail to build for jes
Hello Bernhard,
Thanks for your reply!
I have install the proprietary nvidia drivers and it runs well.
The output of commands which you list as below,
> ldd /usr/bin/freecad
linux-vdso.so.1 (0x7ffe69ae5000)
libhdf5_openmpi.so.103 => /lib/x86_64-linux-gnu/libhdf5_openmpi.so.1
Processing commands for cont...@bugs.debian.org:
> retitle 930587 www.debian.org: release notes fail to build for jessie and
Bug #930587 [www.debian.org] www.debian.org: release notes fail to build for
jessie
Changed Bug title to 'www.debian.org: release notes fail to build for jessie
and' from
Processing commands for cont...@bugs.debian.org:
> retitle 930587 www.debian.org: release notes fail to build for jessie
Bug #930587 [www.debian.org] www.debian.org: release notes fail to build for
jessie
Ignoring request to change the title of bug#930587 to the same title
> and stretch
Unknown c
Processing commands for cont...@bugs.debian.org:
> package release-notes
Limiting to bugs with field 'package' containing at least one of 'release-notes'
Limit currently set to 'package':'release-notes'
> reassign 930587 www.debian.org
Bug #930587 [release-notes] release-notes: fails to build for
Hi Jover,
You are right. I was choosing between release-notes and www.debian.org
but I was not aware that the .dbk files will be regenerated anyway
during the build process. It seems that this should be reassigned
to www.debian.org.
The build script is at
https://salsa.debian.org/webmaster-
Processing control commands:
> tag -1 + unreproducible moreinfo
Bug #919188 [sslh] sslh daemon does not detach from terminal
Added tag(s) unreproducible and moreinfo.
> severity -1 important
Bug #919188 [sslh] sslh daemon does not detach from terminal
Severity set to 'important' from 'critical'
-
Control: tag -1 + unreproducible moreinfo
Control: severity -1 important
Hi Pali,
Pali Rohár wrote:
> severity 919188 critical
Why? You neither explained that it breaks the whole system nor that it
causes other, unrelated packages to break nor that it causes serious
data-loss.
Please check http
Dear Security Team,
I'm ready to upload libqb-1.0.1-1+deb9u1 with the following debdiff:
diff -Nru libqb-1.0.1/debian/changelog libqb-1.0.1/debian/changelog
--- libqb-1.0.1/debian/changelog2016-12-07 14:55:45.0 +0100
+++ libqb-1.0.1/debian/changelog2019-06-16 23:41:50.
Package: src:linux
Version: 4.19.37-3
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
I performed a fresh install using the image debian-testing-amd64-xfce-CD-1.iso
and after installation I could not boot to the desktop, I was left with a black
screen.
I entered tty1 a
Followup-For: Bug #930005
Control: tag -1 patch
The attached patch fixes the linking issue and thus the missing tgetent
symbol. Thereafter the command
regina /usr/share/doc/regina-rexx/examples/regutil.rexx
works on i386, but segfaults on amd64.
Andreas
diff -Nru regina-rexx-3.6/debian/changel
Processing control commands:
> tag -1 patch
Bug #930005 [regina-rexx] regina-rexx: rexxutil error
Added tag(s) patch.
--
930005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi!
On Sun, 2019-06-16 at 14:40:53 +0800, Wenbin Lv wrote:
> Package: release-notes
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> Recent transition from .dbk to .po for the ca language leaves some
> untracked .dbk files in the
Control: severity -1 normal
On Tue, Jun 11, 2019 at 6:09 PM Shengjing Zhu wrote:
>
> Hi,
>
> I checked more carefully on https://github.com/moby/moby/pull/28257
> and https://github.com/moby/moby/issues/14041
> Then I concluded that docker does nothing wrong in this case.
>
[...]
With the reason
Processing control commands:
> severity -1 normal
Bug #865975 [docker.io] docker.io changes iptables default FORWARD policy to
DROP, breaks VM and others
Bug #930302 [docker.io] docker.io changes iptables default FORWARD policy to
DROP, breaks VM and others
Severity set to 'normal' from 'critica
On Sun, Jun 16, 2019 at 11:47 PM Shengjing Zhu wrote:
> So I would suggest we remove rkt from buster.
>
Which means the acbuild and nomad(build-rdepends) will also be removed.
For acbuild, it is also discontinued by upstream[1].
For nomad, you can disable the rkt driver, by patching
client/driver
See below.
On Sat, Jun 15, 2019 at 9:42 PM Andreas Metzler wrote:
>
> On 2019-06-15 Ross Boylan wrote:
> > I've been following this bug because it came up as an issue for a
> > security upgrade to libgnutls-openssl27 in buster. I'm still seeing
> > 3.6.7-3 as the upgrade target.
>
> Hello Ross,
Hi,
On Sun, Jun 16, 2019 at 11:47:16PM +0800, Shengjing Zhu wrote:
> Hi Dmitry,
>
> Upstream doesn't have any update for these 3 CVE for more than 2
> weeks(after the CVE published).
>
> So I'm afraid that rkt is longer maintained, with 2 other concerns:
>
> 1. Most commits since 2019 are about
Hello Gulfstream,
are you by any chance running the proprietary nvidia drivers?
I guess the output of following commands could be
helpful for the maintainer to diagnose this issue.
Could you run them and forward the output to this bug?
which freecad
ldd /usr/bin/freecad
dpkg -S /lib/x86_64-linux
Sorry, typo...
On Sun, Jun 16, 2019 at 11:47 PM Shengjing Zhu wrote:
>
> Hi Dmitry,
>
> Upstream doesn't have any update for these 3 CVE for more than 2
> weeks(after the CVE published).
>
> So I'm afraid that rkt is longer maintained, with 2 other concerns:
s/is longer/is no longer/g
>
> 1. Mo
Hi Dmitry,
Upstream doesn't have any update for these 3 CVE for more than 2
weeks(after the CVE published).
So I'm afraid that rkt is longer maintained, with 2 other concerns:
1. Most commits since 2019 are about typo/documents.
2. Coreos(the company who creates rkt) has been acquired by RedHat.
Control: tags 930321 + pending
Hi Mathieu,
I've prepared an NMU for php-horde-form (versioned as 2.0.18-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it or feel free to override it with a maintainer upload!
Decided to go ahead with a DELAYED/2 only given the a
Processing control commands:
> tags 930321 + pending
Bug #930321 [src:php-horde-form] php-horde-form: CVE-2019-9858
Added tag(s) pending.
--
930321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 patch
Bug #930618 [node-terser] node-terser does not install file mentioned in
package.json's main field and fails Error: Cannot find module 'terser'
Added tag(s) patch.
--
930618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930618
Debian Bug Trackin
Package: node-terser
version: 3.14.1-2
severity: grave
Control: tags -1 patch
pravi@andhaka:~/forge/debian/git/js-team/vue.js$ sudo apt install
node-terser
[sudo] password for pravi:
Sorry, try again.
[sudo] password for pravi:
Reading package lists... Done
Building dependency tree
Reading stat
Your message dated Sun, 16 Jun 2019 12:48:57 +
with message-id
and subject line Bug#871321: fixed in tenshi 0.13-2.1
has caused the Debian Bug report #871321,
regarding tenshi: CVE-2017-11746: should create its PID file before dropping
privileges
to be marked as done.
This means that you cla
Isn't the fact there is no Amarok in Buster considered a problem?
Your message dated Sun, 16 Jun 2019 11:48:53 +
with message-id
and subject line Bug#930577: fixed in coinor-ipopt 3.11.9-2.2
has caused the Debian Bug report #930577,
regarding coinor-libipopt-dev: uses uninitialized memory with MUMPS >= 5.1.0
to be marked as done.
This means that you claim t
Package: chromium
Version: 75.0.3770.90-1
Followup-For: Bug #930469
I tried running it with --temp-profile as Mike suggested and it worked. Any
ideas how can I keep all my profile data such as history and bookmarks?
-- System Information:
Debian Release: 10.0
APT prefers unstable
APT policy
Your message dated Sun, 16 Jun 2019 11:33:33 +
with message-id
and subject line Bug#930591: fixed in node-vue-resource 1.5.1+dfsg-2
has caused the Debian Bug report #930591,
regarding node-vue-resource is broken - TypeError:
vue__WEBPACK_IMPORTED_MODULE_0__.default.http is undefined
to be mar
Hi Drew
On Sun, 16 Jun 2019 at 10:09, Graham Inggs wrote:
> Just as a reference, the commit that solved the problem in upstream is
> coin-or/Ipopt@4c36f88 [2]. The GitHub reference in the commit name is
> wrong because since then the coin-or/Ipopt repo has been replaced with
> the one migrated fr
Your message dated Sun, 16 Jun 2019 10:18:42 +
with message-id
and subject line Bug#811887: fixed in duma 2.5.15-2
has caused the Debian Bug report #811887,
regarding duma: FTBFS with GCC 6: declaration of ... has a different exception
specifier
to be marked as done.
This means that you clai
Control: tag -1 help
On Sun, 16 Jun, 2019 at 1:25 PM, Pirate Praveen
wrote:
When trying to use packaged version of node-vue-resource, Web Console
shows this error. UI elements just show the spinning circle forever.
Upstream is using rollup based build system and we converted it to
webpack
Processing control commands:
> tag -1 help
Bug #930591 [node-vue-resource] node-vue-resource is broken - TypeError:
vue__WEBPACK_IMPORTED_MODULE_0__.default.http is undefined
Added tag(s) help.
--
930591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930591
Debian Bug Tracking System
Contac
Your message dated Sun, 16 Jun 2019 09:06:43 +
with message-id
and subject line Bug#930507: fixed in ompl 1.4.2+ds1-2
has caused the Debian Bug report #930507,
regarding libompl-dev: libeigen required to build against OMPL
to be marked as done.
This means that you claim that the problem has b
Processing commands for cont...@bugs.debian.org:
> severity 930507 serious
Bug #930507 [libompl-dev] libompl-dev: libeigen required to build against OMPL
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
930507: https://bugs.d
Hi Drew
>From a comment to upstream issue #456 [1]:
Just as a reference, the commit that solved the problem in upstream is
coin-or/Ipopt@4c36f88 [2]. The GitHub reference in the commit name is
wrong because since then the coin-or/Ipopt repo has been replaced with
the one migrated from trac, and a
Package: node-vue-resource
Version: 1.5.1-1
severity: grave
Control: block 930404 by -1
When trying to use packaged version of node-vue-resource, Web Console
shows this error. UI elements just show the spinning circle forever.
Upstream is using rollup based build system and we converted it to
Processing control commands:
> block 930404 by -1
Bug #930404 [gitlab] [Meta] move gitlab back to main from contrib
930404 was blocked by: 884306 930529 929829 930262 863294 930588 930372 930560
887620 863293 924552 916221
930404 was not blocking any bugs.
Added blocking bug(s) of 930404: 930591
Processing control commands:
> tags -1 + patch
Bug #930321 [src:php-horde-form] php-horde-form: CVE-2019-9858
Added tag(s) patch.
--
930321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
Hi Mathieu,
On Mon, Jun 10, 2019 at 04:26:18PM +0200, Salvatore Bonaccorso wrote:
> Source: php-horde-form
> Version: 2.0.18-3
> Severity: grave
> Tags: security upstream
> Justification: user security hole
>
> Hi,
>
> The following vulnerability was published for php-h
42 matches
Mail list logo
