Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)

On 27-11-2023 02:11, Aaron Rainbolt wrote: Alright, I have fully rebuilt the copyright file. I also ended up adding the source code for several releases of C-BIOS into the packaging. As this code is in the form of zipped files for the sake of size, it's not exactly practical to provide the new

Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)

code, see e.g. the cbios package in Debian, which contains all info to the upstream sources. (As they're packaged separately, they are not part of the openMSX (source) packages in Debian.) -- Kind regards, Manuel Bilderbeek

Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)

Hi, The license of openMSX has always been GPL 2 only. Is there a problem somewhere? Op zo 26 nov. 2023 09:57 schreef Dr. Bas Wijnen : > Hi, > > First of all, thank you for the report and patch. I'll look in more detail > shortly. > > However, after quickly looking over it, I have one question:

Bug#1035075: Did a test with manual power save

/Mutter/DisplayConfig org.gnome.Mutter.DisplayConfig PowerSaveMode i 0 That does turn off the screen for 12 seconds, but then it's going back on. And 18 seconds later the command finishes... Looks like the same 12 seconds I saw when locking. -- Kind regards, Manuel Bilderbeek

Bug#1035075: gnome-shell: After lock, screen is black, but not blanked (no powersave)

or if there is a workaround, please let me know. Kind regards, Manuel Bilderbeek -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: L

Bug#1034193: minidlna: Patch provided

Package: minidlna Version: 1.3.0+dfsg-2.2+b3 Followup-For: Bug #1034193 Dear Maintainer, Thanks for forwarding this to upstream. In the meantime, I prepared a patch and submitted it there, but of course feel free to use it in the Debian package already. See:

Bug#1034193: minidlna: Dutch localization error: contains Swedish

Package: minidlna Version: 1.3.0+dfsg-2.2+b3 Severity: normal Dear Maintainer, Since I am using Dutch (NL) localization on my PC, I noticed that I suddenly see a Swedish text on my TV when browsing my PC's DLNA directories. In particular, I see the text "Nyligen tillagd" appearing in

Bug#1030549: filelight: Missing dependency on qml-module-org-kde-quickcharts and more

Package: filelight Version: 4:22.12.1-1 Severity: important Dear Maintainer, * What led up to the situation? I haven't used the program in a long while (and kept upgrading my testing system daily). Then I tried it today and I got a blank window with this on the terminal: $ filelight

Bug#1020549: usrmerge: needs a stricter conflict with libpng12-0

Package: usrmerge Version: 31 Followup-For: Bug #1020549 Dear Maintainer, FYI, I ran into exactly the same issue. $ dpkg -l libpng12-0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required

Bug#752767: tracker-miner-fs: It can be turned off...

Package: tracker-miner-fs Followup-For: Bug #752767 Hi all, As an addition to my previous e-mail, here are some hints on how to disable this service: https://askubuntu.com/a/353450 (Thanks to dwfreed on IRC for pointing me to this.) HTH... -- System Information: Debian Release: bookworm/sid

Bug#752767: tracker-extract: Program tracker-extract eat more cpu on start kde session

gnome). Kind regards, Manuel Bilderbeek -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint

Bug#1011014: libsdl2-dev: double-promotion warning when including SDL_rect.h indirectly

Package: libsdl2-dev Version: 2.0.22+dfsg-3 Severity: normal Dear Maintainer, * What led up to the situation? Update in testing to this version. Our application openMSX compiles against SDL2 (see the Debian package). As of the recent update of SDL2 in testing it generates many warnings

Bug#1010148: openmsx: patch for ftbfs on riscv64

attach patch if `repotbug --mutt`? send patch again. -- Kind regards, Manuel Bilderbeek

Bug#783892: thunderbird: Fixed

Package: thunderbird Followup-For: Bug #783892 Dear Maintainer, 1:78.11.0-2 fixed this issue for me. Just to let you know. -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing'), (1, 'experimental') Architecture:

Bug#783892: iceowl-extension: Reminder popup “Dismiss” buttons do nothing

; 1:78.11.0-1 Is there a workaround? Thanks. Kind regards, Manuel Bilderbeek -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Ker

Bug#895378: sky2: sky2: did not recover correctly after waking up from S3

Yes, it is. Just had it yesterday with an updated testing. Op zo 23 mei 2021 14:58 schreef Salvatore Bonaccorso : > Control: tags -1 + moreinfo > > Hi, > > On Sun, Oct 14, 2018 at 11:21:32AM +0200, Laurent Bigonville wrote: > > Source: linux > > Version: 4.18.10-2 > > Followup-For: Bug #895378 >

Bug#975393: hexchat: Workaround

Package: hexchat Version: 2.14.3-3+b2 Followup-For: Bug #975393 Same problem here. A workaround is to remove hexchat-python3, but that also removes Python script support, of course. Kind regards, Manuel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy:

Bug#973495: mingw-w64-common: Conflicting definition of std::max_align_t with stddef.h of gcc-mingw-w64-i686-posix

Package: mingw-w64-common Version: 8.0.0-1 Severity: important Dear Maintainer, When cross compiling for 32-bit Windows, I noticed that some translation units had a different value for std::max_align_t than others. It appears that (for some reason), one included it from:

Bug#956633: libpango-1.0-0: Still happens in 1.46.1-1

regards, Manuel Bilderbeek -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags

Bug#955999: openmsx: Issues with pressing multiple keys

Hi, On 06-04-2020 13:54, Jesús Barrado Varela wrote: > Can you confirm the problem doesn't occur by compiling a previous > version and trying that? I've tried the following today:  * On Debian 10 Buster the bug is present on version 0.15.0-2.  * On Debian 10 Buster the bug is present on

Bug#955999: openmsx: Issues with pressing multiple keys

Hi, I can't reproduce the problem. Just walking the right in MoG and jumping, I keep walking to the right. Are you sure you didn't change something with keyboard hardware or some other keyboard settings? Can you confirm the problem doesn't occur by compiling a previous version and trying

Bug#939768: gimp: It's the gegl mismatch...

Package: gimp Version: 2.10.8-2+b1 Followup-For: Bug #939768 Dear Maintainer, Some discussion on the GIMP IRC channel: what's your gegl version? (you can see with $ gimp -v) using GEGL version 0.4.12 (compiled against version 0.4.14) is that mismatch relevant? in this case, probably not

Bug#928806: evince: Printing when viewing dvi file doesn't work: Permission denied

Package: evince Version: 3.30.2-3 Severity: normal Dear Maintainer, * What led up to the situation? I viewed a DVI file on with evince and clicked on the Print icon in the menu. Selected printer and pressed OK. Nothing happend. Message in terminal: Failed to execute child process “dvipdfm”

Bug#923079: tcl8.6-dev: tcl.pc pkgconfig file not packaged

Package: tcl8.6-dev Version: 8.6.9+dfsg-1 Severity: important Dear Maintainer, It looks like nowadays pkg-config is the (de-facto) standard for finding packages. Unlike most other dev packages and unlike other distros, the Debian dev package of Tcl does not include the tcl.pc file. Please add

Bug#920053: grub-pc: Got a sudden prompt about needing to reinstall, but that fails

Package: grub-pc Version: 2.02+dfsg1-10 Severity: normal Dear Maintainer, * What led up to the situation? This upgrade: [UPGRADE] grub-pc:amd64 2.02+dfsg1-9 -> 2.02+dfsg1-10 [UPGRADE] grub-pc-bin:amd64 2.02+dfsg1-9 -> 2.02+dfsg1-10 during the upgrade I got a prompt that grub was not

Bug#920051: rhythmbox: Complains about missing files, but can just play them

Package: rhythmbox Version: 3.4.3-2 Severity: normal Dear Maintainer, * What led up to the situation? Not sure. Started up Rhythmbox to play some music (it was a couple of days ago when I had done that last time) and suddenly I see it listing about 80% of my files as missing. However, all

Bug#917846: /usr/bin/querybts: querybts doesn't find bug that exists

on3-debian 0.1.33 ii python3-debianbts 2.7.2 ii python3-requests 2.20.0-2 python3-reportbug suggests no packages. -- Configuration Files: /etc/reportbug.conf changed: submit query-bts cc config-files compress email "manuel.bilderb...@gmail.com" realname "Manuel Bilderbeek

Bug#914648: tracker: Confirmed

Package: tracker Followup-For: Bug #914648 Dear Maintainer, I can confirm this issue on my system. It causes 100% CPU usage (on one core)... -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64)

Bug#909535: gnome-shell-extensions: Native Window Placement screws up top-left gesture animation

Package: gnome-shell-extensions Version: 3.30.0-1 Severity: normal Dear Maintainer, * What led up to the situation? I upgraded to GNOME 3.30: [UPGRADE] gnome-flashback:amd64 3.28.0-1 -> 3.30.0-1 [UPGRADE] gnome-flashback-common:amd64 3.28.0-1 -> 3.30.0-1 [UPGRADE] gnome-music:amd64

Bug#881442: Re: shotwell: Crashes when deleting all photos from an event

Hi, Sorry, I completely forgot about this. I just tested it with the current shotwell, and I couldn't quickly reproduce the crash. So I guess it was indeed fixed. Kind regards, Manuel On 02-05-18 08:13, Jörg Frings-Fürst wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, no

Bug#895378: sky2: sky2: did not recover correctly after waking up from S3

Package: src:linux Version: 4.15.11-1 Severity: normal File: sky2 Dear Maintainer, * What led up to the situation? I started up my PC and didn't do anything. The system went into S3. After I woke it up, all worked, except networking. * What exactly did you do (or not do) that was

Bug#892613: sddm: Power Saving -> Blank screen not working when using sddm

Package: sddm Version: 0.17.0-1 Severity: normal Dear Maintainer, I switched from gdm3 to sddm for a while, as gdm3 gave me problems. Everything worked as I expected, except that my monitor wasn't disabled after 5 minutes as what I was used to. My GNOME settings ("Power Saving" -> Blank screen)

Bug#890614: gnome-shell: Greeter doesn't start anymore: attempts every 20 seconds

Package: gnome-shell Followup-For: Bug #890614 I just tried gdm3 again today and now everything works as normal. So I have no idea what fixed it, but the problem doesn't occur here anymore. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'),

Bug#890614: Acknowledgement (gnome-shell: Greeter doesn't start anymore: attempts every 20 seconds)

Hi, Just FYI: I installed xdm and made it the default. This works normally. After logging in I just get gnome-shell as usual. So the problem is explicitly related to the greeter or perhaps gdm3. -- Kind regards, Manuel Bilderbeek

Bug#890614: gnome-shell: Greeter doesn't start anymore: attempts every 20 seconds

Package: gnome-shell Version: 3.26.2-4 Severity: important Dear Maintainer, Since today's dist-upgrade, the greeter isn't working anymore. I see a black screen. Logging shows it attempts to restart every 20 seconds: Feb 16 20:34:51 sonata gnome-session[1544]: gnome-session-binary[1544]:

Bug#888610: gnome-shell: gdm greeter session sometimes exits 1: Can't initialize KMS backend: could not find drm kms device

Hi, On 27-01-18 19:29, Simon McVittie wrote: On Sat, 27 Jan 2018 at 16:02:19 +0100, Manuel Bilderbeek wrote: I do still see the issue at startup (I guess when the greeter is started): ¯ jan 27 10:13:47 sonata gnome-shell[1297]: Can't initialize KMS backend: could not find drm kms device jan

Bug#888052: libgjs0g: Better!

Package: libgjs0g Followup-For: Bug #888052 Dear Maintainer, I installed the latest version of the package, and so far so good! No restarts so far. I do still see the issue at startup (I guess when the greeter is started): jan 27 10:13:47 sonata gnome-shell[1297]: Can't initialize KMS backend:

Bug#888052: gnome-shell: Restarts every 10 minutes related to dbus-org.freedesktop.hostname1.service

Hi, Reporting back as promised. On 24-01-18 00:40, Manuel Bilderbeek wrote: So far, it does! No occurrences ever since I downgraded... I'll evaluate a bit more and let you know. Thanks a lot for your response! Ran the complete day today, without restarts. But it appears to have happened

Bug#888052: gnome-shell: Restarts every 10 minutes related to dbus-org.freedesktop.hostname1.service

Hi, On 23-01-18 20:49, Jason Crain wrote: On Tue, Jan 23, 2018 at 01:24:10PM -0600, Jason Crain wrote: Does downgrading gjs to version 1.50.2-2 fix it? Sorry, I meant try downgrading libgjs0g to version 1.50.2-2. So far, it does! No occurrences ever since I downgraded... I'll evaluate a

Bug#888052: gnome-shell: Restarts every 10 minutes related to dbus-org.freedesktop.hostname1.service

Package: gnome-shell Version: 3.26.2-3 Severity: normal Dear Maintainer, On my system, in an interval of exactly 10 minutes, gnome-shell restarts, always in conjunction with dbus-org.freedesktop.hostname1.service. For example: Jan 22 23:55:12 sonata dbus-daemon[513]: [system] Activating via

Bug#887888: dleyna-server: general protection error

Package: dleyna-server Version: 0.4.0-1.1 Severity: normal Dear Maintainer, I'm experiencing weird behaviour on my system, like gnome-shell terminating every 10 minutes and sometimes I get an automatic logout. At that point in the logging, I noticed: Jan 21 14:02:53 sonata systemd[1554]:

Bug#881442: shotwell: Crashes when deleting all photos from an event

Package: shotwell Version: 0.25.4+really0.24.5-0.1+b1 Severity: normal Dear Maintainer, I found some events with duplicate photos, so I deleted all photos in that event. That caused the Shotwell window to disappear. I guess it crashed. When I tried again running from gdb, I didn't get the crash

Bug#880712: More info...

Hi, OK, I recovered from the situation, thanks to assistance of BenNZ on #debian-next. I'm normally using aptitude with apt-listbugs to maintain my system. A couple of months ago, apt-listbugs pinned binutils (as found in /etc/apt/preferences.d/apt-listbugs): Explanation: Pinned by

Bug#880712: packagekit: Offers to update system, but breaks it

Package: packagekit Version: 1.1.7-1 Severity: important Dear Maintainer, * What led up to the situation? Before logging out of GNOME yesterday evening to shut down, I got a question whether to install pending package updates. I choose YES. After logging out, the system rebooted and quickly

Bug#839884: [Pkg-utopia-maintainers] Bug#839884: network-manager: Confirmed here

NetworkManager-dispatcher.service root 8423 8419 0 23:19 pts/100:00:00 /bin/systemd-tty-ask-password-agent --watch HTH! On 06-10-16 23:37, Michael Biebl wrote: Am 06.10.2016 um 21:42 schrieb Manuel Bilderbeek: Package: network-manager Version: 1.4.2-1 Followup-For: Bug #839884 Dear

Bug#839884: [Pkg-utopia-maintainers] Bug#839884: network-manager: Confirmed here

Hi, On 06-10-16 23:37, Michael Biebl wrote: I also see the hangup: Setting up libkf5widgetsaddons-data (5.26.0-1) ... Setting up network-manager (1.4.2-1) ... and then nothing. ps -Af says: root 4897 2663 0 21:35 pts/200:00:00 /usr/bin/dpkg --status-fd 80 --configure --pending

Bug#839884: network-manager: Confirmed here

Package: network-manager Version: 1.4.2-1 Followup-For: Bug #839884 Dear Maintainer, I also see the hangup: Setting up libkf5widgetsaddons-data (5.26.0-1) ... Setting up network-manager (1.4.2-1) ... and then nothing. ps -Af says: root 4897 2663 0 21:35 pts/200:00:00 /usr/bin/dpkg

Bug#580196: icedove: Attachments don't work on gmail accounts

gonne close this report after over three years without new action. On Sun, Dec 09, 2012 at 09:01:28PM +0100, Manuel Bilderbeek wrote: Hi, On 09-12-12 17:42, Carsten Schoenert wrote: this works with 3.1.16 and 10.0.x. I think this bug is gone or you have still problems with this? No, only

Bug#827705: initscripts: Is this what you mean?

Package: initscripts Version: 2.88dsf-59.4 Followup-For: Bug #827705 Hi, Do you mean this situation I'm in now? $ apt-cache policy initscripts initscripts: Installed: 2.88dsf-59.4 Candidate: 2.88dsf-59.6 Version table: 2.88dsf-59.6 500 500 http://ftp.nl.debian.org/debian

Bug#825853: gnome-session: Fixed?

Package: gnome-session Followup-For: Bug #825853 Dear Maintainer, Looks like this isn't happening anymore as of 2 days ago, so apparently something got fixed in my daily dist-upgrade. I guess it can be closed now. -- System Information: Debian Release: stretch/sid APT prefers stable-updates

Bug#825853: gnome-session: Crash after 5 minutes after logging in

Package: gnome-session Version: 3.20.1-2 Severity: important Dear Maintainer, I logged in after booting my "testing" machine and did nothing (had other stuff to do). When I came back, I noticed it was back on the login screen. I saw this in the journalctl output: mei 30 20:42:18 sonata

Bug#803779: gdm3: Fixed, it seems

Package: gdm3 Followup-For: Bug #803779 Dear Maintainer, As of yesterday, this issue seems to be not happening anymore, so it seems to be fixed It must have happened due to this upgrade: [REMOVE, NOT USED] gir1.2-gdm3:amd64 3.18.0-2 [REMOVE, NOT USED] grilo-plugins-0.2:amd64 0.2.17-1

Bug#825305: gconf2: gsettings-data-convert crashes several times when logging in with GNOME3

Hi, On 27-05-16 20:29, Herbert Fortes (hpfn) wrote: I do not find this error here. Could someone send me a little more information ? gconf2 - 3.2.6-3 gthumb - 3.2.6-3 gconf2 3.2.6-3 gthumb 3:3.4.3-1 As per the state of

Bug#823380: Blank screen after successful login

Package: gdm3 Version: 3.18.0-2 Followup-For: Bug #823380 What the original reporter writes here is very similar to what I reported in #803779, but very different from what the original bug is merged with (#811551) Are you sure it should be merged with #811551? Is there some workaround for this

Bug#825305: gconf2: gsettings-data-convert crashes several times when logging in with GNOME3

Package: gconf2 Version: 3.2.6-3 Severity: normal Dear Maintainer, I was looking at my journalctl output and found these lines: mei 25 21:54:59 sonata gnome-session[1326]: (gsettings-data-convert:1388): GLib-GIO-ERROR **: Settings schema 'org.gnome.gthumb.browser' does not contain a key named

Bug#824707: systemd: I get fsck's every other boot: due to systemd-timesyncd not updating hwclock?

Hi, On 23-05-16 20:04, Manuel Bilderbeek wrote: 3. My BIOS told me at boot today that no RTC clock time was set. I guess my RTC battery is dead. Will replace it. Replaced it last night. Then booted again and set the hwclock. Then booted Debian, no fsck, as I still have the e2fsck.conf

Bug#824707: systemd: I get fsck's every other boot: due to systemd-timesyncd not updating hwclock?

Hi, After a few days, reporting here what's going on now... 1. I haven't seen an fsck of my HDD's ever since I added that e2fsck.conf file 2. When booting, I do get a message that superblock timestamps of my SSD (/dev/sdf1) are too far in the future and I get a very quick fsck of the SDD. It

Bug#600336: Fwd: Bug#600336: rhythmbox: Claims audio device all for itself

Hi, On 20-05-16 15:16, Scott Leggett wrote: I forgot to CC you into the original email and am not sure if you are subscribed to the bug report. I am not, so thanks for sending this mail. Please see below. - Forwarded message from Scott Leggett - Date: Fri, 20 May

Bug#824707: systemd: I get fsck's every other boot: due to systemd-timesyncd not updating hwclock?

Hi, On 19-05-16 23:04, Michael Biebl wrote: Looks like I need to have systemd-timesync run *before* systemd-fsck!? If your hwclock drifts that much, maybe /etc/e2fsck.conf: [options] broken_system_clock=1 (as referenced in my earlier reply) is an option. Can you try that?

Bug#824707: systemd: I get fsck's every other boot: due to systemd-timesyncd not updating hwclock?

Hi, Thanks for taking interest in this annoying problem. Today I again got an fsck at boot... On 18-05-16 23:35, Michael Biebl wrote: fsck.ext[234] should no longer run an fsck because of that. Which version of e2fsprogs have you installed? Should be latest in testing: ii e2fsprogs

Bug#803779: gnome-shell: Screen remains on background for minutes after logging in

Package: gdm3 Followup-For: Bug #803779 Dear Maintainer, Is there any news on this? I keep suffering from this bug... and I have no idea for a workaround. It's really annoying. Any suggestions on what I can try or info I could provide? -- System Information: Debian Release: stretch/sid APT

Bug#817832: apt-listbugs: Aborts complete upgrade instead of skipping package with bug

Hi, On 11-03-16 19:33, Francesco Poli wrote: But: how does pinning help? I don't want it to become permanently pinned. Each pin is automatically removed by a daily cron job, as soon as the bug is fixed in the package version available for installation/upgrade. Hmm, I used to pin something,

Bug#817832: apt-listbugs: Aborts complete upgrade instead of skipping package with bug

nom...@paranoici.org>: > On Thu, 10 Mar 2016 19:22:36 +0100 Manuel Bilderbeek wrote: > > > Package: apt-listbugs > > Version: 0.1.17 > > Severity: normal > > > > Dear Maintainer, > > Hello Manuel, > thanks for using apt-listbugs! > > &g

Bug#817832: apt-listbugs: Aborts complete upgrade instead of skipping package with bug

Package: apt-listbugs Version: 0.1.17 Severity: normal Dear Maintainer, I thought the purpose of this package was to warn you that there is a critical bug in a package you're upgrading, so you can skip upgrading that package. But when you say "No" to the question "Do you want to continue" (or

Bug#813541: nvidia-graphics-drivers: Huge problems 'upgrading' to legacy version

Source: nvidia-graphics-drivers Severity: important Dear Maintainer, I did my daily testing dist-upgrade just now, and I noticed I got a version of the nvidia driver that is not going to work with my old GeForce 9600. I got a nice pop up that the driver is not going to work, so I chose 'No', to

Bug#810938: exim4-daemon-light: Cannot assign requested address: daemon abandoned at each startup

Hi all, OK, so I did an experiment: on the 17th, I reinstalled 'ifupdown' and removed 'ifupdown2' [1]. Since then, I have no more issues... so it was definitely related to that! [1] full log: === Aptitude 0.7.5: log

Bug#810938: exim4-daemon-light: Cannot assign requested address: daemon abandoned at each startup

On 16-01-16 14:36, Marc Haber wrote: /etc/networks has: loopback127.0.0.0 Not sure how to check this in detail, I never had to do this in 15 years of using Debian. You have never used ifconfig or ip addr show to see which IP addresse you have configured? Ah, is that what you're

Bug#810938: exim4-daemon-light: Cannot assign requested address: daemon abandoned at each startup

On 14-01-16 23:55, Marc Haber wrote: On Thu, Jan 14, 2016 at 11:13:34PM +0100, Manuel Bilderbeek wrote: I have no idea what to investigate and how. Check whether you have ::1 and/or 127.0.0.1 on lo. /etc/networks has: loopback127.0.0.0 Not sure how to check this in detail, I never

Bug#810938: exim4-daemon-light: Cannot assign requested address: daemon abandoned at each startup

Hi, On 14-01-16 23:01, Marc Haber wrote: Please keep the bug report always on Cc. My apologies. See /usr/share/doc/exim4-base/README.Debian.gz, chapter 2.5.1 It links to http://www.exim.org/bugzilla/show_bug.cgi?id=92 but that doesn't lead to a bug. At least that is a bug in the

Bug#810938: exim4-daemon-light: Cannot assign requested address: daemon abandoned at each startup

Package: exim4-daemon-light Version: 4.86-7+b1 Severity: important Dear Maintainer, * What led up to the situation? Package upgrades in testing: === Aptitude 0.7.5: log report ma, jan 11 2016 19:12:03 +0100

Bug#788050: systemd-fsck : Check disks at each reboot

Hi, On 29-11-15 01:28, Michael Biebl wrote: Can you boot with systemd.debug-shell on the kernel command line, and then switch to tty9 while the fsck is running and attach strace to the fsckd and fsck process? I want to try this, but for some reason, grub always boots, even if I keep SHIFT

Bug#788050: systemd-fsck : Check disks at each reboot

Hi, On 29-11-15 01:28, Michael Biebl wrote: Does the problem go away if you use "systemctl mask systemd-fsckd.service systemd-fsckd.socket" Yes, it does. Using this I got to see the following while booting, which wasn't visible before: A start job is running... for sda1 (1min23 / no limit)

Bug#788050: systemd-fsck : Check disks at each reboot

On 29-11-15 01:28, Michael Biebl wrote: Am 29.11.2015 um 00:12 schrieb Manuel Bilderbeek: How can I help? Describe your setup in as much detail as possible. LVM, RAID, fstab etc. No RAID, no LVM. I've got a HDD and an SSD. I'm now booting from the SSD. $ cat /etc/fstab # /etc/fstab: static

Bug#788050: systemd-fsck : Check disks at each reboot

Hi again, On 15-11-15 10:06, Michael Biebl wrote: I saw some workaround and suggestions, but is there already a direction of a solution of this issue? I'm afraid not. Not being able to reproduce this issue (on my side) makes this harder. Can you reproduce the issue reliably? As I wrote

Bug#802335: gdm3: gdm 3.18 does not switch to the right tty with a multi seat setup

Package: gdm3 Version: 3.18.0-2 Followup-For: Bug #802335 Dear Maintainer, Looks like I'm also hit with this bug... but I have no idea what a 'seat' is or what 'multiseat' is. I didn't do anything to set that up, I only upgraded some packages and suddenly I get this issue. I described it in bug

Bug#803779: gnome-shell: Screen remains on background for minutes after logging in

Package: gdm3 Version: 3.18.0-2 Followup-For: Bug #803779 Dear Maintainer, Some extra information. During the blank screen, I tried to go to the text console with CTRL-ALT-F1. This resulted in the graphical desktop. Apparently it's under CTRL-ALT-F2, because doing that still gives me the desktop

Bug#788050: systemd-fsck : Check disks at each reboot

Hi, On 15-11-15 10:06, Michael Biebl wrote: I'm afraid not. Not being able to reproduce this issue (on my side) makes this harder. Can you reproduce the issue reliably? So far it happened all 3 boots since the boot count became high enough to do an fsck. So I guess the answer is yes. Each

Bug#804910: systemd: Invisible fsck, looked like a hanging system

Hi, On 14-11-15 14:09, Michael Biebl wrote: And alternative could be, to attach the output of systemd-analyze and "systemd-analyze blame" when such a long fsck happens. I thought I had already done that, but here it is again in full. $ systemd-analyze Startup finished in 3.802s (kernel) +

Bug#804910: systemd: Invisible fsck, looked like a hanging system

Hi, On 14-11-15 13:49, Michael Biebl wrote: Please keep in mind, that fsck for / and /usr is run in the initramfs nowadays and systemd is not yet involved. Can you boot and removing "quiet" from the kernel command line. This should give you more log messages from systemd. OK, I'll try that.

Bug#803779: gnome-shell: Screen remains on background for minutes after logging in

Package: gnome-shell Version: 3.18.1-1 Followup-For: Bug #803779 Dear Maintainer, I did some more experiments and during the background situation, I noticed: - Pressing Esc directly gives me the normal gnome-shell, but other keys do not - Pressing Space or Enter gives me a menu with the items

Bug#803779: gnome-shell: Screen remains on background for minutes after logging in

Package: gnome-shell Version: 3.18.1-1 Severity: important Dear Maintainer, Since about a week (I dist-upgrade testing daily), I see a strange effect after logging in from gdm3: (note: it may mean that gdm3 is the package I should be filing the bug for, but I don't know how to determine that, so

Bug#801191: nvidia-driver: gdm3 can't start anymore (acceleration check failed)

Hi, On 07-10-15 19:02, Andreas Beckmann wrote: On 2015-10-07 18:43, Manuel Bilderbeek wrote: Please send the output of these 2 commands: find /dev/dri* /dev/nvidia* -ls $ find /dev/dri* /dev/nvidia* -ls 107210 drwxr-xr-x 2 root root 60 okt 7 14:13 /dev/dri 10722

Bug#801191: nvidia-driver: gdm3 can't start anymore (acceleration check failed)

OK, thank you all, it works :) 2015-10-07 13:56 GMT+02:00 Diederik de Haas <didi.deb...@cknow.org>: > On Wednesday 07 October 2015 13:42:19 Manuel Bilderbeek wrote: > > I can't use gdm3 anymore. So I also can't easily use gnome or my whole > > desktop anymore > > Try

Bug#801191: nvidia-driver: gdm3 can't start anymore (acceleration check failed)

Package: nvidia-driver Version: 340.93-3 Severity: important Dear Maintainer, * What led up to the situation? I upgraded from 340.93-1 to 340.93-3. * What exactly did you do (or not do) that was effective (or ineffective)? Just booted the computer. When gdm3 was starting all I got

Bug#801191: nvidia-driver: gdm3 can't start anymore (acceleration check failed)

Hi, On 07-10-15 14:07, Andreas Beckmann wrote: Instead of just applying this "workaround" everywhere, can we try to dig into this? Did you upgrade any xorg packages at the same time or were you running xserver-xorg-core 2:1.17.2-1.1 successfully with 340.93-3? This is what was upgraded:

Bug#801191: nvidia-driver: gdm3 can't start anymore (acceleration check failed)

Hi, On 07-10-15 18:31, Andreas Beckmann wrote: Just to double check: you rebooted after putting back the old nvidia-modprobe.conf? Directly after the $ sudo deluser Debian-gdm video I tried to log out and the problem reappeared immediately when gdm3 was trying to show the new login screen.

Bug#794379: Regression: can't play bgr0 AVI's anymore

Package: mplayer2 Version: 2.0-728-g2c378c7-4+b2 Severity: normal Dear Maintainer, * What led up to the situation? I probably an update, I dist-upgrade my testing daily. * What exactly did you do (or not do) that was effective (or ineffective)? I've been able to replay AVI videos

Bug#790366: gthumb: 6000x26000 image doesn't display, even controls not displayed

Hi, On 05-07-15 15:41, Herbert Parentes Fortes Neto (hpfn) wrote: I retried and the problem seems to be only with 05*.png. It only open with gimp. If you try the others first, they will open. Yes, I only reported about the 05 png. Sorry if that was not clear. The file opens fine with: -

Bug#790366: gthumb: 6000x26000 image doesn't display, even controls not displayed

Hi, OK. thanks! Note that I reported the same problem on eog. Perfectly working for these images are viewnior and gpicview (and only taking 469MB of RAM, almost exactly what you expect). Perhaps that gives upstream the right motivation ;-) Kind regards, Manuel On 03-07-15 21:35, Herbert

Bug#790361: qiv: Crashes gnome-shell when viewing large image

Package: qiv Version: 2.3.1-1 Severity: normal Dear Maintainer, I was trying to view a PNG with the following properties: 05_Xak_2_-_Het_Kasteel.png: PNG image data, 6000 x 26000, 8-bit/color RGB, non-interlaced (it can be downloaded here: http://www.msx.org/downloads/xak-ii-map ) After a

Bug#790362: mirage: Uses too much memory

Package: mirage Version: 0.9.5.1-3 Severity: normal Dear Maintainer, I was trying to view a PNG with the following properties: 05_Xak_2_-_Het_Kasteel.png: PNG image data, 6000 x 26000, 8-bit/color RGB, non-interlaced (it can be downloaded here: http://www.msx.org/downloads/xak-ii-map ) It

Bug#790359: eog: 6000x26000 image doesn't display, even controls not displayed

Package: eog Version: 3.16.2-1 Severity: normal Dear Maintainer, I was trying to view a PNG with the following properties: 05_Xak_2_-_Het_Kasteel.png: PNG image data, 6000 x 26000, 8-bit/color RGB, non-interlaced (it can be downloaded here: http://www.msx.org/downloads/xak-ii-map ) After a

Bug#790364: xloadimage: Uses too much memory

Package: xloadimage Version: 4.1-23+b1 Severity: normal Dear Maintainer, I was trying to view a PNG with the following properties: 05_Xak_2_-_Het_Kasteel.png: PNG image data, 6000 x 26000, 8-bit/color RGB, non-interlaced (it can be downloaded here: http://www.msx.org/downloads/xak-ii-map ) It

Bug#790366: gthumb: 6000x26000 image doesn't display, even controls not displayed

Package: gthumb Version: 3:3.4.0-2 Severity: normal Dear Maintainer, I was trying to view a PNG with the following properties: 05_Xak_2_-_Het_Kasteel.png: PNG image data, 6000 x 26000, 8-bit/color RGB, non-interlaced (it can be downloaded here: http://www.msx.org/downloads/xak-ii-map ) After a

Bug#789719: libinput10: Print keypress not working anymore

Package: libinput10 Version: 0.17.0-1 Severity: important Dear Maintainer, * What led up to the situation? After my daily dist-upgrade of my testing distro last Sunday, I can no longer make screenshots with the Print-shortcut. But the binding is still configured as normal. So, I checked what

Bug#766732: gvfsd-dav segfaults in strlen() when browsing directory containing %

Package: gvfs-backends Version: 1.24.1-2+b1 Followup-For: Bug #766732 Dear Maintainer, FWIW, I just installed jessie and dist-upgraded to testing and I see this in my dmesg: [24377.975079] pool[21459]: segfault at 7fadf6b50714 ip 7fad1f99c72e sp 7fad02b46298 error 4 in

Bug#788619: openjdk-7-jdk: Not installable

Package: openjdk-7-jdk Severity: important Dear Maintainer, I tried to install this package, here are the results: $ sudo apt-get install openjdk-7-jdk Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may

Bug#788384: installation-reports: Boots into black screen due to modesetting on nVidia card

Package: installation-reports Severity: important Dear Maintainer, See below. -- Package-specific info: Boot method: USB stick Image version: http://cdimage.debian.org/debian-cd/8.1.0/amd64/iso-cd/debian-8.1.0-amd64-netinst.iso Date: jun 8 22:49 Machine: Custom PC from 2008 Partitions: df

Bug#783501: idutch: Gives a whole load of Word 'x' contains illegal characters errors when setting up

Package: idutch Version: 1:2.10-3 Severity: normal Dear Maintainer, * What led up to the situation? Installing the latest package. When setting up the package during installation: Processing triggers for dictionaries-common (1.23.17) ... ispell-autobuildhash: Processing 'dutch' dict. Word

Bug#772075: gnumeric: Segfaults when undoing Add 1 row in my sheet

Package: gnumeric Version: 1.12.18-1 Severity: important Dear Maintainer, When I was editing my spread sheet, I chose Add 1 row and it got added. Then I saw that the conditional formatting under that row simply broke (I guess that's another bug), so, I pressed CTRL-Z to undo it. Then I got a

  1   2   3   4   5   >