Bug#1070564: libqt5quick5-gles: attempt to upgrade to version 5.15.10+dfsg-3 tries to remove other packages

2024-05-12 Thread Cristian Ionescu-Idbohrn
On 5/11/24 12:53, Dmitry Shachnev wrote: I see you have installed libqt5quick5-gles and the non-GLES variant of libqt5gui5t64. But your hardware does not really use OpenGL ES, right? There was a period during the 64-bit time_t transition when apt could replace libqt5quick5 with

Bug#1070564: libqt5quick5-gles: attempt to upgrade to version 5.15.10+dfsg-3 tries to remove other packages

2024-05-06 Thread Cristian Ionescu-Idbohrn
Package: libqt5quick5-gles Version: 5.15.10+dfsg-2+b3 Severity: important Hi, I see this message: The following packages have been kept back:   libqt5quick5-gles when trying to upgrade. If I attempt to manually install I get another message: The following packages will be REMOVED:   

Bug#1038729: xkb-data: Upgrade wants to remove nVidia drivers

2023-06-21 Thread Cristian Ionescu-Idbohrn
Hi, I'm also affected by this :( # apt policy xkb-data xkb-data:   Installed: 2.35.1-1   Candidate: 2.38-2   Version table: 2.38-2 500     500 http://deb.debian.org/debian sid/main amd64 Packages     500 http://deb.debian.org/debian sid/main i386 Packages  *** 2.35.1-1 100    

Bug#958488: memtest86+: freezes in non-SMP mode at 15%

2022-02-14 Thread Cristian Ionescu-Idbohrn
Version 5.31b+dfsg-4 now behaves as expected on my hardware. Cheers, -- Cristian

Bug#981010: rxvt-unicode: urxvt segfaults at exit

2021-03-15 Thread Cristian Ionescu-Idbohrn
On 3/15/21 7:26 PM, Holger Schröder wrote: I rebuilt rxvt-unicode with the patch and the urxvt segfaults at exit no longer occurs. For me this is fixed. I didn't patch anything, but I suspect I upgraded some dependency and I no longer see the segfaults. Cheers, -- Cristian

Bug#981010: rxvt-unicode: urxvt segfaults at exit

2021-01-25 Thread Cristian Ionescu-Idbohrn
On 1/25/21 4:40 PM, Ryan Kavanagh wrote: Control: tags -1 + moreinfo unreproducible Hi Christian, I can't reproduce this using an empty urxvt configuration. Could you please share whatever resources you've set? $ xrdb -query | grep -i rxvt So, here it is: Aterm.termName:    rxvt

Bug#981010: rxvt-unicode: urxvt segfaults at exit

2021-01-25 Thread Cristian Ionescu-Idbohrn
Package: rxvt-unicode Version: 9.22-8+b1 Severity: normal I do frequently find these messages in the syslog: , | Jan 25 12:56:28 debian kernel: [338440.918130] urxvt[674]: segfault at | 190 ip 7f7a1a2fdc35 sp 7ffcee280480 error 4 in | libc-2.31.so[7f7a1a2e5000+14b000] | Jan 25

Bug#968484: wireshark hard-wired to libsystemd0?

2020-12-14 Thread Cristian Ionescu-Idbohrn
On Wed, 11 Nov 2020, Thorsten Glaser wrote: > On Wed, 11 Nov 2020, Juliusz Chroboczek wrote: > > > Why on earth would a network traffic analyzer depend on system init? > > Please read https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968379#10 > in which all questions regarding this were

Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean

2020-12-06 Thread Cristian Ionescu-Idbohrn
On Tue, 24 Nov 2020, Cristian Ionescu-Idbohrn wrote: > > I interpret that this way: dns-mgr is confused; it concludes something > has changed, queues DNS updates, concludes nothing has changed and > does not commit anything (after first cleaning up resolv.conf). > > I

Bug#976663: elpa-graphviz-dot-mode: appears to need to depend on elpa-company

2020-12-06 Thread Cristian Ionescu-Idbohrn
Package: elpa-graphviz-dot-mode Version: 0.4.2-1 Severity: important Else it fails to install: , | Setting up elpa-graphviz-dot-mode (0.4.2-1) ... | + [ configure = configure ] | + [ -e /var/lib/emacsen-common/state/package/installed/emacsen-common -a -x

Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean

2020-11-24 Thread Cristian Ionescu-Idbohrn
On Mon, 23 Nov 2020, Matteo F. Vescovi wrote: > > FTR, I mainly use a 4G WWAN connection with an integrated module in my > ThinkPad. Sometimes, I also use home/office Wi-Fi. In my case, I use the laptop mostly at home, wired and wireless, same router, dhcp aquired dns, no 4G involved. > I just

Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean

2020-11-22 Thread Cristian Ionescu-Idbohrn
On Sun, 22 Nov 2020, Matteo F. Vescovi wrote: > On 2020-11-04 at 21:09 (+01), Cristian Ionescu-Idbohrn wrote: > > [...] > > > IMO, my remarks and comments are all _but_ snide and stupid. The > > problem here, as I see it, is this maintainer's _arrogant_ attitude. &g

Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean

2020-11-04 Thread Cristian Ionescu-Idbohrn
On Tue, 3 Nov 2020, Michael Biebl wrote: > Am 03.11.2020 um 22:58 schrieb Cristian Ionescu-Idbohrn: > > On Tue, 3 Nov 2020, Michael Biebl wrote: > > > > > > This bug report doesn't contain any relevant information to be > > > useful > > > &

Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean

2020-11-04 Thread Cristian Ionescu-Idbohrn
On Wed, 4 Nov 2020, Michael Biebl wrote: > > Is NM the sole application touching /etc/resolv.conf? > No other application adding entries to /etc/resolv.conf which NM > doesn't know about? I don't know. Is there a way to find out? The mark in /etc/resolv.conf: # Generated by

Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean

2020-11-04 Thread Cristian Ionescu-Idbohrn
On Tue, 3 Nov 2020, Michael Biebl wrote: > > Anything which would make this bug report more more useful. Leave > out any snide remarks and stupid comments if you can. Alright, one stupid thing is the subject line. Should be: # systemctl restart NetworkManager.service instead (cut/paste

Bug#973701: [Pkg-utopia-maintainers] Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean

2020-11-03 Thread Cristian Ionescu-Idbohrn
On Tue, 3 Nov 2020, Michael Biebl wrote: > > This bug report doesn't contain any relevant information to be useful Bisides the expected comment, what "relevant information" would I need to provide to make this bug report useful? I'd be more than happy to provide it. -- Cristian

Bug#973701: network-manager: 'systemctl restart ModemManager.service' wipes /etc/resolve.conf (almost) clean

2020-11-03 Thread Cristian Ionescu-Idbohrn
Package: network-manager Version: 1.27.91-1 Severity: grave /etc/resolve.conf includes the expected configuration (WRT nameservers) on bootup. After upgrading network-manager and restarting it, /etc/resolve.conf (which is a symlink to /run/NetworkManager/resolv.conf) is basically wiped out.

Bug#968396: wireguard-dkms: kernel module fails to build

2020-09-14 Thread Cristian Ionescu-Idbohrn
On Fri, 14 Aug 2020, Thomas K. wrote: > > Package: wireguard-dkms > Version: 0.0.20200128-1 > Severity: normal I'm in the same boat (almost). Also raspbian. Package: wireguard-dkms Version: 0.0.20200318-1~bpo10+1 I'd set the Severity: important, as the bug makes the package unusable for me.

Bug#968379: wireshark-common: versioned dependency on libsystemd0 breaks installability with elogind

2020-08-19 Thread Cristian Ionescu-Idbohrn
On Wed, 19 Aug 2020, Thorsten Glaser wrote: > On Wed, 19 Aug 2020, Cristian Ionescu-Idbohrn wrote: > > > > libelogind0 actually *does* implement much of libsystemd0's ABI. > > > Just wait for the new version. > > > > Nothing pesonal. This has been gone for

Bug#968379: wireshark-common: versioned dependency on libsystemd0 breaks installability with elogind

2020-08-19 Thread Cristian Ionescu-Idbohrn
On Mon, 17 Aug 2020, Thorsten Glaser wrote: > On Mon, 17 Aug 2020, Cristian Ionescu-Idbohrn wrote: > > > > As a workaround you can use equivs to install a dummy package that > > > Provides: libsystemd0 (99:99) to satisfy wireshark-common's > > > I would h

Bug#968379: wireshark-common: versioned dependency on libsystemd0 breaks installability with elogind

2020-08-17 Thread Cristian Ionescu-Idbohrn
On Mon, 17 Aug 2020, Balint Reczey wrote: > > Hi Cristian, Balint, > As a workaround you can use equivs to install a dummy package that > Provides: libsystemd0 (99:99) to satisfy wireshark-common's > dependencies and lose only the ability to dissect journals which most > likely you are not

Bug#968379: wireshark-common: versioned dependency on libsystemd0 breaks installability with elogind

2020-08-16 Thread Cristian Ionescu-Idbohrn
On Fri, 14 Aug 2020, Balint Reczey wrote: > > Wireshark parses systemd journals and for doing so it depends on > libsystemd0. > The version it depends on is controlled only by the used symbols and > wireshark only build-depends on libsystemd-dev. But Balint, reassigning that bug to elogind

Bug#968484: wireshark hard-wired to libsystemd0?

2020-08-16 Thread Cristian Ionescu-Idbohrn
On Sun, 16 Aug 2020, Harald Dunkel wrote: > > ??? There is no libsystemd0 installed, so it must have been > referenced by wireshark. Do you think this could be replaced by > "libelogind0 | libsystemd0"? in the dependencies? Me too, but different. The cause seems to be the hard dependency of

Bug#968357: rasdaemon: mountdebugfs no longer available

2020-08-13 Thread Cristian Ionescu-Idbohrn
Package: rasdaemon Version: 0.6.6-1 Severity: normal The mountdebugfs script is no longer provided by the blktrace package, since a while back: blktrace (1.2.0-1) unstable; urgency=medium ... * Remove debugfs mounting init script, as systemd is moutning debugfs

Bug#967546: udev: missing /dev/stdin etc.

2020-08-11 Thread Cristian Ionescu-Idbohrn
On Tue, 4 Aug 2020, Jakub Wilk wrote: > > Package: udev > Version: 246-2 Shouldn't this be "Severity: important"? The OS startup can break. > I use sysvinit. After upgrading udev from 245.7-1 to 246-2 and rebooting, > these symlinks went missing: > > /dev/fd > /dev/stderr > /dev/stdin >

Bug#958488: memtest86+: freezes in non-SMP mode at 15%

2020-07-16 Thread Cristian Ionescu-Idbohrn
Similar behaviour here :( CPU selection (parallel, round robin, sequential) does not matter. It just chokes shortly after start. Keyboard control lost. Only the power button is usable. This is a 16G RAM, BIOS boot: Machine: Type: Laptop System: HP product: HP Laptop 14-bp0xx v:

Bug#961807: solaar: missing dependency to python3-pyudev

2020-05-29 Thread Cristian Ionescu-Idbohrn
Package: solaar Version: 1.0.2+dfsg-1 Severity: normal $ solaar --version Solaar: missing required system package python3-pyudev -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign

Bug#958511: rasdaemon: use of uninitialized value

2020-04-23 Thread Cristian Ionescu-Idbohrn
Package: rasdaemon Version: 0.6.5-1+b1 Severity: normal Tags: patch I observed this error displayed at start: # /etc/init.d/rasdaemon start ... Use of uninitialized value in lc at /usr/sbin/ras-mc-ctl line 759. The attached patch works around it. -- System Information:

Bug#956530: can-utils: version 2020.02.04-1 fails to install

2020-04-12 Thread Cristian Ionescu-Idbohrn
Package: can-utils Version: 2018.02.0-1 Severity: normal Preparing to unpack .../can-utils_2020.02.04-1_amd64.deb ... Unpacking can-utils (2020.02.04-1) over (2018.02.0-1) ... dpkg: error processing archive /var/cache/apt/archives/can-utils_2020.02.04-1_amd64.deb (--unpack): trying to overwrite

Bug#947465: scrcpy: please package latest version, 1.12.1

2019-12-27 Thread Cristian Ionescu-Idbohrn
Package: scrcpy Version: 1.11+ds-1 Severity: normal Dear Maintainer, The latest version (actually 1.12) apparently fixes 2 upstream bugs (#940 and #944) which render the application(s) unusable for me. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy:

Bug#947350: rasdaemon: does the package really need the hard dependency to systemd?

2019-12-25 Thread Cristian Ionescu-Idbohrn
Package: rasdaemon Version: 0.6.4-2 Severity: normal Dear Maintainer, The package would be removed if/when systemd is removed, even though it works perfectly well in a sysvinit system. The package does not apear to need that hard dependency, as both an initscript and unit files are provided.

Bug#935304: libpam-systemd: Please relax Depends: systemd-sysv (was: Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful) (fwd)

2019-09-29 Thread Cristian Ionescu-Idbohrn
Bummer... Sorry, was #935304 it was aimed for. -- Forwarded message -- Date: Sun, 29 Sep 2019 11:00:10 +0200 (CEST) From: Cristian Ionescu-Idbohrn To: 940...@bugs.debian.org On Sun, 29 Sep 2019, Mark Hindley wrote: > On Sat, Sep 28, 2019 at 11:41:56AM +0200, Thorsten Gla

Bug#940034: libpam-systemd: Please relax Depends: systemd-sysv (was: Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful)

2019-09-29 Thread Cristian Ionescu-Idbohrn
On Sun, 29 Sep 2019, Mark Hindley wrote: > On Sat, Sep 28, 2019 at 11:41:56AM +0200, Thorsten Glaser wrote: > > On Sat, 28 Sep 2019, Cristian Ionescu-Idbohrn wrote: > > > > > 1. install sysvinit-core; that removes systemd-sysv but nothing else > > >sy

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-29 Thread Cristian Ionescu-Idbohrn
On Sat, 28 Sep 2019, Thorsten Glaser wrote: > On Sat, 28 Sep 2019, Cristian Ionescu-Idbohrn wrote: > > > 1. install sysvinit-core; that removes systemd-sysv but nothing else > >systemd related > > > Souldn't that work? > > It would, if but for libpam-system

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-28 Thread Cristian Ionescu-Idbohrn
Mark, On Fri, 27 Sep 2019, Mark Hindley wrote: > > Thanks. The aim of preventing accidental removal of systemd is very > reasonable. However, using this approach the hurdle you create even > to a user who really wants to uninstall is pretty high. Few people > will continue having seen the

Bug#925344: polkit-qt-1: Please support new logind virtual packages

2019-09-22 Thread Cristian Ionescu-Idbohrn
Maintainers, On Sat, 23 Mar 2019, Mark Hindley wrote: > > Package: polkit-qt-1 > Version: 0.112.0-6 > Severity: normal > Tags: patch > > Dear Maintainer, > > Please change polkit-qt-1 to use the new default-logind and logind > virtual packages. This will enable binaries built from

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

2019-09-22 Thread Cristian Ionescu-Idbohrn
On Sat, 21 Sep 2019, Mark Hindley wrote: > On Sat, Sep 21, 2019 at 06:51:16PM +0200, Cristian Ionescu-Idbohrn wrote: > > > Would you, please, start a new bug for this unless you really think > > > it is the same issue (apt being broken by continuing to uninstall > >

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

2019-09-21 Thread Cristian Ionescu-Idbohrn
On Sat, 21 Sep 2019, Mark Hindley wrote: > On Sat, Sep 21, 2019 at 04:35:39PM +0200, Cristian Ionescu-Idbohrn wrote: > > I'm interested in this, but my systems (unstable and testing) are > > in a slightly different state. Let's take unstable, for example: > > Thanks for th

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

2019-09-21 Thread Cristian Ionescu-Idbohrn
On Sat, 21 Sep 2019, Mark Hindley wrote: > > Removing the pending tag as I don't think there is anything for > elogind to do to fix this. Hi, I'm interested in this, but my systems (unstable and testing) are in a slightly different state. Let's take unstable, for example: , | #

Bug#915834: fixed in irqbalance 1.5.0-2

2019-08-21 Thread Cristian Ionescu-Idbohrn
On Sat, 12 Jan 2019, Andreas Henriksson wrote: > > Source: irqbalance > Source-Version: 1.5.0-2 > > We believe that the bug you reported is fixed in the latest version of > irqbalance, which is due to be installed in the Debian FTP archive. > > A summary of the changes between this version and

Bug#925142: hp-plugin generates libsane udev rules lacking LABEL

2019-05-06 Thread Cristian Ionescu-Idbohrn
On Wed, 20 Mar 2019, Christian Kastner wrote: > > Package: hplip > Version: 3.18.12+dfsg0-2 > Severity: minor > > The utility hp-plugin generated a file S99-2000S1.rules in > /etc/udev/rules.d/, which I've attached. This sets up permissions for my > HP LaserJet Pro MFP 176n. > > Note that in

Bug#923478: initscripts use unsafe `: >` shell command to create files

2019-04-14 Thread Cristian Ionescu-Idbohrn
On Sun, 14 Apr 2019, Dmitry Bogatov wrote: > > Definitely. But default one is from bin:util-linux. On my sid/unstable: # dpkg -S /bin/login login: /bin/login # dpkg -s login Package: login Essential: yes Status: install ok installed Priority: required Section: admin Installed-Size: 2695

Bug#923478: initscripts use unsafe `: >` shell command to create files

2019-04-11 Thread Cristian Ionescu-Idbohrn
On Thu, 11 Apr 2019, Dmitry Bogatov wrote: > > Warning message and make do_start return 1, I guess. This is what I can come up with: >From 1ae8cb1cb6a306281ccddfa7aa67c13f6cb23ab5 Mon Sep 17 00:00:00 2001 From: Cristian Ionescu-Idbohrn Date: Thu, 11 Apr 2019 14:36:47 +0200 Subjec

Bug#923478: initscripts use unsafe `: >` shell command to create files

2019-04-08 Thread Cristian Ionescu-Idbohrn
On Mon, 8 Apr 2019, Dmitry Bogatov wrote: > [2019-04-07 10:52] Cristian Ionescu-Idbohrn > > > On Sat, 6 Apr 2019, Dmitry Bogatov wrote: > > > > The redirection in /etc/init.d/bootmisc.sh on line 29 is _not_ error > > handled. Writing to a file can fail (for

Bug#923478: initscripts use unsafe `: >` shell command to create files

2019-04-07 Thread Cristian Ionescu-Idbohrn
On Sat, 6 Apr 2019, Dmitry Bogatov wrote: > [2019-04-05 11:11] Cristian Ionescu-Idbohrn > > > Thing is neither the `:' nor the `true' commands are needed. To > > truncate a file it's sufficient to redirect _nothing_ to that file. > > > > $ dash -c '>/tm

Bug#923478: initscripts use unsafe `: >` shell command to create files

2019-04-05 Thread Cristian Ionescu-Idbohrn
On Thu, 28 Feb 2019, Thorsten Glaser wrote: > > I’d say that aborting might be preferrable, but I checked your patch. > > In the first case, it’s indeed preferrable to continue the init script > (and have the two additional error messages from chmod and chgrp, but > it continue on), and in the

Bug#925301: svtplay-dl: crashed on svtplay.se, Rapport news download

2019-03-23 Thread Cristian Ionescu-Idbohrn
This seems to be corrected in upstream git 2.1-46-g05c322a. Cheers, -- Cristian

Bug#925301: svtplay-dl: crashed on svtplay.se, "Rapport" news download

2019-03-22 Thread Cristian Ionescu-Idbohrn
Package: svtplay-dl Version: 2.1-1 Severity: important This is what I see, both with the packaged version 2.1-1 and upstream master 2.1-41-gdcbf6a8. I've seen this both with yesterday's 18.00 news and today's 16.00 news: $ /usr/bin/svtplay-dl -g

Bug#914126: svtplay-dl: bugs out on urplay.se

2019-03-06 Thread Cristian Ionescu-Idbohrn
On Tue, 5 Mar 2019, Olof Johansson wrote: > On 19-01-09 19:16 +0100, Cristian Ionescu-Idbohrn wrote: > > It redirects to streaming-loadbalancer.ur.se/loadbalancer.json > > (130.242.59.74), which seems to be _the real problem_ (supports _only_ > > TLS 1.0/SSL3). loadbala

Bug#923642: grub-pc: package upgrade triggers assemble md arrays, which fails

2019-03-04 Thread Cristian Ionescu-Idbohrn
I just discovered the bug is triggered from udisks2 too. Easily reproducible: # apt-get --reinstall install udisks2 Please feel free to reassign this bug to the rightful package. -- Cristian

Bug#923642: grub-pc: package upgrade triggers assemble md arrays, which fails

2019-03-03 Thread Cristian Ionescu-Idbohrn
Package: grub-pc Version: 2.02+dfsg1-12 Severity: normal I find this in the system logs: , | Mar 2 12:12:48 debian kernel: <1052>[2404365.421416] systemd-udevd[20006]: Process '/sbin/mdadm --incremental --export /dev/sda1 --offroot /dev/disk/by-id/wwn-0x5000c5005ad68f36-part1

Bug#921841: wmweather: fails to fetch weather data

2019-02-09 Thread Cristian Ionescu-Idbohrn
Package: wmweather Version: 2.4.6-2+b1 Severity: important Stopped working some 5-6 days ago. Prints this on the console: , | wmweather: Received error 302 while fetching ESMS from NOAA, aborting | wmweather: Please send a bug report to ` and returns exit status 1. Run under `strace'

Bug#920689: grub-common: /dev/sdd: open failed: No medium found

2019-01-28 Thread Cristian Ionescu-Idbohrn
Package: grub-common Version: 2.02+dfsg1-10 Severity: normal Bellow, steps to reproduce the bug and my interpretation. During kernel startup, an USB wifi dongle is detected and a firmware blob is loaded to a storage device on the dongle: Jan 22 10:37:36 kernel: [5.344564] rtl8192cu: Chip

Bug#914126: svtplay-dl: bugs out on urplay.se

2019-01-09 Thread Cristian Ionescu-Idbohrn
On Fri, 23 Nov 2018, Olof Johansson wrote: > On 18-11-19 18:37 +0100, Cristian Ionescu-Idbohrn wrote: > > This is what I see: > ... > > requests.exceptions.SSLError: > > HTTPSConnectionPool(host='streaming-loadbalancer.ur.se', port=443): Max > > retries exceede

Bug#916678: systemd: Caught , dumped core as pid 2097

2018-12-18 Thread Cristian Ionescu-Idbohrn
On Mon, 17 Dec 2018, Bernhard Übelacker wrote: > > Hello Cristian Ionescu-Idbohrn, > following is what I get from a buster amd64 qemu VM, > with explicitly downgraded systemd packages to 239-13: > > It has quite a similarity to upstream bug [1]. > And upstream received a fi

Bug#916678: systemd: Caught , dumped core as pid 2097

2018-12-18 Thread Cristian Ionescu-Idbohrn
On Tue, 18 Dec 2018, Michael Biebl wrote: > > first, thanks a lot Bernhard for providing a properly annotated > backtrace! It does indeed look very similar to the one in [1] Agreed. > Am 18.12.18 um 18:45 schrieb Bernhard Übelacker: > > Am 18.12.2018 um 09:35 schrieb Cristi

Bug#916678: systemd: Caught , dumped core as pid 2097

2018-12-17 Thread Cristian Ionescu-Idbohrn
On Mon, 17 Dec 2018, Michael Biebl wrote: > > What's the output of > coredumpctl list # coredumpctl list No coredumps found. > ls -la /var/lib/systemd/coredump/ # ls -l /var/lib/systemd/coredump/ -rw-r- 1 root root 873282 Dec 16 17:16

Bug#916678: systemd: Caught , dumped core as pid 2097

2018-12-17 Thread Cristian Ionescu-Idbohrn
On Mon, 17 Dec 2018, Michael Biebl wrote: > > Do you by chance still have a core file of the crash? If there were one, where would I find it? Are there instructions somewhere? I do see both /usr/lib/sysctl.d/50-coredump.conf and: # cat /proc/sys/kernel/core_pattern

Bug#916678: systemd: Caught , dumped core as pid 2097

2018-12-17 Thread Cristian Ionescu-Idbohrn
On Mon, 17 Dec 2018, Michael Biebl wrote: > > Control: severity -1 important > Control: tags -1 moreinfo > > Am 17.12.18 um 11:25 schrieb Cristian Ionescu-Idbohrn: > > > | systemd[1]: Caught , dumped core as pid 2097. > > Please try to get a backtrace follo

Bug#916678: systemd: Caught , dumped core as pid 2097

2018-12-17 Thread Cristian Ionescu-Idbohrn
Package: systemd Version: 239-13 Severity: critical Justification: breaks the whole system While trying to upgrade postfix* packages I ended up in this mess :( Every attempt (I know off) to get out of it failed :( I also lost the ability to ssh login. , | systemd[1]: Caught , dumped core as

Bug#914126: svtplay-dl: bugs out on urplay.se

2018-11-24 Thread Cristian Ionescu-Idbohrn
On Sat, 24 Nov 2018, Cristian Ionescu-Idbohrn wrote: > On Fri, 23 Nov 2018, Olof Johansson wrote: > > On 18-11-19 18:37 +0100, Cristian Ionescu-Idbohrn wrote: > > > This is what I see: > > ... > > > requests.exceptions.SSLError: > > > HTTPSConnectionPool

Bug#914126: svtplay-dl: bugs out on urplay.se

2018-11-24 Thread Cristian Ionescu-Idbohrn
On Fri, 23 Nov 2018, Olof Johansson wrote: > On 18-11-19 18:37 +0100, Cristian Ionescu-Idbohrn wrote: > > This is what I see: > ... > > requests.exceptions.SSLError: > > HTTPSConnectionPool(host='streaming-loadbalancer.ur.se', port=443): Max > > retries exceede

Bug#914126: svtplay-dl: bugs out on urplay.se

2018-11-19 Thread Cristian Ionescu-Idbohrn
Package: svtplay-dl Version: 1.9.11-1 Severity: important This is what I see: DEBUG [1542646174.83] /usr/bin/svtplay-dl/svtplay_dl/__init__.py/get_media: version: 1.9.11 DEBUG [1542646174.83] /usr/bin/svtplay-dl/svtplay_dl/utils/__init__.py/request: HTTP getting

Bug#538334: initscripts: /etc/init.d/bootlogd oddities

2018-11-16 Thread Cristian Ionescu-Idbohrn
On Fri, 16 Nov 2018, Dmitry Bogatov wrote: > [2018-11-15 12:43] Cristian Ionescu-Idbohrn > > > The point I was trying to make is that with code like this: > > > > cd /var/log && { > > ... do stuff ... > > } > > ^ > >

Bug#538334: initscripts: /etc/init.d/bootlogd oddities

2018-11-15 Thread Cristian Ionescu-Idbohrn
On Thu, 15 Nov 2018, Dmitry Bogatov wrote: > > I am aware, that this bug is 9 years old. I partially applied this > patch. See `b6022b1' at https://salsa.debian.org/debian/sysvinit. Still, things happen ;) > > Similar with above. Inverting logic will keep you on the right path. > > > > -

Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken

2018-11-13 Thread Cristian Ionescu-Idbohrn
On Tue, 13 Nov 2018, Russel Winder wrote: > > > Try this: > > > > https://snapshot.debian.org/binary/firehol/ > > Thanks for the pointer. I run Approx, so I have the history of > packages here anyway. The issue is whether I have to delve into it > for manual installation, or whether the

Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken

2018-11-13 Thread Cristian Ionescu-Idbohrn
On Tue, 13 Nov 2018, Russel Winder wrote: > > > It does not look as a solution anyway. > > And the issue does not seem to be a FireHOL issue. > > I guess that we have to stick to package 3.1.6+ds-4 for a while. > > I've held all but one machine on 3.1.6+ds-4 but now need to revert > the one

Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken

2018-11-13 Thread Cristian Ionescu-Idbohrn
On Tue, 13 Nov 2018, Jerome BENOIT wrote: > On 12/11/2018 22:42, Cristian Ionescu-Idbohrn wrote: > > You don't happen to have that "move everything from /bin, /sbin, /lib > > to /usr/..." package installed? > > Do know have the short name (or regular name) of this

Bug#912768: hplip-data: hp-toolbox fsck

2018-11-12 Thread Cristian Ionescu-Idbohrn
On Mon, 12 Nov 2018, Brian Potkin wrote: > On Mon 12 Nov 2018 at 19:28:05 +0100, Cristian Ionescu-Idbohrn wrote: > > On Mon, 12 Nov 2018, Brian Potkin wrote: > > > > > > A small favour, Cristian. Please do > > > > > > avahi-browse -rt _scanner._t

Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken

2018-11-12 Thread Cristian Ionescu-Idbohrn
On Mon, 12 Nov 2018, Russel Winder wrote: > > > Can you get te version og the ffirehol package ? > > |> dpkg -l *firehol* > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err:

Bug#912768: hplip-data: hp-toolbox fsck

2018-11-12 Thread Cristian Ionescu-Idbohrn
On Mon, 12 Nov 2018, Brian Potkin wrote: > On Thu 08 Nov 2018 at 20:43:04 +0100, Cristian Ionescu-Idbohrn wrote: > > On Tue, 6 Nov 2018, Till Kamppeter wrote: > > > > > > After applying this change "scanimage -L" discovers also my > > > scanner whe

Bug#912624: closed by Jerome Benoit (Bug#912624: fixed in firehol 3.1.6+ds-4)

2018-11-11 Thread Cristian Ionescu-Idbohrn
On Sun, 11 Nov 2018, Cristian Ionescu-Idbohrn wrote: > On Sun, 11 Nov 2018, Jerome BENOIT wrote: > > > > Hello, I am sorry to read that. > > > > When you say `This is sysV init, _not_ systemd', > > do you mean that you run on a Debian box (but not a Devuan box

Bug#912624: closed by Jerome Benoit (Bug#912624: fixed in firehol 3.1.6+ds-4)

2018-11-11 Thread Cristian Ionescu-Idbohrn
ing the message bellow that I managed to overwrite the conf-files (both /etc/default/firehol and /etc/firehol/firehol.conf) in the process. I'll continue investigation, though. > On 10/11/2018 18:05, Cristian Ionescu-Idbohrn wrote: > > On Wed, 7 Nov 2018, Debian B

Bug#912624: closed by Jerome Benoit (Bug#912624: fixed in firehol 3.1.6+ds-4)

2018-11-10 Thread Cristian Ionescu-Idbohrn
On Wed, 7 Nov 2018, Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > which was filed against the firehol package: > > #912624: firehol: both 3.1.5+ds1-3 and 3.1.6+ds-1 broken for me > > It has been closed by Jerome Benoit . > > Their

Bug#912768: hplip-data: hp-toolbox fsck

2018-11-08 Thread Cristian Ionescu-Idbohrn
On Tue, 6 Nov 2018, Till Kamppeter wrote: > > After applying this change "scanimage -L" discovers also my scanner when > connected to the network and I can scan from any SANE-based application > without needing a print queue using the "hp" CUPS backend of HPLIP. Till and Brian, I now managed to

Bug#912768: hplip-data: hp-toolbox fsck

2018-11-07 Thread Cristian Ionescu-Idbohrn
On Tue, 6 Nov 2018, Till Kamppeter wrote: > [...] > Now I did some debugging and found out that "scanimage -l" discovers > the scanner with the URI (device on network, note the "hp_" missing > in the model name, upper/lower case is ignored by HPLIP): > >

Bug#912768: hplip-data: hp-toolbox fsck

2018-11-06 Thread Cristian Ionescu-Idbohrn
On Mon, 5 Nov 2018, Brian Potkin wrote: > > It would be useful to have what happens with > > scanimage -d "hpaio:/net/HP_ColorLaserJet_MFP_M278-M281?ip=192.168.x.y" > > out.pnm > > for 3.18.10+dfsg0-1. > > Does the scanner work? Do you get out.pnm? Will do. I'll try to find the time within

Bug#912768: hplip-data: hp-toolbox fsck

2018-11-05 Thread Cristian Ionescu-Idbohrn
On Mon, 5 Nov 2018, Brian Potkin wrote: > On Sun 04 Nov 2018 at 23:21:14 +, Brian Potkin wrote: > > > avahi-deamon is essential; there were no instructions to uninstall it. > > Without it you will be unable to detect the DNS-SD broadcasts of the > > printer/scanner device. Put it back. > >

Bug#912768: hplip-data: hp-toolbox fsck

2018-11-04 Thread Cristian Ionescu-Idbohrn
On Sun, 4 Nov 2018, Brian Potkin wrote: > > Can we just forget about the bug you reported for a while and, to begin > with, get you printing satisfactorily? But than you forget about the scanning, don't you, which is the major part of the problem. > Why tie yourself into the tyranny of vendor

Bug#912768: hplip-data: hp-toolbox fsck

2018-11-04 Thread Cristian Ionescu-Idbohrn
On Sun, 4 Nov 2018, Cristian Ionescu-Idbohrn wrote: > On Sat, 3 Nov 2018, Brian Potkin wrote: > > On Sat 03 Nov 2018 at 19:20:42 +0100, Cristian Ionescu-Idbohrn wrote: > > > > > Package: hplip-data > > > Version: 3.18.10+dfsg0-1 > > > Severity: grave >

Bug#912768: hplip-data: hp-toolbox fsck

2018-11-04 Thread Cristian Ionescu-Idbohrn
On Sat, 3 Nov 2018, Brian Potkin wrote: > On Sat 03 Nov 2018 at 19:20:42 +0100, Cristian Ionescu-Idbohrn wrote: > > > Package: hplip-data > > Version: 3.18.10+dfsg0-1 > > Severity: grave > > Justification: renders package unusable > > > If you would exp

Bug#912765: hplip: hp-doctor broken

2018-11-04 Thread Cristian Ionescu-Idbohrn
On Sat, 3 Nov 2018, Brian Potkin wrote: > On Sat 03 Nov 2018 at 19:02:37 +0100, Cristian Ionescu-Idbohrn wrote: > > > Package: hplip > > Version: 3.18.10+dfsg0-1 > > Severity: grave > > Justification: renders package unusable > > > > $ hp-doctor > &g

Bug#912768: hplip-data: hp-toolbox fsck

2018-11-03 Thread Cristian Ionescu-Idbohrn
Package: hplip-data Version: 3.18.10+dfsg0-1 Severity: grave Justification: renders package unusable $ hp-toolbox HP Linux Imaging and Printing System (ver. 3.18.10) HP Device Manager ver. 15.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY.

Bug#912765: hplip: hp-doctor broken

2018-11-03 Thread Cristian Ionescu-Idbohrn
Package: hplip Version: 3.18.10+dfsg0-1 Severity: grave Justification: renders package unusable $ hp-doctor Traceback (most recent call last): File "/usr/bin/hp-doctor", line 42, in check_extension_module_env('cupsext') File "/usr/share/hplip/base/g.py", line 339, in

Bug#912624: firehol: both 3.1.5+ds1-3 and 3.1.6+ds-1 broken for me

2018-11-01 Thread Cristian Ionescu-Idbohrn
Package: firehol Version: 3.1.5+ds1-2 Severity: important 3.1.5+ds1-2 is the (downgraded) version that works for me. This is sysV init, _not_ systemd. Both 3.1.5+ds1-3 and 3.1.6+ds-1 fail on upgrade. Messages are: [FAIL] Restarting firewall: firehol failed! invoke-rc.d:

Bug#905305: emacs-common: terrible mess

2018-08-07 Thread Cristian Ionescu-Idbohrn
On Mon, 6 Aug 2018, Rob Browning wrote: > > As far as emacs is concerned, it's intended to fully displace the > emacsXY packages, hence the conflicts with all of the emacsXY-common > pacakges in the new emacsen-common. Yes. And it seems testing/buster is even a bigger mess, as emacs (and

Bug#905305: emacs-common: terrible mess

2018-08-06 Thread Cristian Ionescu-Idbohrn
On Sun, 5 Aug 2018, Cristian Ionescu-Idbohrn wrote: > > The only one I regret seeing go away is: > > /usr/share/emacs25/site-lisp/emacs-goodies-el/align-string.el This happens on a debian testing box: Setting up emacs-goodies-el (40.0) ... Install emacsen-common for ema

Bug#905305: emacs-common: terrible mess

2018-08-05 Thread Cristian Ionescu-Idbohrn
On Sun, 5 Aug 2018, Rob Browning wrote: > > If you can tell what's going wrong, please consider filing bugs against > the relevant add-on packages, or contacting #debian-emacsen or > debian-emac...@lists.debian.org. Thanks. Showed up the culprit was initz package (which I don't use since quite

Bug#905305: emacs-common: terrible mess

2018-08-02 Thread Cristian Ionescu-Idbohrn
Package: emacs-common Version: 1:25.2+1-8 Severity: important Recent updates/transitions give me a hard time. I had to remove older versions 23 amd 24 because of package upgrade failures. The only installed version now is emacs25. Been using debian and emacs for some 20 years. This is a system

Bug#900025: /usr/lib/x86_64-linux-gnu/libm.so: invalid ELF header

2018-07-30 Thread Cristian Ionescu-Idbohrn
On Sun, 29 Jul 2018, Brian Potkin wrote: > > tags 900025 moreinfo > thanks > > On Thu 24 May 2018 at 21:12:47 +0200, Cristian Ionescu-Idbohrn wrote: > > > Package: libc6-dev > > Version: 2.27-3 > > Severity: normal > > > > Not sure if this sh

Bug#745411: hplip: hplip_config_usb_printer producing kernel Call Trace

2018-07-30 Thread Cristian Ionescu-Idbohrn
On Mon, 30 Jul 2018, Brian Potkin wrote: > > tags 745411 moreinfo > thanks > > On Mon 21 Apr 2014 at 14:50:36 +0200, Cristian Ionescu-Idbohrn wrote: > > > > Is there _any_ standard procedure I could use instead, to avoid > > mangling 56-hpmud.rules? > >

Bug#901557: chkrootkit: false positive - Warning: /sbin/init INFECTED

2018-06-14 Thread Cristian Ionescu-Idbohrn
Package: chkrootkit Version: 0.52-2 Severity: normal There's a bug on line 1027 in /usr/sbin/chkrootkit: if [ "${QUIET}" != "t" ];then printn "Searching for Suckit rootkit... "; fi if [ ${SYSTEM} != "HP-UX" ] && ( ${strings} ${ROOTDIR}sbin/init | ${egrep} '\.sniffer' || \

Bug#900025: /usr/lib/x86_64-linux-gnu/libm.so: invalid ELF header

2018-05-26 Thread Cristian Ionescu-Idbohrn
On Fri, 25 May 2018, Aurelien Jarno wrote: > On 2018-05-24 21:12, Cristian Ionescu-Idbohrn wrote: > > Package: libc6-dev > > Version: 2.27-3 > > Severity: normal > > > > Not sure if this should be filed against simple-scan. In that case > > feel free to

Bug#900025: Acknowledgement (/usr/lib/x86_64-linux-gnu/libm.so: invalid ELF header)

2018-05-24 Thread Cristian Ionescu-Idbohrn
This is what I find on my box: /lib/i386-linux-gnu/libm.so.6: symbolic link to libm-2.27.so /lib/x86_64-linux-gnu/libm.so.6: symbolic link to libm-2.27.so /lib32/libm.so.6: symbolic link to libm-2.27.so /libx32/libm.so.6: symbolic link to libm-2.27.so

Bug#900025: /usr/lib/x86_64-linux-gnu/libm.so: invalid ELF header

2018-05-24 Thread Cristian Ionescu-Idbohrn
Package: libc6-dev Version: 2.27-3 Severity: normal Not sure if this should be filed against simple-scan. In that case feel free to reassign. simple-scan: common/utils.c 188: unable to load library libm.so: /usr/lib/x86_64-linux-gnu/libm.so: invalid ELF header Adn these are the contents of

Bug#774711: openssh 7.6 changes

2018-04-21 Thread Cristian Ionescu-Idbohrn
On Fri, 20 Apr 2018, Matt Taggart wrote: > > Debian users wanting to drop support for the legacy crypto options > mentioned previously in this bug can use the following: > > === > HostKeyAlgorithms

Bug#889487: linux-image-4.14.0-2-amd64: please enable CONFIG_X86_MCELOG_LEGACY

2018-02-20 Thread Cristian Ionescu-Idbohrn
On Tue, 20 Feb 2018, Ben Hutchings wrote: > On Sun, 2018-02-18 at 22:31 +0100, Cristian Ionescu-Idbohrn wrote: > > On Tue, 6 Feb 2018, Roger Lynn wrote: > > > On 04/02/18 02:00, Jon DeVree wrote: > > > > On Sun, Feb 04, 2018 at 01:03:59 +0100, Ben Hutchings wrote: &g

Bug#889487: linux-image-4.14.0-2-amd64: please enable CONFIG_X86_MCELOG_LEGACY

2018-02-18 Thread Cristian Ionescu-Idbohrn
On Tue, 6 Feb 2018, Roger Lynn wrote: > On 04/02/18 02:00, Jon DeVree wrote: > > On Sun, Feb 04, 2018 at 01:03:59 +0100, Ben Hutchings wrote: > >> This was unintentional, but I think it's correct. The Kconfig says to > >> use rasdaemon which is already packaged and in stable. > > > > rasdaemon

Bug#889468: libsane-hpaio: similar story, different model

2018-02-03 Thread Cristian Ionescu-Idbohrn
Package: libsane-hpaio Version: 3.17.10+repack0-2 Followup-For: Bug #879719 And the model is a: HP Color LaserJet MFP M281fdw. After duplicating the [hp_color_laserjet_mfp_m277dw] configuration block and modifying it: -[hp_color_laserjet_mfp_m277dw] +[hp_colorlaserjet_mfp_m278-m281] and:

Bug#888027: xfce4-power-manager: possibly a lot of stuff broken because of libpam-runtime missing libpam-runtime option "2. Register user sessions in the systemd control group hierarchy"

2018-01-22 Thread Cristian Ionescu-Idbohrn
Package: xfce4-power-manager Version: 1.4.4-4 Severity: important Not setting "2. Register user sessions in the systemd control group hierarchy" in libpam-runtime, when running under systemd init will break most stuff under power-manager settings. Unfortunatelly: # dpkg-reconfigure -p

  1   2   3   4   5   6   7   >