Package: crossgrader
Version: 0.0.3+nmu4
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Attempting to run:
crossgrader amd64 --second-stage
if the package is required in the old i386 installat
Package: bind9
Version: 1:9.20.4-3
Followup-For: Bug #1090804
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
After some more testing I found that the old versions of the init script
explicitly tested for [ -x /s
Package: bind9
Version: 1:9.20.4-3
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Sometime in the past an upgrade to bind9 stopped calling resolvconf on
startup/shutdown, leaving the resolver as
Package: wireplumber
Followup-For: Bug #1089865
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
Please close the bug report, unable to reproduce the issue now.
* What led up to the situation?
* What exactly did you do (or not do) that was ef
Package: wireplumber
Version: 0.5.7-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
After the following upgrades were applied and logged out and in again,
wireplumber did not start from daemon
Package: inkscape
Version: 1.2.2-6
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Either upgrading to version 1.2.2-6 or downgrading from it.
Preparing to unpack .../lib2geom1.2.0t64_1.2.2-4+b1
Package: mesa-vdpau-drivers
Version: 24.3.0~rc2-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading upgrading mesa-libgallium without upgrading mesa-vdpau-drivers to
the same version
Package: plasma-workspace
Version: 4:5.27.11.1-1+b2
Followup-For: Bug #1073293
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrading to 4:5.27.11.1-1+b2 caused session restore to fail again.
Manually copying
Package: plasma-workspace
Version: 4:5.27.11.1-1
Severity: important
Tags: patch upstream
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading from plasma-workspace 4:5.27.10* to 4:5.27.11*
* What exactl
Package: plasma-desktop
Version: 4:5.27.11-1
Followup-For: Bug #1072905
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
I rebuilt
Package: plasma-desktop
Version: 4:5.27.11-1
Followup-For: Bug #1072905
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What
Package: plasma-desktop
Version: 4:5.27.11-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrades to unstable between 29th May and 5th June 2024 caused
"On login, launch apps that were open:
Package: libglib2.0-0t64
Version: 2.80.0-10
Followup-For: Bug #1070730
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading libglib2.0-0t64 from 2.80.0-9 to 2.80.0-10 broke Japanese input
with mozc to chromi
Package: ibus
Version: 1.5.29-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading libglib2.0 related packages from 2.80.0-9 to 2.80.0-10
chromium, firefox and discord refused to accep
This was without actually changing /etc/defaukt/hd-idle from what was in the
packages.
The /etc/init.d/hd-idle script on the 1.12+ds-1 package just tries to start
hd-idle with not parameters.
Arthur.
On 22 April 2024 4:08:49 pm ACST, Alex Mestiashvili
wrote:
>On 4/22/24 02:54, Arthur Ma
Package: hd-idle
Version: 1.21+ds-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Setting up hd-idle (1.21+ds-1) ...
Installing new version of config file /etc/default/hd-idle ...
Installing ne
Package: awesfx
Version: 0.5.2-1.1+b1
Severity: normal
Tags: upstream
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
running asfxload on post 6.8.0 kernel
* What exactly did you do (or not do) that was effec
Package: kmod
Version: 31+20240202-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading kmod to 31+20240202-1 from 31-1
Then building a kernel using:
MAKEFLAGS='HOSTCC=gcc-14 CC=gcc-1
Package: fp-utils-3.2.2
Version: 3.2.2+dfsg-30
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Performing actions...
(Reading database ... 659226 files and directories currently installed.)
Prepa
Package: firmware-amd-graphics
Version: 20230625-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
A long time ago on a motherboard far away lived an AMD graphics card
code-named Cedar.
Cedar
Package: libgbm1
Followup-For: Bug #1054645
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
Reported as:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10228
*** End of the template - remove these template lines ***
Package: libavcodec-extra60
Version: 7:6.1-2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrading ffmpeg related packages
ffmpeg (7:6.1-2) over (7:6.0-9+b1)
>From gdb:
Thread 25 "vlc" rece
Many thanks for your help!
Arthur.
On 24 September 2023 9:33:06 pm ACST, Debian Bug Tracking System
wrote:
>This is an automatic notification regarding your Bug report
>which was filed against the konsole package:
>
>#1052542: konsole: version 4:23.08.1-1 missing changelog especially how to
>
Package: konsole
Version: 4:22.12.3-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading from 4:22.12.3-1 to 4:23.08.1-1
* What exactly did you do (or not do) that was effective (or
Package: libnss3
Followup-For: Bug #1038917
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
Version 2:3.90-3 fixed the crash issu
Package: libnss3
Version: 2:3.89-2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading libnss3 packages to 2:3.90-2
firefox kept crashing on startup
* What exactly did you do (or not d
Package: unixodbc-common
Version: 2.3.11-3
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Attempting to upgrade odbc related packages from 2.3.11-2 to 2.3.11-3
* What exactly did you do (
Package: libqt5core5a
Version: 5.15.8+dfsg-6
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
[UPGRADE] libqt5concurrent5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5core5a:amd64 5.15.
Package: libqt5core5a
Version: 5.15.8+dfsg-4
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Doing the following upgrade:
[UPGRADE] libqt5concurrent5:amd64 5.15.8+dfsg-3 -> 5.15.8+dfsg-4
[UPG
Package: grub-pc
Version: 2.06-8
Followup-For: Bug #1030934
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
If I addeded
GRUB_C
Package: grub-pc
Version: 2.06-8
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading or downgrading or reinstalling the grub-pc package
* What exactly did you do (or not do) that was e
Package: exim4-config
Version: 4.96-4
Followup-For: Bug #493526
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
See also bug #1019941 - by setting a "localhost" mail name and hence
/etc/mailname contained localho
Package: exim4-config
Version: 4.96-4
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Local delivery of mail for root on this machine which was aliased to my
username on this machine was inste
Package: exim4-config
Version: 4.96-4
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
The text box information for 'mail name' which sets /etc/mailname is
confusing:
The 'mail name' is the do
Package: sse3-support
Followup-For: Bug #1019556
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Trying to upgrade sse3-support from 13 to 14
* What exactly did you do (or not do) that was effective (or
Package: chromium
Version: 105.0.5195.52-1
Followup-For: Bug #1018937
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
When I ran
Package: chromium
Version: 104.0.5112.101-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrading chromium (105.0.5195.52-1) over (104.0.5112.101-1).
when attempting to launch chromium ha
Package: libspdlog-dev
Version: 1:1.10.0+ds-0.3
Followup-For: Bug #1017700
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Trying to upgrade packages:
am64:/usr/src/linux# aptitude -u
Performing actions...
(Read
- Original Message -
From: "Sebastian Andrzej Siewior"
To:"Arthur Marsh" ,
Cc:
Sent:Mon, 20 Jun 2022 19:16:36 +0200
Subject:Re: Bug#1012564: openssl: ckermit can't connect to telnetd-ssl
with openssl 3.0.3-7
On 2022-06-20 19:10:27 [+0200], To Arthur Ma
Package: openssl
Version: 3.0.3-8
Followup-For: Bug #1012564
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I also found that telnet-ssl and ckermit could not connect to telnetd-ssl
if openssl 3.0.3-8 was instal
On 10 June 2022 3:51:29 am ACST, Sebastian Andrzej Siewior
wrote:
>On 2022-06-09 23:18:07 [+0930], Arthur Marsh wrote:
>…
>> *** Reporter, please consider answering these questions, where appropriate
>> ***
>>
>>* What led up to the situation?
>>
&g
Package: openssl
Version: 3.0.3-7
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrading openssl, libssl3 to 3.0.3-7 from 3.0.3-6 on host system prevented
ckermit 305~alpha07-1+b1 on clien
Still happening after upgrading libssl3 to 3.0.3-3
Arthur.
On 14 May 2022 8:42:04 pm ACST, Debian Bug Tracking System
wrote:
>Thank you for filing a new Bug report with Debian.
>
>You can follow progress on this Bug here: 1010968:
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010968.
>
Package: telnetd-ssl
Version: 0.17.41+0.2-3.3+b1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
[UPGRADE] telnetd-ssl:amd64 0.17.41+0.2-3.3 -> 0.17.41+0.2-3.3+b1
Bug also observed on i386 ar
Package: texmaker
Version: 5.0.3-1+b4
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Preparing to unpack .../09-texmaker_5.1.2+dfsg-1_amd64.deb ...
Unpacking texmaker (5.1.2+dfsg-1) over (5.0
Package: plasma-workspace-data
Version: 4:5.24.2-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrade:
Preparing to unpack .../plasma-workspace-data_4%3a5.24.2-1_all.deb ...
Unpacking pla
Package: libtsan2
Version: 12-2023-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Performing actions...
Selecting previously unselected package cpp-12.
(Reading database ... 631827 file
Package: powertop
Version: 2.13-2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Running /usr/sbin/powertop --auto-tune
left the optical mouse LED off and the cursor frozen in X.
* What exa
Package: kexec-tools
Version: 1:2.0.22-2+b1
Followup-For: Bug #992482
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
kexec-tools still tries to use /bin/run-parts whereas run-parts is in /usr/bin
since debianuti
Package: debianutils
Version: 5.3-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrading debianutils to 5.x breaks resolvconf <= 1.87 as it has run-parts
hard-coded to /bin/run-parts
See
Package: plasma-desktop
Version: 4:5.21.5-2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Some recent upgrade of plasma-desktop or associated packages.
* What exactly did you do (or not do)
Correction, /etc/init.d/kexec cannot find run-parts with newer than 4.x
versions of debianutils (which isn't even listed as a dependency of
kexec-tools).
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Package: kexec-tools
Version: 1:2.0.22-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrading debianutils to later than 4.x
* What exactly did you do (or not do) that was effective (o
Package: debianutils
Version: 5.1-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading debianutils beyond 4.x
* What exactly did you do (or not do) that was effective (or
ineff
Package: pulseaudio
Version: 14.2-2
Severity: normal
Tags: upstream
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Some unknown upgrade lead to me having to manually select audio profile on
initial KDE plasma s
Package: gcc-11
Version: 11-20210306-1
Severity: normal
Tags: upstream
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Attempting to build Linux kernel 5.12.0-rc2 with gcc-11
* What exactly did you do (or not
030, Arthur Marsh wrote:
>>Hi, I ran debuild -b after applying your second patch on top of
>your
>>first patch, and received the following result:
>
>Can you try building it in a pbuilder or sbuilder chroot.
>
>Mark
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
rror: debian/rules build subprocess returned exit
status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -b failed
- Original Message -
From: "Mark Hindley"
To:"Arthur Marsh" ,
Cc:
Sent:Fri, 14 Dec 2018 00:57:51 +
Subject:Re: Bug#916247:
After applying the patch suggested for Debian bug 916212 for elogind,
I could restart elogind (239.3-1+patch) without experiencing problems
in the currently running user session.
However, the upgrade 239.1+20181115-1 -> 239.3-1+patch still
resulted in mplayer not being able to play a new track
Hi Mark, this patch seems to have solved the problem of elogind not
restarting during the 239.1+20181115-1 -> 239.3-1 upgrade thanks.
Arthur
- Original Message -
From: "Mark Hindley"
To:"Arthur Marsh" ,
Cc:
Sent:Wed, 12 Dec 2018 17:23:38 +
Subject:Re: Bu
Package: elogind
Version: 239.3-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
running
service elogind restart
from within a desktop session, elogind restarted alright, but with the
next au
Package: elogind
Version: 239.3-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
aptitude upgrade:
[UPGRADE] elogind:amd64 239.1+20181115-1 -> 239.3-1
[UPGRADE] libelogind0:amd64 239.1+20181115
okular 4:17.12.2-2.1 on amd64 also had problems after being prelinked
recently:
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = okular path = /usr/bin pid = 11571
KCrash: Arguments: /usr/bin/okular ZH Toolbox Pack_Dec18.pdf
KCrash: Attempting to start /usr/lib/x86_64-l
The problem with running grub-install was due to consolekit:amd64
1.2.1-4 installing /usr/share/locale/*gmo directories.
Package: grub-pc
Version: 2.02+dfsg1-9
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Attempting to upgrade grub (was set to install grub to /dev/sdb )
* What exactly did you do (or not do)
Package: prelink
Version: 0.0.20131005-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
kdewallet and plasmashell crashing when attempting to restart them
* What exactly did you do (or not d
Package: plasma-workspace
Version: 4:5.13.5-1+b1
Severity: important
File: /usr/bin/plasmashell
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrading packages that plasmashell depended on.
* What exactly
Package: util-linux
Version: 2.32.1-0.1
Severity: important
File: /bin/su
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading util-linux, when did su to root, /usr/sbin wasn't in PATH like
happened with ear
Package: libkwalletbackend5-5
Version: 5.47.0-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading kwallet related libraries from 5.47 to 5.49 I couldn't not access
my passwords stored
Package: kernel-package
Version: 13.018+nmu1
Followup-For: Bug #890817
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Commit appears to be:
https://github.com/torvalds/linux/commit/01f0e5cdedea448ea48eaddc13665
Package: kernel-package
Version: 13.018+nmu1
Followup-For: Bug #890817
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
As of a commit that hit the Linus git head in the last 24 hours again I can't
get an i386 bui
018 at 08:32:18AM +0930, Arthur Marsh wrote:
>> results in machine shutdown. Setting CONCURRENCY_LEGVEL=1 avoids the
>problem.
>
>While gcc may use the system in unusual ways, it does not have the
>permissions to shutdown a system.
>
>If a user space program breaks a system,
Package: gcc-8
Version: 8.2.0-3
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Building a kernel using
CONCURRENCY_LEVEL=2 \
MAKEFLAGS="HOSTCC=gcc-8 CC=gcc-8 LD=ld.gold V=1 VERBOSE=1 KCFLAGS=-m
Package: timidity
Followup-For: Bug #901148
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
After a couple of weeks away I forgot that I had held off upgrading to
timidity 2.14.0-2 and later, and spent several hours again trying to
figure out why
Package: xserver-xorg-core
Followup-For: Bug #902965
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
After building the source package xserver-xorg-video-ati with the patches
above and installing the resulting xserver-xorg-video-radeon_18.0.1-1_amd
Package: xserver-xorg-core
Version: 2:1.20.0-3
Followup-For: Bug #902965
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
As another data point, with current Linux git head kernel, xserver-xorg-core
2:1.20.0-3 and radeon driver, I don't get lxdm sta
Package: xserver-xorg-core
Followup-For: Bug #902965
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
Failed startup /var/log/lxdm.log with xserver-xorg-core 2:1.20.0-3:
** Message: 11:08:32.447: find greeter (nil)
** Message: 11:08:32.447: find i
Package: xserver-xorg-core
Version: 2:1.20.0-3
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading to 2:1.20.0-3 results in lxdm failing to start xserver
* What exactly did you do (or n
ii kernel-common 13.018+nmu1
pn uboot-mkimage
Versions of packages kernel-package suggests:
ii libncurses-dev 6.1+20180210-4
pn linux-source
-- Configuration Files:
/etc/kernel-pkg.conf changed:
maintainer := Arthur Marsh
email := arthur.ma...@internode.on.net
priority := Low
--
ged:
maintainer := Arthur Marsh
email := arthur.ma...@internode.on.net
priority := Low
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/share/kernel-package/ruleset/misc/version_vars.mk
(from kernel-package package)
debsums: changed file /usr/share/kernel-package/
Package: ntpsec
Version: 1.1.0+dfsg1-1
Followup-For: Bug #901439
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
As suggested, ru
Package: ntpsec
Version: 1.1.0+dfsg1-1
Followup-For: Bug #901439
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the
Package: ntp
Followup-For: Bug #901363
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
Upgrading kernel to one that had the follo
Package: ntpsec
Followup-For: Bug #901439
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
Upgraded kernel to:
https://github.com
Package: ntpsec
Version: 1.1.0+dfsg1-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
After having problems with ntp package with post-4.17.0 kernels, tried
ntpsec, which also ran fine under 4.1
Package: ntp
Version: 1:4.2.8p11+dfsg-1
Followup-For: Bug #901363
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
Ran with a 4.17
Package: ntp
Version: 1:4.2.8p11+dfsg-1
Followup-For: Bug #901363
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was th
Package: ntp
Version: 1:4.2.8p11+dfsg-1
Followup-For: Bug #901363
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was th
Package: ntp
Version: 1:4.2.8p11+dfsg-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Noticing that time had drifted when running new kernels:
12 Jun 12:07:53
ntpdate[5469]: step time server
Package: timidity
Version: 2.14.0-3
Followup-For: Bug #901148
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the ou
Package: timidity
Version: 2.14.0-3
Followup-For: Bug #901148
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
restarting pc, starting KDE plasma desktop - no sound in KDE plasma desktop
* What exactly did you
Package: timidity
Followup-For: Bug #901148
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
Upgrading to timidity 2.14.0-3 and ru
Package: timidity
Version: 2.14.0-2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I upgraded to 2.14.0-2, shut down and rebooted to load a new kernel,
sound working outside KDE but not inside K
Package: mkvtoolnix-gui
Version: 23.0.0-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading libcmark:
[UPGRADE] libcmark0:amd64 0.26.1-1.1 -> 0.28.3-1
* What exactly did you do (or n
Package: bind9
Version: 1:9.11.3+dfsg-1
Followup-For: Bug #894000
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
After resetting the permissions of /var/run/bind to group bind and g+w,
it seems to be running fin
Package: bind9
Version: 1:9.11.3+dfsg-1
Followup-For: Bug #894000
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Checking on syslog:
Mar 26 16:16:35 localhost named[2031]: loading configuration: permission deni
Package: bind9
Version: 1:9.11.3+dfsg-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
trying to upgrade bind9 and associated packages:
Setting up bind9 (1:9.11.3+dfsg-1) ...
[] Stopping
maintainer := Arthur Marsh
email := arthur.ma...@internode.on.net
priority := Low
-- no debconf information
ggests:
ii libncurses5-dev [libncurses-dev] 6.1-1
pn linux-source
-- Configuration Files:
/etc/kernel-pkg.conf changed:
maintainer := Arthur Marsh
email := arthur.ma...@internode.on.net
priority := Low
-- no debconf information
Package: konsole
Version: 4:17.08.3-1
Followup-For: Bug #829002
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
randomly seems to change with upgrading packages (latest case was with mesa
libraries)
konsole was
1 - 100 of 1598 matches
Mail list logo
