Bug#865389: plasma-desktop: incorrect German translation of icon sizes

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=381467 signature.asc Description: This is a digitally signed message part.

Bug#827184: [Pkg-kde-extras] Bug#827184: yakuake: "Manage Profiles" settings option doesn't work

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=360072 signature.asc Description: This is a digitally signed message part.

Bug#876421: akonadi-backend-postgresql does not support PostgreSql 10

Package: akonadi-backend-postgresql Version: 4:16.04.3-6 Severity: important Just got an upgrade of my postgres packages from 9.6 to 10 and upgraded my (main) cluster containing my akonadi database. While kmail does seem to work*, it looks like all my mails are now marked as unread :-/ So did the

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

This is essentially a +1 message and downgrading udisks2 + libudisks2-0 to the testing version fixed it for me too signature.asc Description: This is a digitally signed message part.

Bug#877922: kwin-x11 carsh with qt-5.9.2

On zaterdag 7 oktober 2017 12:15:18 CEST Eric Valette wrote: > ii libqt5x11extras5 5.9.1-2+b1 That package is still at the 'old' version. Wouldn't be surprised if that has something to do with it. signature.asc Description: This is a digitally signed message part.

Bug#877910: irssi-plugin-xmpp: Fails to install due to conflict with irssi

Package: irssi-plugin-xmpp Version: 0.54-1 Severity: grave Justification: renders package unusable Trying to upgrade the package to 0.54-1 from 0.53-1+b1 fails with the following error: Preparing to unpack .../irssi-plugin-xmpp_0.54-1_amd64.deb ... Unpacking irssi-plugin-xmpp:amd64 (0.54-1) over

Bug#879960: libqt5sql5-psql: [libqt5sql5-psql] basic support postgresql-10

On donderdag 23 november 2017 09:34:40 CET Dmitry Shachnev wrote: > Thank you. The fix is applied in Git now, will be in the next upload. \o/ signature.asc Description: This is a digitally signed message part.

Bug#884652: [Pkg-kde-extras] Bug#884652: quassel-client: connection password stored in plan Ascii in a chmod 644 file

On maandag 18 december 2017 06:21:44 CET Heinrich Schuchardt wrote: > the configuration of quassel client is stored in > ~/.config/quassel-irc.org/quasselclient.conf > This file was created on my system as chmod 644. So it is world readable. That's also what I thought, but it's not as bad as one

Bug#806500: [Pkg-kde-extras] Bug#806500: Bug#884652: quassel-client: connection password stored in plan Ascii in a chmod 644 file

On maandag 18 december 2017 21:08:46 CET Felix Geyer wrote: > Well, that's the unfortunate state of security on the Linux desktop (and > other major desktop OSes). Largely there is no privilege separation between > applications. > They all run in the same context so they can't really keep secrets

Bug#806500: [Pkg-kde-extras] Bug#806500: Bug#884652: quassel-client: connection password stored in plan Ascii in a chmod 644 file

On maandag 18 december 2017 23:27:54 CET Heinrich Schuchardt wrote: > Storing the password in the KDE wallet manager would mean that the > password could only be retrieved when the wallet is open. Problem with that is that it creates a dependency on KDE, while quassel only needs QT

Bug#881973: kde-spectacle: Please build against libkf5kipi32.0.0 in experimental

Package: kde-spectacle Version: 16.08.3-2 Severity: wishlist Currently you can't install gwenview from experimental together with kde-spectacle as both kde-spectacle versions (sid+experimental) are build against libkf5kipi31.0.0. Therefor hereby the request for a rebuild of kde-spectacle in

Bug#883435: akonadi-backend-postgresql: akonadictl start fails with Postgresql 10 installed, likely needs a rebuild

Package: akonadi-backend-postgresql Version: 4:17.08.0-1 Severity: important Now that qt does support Postgresql 10 (#876421) I upgraded my Postgresql packages to 10 and migrated the cluster (from 9.6). After that I did 'akonadictl start' and noticed it was still using Postgresql 9.6. So I purged

Bug#883997: libkscreenlocker5: screen lock with photo slideshow eats up all memory and triggers oom killer

On zondag 10 december 2017 10:19:24 CET Philipp Huebner wrote: > Looking at syslog after the reboot, I see that oom killer was triggered > several times, as there was no free RAM and no free SWAP left any more. > It also shows that libkscreenlocker5 is using by far the most memory, > and every

Bug#837513: obsolete

On woensdag 6 december 2017 22:47:19 CET Wolfgang Rohdewald wrote: > Why do I actively have to search for kajongg bug reports? > > Is there some way you can setup automatic notification for kajongg bugs? Hit the 'Subscribe' button on https://tracker.debian.org/pkg/kajongg signature.asc

Bug#879794: [Pkg-kde-extras] Bug#879794: kwave: burns CPU

On donderdag 26 oktober 2017 05:20:45 CEST Matthias Urlichs wrote: > ii libkf5configcore5 5.28.0-2 > ii libkf5configwidgets5 5.37.0-2 You have a whole bunch of misfitting versions of framework components. Make sure all the libkf5* packages have the same version (5.37.0-2)

Bug#879960: libqt5sql5-psql: [libqt5sql5-psql] basic support postgresql-10

On Friday, October 27, 2017 11:34:08 PM CEST Damir R. Islamov wrote: > Tags: patch > >* QT-5.9.[1,2] (and future QT-5.10?) in the upstram do not support > PostgreSQL 10. Thanks for this patch! I ran into this problem with https://bugs.debian.org/cgi-bin/bugreport.cgi? bug=876421 and thus

Bug#898320: kdeconnect: 1.3.0 does not work with 1.8.2 android version

On vrijdag 11 mei 2018 10:18:06 CEST Eric Valette wrote: > It can be on the client side (android both and 1.8.2 android version > both) but I have two differents. It could be network but no firewall and > both machines do see each other using ssh, upnp, ... With me it also fails from time to time

Bug#900957: kmail: Unable to contact

On donderdag 7 juni 2018 12:15:27 CEST Griera wrote: > virtually every time while attempting to display emails, the colour of the > names of all email folders in the KMail section turns red, and the status > indicator line shows: > "Unable to fetch item from backend (collection-1): Unable to

Bug#901488: Please provide static archives inside libtqt4-dev !

On vrijdag 15 juni 2018 02:30:46 CEST Lisandro Damián Nicanor Pérez Meyer wrote: > > No, because of porting, it doesn't. But that time, that's on my side. > > Though please note that no Bitcoin forks got ported to qt5 in general, > > ever (not Bitcoin core itself, not Litecoin, not Peercoin.

Bug#899274: KMail does not always remember the desired message list columns

On dinsdag 22 mei 2018 14:20:38 CEST Sandro Knauß wrote: > Control: reassign -1 src:qtbase-opensource-src 5.10.1+dfsg-6 > Control: forward -1 https://bugreports.qt.io/browse/QTBUG-65478 > Control: affects -1 kmail > ... > I can confirm this bug. On kdepim-us...@kde.org it was mentioned that this >

Bug#899274: KMail does not always remember the desired message list columns

On woensdag 30 mei 2018 01:11:50 CEST Sandro Knauß wrote: > But I do not understand the bugtracker for Qt within which version > what is fixed. I don't understand it either (apparently) as to me the bug you mentioned/ linked indicated to me it should've been fixed 'long' (in Sid terms) ago ;) >

Bug#900640: garmin-forerunner-tools: Lots of URLs/addresses are incorrect

On zondag 3 juni 2018 08:48:13 CEST you wrote: > Good question > > As for me, I'm in the process of stepping out from Debian, as my > priorities have progressively switched from Debian work to other > activities over the years. > > I tried to prepare this properly, but the shutdown of Alioth

Bug#875061: Package info

Some info on this package and it's state: - The earliest bug report in BTS is from January 2012 ... with not a single response. With the other bugs, there has been 1 response in March 2012 ('try upstream') by the maintainer, none with the others (7 total, including this one) - Latest upload is

Bug#900640: garmin-forerunner-tools: Lots of URLs/addresses are incorrect

Package: garmin-forerunner-tools Version: 0.10repacked-10+b1 Severity: normal As the maintainer address is no longer functional (see #899519), I'm sending it (also) directly to the listed maintainers. Hopefully that's not (too) inappropriate. I recently bought a Garmin Forerunner 645 Music and

Bug#879787: transition: qtbase-opensource-src 5.9.2

On donderdag 26 oktober 2017 00:40:44 CEST Dmitry Shachnev wrote: > Qt 5.9.2 is a bugfix release in 5.9 LTS series, yet it has some minor > private ABI breaks so we have bumped the ABI virtual package names. Just did an 'aptitude safe-upgrade' on my sid machine and noticed the following packages

Bug#886286: torbrowser-launcher: Tor Browser says .onion sites (like http://sejnfjrq6szgca7v.onion/) are not secure

On donderdag 4 januari 2018 07:11:14 CET intrigeri wrote: > The good news is that upstream acknowledges that the current situation > is not ideal and is working on it: > https://trac.torproject.org/projects/tor/ticket/23247 Excellent, thank. > Now, Tor Browser is not in Debian I was indeed

Bug#888439: [Pkg-bluetooth-maintainers] Bug#888439: bluetooth: Bluetooth dont work when laptop turn on

On donderdag 25 januari 2018 16:58:36 CET Gines Priede wrote: > dmesg | grep -i blue > [2.500562] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is > unblocked > [2.823689] Bluetooth: hci0: read Intel version: 370810011003110e00 > [2.824895] bluetooth hci0: firmware:

Bug#884956: Now hidpi scaling is even more broken

On zondag 18 februari 2018 17:06:36 CET wm4 wrote: > Debian doesn't provide an easy way to rollback Like Lisandro already pointed out, there's testing if you use sid. But there is always http://snapshot.debian.org which allows you to go back to any version ever uploaded to Debian (at least since

Bug#884956: Debian testing

On donderdag 22 februari 2018 09:44:21 CET wm4 wrote: > So much for testing being better for stability. If you want stability you should use Debian Stable. If you want to use Testing or Sid, you should expect that things can break *and* be able to cope with that. If you're not yet there, but

Bug#886286: torbrowser-launcher: Tor Browser says .onion sites (like http://sejnfjrq6szgca7v.onion/) are not secure

Package: torbrowser-launcher Version: 0.2.8-6 Severity: normal Tags: upstream If you go to http://sejnfjrq6szgca7v.onion/ (debian.org onion site) with Tor Browser, obtained via torbrowser-launcher program, you don't see the green bar/lock like you see with https sites. If you click on the 'i'

Bug#901919: nvidia-driver: black screen with the latest Linux kernel - general protection fault

Package: nvidia-driver Version: 390.59-1 Followup-For: Bug #901919 Control tag -1 confirmed I can confirm this issue which occured with 4.16.16-1, but not with 4.16.12-1 my relevant part of kern.log Jun 13 16:32:53 bagend kernel: [6.992399] [ cut here ] Jun 13

Bug#904988: /bin/su does not set $PATH

On Fri, 3 Aug 2018 09:16:45 +0200 Andreas Henriksson wrote: > You'll be happy to see that a NEWS entry has already been added for > this, see: > https://salsa.debian.org/debian/util-linux/commit/ b95fbe9d79173058204e226531f4b1f9ad2f26f7 > I was also surprised by this new behavior. I liked

Bug#891773: grub-pc: segfault when running /etc/kernel/postrm.d/zz-update-grub

Package: grub-pc Version: 2.02+dfsg1-2 Severity: normal Latest update brought this new version of GRUB with it, but when it's running /etc/kernel/postrm.d/zz-update-grub, I get several segfaults. This happened on the update of grub-pc, but it also happened when I removed (some) kernel(s) from my

Bug#891773: Related bug #871229 (but it didn't break my system))

On donderdag 1 maart 2018 15:14:40 CET John Paul Adrian Glaubitz wrote: > >> If you have a .deb package, then yes. > > > > I just uploaded a patched version of grub2 to my Debian webspace [1]. > > PS: grub-probe is located in the grub-common package, so it should hopefully > be enough to just

Bug#891773: Related bug #871229 (but it didn't break my system))

On donderdag 1 maart 2018 14:25:25 CET John Paul Adrian Glaubitz wrote: > It might be that this patch fixes it [1]. I can build a grub package > with the patch and provide it for testing purpose. Anyone who is > affected by the bug would be willing to test my packages? If you have a .deb package,

Bug#871229: Bug#891773: Related bug #871229 (but it didn't break my system))

Backtrace: # gdb /usr/sbin/grub-probe core GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO

Bug#891773: Acknowledgement (grub-pc: segfault when running /etc/kernel/postrm.d/zz-update-grub)

Figured out it was 'update-grub' where the segfault occured. Installed grub-common-dbgsym and grub2-common-dbgsym, but that didn't result in more info But in /var/log/kern.log I noticed the following: Mar 1 11:43:09 bagend kernel: [ 1763.332006] device-mapper: uevent: version 1.0.3 Mar 1

Bug#891773: Related bug #871229 (but it didn't break my system)

Checked pkg-grub-devel and found related bug #871229. Normally I'd merge the bugs, but this bug didn't break my system. I have rebooted my PC and the boot process *may* have taken a bit longer, I'm not sure. But the boot was successful. Also I just updated my Sid system, no major things like in

Bug#891773: Related bug #871229 (but it didn't break my system))

On donderdag 1 maart 2018 17:02:28 CET John Paul Adrian Glaubitz wrote: > I have updated the packages with the patch I just came up with: > > https://people.debian.org/~glaubitz/grub-891773/ > > Can you retry? No more segfaults :-) signature.asc Description: This is a digitally signed message

Bug#892360: systemd: No problem on my amd64 systems

Package: systemd Followup-For: Bug #892360 Wanting to let you know that I had no problem on my PC (from which I'm reporting) and also not on my laptop. I did not have to specify any (systemd related) kernel parameters $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.15.0-1-amd64

Bug#883022: Maybe we should rename this one?

On Wed, 06 Dec 2017 19:55:10 -0300 Lisandro Damián Nicanor Pérez Meyer wrote: > I suffer from the same bug. But note that it tries to access > /usr/local/sbin/ and that's why apparmor is complaining. > > Maybe we should retitle this bug? Or should I open a new one? >

Bug#892360: systemd: No problem on my amd64 systems

On donderdag 8 maart 2018 20:49:54 CET Elimar Riesebieter wrote: > Well, I reported the initial reportfor x86 only, though. Correct. apt-listbug did show it for my amd64 system though and later on there were messages indicating that amd64 could also be affected. > > CONFIG_CGROUP_CPUACCT=y > As

Bug#891656: chromium: uBlock Origin and HTTPS Everywhere crash with 65.0.3325.146-1, not before

Package: chromium Version: 65.0.3325.146-1 Followup-For: Bug #891656 My extensions worked fine with 64.0.3282.119-2+b2 but after having just upgraded to 65.0.3325.146-1, both uBlock Origin and HTTPS Everywhere crash. Started chromium with logging and the part till the 2nd 'Core file will not be

Bug#896189: Indeed not fixed in 3.0.1-7

Just got version 3.0.1-7 and it indeed (still) fails in postinst: # aptitude safe-upgrade The following partially installed packages will be configured: libopenmpi-dev openmpi-bin No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not

Bug#896644: Indeed not fixed in 3.0.1-7

Forwarding msg send to #896189 to correct bug address ... On maandag 23 april 2018 02:58:03 CEST Diederik de Haas wrote: > Just got version 3.0.1-7 and it indeed (still) fails in postinst: > > # aptitude safe-upgrade > The following partially installed packages will be configured: &g

Bug#896644: Looks like it is fixed in 3.0.1-8

I think this bug is the same as #696189 and that one got fixed with 3.0.1-8 and it indeed installed correctly on my system. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896189#53 signature.asc Description: This is a digitally signed message part.

Bug#894457: Acknowledgement (python3-distutils: Install error: "trying to overwrite '/usr/lib/python3.6/distutils/__init__.py'")

Control: severity -1 serious Control: merge -1 894458 Control: severity 894456 serious Control: merge 894456 894458 thx signature.asc Description: This is a digitally signed message part.

Bug#894457: python3-distutils: Install error: "trying to overwrite '/usr/lib/python3.6/distutils/__init__.py'"

Package: python3-distutils Version: 3.6.5~rc1-3 Severity: normal The version as stated above is incorrect, the issue is with trying to install version 3.6.5-1. As it looks like various Debian infra aren't yet aware of this new version, I'll leave it up to the maintainer to fix it. Here's part of

Bug#894489: pulseaudio-equalizer: Please upgrade to Qt5 instead of Qt4

Package: pulseaudio-equalizer Version: 11.1-4 Severity: normal I wanted to install pulseaudio-equalizer but bailed out when I saw this: # aptitude install pulseaudio-equalizer The following NEW packages will be installed: libqt4-designer{a} libqt4-help{a} libqt4-scripttools{a} libqt4-test{a}

Bug#891773: Related bug #871229 (but it didn't break my system))

On vrijdag 2 maart 2018 09:49:39 CET John Paul Adrian Glaubitz wrote: > Here's an updated patch sparc64-support.patch which should address the > issue, > it contains these two patches: > > http://lists.gnu.org/archive/html/grub-devel/2018-03/msg00016.html > >

Bug#910811: xenstore-utils: upgrade error: xenstore-utils_4.11.1 unpack error with '/usr/share/man/man1/xenstore-chmod.1.gz'

Package: xenstore-utils Version: 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 Severity: normal while doing 'aptitude safe-upgrade' with today's updates, I got the following error: Unpacking xenstore-utils (4.11.1~pre.20180911.5acdd26fdc+dfsg-2) over (4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9) ... dpkg:

Bug#911457: Add pending tag

Control: tag -1 pending signature.asc Description: This is a digitally signed message part.

Bug#852324: Not a fatal error/warning

On Wed, 26 Jul 2017 19:23:23 +0200 Helio Loureiro wrote: > He clearly states it isn't booting. It is crashing. No, that is an incorrect assessment. I called it an error because I saw a stacktrace which I associate with an error, even though the first line after "[ cut here ]" said warning.

Bug#852324: closed by Ben Hutchings (Re: [xen] x86/mm: Found insecure W+X mapping)

On woensdag 31 oktober 2018 04:27:04 CET you wrote: > Version: 4.17~rc3-1~exp1 > > This was fixed upstream in Linux 4.17-rc1. > > Ben. You are awesome :) I was/am on the verge of upgrading that system from Stretch to Buster, which would upgrade both Xen (to 4.11) and the kernel (some which

Bug#913366: Now properly setting forwarded address

Control: forwarded -1 https://github.com/micahflee/torbrowser-launcher/pull/360 signature.asc Description: This is a digitally signed message part.

Bug#913366: Acknowledgement (torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch)

Control: forwarded -1 https://github.com/micahflee/torbrowser-launcher/pull/ 360 signature.asc Description: This is a digitally signed message part.

Bug#913366: torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch

Package: torbrowser-launcher Version: 0.3.1-1 Severity: grave Tags: upstream patch Justification: renders package unusable I had applied the patch before, but I guess it got overwritten with a new version (which I thought wasn't supposed to happen without asking). Applied the patch again and then

Bug#852324: closed by Ben Hutchings (Re: [xen] x86/mm: Found insecure W+X mapping)

On zaterdag 3 november 2018 03:02:07 CET Ben Hutchings wrote: > > I was/am on the verge of upgrading that system from Stretch to Buster, > > which would upgrade both Xen (to 4.11) and the kernel (some which would > > include the fix). > > Would it be useful to first upgrade just the kernel (and

Bug#909585: RFP: rapidcheck -- RapidCheck is a C++ framework for property based testing inspired by QuickCheck and other similar frameworks.

Package: wnpp Severity: wishlist * Package name: rapidcheck * URL : https://github.com/emil-e/rapidcheck * License : BSD 2-clause Programming Lang: C++ Description : RapidCheck is a C++ framework for property based testing inspired by QuickCheck and other similar

Bug#915689: prevent from migrating to testing

On Fri, 11 Jan 2019 14:51:05 -0500 Michael Stone wrote: > On Fri, Jan 11, 2019 at 01:57:28PM -0500, Michael Stone wrote: > >There never should have been an NMU simply replacing rng-tools with > >rng-tools5. I did not notice that this had happened. > > Also, the correct fix for buster is an

Bug#919888: google-authenticator: New upstream release (1.05 or new git snapshot) and incorrect homepage

Package: google-authenticator Version: 20170702-2 Severity: wishlist The upload of 20170702-1 mentioned a git commit from https://github.com/google/google-authenticator-libpam/ but https://github.com/google/google-authenticator/ is listed as homepage.

Bug#915689: Bug#919893: package shouldn't exist

On zondag 20 januari 2019 16:59:11 CET Thorsten Glaser wrote: > I’m very much against just saying this package > “should not exist” I'm inclined to agree with this as the source (+ features/parameters) for this package is substantially different from rng-tools/rng-tools5. AFAICT the problem

Bug#915689: Bug#919893: package shouldn't exist

On maandag 21 januari 2019 13:34:19 CET Michael Stone wrote: > On Mon, Jan 21, 2019 at 01:15:13PM +0100, Diederik de Haas wrote: > >On zondag 20 januari 2019 16:59:11 CET Thorsten Glaser wrote: > >> I’m very much against just saying this package > >> “should not exist” &

Bug#915689: Fwd: Re: Bug#919893: package shouldn't exist

On maandag 21 januari 2019 17:13:42 CET Michael Stone wrote: > >Entropy generation for the creation of SSH keys as the netinstaller is > >mostly used in headless situations. > >https://github.com/debian-pi/raspbian-ua-netinst/issues/42 > > That functionality doesn't require the old package; will

Bug#902443: Please add DAEMON_OPS to the service file

On Tue, 11 Dec 2018 11:03:06 -0500 Scott Kitterman wrote: > What does this accomplish? As far as I can see, DAEMON_OPTS is never defined > (defaults isn't sourced and AIUI there's no easy way to do that). It is defined in /etc/init.d/quasselcore (with value "", but one can change that)

Bug#902443: [Pkg-kde-extras] Bug#902443: Bug#902443: Please add DAEMON_OPS to the service file

On woensdag 12 december 2018 02:48:25 CET Scott Kitterman wrote: > >It is defined in /etc/init.d/quasselcore (with value "", but one can > >change that) > > Right, but that's for sysv init, not the systemd service file. I don't > believe systemd looks in /etc/init.d at all. > > Did you test

Bug#902443: [Pkg-kde-extras] Bug#902443: Please add DAEMON_OPS to the service file

On woensdag 12 december 2018 04:47:37 CET Scott Kitterman wrote: > > My reaction was in response to "DAEMON_OPTS is never defined" > > OK. I guess I should have been clearer: > > Never defined in the systemd unit file. I agree. Consequently the patch seems incomplete. Now your other remark

Bug#914318: sleepyhead: new upstream release (v1.1)

Package: sleepyhead Version: 1.0.0-beta-2+dfsg-6 Severity: wishlist Although there isn't a tag for it at https://gitlab.com/sleepyhead/sleepyhead-code/ if you look at master's version.h, it shows version 1.1. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT

Bug#914318: sleepyhead: new upstream release (v1.1)

On maandag 26 november 2018 21:19:59 CET Sergio Durigan Junior wrote: > Just an update on this: I'm trying to get in touch with the upstream > maintainer and ask him to properly tag the repository with the release > versions. I prefer to proceed once this is addressed upstream. I totally

Bug#924895: No problems since updating ucodes from upstream git

I updated /lib/firmware/amd-ucode/*.bin from upstream git (commit 7bc246451318b3536d9bfd3c4e46d541a9831b33) and updated initramfs (I'm not sure that's the right place) and since then I haven't had the problem anymore. I realize that we're in freeze mode, but the 18.50 release looks to become

Bug#924895: amd64-microcode: APIC e microcode 8001137

Package: amd64-microcode Version: 3.20181128.1 Severity: normal I'm not sure whether this is the correct package to report it against, but a web search indicated it could be something with microcode. I recently updated my BIOS on my Asus ROG CROSSHAIR VII HERO MB and the changelog contained the

Bug#922145: irssi: trying to overwrite '/usr/share/irssi/help/otr', which is also in package irssi-plugin-otr

Package: irssi Version: 1.1.2-1 Severity: important Got an update for version 1.2.0-1, but I also have irssi-plugin-otr installed, which resulted in the following upgrade error: # aptitude safe-upgrade The following packages will be upgraded: bind9-host dnsutils irssi irssi-plugin-otr ...

Bug#922145: closed by Rhonda D'Vine (Bug#922145: fixed in irssi 1.2.0-2)

On woensdag 13 februari 2019 15:51:04 CET you wrote: > #922145: irssi: trying to overwrite '/usr/share/irssi/help/otr', which is > also in package irssi-plugin-otr > > It has been closed by Rhonda D'Vine . I think it's not actually fixed as I just got the error again. Now with version 1.2.0-2,

Bug#922145: closed by Rhonda D'Vine (Bug#922145: fixed in irssi 1.2.0-2)

nvm, doing another 'aptitude safe-upgrade' right after made the problem go away again. signature.asc Description: This is a digitally signed message part.

Bug#924895: Updating metadata

Control: retitle -1 Freezes and spontaneous reboot on first/early editions of AMD Ryzen CPUs (was: APIC e microcode 8001137) Control: tags -1 patch Control: notfound -1 3.20181128.1 signature.asc Description: This is a digitally signed message part.

Bug#929820: nmu: cdebootstrap_0.7.7+b11

Thanks for the addional info and for scheduling it. On zondag 2 juni 2019 11:07:50 CEST Paul Gevers wrote: > On 31-05-2019 22:38, Diederik de Haas wrote: > > nmu cdebootstrap_0.7.7+b11 . ANY . buster . -m "Rebuild for change in > > libdebi

Bug#554444: Same issue as already reported, and partially fixed

Control: severity -1 serious Hi, This is the same issue as https://bugs.debian.org/904699, which is actually an issue in libdebian-installer (https://bugs.debian.org/55). The fix has actually been made. But the problem is that it needs an unblock ack from the d-i team

Bug#929172: Same issue as already reported, and partially fixed

On vrijdag 31 mei 2019 21:52:38 CEST Paul Gevers wrote: > On 31-05-2019 21:16, Diederik de Haas wrote: > > Control: severity -1 serious > > Please don't use this if you CC multiple bugs that aren't all of the > same severity. Sorry about that, didn't realize that it would aff

Bug#929820: nmu: cdebootstrap_0.7.7+b11

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu cdebootstrap_0.7.7+b11 . ANY . buster . -m "Rebuild for change in libdebian-installer (v0.119)" I don't know if this is the correct way, but cdebootstrap-static needs a rebuild to pick

Bug#928631: Question

On vrijdag 21 juni 2019 16:53:11 CEST Dean Loros wrote: > Can I confirm that this is a problem with AMD graphics only--or will this > affect all systems regardless of Video card type? Yes. (bug is filed against firmware-amd-graphics) Michael Becker: what CPU do you have? Antonio De Luci: Are

Bug#928631: Question

Just got a msg from Michael send to me personally, I assume by accident. Summary of the affected systems: AMD Ryzen 1700X + VEGA64 + Sid AMD Ryzen 2700X + VEGA64 + Sid AMD Ryzen 2700X + VEGA56 + Sid It's up to the maintainers, but as I said, I would be fine if severity of the bug is lowered or

Bug#554444: Rebuild for cdebootstrap-static?

Thanks for upping the limit in libdebian-installer :) But doesn't it require a rebuild for cdebootstrap-static to pick up this change? If so, could you do or request it? TIA, Diederik signature.asc Description: This is a digitally signed message part.

Bug#924895: Updating microcode files didn't help, maybe a kernel problem after all

On dinsdag 26 maart 2019 16:11:47 CEST Diederik de Haas wrote: > I updated /lib/firmware/amd-ucode/*.bin from upstream git (commit > 7bc246451318b3536d9bfd3c4e46d541a9831b33) and updated initramfs (I'm not > sure that's the right place) and since then I haven't had the problem

Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub

On zaterdag 18 mei 2019 14:08:17 CEST Michael Becker wrote: > But I did not notice any spontaneous reboots so far. The spontaneous reboots seems to be an entirely different issue, see https:// bugs.debian.org/cgi-bin/bugreport.cgi?bug=924895#15 for details. signature.asc Description: This is a

Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub

On dinsdag 21 mei 2019 19:24:07 CEST Romain Perier wrote: > Hi, Hi, > firmware-amd-graphics 20190502-1 is based onto upstream commit > 92e17d0dd2437140fab044ae62baf69b35d7d1fa, that is commit "amdgpu: update > vega20 to the latest 19.10 firmware" . Two commits behind there is commit > "amdgpu:

Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub

On dinsdag 21 mei 2019 21:20:18 CEST Diederik de Haas wrote: > Checking 'git log' for that specific file before I did the test made me > conclude it wouldn't make a difference with packaged version 20190114-1 > (but did the test anyway as requested). To verify whether that single fi

Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub

On dinsdag 21 mei 2019 21:20:18 CEST Diederik de Haas wrote: > What was the reason for the test? FTR: before I did the test I had already downgraded firmware-amd-graphics and consequently also firmware-linux-nonfree and firmware-misc-nonfree back to version 20190114-1 signature.asc Descript

Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub

Package: firmware-amd-graphics Version: 20190502-1 Severity: critical Justification: breaks the whole system Today's Sid update brought in new kernel and various firmware updates, after which I rebooted the system. Saw Grub loading, but after it started kernel 4.19.0-5-amd64, it stopped loading

Bug#554444: Ping?

I just tried to install a Buster system with cdebootstrap(-static) and that fails because this bug is not fixed. According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904699#15, increasing READSIZE from 16384 to 65536 'fixes' it. I agree that 65536 is also just a random number, but so

Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found

Package: grub-efi-amd64 Followup-For: Bug #931896 I don't have grub-efi-amd64 installed, but I ran into the same problem. The only enabled lines in /etc/default/grub are these: GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`

Bug#928631:

Hi, On zondag 14 juli 2019 21:38:14 CEST Hillel Lubman wrote: > 20190502-1 is already outdated, since amdgpu firmware had some updates > upstream: > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > /log/amdgpu > > Does this problem still occur if you use latest

Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found

Thanks for your reply, it was very helpful :) On zaterdag 13 juli 2019 09:05:44 CEST Sven Joachim wrote: > Most likely you had grub configured to install to the wrong disk, this > is what happened to me. When I installed an SSD into my old PC back in > December 2016, I copied all files from the

Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found

On maandag 15 juli 2019 00:33:31 CEST Colin Watson wrote: > > In the not too distant future, I'll remove that old drive (with WinXP on > > it) from my system and my guess is that I then will have a problem. > > That shouldn't be the case: we store the installation device using a >

Bug#931896: grub-efi-amd64: symbol `grub_file_filters` not found

On maandag 15 juli 2019 11:22:55 CEST Colin Watson wrote: > output of "sudo debconf-show grub-pc | grep install_devices:". Ohhh, that is an interesting command :) > You certainly do need to run "dpkg-reconfigure grub-pc" to match what > your BIOS is configured to boot from. However, once you

Bug#932750: Package is now orphaned

Just noticed that the package is now officially orphaned https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939421 signature.asc Description: This is a digitally signed message part.

Bug#864945: Isn't this bug fixed with version 1.20171006 ?

I just checked salsa and it appears the first version after the patch for this bug was 1.20171006, so shouldn't this bug be closed by that version? signature.asc Description: This is a digitally signed message part.

Bug#931739: [Pkg-kde-extras] Bug#931739: quassel-core: key too small error after upgrade to buster

On donderdag 18 juli 2019 20:11:46 CEST RedOmen wrote: > I tried to use the instructions here: > https://bugs.quassel-irc.org/projects/quassel-irc/wiki/Client-Core_SSL_suppo > rt but could not get it to work. > > I ended up having to remove all the /var/lib/quassel/ files and running >

Bug#941363: [filezilla] Filezilla doesn't start, returns an undefined symbol error

Package: filezilla Version: 3.39.0-2 Followup-For: Bug #941363 Confirming that I have the exact same issue. I don't remember exactly when, but this issue started somewhere between 1 and 2 weeks ago, iow not today. My sources.list only contains http://httpredir.debian.org/debian/, thus it is a

Bug#943979: postgresql-12-pg-checksums: Shouldn't it upgrade to this version when upgrading to postgresql.*-12?

Package: postgresql-12-pg-checksums Version: 1.0-2 Severity: minor I just upgraded my postgresql packages from version 11 to 12, but this package wasn't upgraded with it, I had to manually install it. Not a problem in itself, but it makes sense to me if it was upgraded alongside the other

Bug#943979: postgresql-12-pg-checksums: Shouldn't it upgrade to this version when upgrading to postgresql.*-12?

Hi, On zaterdag 2 november 2019 15:55:26 CET Christoph Berg wrote: > it makes sense to allow both packages to be installed in parallel. Quite true. You need both in order to upgrade your cluster. > Apt doesn't know that installing postgresql-12 next to postgresql-11 should > imply installing

<    1   2   3   4   5   6   7   8   9   10   >