Bug#1058932: RFP: forgejo -- a self-hosted lightweight software forge
On Mon, 25 Dec 2023 11:36:59 +0800 Maytham Alsudany wrote: > > There's already an RFP for gitea (#935834), which forgejo is based on. > Hello Maytham, there is a comparison available on: https://forgejo.org/compare/ to me it looks like forgejo has more a full open source (main) spirit? mvg, Wim
Bug#1058932: RFP: forgejo -- a self-hosted lightweight software forge
Package: wnpp Severity: wishlist * Package name: forgejo Version : latest stable Upstream Author : ? * URL : https://forgejo.org * License : MIT Programming Lang: Go Description : a self-hosted lightweight software forge Forgejo is a self-hosted lightweight software forge. Easy to install and low maintenance, it just does the job. Brought to you by an inclusive community under the umbrella of Codeberg e.V., a democratic non-profit organization, Forgejo can be trusted to be exclusively Free Software. It focuses on security, scaling, federation and privacy. It supports among others: git, wiki, issues, email, collaboration, .. -- It would be nice to have it in Debian, as apart from Redmine there no "easy" to setup project management software available. Some work has already been done? https://codeberg.org/forgejo-contrib/forgejo-deb
Bug#1054415: cockpit-ws: remotectl command missing?
Martin Pitt schreef op ma 23-10-2023 om 17:36 [+0200]: > > This is intended, see > https://cockpit-project.org/blog/cockpit-252.html > Hello Martin, as a follow-up to that link if the manpages are generated correctly: https://manpages.debian.org/unstable/cockpit-ws/remotectl.8.en.html https://manpages.debian.org/bullseye/cockpit-ws/remotectl.8.en.html remotectl is present in unstable and testing as well? mvg, Wim
Bug#1054415: cockpit-ws: remotectl command missing?
Martin Pitt schreef op ma 23-10-2023 om 17:36 [+0200]: > > Control: tag -1 wontfix > > > This is intended, see > https://cockpit-project.org/blog/cockpit-252.html > > Out of interest, why do you need it? Hello Martin, i was setting up the https://elephant-shed.io/ , which has this dependency in one of the scripts of the elehant-shed- cockpit package mvg, Wim > If you want to set up a key for cockpit-ws > in advance, there are usually better tools (ansible, linux-system- > roles, > LetsEncrypt, etc.), and in the worst case you can still call > /usr/lib/cockpit/cockpit-certificate-ensure . > > Martin
Bug#1009176: radicale: solution
Jonas Smedegaard schreef op vr 08-04-2022 om 14:38 [+0200]: > Alternatively, for the systemd service unit file you can try this: > > systemd-delta > > ...or compare manually with the file here: > https://salsa.debian.org/debian/radicale/-/blob/debian/3.1.5-1_bpo11+1/debian/radicale.service interesting: my service file is different, so i probably made it myself quite a while ago, as there does not seem to be a service file in https://packages.debian.org/buster/all/radicale/download conclusion: a upgrade of radicale does not upgrade the service file (or asks to), (as it was probably expecting none) hth, Wim
Bug#1009176: radicale: solution
Jonas Smedegaard schreef op vr 08-04-2022 om 13:45 [+0200]: > Quoting wim (2022-04-08 12:15:49) > > i had the same problem, > > changing the service type to simple in > > /etc/systemd/system/radicale.service > > solved this issue > > That sounds odd: Default type is documented to be "simple". > > Are you sure you used the default systemd service unit before that > edit? i don't recall changing it, (but also not 100%sure) but this is on a debian 9>10>11 machine, so maybe this is remnant from the dist-upgrade process? > > > - Jonas >
Bug#1003717: xserver-xorg-video-nouveau: ttm buffer eviction failed + failed to load nvd9_fuc084 (regression db11-db10)
Package: xserver-xorg-video-nouveau Version: 1:1.0.17-1 Severity: serious Justification: serious Hello, This behaviour started with the upgrade from debian 10 to debian 11, (regression) and has gotten worse since, the graphical interface locks up on frequent base for a long time, (more than once per hour, locking up from 10minutes to more than a hour, rebooting with a hard reset) rendering the laptop useless it might be related to the following bugs: #990662 #989705 #903426 the errors from dmesg, * [TTM] Buffer eviction failed * firmware: failed to load nouveau/nvd9_fuc084 (maybe onrelated?) a file is attached with more background. hth, Wim -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Oct 5 2015 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Dec 16 18:08 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98M [Quadro NVS 160M] [10de:06eb] (rev a1) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 0 /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 5.10.0-10-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.84-1 (2021-12-08) Xorg X server log files on system: -- -rw-r--r-- 1 wim wim 44389 Mar 27 2019 /home/wim/.local/share/xorg/Xorg.2.log -rw-r--r-- 1 wim wim 42624 Nov 12 2019 /home/wim/.local/share/xorg/Xorg.1.log -rw-r--r-- 1 wim wim 47577 Nov 12 2019 /home/wim/.local/share/xorg/Xorg.0.log -rw-r--r-- 1 root root 63438 Nov 23 11:31 /var/log/Xorg.1.log -rw-r--r-- 1 root root 43325 Jan 14 09:22 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [36.852] X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 [36.852] Build Operating System: linux Debian [36.852] Current Operating System: Linux lolifant 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 [36.852] Kernel command line: BOOT_IMAGE=/vmlinuz-5.10.0-10-amd64 root=/dev/mapper/lolifant--vg-root ro quiet [36.852] Build Date: 16 December 2021 05:08:23PM [36.852] xorg-server 2:1.20.11-1+deb11u1 (https://www.debian.org/support) [36.852] Current version of pixman: 0.40.0 [36.852]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [36.852] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [36.852] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 14 09:05:05 2022 [36.956] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [36.989] (==) No Layout section. Using the first Screen section. [36.989] (==) No screen section available. Using defaults. [36.989] (**) |-->Screen "Default Screen Section" (0) [36.989] (**) | |-->Monitor "" [36.996] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [36.996] (==) Automatically adding devices [36.996] (==) Automatically enabling devices [36.996] (==) Automatically adding GPU devices [36.996] (==) Max clients allowed: 256, resource mask: 0x1f [37.035] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [37.035]Entry deleted from font path. [37.060] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [37.060] (==) ModulePath set to "/usr/lib/xorg/modules" [37.060] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [37.060] (II) Loader magic: 0x557d2d752e40 [37.060] (II) Module ABI versions: [37.060]X.Org ANSI C Emulation: 0.4 [37.060]X.Org Video Driver: 24.1 [37.060]X.Org XInput driver : 24.1 [37.060]X.Org Server Extension : 10.0 [37.061] (++) using VT number 7 [37.061] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [37.062] (II) xfree86: Adding drm device (/dev/dri/card0) [37.072] (--) PCI:*(1@0:0:0) 10de:06eb:1028:024f rev 161, Mem @ 0xf500/16777216, 0xe000/268435456, 0xf200/33554432, I/O @ 0xdf00/128, BIOS @ 0x/131072 [37.079] (II) LoadModule: "glx" [37.103] (II)
Bug#990662: firmware-misc-nonfree: confirmation
Package: firmware-misc-nonfree Version: 20210315-3 Followup-For: Bug #990662 Hello, a confirmation of this bug # dmesg | grep -i nouv [2.688397] nouveau :01:00.0: vgaarb: deactivate vga console [2.690019] nouveau :01:00.0: NVIDIA G98 (298580a2) [2.725486] nouveau :01:00.0: bios: version 62.98.73.00.04 [2.745965] nouveau :01:00.0: fb: 256 MiB GDDR3 [2.825306] nouveau :01:00.0: DRM: VRAM: 256 MiB [2.825307] nouveau :01:00.0: DRM: GART: 1048576 MiB [2.825311] nouveau :01:00.0: DRM: TMDS table version 2.0 [2.825315] nouveau :01:00.0: DRM: DCB version 4.0 [2.825317] nouveau :01:00.0: DRM: DCB outp 00: 01000323 00010034 [2.825320] nouveau :01:00.0: DRM: DCB outp 01: 02011300 0028 [2.825324] nouveau :01:00.0: DRM: DCB outp 02: 02022386 0f200010 [2.825325] nouveau :01:00.0: DRM: DCB outp 03: 02022332 00020010 [2.825328] nouveau :01:00.0: DRM: DCB outp 04: 040333a6 0f200010 [2.825329] nouveau :01:00.0: DRM: DCB outp 05: 04033312 00020010 [2.825332] nouveau :01:00.0: DRM: DCB conn 00: 0040 [2.825334] nouveau :01:00.0: DRM: DCB conn 01: 0100 [2.825337] nouveau :01:00.0: DRM: DCB conn 02: 5246 [2.825338] nouveau :01:00.0: DRM: DCB conn 03: a346 [2.830444] nouveau :01:00.0: DRM: MM: using M2MF for buffer copies [2.921951] nouveau :01:00.0: DRM: allocated 1920x1200 fb: 0x5, bo 5b258a42 [2.922019] fbcon: nouveaudrmfb (fb0) is primary device [4.248388] nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer device [4.268803] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0 [ 53.775327] nouveau :01:00.0: firmware: failed to load nouveau/nv98_fuc084 (-2) [ 53.775333] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084 failed with error -2 [ 53.775345] nouveau :01:00.0: firmware: failed to load nouveau/nv98_fuc084d (-2) [ 53.775347] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084d failed with error -2 [ 53.775349] nouveau :01:00.0: msvld: unable to load firmware data [ 53.775351] nouveau :01:00.0: msvld: init failed, -19 [ 72.661417] nouveau :01:00.0: firmware: failed to load nouveau/nv98_fuc084 (-2) [ 72.661425] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084 failed with error -2 [ 72.661436] nouveau :01:00.0: firmware: failed to load nouveau/nv98_fuc084d (-2) [ 72.661438] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084d failed with error -2 [ 72.661440] nouveau :01:00.0: msvld: unable to load firmware data [ 72.661443] nouveau :01:00.0: msvld: init failed, -19 [ 227.014093] nouveau :01:00.0: fifo: CACHE_ERROR - ch 3 [Xorg[692]] subc 0 mthd 0060 data beef0201 [ 366.102466] nouveau :01:00.0: fifo: CACHE_ERROR - ch 3 [Xorg[692]] subc 3 mthd 1b00 data # lshw -C Display *-display description: VGA compatible controller product: G98M [Quadro NVS 160M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:28 memory:f500-f5ff memory:e000-efff memory:f200-f3ff ioport:df00(size=128) memory:c-d hth, Wim -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/2 CPU threads) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8), LANGUAGE=nl_BE:nl Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-misc-nonfree depends on no packages. firmware-misc-nonfree recommends no packages. Versions of packages firmware-misc-nonfree suggests: ii initramfs-tools 0.140 -- no debconf information
Bug#968093: libinput10: confirmation (using bumblebee as well)
wim schreef op wo 12-01-2022 om 15:57 [+0100]: > but my system does indeed lag noticeabily, both mouse and keyboard as > the screen, this can probably be safely ignored, as i forgot that cuda was the reason for using this setup, without cuda processes running the lag or slow respons is gone hth, Wim
Bug#848938: xserver-xorg-video-nouveau: the same on XFCE
Package: xserver-xorg-video-nouveau Version: 1:1.0.17-1 Followup-For: Bug #848938 Hello, the same problem on XFCE, when does it seem to occur: * at random, returning often back to normal after 1-30 minutes * after a energy black screen, returning often back to normal after 1-30 minutes * after a unlock of locked screen, returning often back to normal after 1-30 minutes hth, Wim More output: # dmesg | grep -i nouv [2.445524] nouveau :01:00.0: vgaarb: deactivate vga console [2.448140] nouveau :01:00.0: NVIDIA G98 (298580a2) [2.493599] nouveau :01:00.0: bios: version 62.98.73.00.04 [2.514380] nouveau :01:00.0: fb: 256 MiB GDDR3 [2.599399] nouveau :01:00.0: DRM: VRAM: 256 MiB [2.599401] nouveau :01:00.0: DRM: GART: 1048576 MiB [2.599404] nouveau :01:00.0: DRM: TMDS table version 2.0 [2.599405] nouveau :01:00.0: DRM: DCB version 4.0 [2.599407] nouveau :01:00.0: DRM: DCB outp 00: 01000323 00010034 [2.599409] nouveau :01:00.0: DRM: DCB outp 01: 02011300 0028 [2.599411] nouveau :01:00.0: DRM: DCB outp 02: 02022386 0f200010 [2.599413] nouveau :01:00.0: DRM: DCB outp 03: 02022332 00020010 [2.599414] nouveau :01:00.0: DRM: DCB outp 04: 040333a6 0f200010 [2.599416] nouveau :01:00.0: DRM: DCB outp 05: 04033312 00020010 [2.599417] nouveau :01:00.0: DRM: DCB conn 00: 0040 [2.599419] nouveau :01:00.0: DRM: DCB conn 01: 0100 [2.599420] nouveau :01:00.0: DRM: DCB conn 02: 5246 [2.599421] nouveau :01:00.0: DRM: DCB conn 03: a346 [2.603009] nouveau :01:00.0: DRM: MM: using M2MF for buffer copies [2.697488] nouveau :01:00.0: DRM: allocated 1920x1200 fb: 0x5, bo 0df0c147 [2.697551] fbcon: nouveaudrmfb (fb0) is primary device [4.032909] nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer device [4.053179] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0 [ 21.281064] nouveau :01:00.0: firmware: failed to load nouveau/nv98_fuc084 (-2) [ 21.281070] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084 failed with error -2 [ 21.281080] nouveau :01:00.0: firmware: failed to load nouveau/nv98_fuc084d (-2) [ 21.281082] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084d failed with error -2 [ 21.281084] nouveau :01:00.0: msvld: unable to load firmware data [ 21.281087] nouveau :01:00.0: msvld: init failed, -19 [ 37.682811] nouveau :01:00.0: firmware: failed to load nouveau/nv98_fuc084 (-2) [ 37.682818] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084 failed with error -2 [ 37.682829] nouveau :01:00.0: firmware: failed to load nouveau/nv98_fuc084d (-2) [ 37.682831] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084d failed with error -2 [ 37.682834] nouveau :01:00.0: msvld: unable to load firmware data [ 37.682836] nouveau :01:00.0: msvld: init failed, -19 [ 315.899775] nouveau :01:00.0: fifo: CACHE_ERROR - ch 3 [Xorg[683]] subc 3 mthd 1b00 data [ 361.958699] nouveau :01:00.0: fifo: CACHE_ERROR - ch 3 [Xorg[683]] subc 3 mthd 1b00 data [ 413.310191] nouveau :01:00.0: fifo: CACHE_ERROR - ch 3 [Xorg[683]] subc 0 mthd 0060 data beef0201 xorg.log EE: [ 8826.477] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied # dmidecode | grep -i nvi -n3 301-On Board Device Information 302-Type: Video 303-Status: Enabled 304:Description: NVIDIA Quadro NVS 160M 305- 306-Handle 0x0A01, DMI type 10, 6 bytes 307-On Board Device Information -- 490-Header and Data: 491-D8 09 00 D8 01 03 01 F0 03 492-Strings: 493:NVidia Corp. 494- 495-62.98.73.00.04 496- hth, Wim -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Oct 5 2015 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Apr 13 2021 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98M [Quadro NVS 160M] [10de:06eb] (rev a1) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 0 /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 5.10.0-9-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.70-1 (2021-09-30) Xorg X server log files on system: -- -rw-r--r-- 1 wim wim 44389 Mar 27 2019 /home/wim/.local/share/xorg/Xorg.2.log -rw-r--r-- 1 wim wim 42624 Nov 12 2019 /home/wim/.local/share/xorg/Xorg.1.log -rw-r--r-- 1 wim wim 47577 Nov 12 2019
Bug#992335: shim-helpers-amd64-signed: grub install: error: failed to register the EFI boot entry, no space left on device
This bug can probably be closed now. Feedback for other reading this: 1. After rebooting the mok management was shown 2. It rebooted by itself after a minute or so 3. No password was entered, even though it was asked twice by configuration of the shim-helpers package to enter such a password 4. The machine boot sequence continued 5. Once booted, i checked to see if secure boot was enabled and if tis was running the latest kernel in boot dir: $ mokutil --sb-state SecureBoot enabled (ok) $ uname -a Linux blauwbok 5.10.0-0.bpo.8-amd64 #1 SMP Debian 5.10.46-2~bpo10+1 (2021-07-22) x86_64 GNU/Linux (which was the latest installed) hth, Wim
Bug#992335: shim-helpers-amd64-signed: grub install: error: failed to register the EFI boot entry, no space left on device
Steve McIntyre schreef op vr 20-08-2021 om 14:50 [+0100]: > On Fri, Aug 20, 2021 at 03:40:48PM +0200, Wim Bertels wrote: > > Steve McIntyre schreef op vr 20-08-2021 om 14:29 [+0100]: > > > Nod. The problem is that your system is failing to create/update > > > an > > > EFI boot variable in its NVRAM. The most common issue that causes > > > this > > > is system log reports in /sys/fs/pstore/ . Could you check and > > > see if > > > there are any files there please? > > > > Yes, there are many files, all from 'nov 7 2019' which could be the > > installation date. > > > > # ls /sys/fs/pstore/ -altr > > totaal 0 > > -r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250037001 > > -r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250036001 > > -r--r--r-- 1 root root 1800 nov 7 2019 dmesg-efi-157315250035002 > > -r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250035001 > > -r--r--r-- 1 root root 1800 nov 7 2019 dmesg-efi-157315250034002 > > > > An example of the content, most of them about nouveau: > > OK, that's junk that you can simply delete. If you do that, things > should clear up for you. Depending on the firmware of your computer > (and its handling of EFI variables), you *might* need to reboot for > the space to free up completely. In that case, I'd recomment that you > have an installer USB (or similar) handy just in case things don't > > boot. > ok, emptied it(, without rebooting) /sys/fs/pstore# rm dmesg-efi-1573* That seemed to do trick, --configure gives no errors, just reporting this, in case the system doesn't reboot (password for eufi change was asked) # dpkg --configure shim-helpers-amd64-signed Instellen van shim-helpers-amd64-signed (1+15.4+5~deb10u1) ... Installeren voor x86_64-efi-platform. Installatie is afgerond. Er werden geen fouten gerapporteerd. # dpkg --configure shim-signed Instellen van shim-signed:amd64 (1.36~1+deb10u2+15.4-5~deb10u1) ... Installeren voor x86_64-efi-platform. Installatie is afgerond. Er werden geen fouten gerapporteerd. hth, Wim
Bug#992335: shim-helpers-amd64-signed: grub install: error: failed to register the EFI boot entry, no space left on device
Steve McIntyre schreef op vr 20-08-2021 om 14:29 [+0100]: > Control: reassign -1 grub-efi-amd64 > > Hi wim, > > On Tue, Aug 17, 2021 at 03:22:49PM +0200, wim wrote: > > Package: shim-helpers-amd64-signed > > Version: 1+15.4+5~deb10u1 > > Severity: normal > > > > Hello, > > > > This is the setup: > > OK, this is a problem being reported by grub-install, called by > shim-helpers-amd64-signed as it's installed. Reassigning to one of > the > grub packages. > > > # df -h > > BestandssysteemGrootte Gebruikt Besch Geb% > > Aangekoppeld op > > udev 32G0 32G 0% > > /dev > > .. > > /dev/mmcblk0p13,7G 64K 3,7G 1% > > /media/wim/MICROSD > > /dev/sr0 88M 88M 0 100% > > /media/wim/20190318_164558 > > > > So /boot/efi and /boot have free space > > Nod. The problem is that your system is failing to create/update an > EFI boot variable in its NVRAM. The most common issue that causes > this > is system log reports in /sys/fs/pstore/ . Could you check and see if > there are any files there please? Yes, there are many files, all from 'nov 7 2019' which could be the installation date. # ls /sys/fs/pstore/ -altr totaal 0 -r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250037001 -r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250036001 -r--r--r-- 1 root root 1800 nov 7 2019 dmesg-efi-157315250035002 -r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250035001 -r--r--r-- 1 root root 1800 nov 7 2019 dmesg-efi-157315250034002 An example of the content, most of them about nouveau: # cat /sys/fs/pstore/dmesg-efi-157332678916001 Oops#1 Part16 <4>[ 105.363372] ? __switch_to+0x7a/0x3e0 <4>[ 105.363373] ? __switch_to_asm+0x34/0x70 <4>[ 105.363374] pm_runtime_work+0x82/0x90 <4>[ 105.363375] process_one_work+0x1a7/0x3b0 <4>[ 105.363375] worker_thread+0x30/0x390 <4>[ 105.363376] ? create_worker+0x1a0/0x1a0 <4>[ 105.363377] kthread+0x112/0x130 <4>[ 105.363378] ? __kthread_parkme+0x70/0x70 <4>[ 105.363378] ret_from_fork+0x1f/0x40 <4>[ 105.363379] ---[ end trace b62441a5f9a44a7c ]--- <2>[ 105.364066] nouveau :01:00.0: tmr: stalled at <4>[ 105.364067] [ cut here ] <4>[ 105.364067] nouveau :01:00.0: timeout <4>[ 105.364096] WARNING: CPU: 5 PID: 557 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmtu102.c:47 tu102_vmm_flush+0x128/0x140 [nouveau] <4>[ 105.364097] Modules linked in: nls_utf8 isofs fuse ctr ccm rfcomm cmac snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress arc4 iwlmvm intel_rapl mac80211 bnep iwlwifi btusb btrtl btbcm btintel bluetooth cfg80211 drbg ansi_cprng ecdh_generic hp_wmi ecc sparse_keymap snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_realtek kvm nls_ascii nls_cp437 snd_hda_codec_generic vfat irqbypass efi_pstore fat ledtrig_audio intel_cstate snd_usb_audio uvcvideo snd_hda_intel cdc_ether videobuf2_vmalloc usbnet videobuf2_memops snd_hda_codec intel_uncore videobuf2_v4l2 videobuf2_common snd_usbmidi_lib r8152 snd_rawmidi snd_hda_core snd_seq_device mii intel_rapl_perf efivars videodev snd_hwdep joydev rtsx_pci_ms iTCO_wdt snd_pcm mei_me iTCO_vendor_support serio_raw intel_wmi_thunderbolt pcspkr watchdog wmi_bmof pcc_cpufreq tpm_crb memstick sg usblp media snd_timer rfkill mei The ones that are not: # cat $(grep -L nouv * ) Oops#1 Part2 <4>[ 200.823189] RDX: 0029 RSI: 00b4 RDI: c03e <4>[ 200.823190] RBP: aa238675bd98 R08: R09: <4>[ 200.823191] R10: R11: R12: <4>[ 200.823192] R13: 7fff R14: 9530e3ea83c0 R15: <4>[ 200.823193] ? common_interrupt+0xa/0xf <4>[ 200.823195] ? __bpf_prog_run32+0x39/0x60 <4>[ 200.823196] ? __seccomp_filter+0x6a/0x680 <4>[ 200.823198] ? __seccomp_filter+0x7a/0x680 <4>[ 200.823199] ? devkmsg_read+0x73/0x2c0 <4>[ 200.823200] ? devkmsg_read+0x165/0x2c0 <4>[ 200.823202] ? syscall_trace_enter+0x192/0x2b0 <4>[ 200.823204] ? do_syscall_64+0x104/0x130 <4>[ 200.823205] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 <4>[ 200.823206] Modules linked in: snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress arc4 intel_rapl iwlmvm mac80211 btusb snd_hda_codec_hdmi btrtl btbcm btintel bluetooth uvcvideo x86_pkg_temp_thermal videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 iwlwifi snd_hda_codec_realtek videobuf2_common intel_powerclamp videodev coretemp snd_hda_codec_generic kvm_intel ledtrig_audio cfg80211 snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm rtsx_pci_ms memstick media kvm snd_timer processor_thermal_device
Bug#982357: postgresql-13-cron: upgrade from v12 to v13 does not work (via apt.postgresql.org)
Package: postgresql-13-cron Version: 1.3.0-2.pgdg100+1 Severity: important Dear Maintainer, a pg_upgrade from v12 to v13 (with a working pg_cron (postgresql-12-cron) on the v12 cluster) does not seem to work. postgresql-13-cron is also installed. the extension, though installed, is not found during the upgrade. (other extensions are found, so i'm guessing this not a issue of pg_upgrade) the configuration parameter "cron.database_name" and the extension "pg_cron" reported as the problem. repository: apt.postgresql.org for buster (even though this is not the main debian repository, if i'm not mistaking more or less maintainers work on this, and eventually this will into debian) hth, Wim the error log: # pg_upgradecluster 12 2021 | tee &> /tmp/u_12_2021_13 ERROR: unrecognized configuration parameter "cron.database_name" CONTEXT: PL/pgSQL function inline_code_block line 3 at IF ERROR: extension "pg_cron" does not exist ERROR: schema "cron" does not exist ERROR: schema "cron" does not exist pg_restore: error: could not execute query: ERROR: schema "cron" does not exist Command was: ALTER TABLE cron.job DISABLE TRIGGER ALL; pg_restore: error: could not execute query: ERROR: schema "cron" does not exist Command was: COPY "cron"."job" ("jobid", "schedule", "command", "nodename", "nodeport", "database", "username", "active") FROM stdin; pg_restore: error: could not execute query: ERROR: schema "cron" does not exist Command was: ALTER TABLE cron.job ENABLE TRIGGER ALL; pg_restore: from TOC entry 2914; 0 0 SEQUENCE SET jobid_seq wim pg_restore: error: could not execute query: ERROR: schema "cron" does not exist LINE 1: SELECT pg_catalog.setval('"cron"."jobid_seq"', 9, true); ^ Command was: SELECT pg_catalog.setval('"cron"."jobid_seq"', 9, true); -- System Information: Debian Release: 10.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8), LANGUAGE=nl_BE:nl (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages postgresql-13-cron depends on: ii libc6 2.28-10 ii libpq5 13.1-1.pgdg100+1 ii postgresql-13 13.1-1.pgdg100+1 postgresql-13-cron recommends no packages. postgresql-13-cron suggests no packages. -- no debconf information
Bug#931306: +1
-- mvg, Wim Bertels -- Lector UC Leuven-Limburg -- What I tell you three times is true. -- Lewis Carroll
Bug#931640: webext-ublock-origin: confirmation
Markus Koschany schreef op zo 10-11-2019 om 21:05 [+0100]: > > Am 10.11.19 um 20:36 schrieb wim: > > Package: webext-ublock-origin > > Version: 1.18.4+dfsg-2 > > Followup-For: Bug #931640 > > > > Hello, > > > > confirmation: > > the extension/addon > > is not active or visible in firefox-esr > > on the installed addons/extensions page > > Please disable and reenable the addon and then restart Firefox. This seems to fix it, thank you, Wim > > Thanks, > > Markus >
Bug#943494: vokoscreen: outputs black video
> Hi Wim, > > Seems a problem with your video card or acceleration. Can you try in > other machine? Hallo Eriberto, i tested this with recordmydesktop and kazam as well, as with ctrl alt shift r in the gnome, recordmydesktop and kazam: blank black screen ctrl alt shift r: empty file also, printscreen doesn't work so it's problably not vokoscreen related, if given a chance i will try it on another machine just to know do you use wayland? i'm on wayland $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type should give you the env, my case: wayland hth, Wim > > Eriberto
Bug#943494: vokoscreen: outputs black video
> > Hi Wim, > > I think it is a problem in your system. Can you try in a fresh Debian > install? vokoscreen is working fine. Hello Eriberto, i have also tried with it a fresh vm install, the same behaviour, with additionaly: * crash on recording a window also , i notice that only the mouse pointer gets recorded to a black background hth, Wim > > Regards, > > Eriberto
Bug#919385: postgresql-common: alter system set port ignored by pg-commands
Hallo, in my opinion the cleanest patch would be to change the file location of postgresql.auto.conf to the /etc/postgresql/version/cluster directory. But a you pointed out, this is hardcoded into postgresql. So a patch to postgresql for enabling this, means making this a compile time option instead of being hardcoded. This option eg --location_of_postgresql_auto could then be set at compile time. hth, Wim Van: Christoph Berg Verzonden: woensdag 27 februari 2019 15:37 Aan: Wim Bertels; 919...@bugs.debian.org Onderwerp: Re: Bug#919385: postgresql-common: alter system set port ignored by pg-commands I was looking into several ideas that all have some problems. 0. Look into pg_settings Doesn't work because we can only query the database if we already know the port 1. Put the port on the postgres command line (postgres -p ) Works, but then restarting the server is hard once the port got changed. `pg_ctl restart` will even preserve the last command line. 2. Put the port into a file next to /var/run/postgresql/11-main.pid Has several consistency issues. If the port is changed, the file is not updated immediately. If the cluster is shut down, should the file be removed? 3. Write a suid wrapper that read postgresql.auto.conf suid programs are a security nightmare. 4. Patch PostgreSQL such that it puts the port into external_pid_file, i.e. into /var/run/postgresql/11-main.pid Patching the server is evil, and it breaks applications reading the external file that are not prepared to ignore extra information The bottom line is that #4 looks most attractive, but I'm not fixing this in postgresql-common now. I will try sending a patch for #4 to upstream and see if it gets accepted for PG 12+. If so, we can still patch the older versions on our side. Christoph
Bug#919385: postgresql-common: alter system set port ignored by pg-commands
> But in actual practise, there is a problem, postgresql.auto.conf is > stored inside PGDATA, which is not readable by anyone except postgres > and root, so settings modified that way are only visible (and used) > for these users. ok, thank you for the clarification Christoph, root and postgres do indeed give the correct information, other users don't. > > I don't see how we can sanely get out of this problem. The idea of > connecting to the server to query pg_settings has the problem that > it's more heavyweight, and of course we need to know the port to be > able to connect... Storing the port in yet another location doesn't > seem attractive either. if i compare the permission settings of the 2 conf files: -rw-r--r-- 1 postgres postgres 22983 feb 14 12:45 /etc/postgresql/11/oefensets/postgresql.conf -rw--- 1 postgres postgres 385 mrt 2 2018 /var/lib/postgresql/11/oefensets/postgresql.auto.conf why are they different? if it's important that postgresql.auto.conf isn't readable by other, then why is postgresql.conf, if it is an option: storing the postgresql.auto.conf in the /etc/postgresql/11/oefensets/ dir would open the option to set the permissions to -rw-r--r-- Or is there a good reason not to store this file here? > > Christoph -- mvg, Wim Bertels -- If more of us valued food and cheer and song above hoarded gold, it would be a merrier world. -- J.R.R. Tolkien
Bug#922764: libreoffice-base: schema not respected in copy/paste of calc_table to base_table
Package: libreoffice-base Version: 1:5.2.7-1+deb9u5 Severity: normal Hallo, U can use copy/paste between calc and base to create a database table form calc data. I tested this with postgresql Backend setup: * pg server * user user1 * database db1 ** schema schema1 ** schema schema2 When u paste the data (from calc) into the schema1 (in base) the schema is ignored or it will give an error. When u try the same with a different database client, this will work. Given the error base gives, it seems it only reads the default search_path of the logged in user, and completely ignores the schema1 in which it was pasted. This allowing only to paste in a schema that is in the default path of user1. PS: set search_path to schema1; is not recognized in base Suggestion: make the paste command in base schema aware hth, Wim -- System Information: Debian Release: 9.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8), LANGUAGE=nl_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreoffice-base depends on: ii dpkg 1.18.25 ii libc6 2.24-11+deb9u3 ii libgcc1 1:6.3.0-18+deb9u1 ii libreoffice-base-core 1:5.2.7-1+deb9u5 ii libreoffice-base-drivers 1:5.2.7-1+deb9u5 ii libreoffice-core 1:5.2.7-1+deb9u5 ii libstdc++66.3.0-18+deb9u1 ii uno-libs3 5.2.7-1+deb9u5 ii ure 5.2.7-1+deb9u5 Versions of packages libreoffice-base recommends: ii default-jre [java5-runtime]2:1.8-58 ii libreoffice-java-common1:5.2.7-1+deb9u5 ii libreoffice-writer 1:5.2.7-1+deb9u5 ii openjdk-8-jre [java5-runtime] 8u181-b13-2~deb9u1 Versions of packages libreoffice-base suggests: pn libreoffice-gcj ii libreoffice-report-builder 1:5.2.7-1+deb9u5 pn unixodbc Versions of packages libreoffice-core depends on: ii fontconfig2.11.0-6.7+b1 ii fonts-opensymbol 2:102.7+LibO5.2.7-1+deb9u5 ii libboost-date-time1.62.0 1.62.0+dfsg-4 ii libc6 2.24-11+deb9u3 ii libcairo2 1.14.8-1 ii libclucene-contribs1v52.3.3.4+dfsg-1 ii libclucene-core1v52.3.3.4+dfsg-1 ii libcmis-0.5-5v5 0.5.1+git20160603-3+b1 ii libcups2 2.2.1-8+deb9u2 ii libcurl3-gnutls 7.52.1-5+deb9u9 ii libdbus-1-3 1.10.26-0+deb9u1 ii libdbus-glib-1-2 0.108-2 ii libdconf1 0.26.0-2+b1 ii libeot0 0.01-4+b1 ii libexpat1 2.2.0-2+deb9u1 ii libexttextcat-2.0-0 3.4.4-2+b1 ii libfontconfig12.11.0-6.7+b1 ii libfreetype6 2.6.3-3.2 ii libgcc1 1:6.3.0-18+deb9u1 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libglew2.02.0.0-3+b1 ii libglib2.0-0 2.50.3-2 ii libgltf-0.0-0v5 0.0.2-5 ii libglu1-mesa [libglu1]9.0.0-2.1 ii libgraphite2-31.3.10-1 ii libharfbuzz-icu0 1.4.2-1 ii libharfbuzz0b 1.4.2-1 ii libhunspell-1.4-0 1.4.1-2+b2 ii libhyphen02.8.8-5 ii libice6 2:1.0.9-2 ii libicu57 57.1-6+deb9u2 ii libjpeg62-turbo 1:1.5.1-2 ii liblangtag1 0.6.2-1 ii liblcms2-22.8-4+deb9u1 ii libldap-2.4-2 2.4.44+dfsg-5+deb9u2 ii libmythes-1.2-0 2:1.2.4-3 ii libneon27-gnutls 0.30.2-2 ii libnspr4 2:4.12-6 ii libnss3 2:3.26.2-1.1+deb9u1 ii libodfgen-0.1-1 0.1.6-2 ii libpcre3 2:8.39-3 ii libpng16-16 1.6.28-1 ii librdf0 1.0.17-1.1 ii libreoffice-common1:5.2.7-1+deb9u5 ii librevenge-0.0-0 0.0.4-6 ii libsm62:1.2.2-1+b3 ii libstdc++66.3.0-18+deb9u1 ii libx11-6 2:1.6.4-3+deb9u1 ii libxext6 2:1.3.3-1+b2 ii libxinerama1 2:1.1.3-1+b3 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 ii libxrandr22:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.11.1.29-2.1 ii uno-libs3 5.2.7-1+deb9u5 ii ure 5.2.7-1+deb9u5 ii zlib1g1:1.2.8.dfsg-5 Versions of packages libreoffice-core recommends: ii libpaper-utils 1.1.24+nmu5 Versions of packages libreoffice-base is related to: pn libmyodbc pn libmysql-java pn libpg-java pn libsapdbc-java pn libsqliteodbc pn mdbtools pn odbc-postgresql pn tdsodbc pn unixodbc -- no debconf information
Bug#810615: postgresql-common: confirmation voor 10>11
Package: postgresql-common Version: 199.pgdg90+1 Followup-For: Bug #810615 Hallo, i suspect the postgresql.auto.conf is not read at all by pg_upgradecluster howto reproduce 1. create a new cluster version 10 2. change a setting like the port or even a settings that would give an error if not correct, for example ssl=on in the standard conf with a custom non default certificate via alter system 3. upgrade the cluster 3.1 port will not be applied 3.2 will not start unless the postgresql.auto.conf is copied over manually (in case of the custom certificate) hth, Wim -- System Information: Debian Release: 9.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8), LANGUAGE=nl_BE:nl (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages postgresql-common depends on: ii adduser 3.115 ii debconf [debconf-2.0] 1.5.61 ii init-system-helpers 1.48 ii lsb-base 9.20161125 ii postgresql-client-common 199.pgdg90+1 ii procps2:3.3.12-3+deb9u1 ii ssl-cert 1.0.39 ii ucf 3.0036 Versions of packages postgresql-common recommends: ii e2fsprogs 1.43.4-2 ii logrotate 3.11.0-0.1 Versions of packages postgresql-common suggests: pn libjson-perl -- debconf information: postgresql-common/obsolete-major: postgresql-common/catversion-bump: postgresql-common/ssl: true
Bug#919933: certbot: confirmation
Package: certbot Version: 0.10.2-1 Followup-For: Bug #919933 Hallo, the problem is that "TLS-SNI-01" is not supported anymore: https://community.letsencrypt.org/t/february-13-2019-end-of-life-for-all-tls-sni-01-validation-support/74209 the successor "TLS-ALPN-01" was only introduced last summer july 2018: https://community.letsencrypt.org/t/tls-alpn-validation-method/63814/2 alle of the letsencrypt clients found on https://wiki.debian.org/LetsEncrypt are the latest from 2017, none of them implement TLS-ALPN-01 So very soon all the certificates generated using these methods will be invalidated (ie expired). In my opinion this is a security issue for the stable distribution, a client (eg certbot) which supports "TLS-ALPN-01" should be updated in stable. Workaround: use the backport version hth, Wim -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/3 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8), LANGUAGE=nl_BE:nl (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages certbot depends on: ii init-system-helpers 1.48 ii python 2.7.13-2 ii python-certbot 0.10.2-1 certbot recommends no packages. Versions of packages certbot suggests: ii python-certbot-apache 0.10.2-1 pn python-certbot-doc -- no debconf information
Bug#911054: workrave: desktop instability in multimonitor (3) setup
I don't have other desktop problems, ie with other programs drivers being used: ii libdrm-nouveau2:amd64 2.4.74- 1amd64Userspace interface to nouveau-specific kernel DRM services -- runtime ii xserver-xorg-video-nouveau1:1.0.13- 3 amd64X.Org X server -- Nouveau display driver hth, Wim Van: Francois Marier Verzonden: maandag 15 oktober 2018 09:31 Aan: Wim Bertels; 911...@bugs.debian.org Onderwerp: Re: Bug#911054: workrave: desktop instability in multimonitor (3) setup On 2018-10-15 at 09:03:54, wim wrote: > in about 80% of the cases, whenever workrave tries to "intervene" with a > break or other notice, > the desktop flickers and needs reloading, > sometimes the desktop needs to be restarted > > this could be related to #503684 ? I just closed that old bug. It's been working fine for me for many years. I would be surprised if workrave was able to cause that much trouble to your X session. Perhaps Xorg drivers are the problem? Francois -- https://fmarier.org/
Bug#893001: xserver-xorg-video-nouveau: kernel rejected pushbuf (pgadmin4)
Package: xserver-xorg-video-nouveau Version: 1:1.0.13-3 Severity: normal Hallo, using pgadmin4 from apt.postgresql.org on debian stretch, the following nouveau error is thrown, this bug has been reported to pgadmin4 dev on apt.postgresql.org as well, but it seems a nouveau problem: output (in dutch): " $ pgadmin4 Python path: "/usr/lib/python3/dist-packages" Python Home: "" Webapp path: "/usr/share/pgadmin4/web/pgAdmin4.py" /usr/lib/python3/dist-packages/flask_migrate/__init__.py:4: ExtDeprecationWarning: Importing flask.ext.script is deprecated, use flask_script instead. from flask.ext.script import Manager [0315/133200:ERROR:nss_util.cc(839)] After loading Root Certs, loaded==false: NSS error code: -8018 nouveau: kernel rejected pushbuf: Bestand of map bestaat niet nouveau: ch8: krec 0 pushes 1 bufs 5 relocs 0 nouveau: ch8: buf 0002 0004 0004 nouveau: ch8: buf 0001 0006 0004 0004 nouveau: ch8: buf 0002 0041 0004 0004 nouveau: ch8: buf 0003 003f 0002 0002 0002 nouveau: ch8: buf 0004 0023 0002 0002 nouveau: ch8: psh 053908 053a18 nouveau:0x0004a200 nouveau:0x0001 nouveau:0x0004a314 nouveau:0x0400 nouveau:0x0018a21c nouveau:0x nouveau:0x0040 nouveau:0x0400 nouveau:0x0100 nouveau:0x0001 nouveau:0x nouveau:0x0008a238 nouveau:0x nouveau:0x nouveau:0x0008a30c nouveau:0x209f7000 nouveau:0x209b7000 nouveau:0x0004a234 nouveau:0x nouveau:0x0010a31c nouveau:0x0400 nouveau:0x0100 nouveau:0x0101 nouveau:0x nouveau:0x00148200 nouveau:0x00d5 nouveau:0x nouveau:0x0040 nouveau:0x0001 nouveau:0x nouveau:0x00108218 nouveau:0x0100 nouveau:0x0100 nouveau:0x nouveau:0x20517000 nouveau:0x00148230 nouveau:0x00cf nouveau:0x nouveau:0x0040 nouveau:0x0001 nouveau:0x nouveau:0x00108248 nouveau:0x0100 nouveau:0x0100 nouveau:0x nouveau:0x209b7000 nouveau:0x0004888c nouveau:0x nouveau:0x001088b0 nouveau:0x nouveau:0x nouveau:0x0100 nouveau:0x0100 nouveau:0x001088c0 nouveau:0x nouveau:0x0001 nouveau:0x nouveau:0x0001 nouveau:0x001088d0 nouveau:0x nouveau:0x nouveau:0x nouveau:0x nouveau:0x00107b00 nouveau:0x nouveau:0x20217000 nouveau:0x0063 nouveau:0x1000f010 Segmentatiefout " hth, Wim -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Oct 5 2015 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Oct 14 13:36 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98M [Quadro NVS 160M] [10de:06eb] (rev a1) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.9.0-6-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) Xorg X server log files on system: -- -rw-r--r-- 1 root root 30877 Jul 25 2016 /var/log/Xorg.1.log -rw-r--r-- 1 root root 73567 Aug 28 2017 /var/log/Xorg.0.log -rw-r--r-- 1 wim wim 43778 Mar 15 12:53 /home/wim/.local/share/xorg/Xorg.1.log -rw-r--r-- 1 wim wim 46369 Mar 15 12:55 /home/wim/.local/share/xorg/Xorg.0.log Contents of most recent Xorg X server log file (/home/wim/.local/share/xorg/Xorg.0.log): [51.318] (--) Log file renamed from "/home/wim/.local/share/xorg/Xorg.pid-1740.log" to "/home/wim/.local/share/xorg/Xorg.0.log" [51.319] X.Org X Server 1.19.2 Release Date: 2017-03-02 [51.319] X Protocol Version 11, Revision 0 [51.319] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian [51.319] Current Operating System: Linux lolifant 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 [51.319] Kernel command line: BOOT_IMAGE=/vmlinuz-4.9.0-6-amd64 root=/dev/mapper/lolifant--vg-root ro quiet [51.319] Build Date: 16 October 2017 08:19:45AM [51.319] xorg-server 2:1.19.2-1+deb9u2
Bug#890831: tora: Connectiontype PostgreSQL not present
Package: tora Version: 2.1.3-3 Severity: normal Hallo, using a fresh debian install, the only connection type present is mysql, this is the only option, no other, like for example postgresql can be selected; even though the description of tora also mentions postgresql. Can anyone confirm this? Hth, Wim -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8), LANGUAGE=nl_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tora depends on: ii libc62.24-11+deb9u1 ii libgcc1 1:6.3.0-18 ii libpq5 10.2-1.pgdg90+1 ii libqscintilla2-12v5 2.9.3+dfsg-4 ii libqt4-network 4:4.8.7+dfsg-11 ii libqt4-sql 4:4.8.7+dfsg-11 ii libqt4-xml 4:4.8.7+dfsg-11 ii libqtcore4 4:4.8.7+dfsg-11 ii libqtgui44:4.8.7+dfsg-11 ii libstdc++6 6.3.0-18 tora recommends no packages. tora suggests no packages. -- no debconf information
Bug#890830: pgmodeler: unable to connect to remote dbcluster with ssl
Package: pgmodeler Version: 0.8.2-1.pgdg90+1 Severity: normal Hallo, i'm unable to add a new working connection to pgmodeler use case: host: remote host port: non standard sslmode : require alias, user, password supplied the given error is fs_auth no password supplied, even though it is filled in. Remark: the password is shown in the connection box!, not starred out or anything.. Can anyone confirm this? Hth, Wim -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8), LANGUAGE=nl_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pgmodeler depends on: ii libc6 2.24-11+deb9u1 ii libgcc1 1:6.3.0-18 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libpq510.2-1.pgdg90+1 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5gui55.7.1+dfsg-3+b1 ii libqt5network55.7.1+dfsg-3+b1 ii libqt5printsupport5 5.7.1+dfsg-3+b1 ii libqt5svg55.7.1~20161021-2+b2 ii libqt5widgets55.7.1+dfsg-3+b1 ii libstdc++66.3.0-18 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 ii pgmodeler-common 0.8.2-1.pgdg90+1 pgmodeler recommends no packages. pgmodeler suggests no packages. -- no debconf information
Bug#890422: unoconv: Not using the literal filename for output
Package: unoconv Version: 0.7-1.1 Severity: normal Hallo, running unoconv -d presentation -f pdf -o /home/me/somedir/ some_file.odp creates /home/me/somedir/.pdf file in the past my scripts worked fine, creating the expected /home/me/somedir/some_file.pdf file Can anyone reproduce this? hth, Wim -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8), LANGUAGE=nl_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages unoconv depends on: ii python3 3.5.3-1 ii python3-uno 1:5.2.7-1+deb9u2 Versions of packages unoconv recommends: ii libreoffice-calc 1:5.2.7-1+deb9u2 ii libreoffice-draw 1:5.2.7-1+deb9u2 ii libreoffice-impress 1:5.2.7-1+deb9u2 ii libreoffice-writer 1:5.2.7-1+deb9u2 unoconv suggests no packages. -- no debconf information
Bug#876742: closed by Benjamin Drung <benjamin.dr...@profitbricks.com> (Re: Bug#876742: ImportError: No module named 'Redmine')
Hallo, for documentation: > from redminelib import Redmine should be > from redmine import Redmine (in the debian package) mvg, Wim Op 25-09-17 om 17:57 schreef Debian Bug Tracking System: > This is an automatic notification regarding your Bug report > which was filed against the python3-redmine package: > > #876742: ImportError: No module named 'Redmine' > > It has been closed by Benjamin Drung. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Benjamin Drung > by > replying to this email. > >
Bug#874463: dnssec-trigger: cifs mount fails
Package: dnssec-trigger Version: 0.13-6 Severity: normal Hallo, With dnssec-trigger enabled i can't mount cifs shares. Without dnssec-trigger i can mount these cifs shares. Tested and all failed: * validate_connection_provided_zones=yes and no * add_wifi_provided_zones=no and yes * adding search from standard resolv.conf to conf of dnssec-trigger.conf ** standard=without running dnssec-trigger Checked in the two setups (with and without dnssec-trigger): hostname, domainname, dnsdomainname, nisdomainname, ypdomainname are the same Possibly related: #871177 and #776778 A workaround could be to have a dnssec exception list, which are no treated by dnssec It is also possible that this an "unbound" bug (package). I hope this helps. mvg, Wim -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8), LANGUAGE=nl_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dnssec-trigger depends on: ii gir1.2-networkmanager-1.0 1.6.2-3 ii init-system-helpers1.48 ii libc6 2.24-11+deb9u1 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-0 2.50.3-2 ii libgtk2.0-02.24.31-2 ii libldns2 1.7.0-1 ii libssl1.1 1.1.0f-3 ii python 2.7.13-2 ii python-gi 3.22.0-2 ii python-lockfile1:0.12.2-2 ii unbound1.6.0-3 dnssec-trigger recommends no packages. dnssec-trigger suggests no packages. -- Configuration Files: /etc/dnssec-trigger/dnssec-trigger.conf changed: domain: "" search: "intranet.changed.domain changed.domain int.changed.domain" url: "http://ster.nlnetlabs.nl/hotspot.txt OK" url: "http://fedoraproject.org/static/hotspot.txt OK" tcp80: 185.49.140.67 tcp80: 2a04:b900::10:0:0:67 ssl443: 185.49.140.67 7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF ssl443: 2a04:b900::10:0:0:67 7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF -- no debconf information
Bug#839156: "/usr/bin/passenger-config: No such file or directory"
Hallo Antonio, Bram seems (or seemed) to have the same problem. https://lists.debian.org/debian-user/2015/07/msg00672.html mvg, Wim Antonio Terceiro schreef op do 29-09-2016 om 10:33 [-0700]: > On Thu, Sep 29, 2016 at 05:08:21PM +0200, Wim Bertels wrote: > > Package: libapache2-mod-passenger > > Version: 4.0.53-1 > > Severity: normal > > > > Hallo, > > > > after installing redmine and using passenger, > > i get the following apache error. > > " > > App 6930 stdout: > > App 6930 stderr: env: > > App 6930 stderr: /usr/bin/passenger-config: No such file or directory > > [ 2016-09-29 16:48:35.9982 6799/7fac56439700 Pool2/SmartSpawner.h:298 ]: > > Preloader for /usr/share/redmine started on PID 6930, listening on > > unix:/tmp/passenger.1.0.6792/generation-0/backends/preloader.1ah706b > > " > > > > i can't find a package in stable containing this file. > > that is probably a sign that you are mixing non-packaged stuff, in which > case you are on your own. are you sure you installed passenger from > debian? which web webserver exactly are you using? > > you need to provide way more information if you want any possibility of > someone else understanding what is going on.
Bug#839156: "/usr/bin/passenger-config: No such file or directory"
Package: libapache2-mod-passenger Version: 4.0.53-1 Severity: normal Hallo, after installing redmine and using passenger, i get the following apache error. " App 6930 stdout: App 6930 stderr: env: App 6930 stderr: /usr/bin/passenger-config: No such file or directory [ 2016-09-29 16:48:35.9982 6799/7fac56439700 Pool2/SmartSpawner.h:298 ]: Preloader for /usr/share/redmine started on PID 6930, listening on unix:/tmp/passenger.1.0.6792/generation-0/backends/preloader.1ah706b " i can't find a package in stable containing this file. They only reference is http://logs.ryanbigg.com/p/phaidros There seems to be a fix? http://projects.theforeman.org/issues/12744 There are some problems with the installation, as it is a production system, i'm not testing the patch. At this moment a can't pinpoint the cullprit, but the only error i'm getting after adapting apache 2.4 style (also before with apache 2.2) mvg, Wim -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (50, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#812747: reproducing bug: probably a epiphany bug
Hallo, i fixed this problem by removing the state files of epiphany ~/.config/epiphany$ rm session_state.xml* And then tried to reproduce the bug, i doenst always happen, but after trying 5 times the bug was there again, again after removing the state files of epiphany, the debian-reference command works fine again. So this is a epiphany bug reassign 812747 epiphany-browser -- mvg, Wim signature.asc Description: This is a digitally signed message part
Bug#808125: libreoffice-base: c/p from calc to create table, character_data does not exist on postgresql
> > Problem: > > - base takes a datatype character_data which doens't exist in postgresql, > > it should be varchar for example > > > Sounds like https://bugs.documentfoundation.org/show_bug.cgi?id=92538? > > Which suggests at least that it's definitely only PostgreSQL being affected > and that only with the "native" connection which might make it a bug of > libreoffice-sdbc-postgresql... Nice link, didn't find it, but i think its more likely to be unrelated to postgresql, but related to base (and possibly only sdbc as you say) i checked the oracle docu: there is also no character_datatype.. https://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#i3253 To continue: i tried the same setup with a local hsqldb: * there the character_data type doesn't exist and isn't even available as an option, the value here is varchar , as it should be mvg, Wim
Bug#786393: systemd: should not try to open encrypted devs that were already opened succesfully, workaround
Hallo, Debugging what happens on fresh installation with an encrypted / partition and a normaal /boot partition 1. The loaded initramfs image (which was generated with a the version of crypttab at the moment of generation, let's call it crypttab_initramfs), opens the entries in crypttab_initramfs 2. At that point / (and also /etc or /etc/crypttab) is accessible for systemd. 3. Here the problem begins: systemd tries to re-open all the entries in /etc/crypttab; this makes sense for entries that could or should not be opened by initramfs; this doesnt make sense for entries that were already opened. Systemd should not try to open entries in /etc/crypttab that already have been opened. (?a race condition because of the structure of systemd?) U can simulate this. 1. Create an encrypted system, normal /boot, encrypted /root and maybe other encrypted devs 2. Generate the initramfs to boot with (eg update-initramfs) 3. ! Then change the crypttab entries to use a keyfile from a device (passdev script) and don't update the initramfs image. 4. Reboot 5. U will get the 1m30 delay caused by a job started by systemd using the keyfile again As a workaround (on your own resposibility!), to get rid of the delay and still boot using a keyfile: just generate the initramfs image with the setup u want, and then change /etc/crypttab entries to passphrase entries For example crypttab used to generate initramfs image: crypt_root UUID=1b5 /dev/disk/by-label/ext_dev:/dir/key:10 luks,tries=1,keyscript=passdev crypt_swap UUID=8af crypt_root luks,tries=1,keyscript=decrypt_derived Then change to crypt_root UUID=1b5 none luks crypt_swap UUID=8af crypt_root luks,tries=1,keyscript=decrypt_derived and don't regenerate the initramfs image!, just reboot. hth, Wim Bertels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786393: systemd: should not try to open encrypted devs that were already opened succesfully, workaround
Hallo, The file /etc/init/cryptdisk.conf refers to a possible race condition (/lib/cryptsetup/cryptdisks.functions) # This job currently still does not guarantee a race-free startup; instances # of cryptdisks-udev may be started in parallel with this job. hth, Wim Referencing: 3. Here the problem begins: systemd tries to re-open all the entries in /etc/crypttab; this makes sense for entries that could or should not be opened by initramfs; this doesnt make sense for entries that were already opened. Systemd should not try to open entries in /etc/crypttab that already have been opened. (?a race condition because of the structure of systemd?) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786393: systemd: keyscript crypttab ignore, but booting ok with a annoying 1m30 delay
Hallo, i tried out the graphical bugreport instead of the text version, this is probably a duplicate of Bug#618862 Another note: * there is no fallback to passphrase when the device with the keyfile is not plugged in (using :timeout en tries) mvg, Wim Van: wim wim.bert...@khleuven.be Verzonden: donderdag 21 mei 2015 11:37 Aan: Debian Bug Tracking System Onderwerp: Bug#786393: systemd: keyscript crypttab ignore, but booting ok with a annoying 1m30 delay Package: systemd Version: 215-17 Severity: normal Hallo, Context, clean jessie installation: * Setting up LVM + cryptsetup boot + keyscript + systemd * 2 harddisk (slow and fast) ** 1. Booting with passphrases works fine ** 2. Booting with a single passphrase an using decrypt_derived works fine to load second lvm (although there is message that systemd doensn't understand the option that's being used, ignoring) *** 3. Now adding a keyfile to the first luks entry in crypttab instead of using a passphrase *** 4. This works with the passdev script, but starts always adds an delay of 1m30 How is this delay caused: by a job start that seems to want the use the keyfile with the syntax found in the crypttab Some notes: * Following $9. The decrypt_derived keyscript$ in /usr/share/doc/cryptsetup/README.initramfs.gz u need 'vgchange -a y' or vgchange -a n' when working with lvm * 'cryptsetup status crypt_drive' shows inactive, while drives are loaded and being used? hth, Wim -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-6 ii libc6 2.19-18 ii libcap2 1:2.24-8 ii libcap2-bin 1:2.24-8 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-17 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev215-17 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus1.8.16-1 ii libpam-systemd 215-17 Versions of packages systemd suggests: pn systemd-ui none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734516: apache2-mpm-itk: apache restart .. could not bind to address [::]:80
Package: apache2-mpm-itk Version: 2.2.22-13 Severity: normal Dear Maintainer, Context: - running apache2-mpm-itk (with php) - about 500 different vhosts (dynamically, different user space, hence mpm-itk version) and some generic apache vhosts - a cron script that does some checks, and then restart the webserver every day Log: - not much found there There are no other services running using port 80. This bug only occured (and will probably occur) a few times, so i think it has to do with the user interaction with a website. I suspect that when a user connects justs before (or while, after) restarting the webserver, the restart fails as then the port is already taken, but this is just a guess. Unfornately i cannot add addition information other than: Restarting web server: apache2 ... waiting (98)Address already in use: make_sock: could not bind to address [::]:80 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs Action 'start' failed. The Apache error log may have more information. failed! hth, Wim -- Package-specific info: List of enabled modules from 'apache2 -M': alias auth_basic authn_file authnz_ldap authz_default authz_groupfile authz_host authz_svn authz_user autoindex cgi dav dav_svn deflate dir env ldap macro mime negotiation passenger perl php5 reqtimeout rewrite setenvif ssl status List of enabled php5 extensions: curl gd ldap pdo pdo_pgsql pgsql pspell suhosin -- System Information: Debian Release: 7.3 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=nl_BE@euro, LC_CTYPE=nl_BE@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages apache2-mpm-itk depends on: ii apache2.2-bin 2.2.22-13 ii apache2.2-common 2.2.22-13 apache2-mpm-itk recommends no packages. apache2-mpm-itk suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730032: redmine: local file cvs repository doesn't load in redmine (needs /tmp/cvs2 dir)
Package: redmine Version: 1.4.4+dfsg1-2+deb7u1 Severity: normal Hallo, this is the setup: * on the server a cvs repo and redmine installed (* cvs repo needs only to be showed as a archive) IF CVSROOT in redmine is: /var/lib/cvs/cluster the module is demo THEN the webinterface of redmine can't show the project Checks done: www-data needs to be able to checkout the cvs repo, so i made sure this works locally (eg sudo -u www-data cvs -d /var/lib/cvs/cluster checkout demo) (this works after putting permissions in order) but then redmine internally needs a directory /tmp/cvs2 which doenst exist. So a patch in my opinion would be: - let www-data make the dir /tmp/cvs2 if it doesnt exist apache log: cvs [rlog aborted]: cannot stat /tmp/cvs2: No such file or directory cvs [rls aborted]: cannot stat /tmp/cvs2: No such file or directory I did not test this on other machines, so it could be just a local problem. mvg, Wim -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=nl_BE@euro, LC_CTYPE=nl_BE@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages redmine depends on: ii bundler 1.1.4-6 ii dbconfig-common 1.8.47+nmu1 ii debconf [debconf-2.0] 1.5.49 ii rails 2:2.3.14.2 ii redmine-pgsql 1.4.4+dfsg1-2+deb7u1 ii ruby 1:1.9.3 ii ruby-coderay 1.0.6-2 ii ruby-fastercsv1.5.5-1 ii ruby-net-ldap 0.3.1-2 ii ruby-rack 1.4.1-2.1 ii ruby-rails-2.32.3.14-4 ii ruby1.8 [ruby-interpreter]1.8.7.358-7 ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-8.1+deb7u1 ii rubygems 1.8.24-1 redmine recommends no packages. Versions of packages redmine suggests: pn bzr none ii cvs 2:1.12.13+real-9 pn darcs none ii git 1:1.7.10.4-1+wheezy1 pn mercurial none pn ruby-openid none ii ruby-rmagick 2.13.1-6 ii subversion1.6.17dfsg-4+deb7u4 -- debconf information: redmine/instances/default/passwords-do-not-match: redmine/instances/default/db/basepath: redmine/instances/default/pgsql/changeconf: false redmine/default-language: ${defaultLocale} redmine/instances/default/pgsql/no-empty-passwords: redmine/instances/default/pgsql/manualconf: redmine/instances/default/pgsql/authmethod-admin: ident redmine/instances/default/pgsql/admin-user: postgres redmine/instances/default/pgsql/authmethod-user: password redmine/old-instances: redmine/instances/default/upgrade-error: abort redmine/instances/default/upgrade-backup: true redmine/instances/default/mysql/admin-user: root redmine/instances/default/mysql/method: unix socket redmine/instances/default/remove-error: abort redmine/instances/default/dbconfig-remove: redmine/instances/default/remote/port: * redmine/instances/default/dbconfig-install: true redmine/instances/default/remote/newhost: redmine/instances/default/missing-db-package-error: retry redmine/instances/default/pgsql/method: unix socket * redmine/instances/default/database-type: pgsql redmine/missing-redmine-package: redmine/instances/default/dbconfig-reinstall: false redmine/instances/default/db/app-user: redmine redmine/instances/default/default-language: nl redmine/notify-migration: redmine/instances/default/db/dbname: redmine_default redmine/instances/default/purge: false redmine/current-instances: default redmine/instances/default/remote/host: redmine/instances/default/dbconfig-upgrade: true redmine/instances/default/internal/reconfiguring: false redmine/instances/default/install-error: retry redmine/instances/default/internal/skip-preseed: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728795: redmine: Gem.source_index is deprecated, use Specification (debian stable)
Package: redmine Version: 1.4.4+dfsg1-2+deb7u1 Severity: minor Dear Maintainer, Redmine was installed in wheezy, upgraded to squeeze, psql backend This is a minor report, just intended as feedback to the maintainer and possible devs: The syslog warning is: NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/redmine/vendor/rails/railties/lib/rails/gem_dependency.rb:21 this is probably? solved in newer versions of redmine, i did not check this. mvg, Wim -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=nl_BE@euro, LC_CTYPE=nl_BE@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages redmine depends on: ii bundler 1.1.4-6 ii dbconfig-common 1.8.47+nmu1 ii debconf [debconf-2.0] 1.5.49 ii rails 2:2.3.14.2 ii redmine-pgsql 1.4.4+dfsg1-2+deb7u1 ii ruby 1:1.9.3 ii ruby-coderay 1.0.6-2 ii ruby-fastercsv1.5.5-1 ii ruby-net-ldap 0.3.1-2 ii ruby-rack 1.4.1-2.1 ii ruby-rails-2.32.3.14-4 ii ruby1.8 [ruby-interpreter]1.8.7.358-7 ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-8.1+deb7u1 ii rubygems 1.8.24-1 redmine recommends no packages. Versions of packages redmine suggests: pn bzr none ii cvs 2:1.12.13+real-9 pn darcs none ii git 1:1.7.10.4-1+wheezy1 pn mercurial none pn ruby-openid none ii ruby-rmagick 2.13.1-6 ii subversion1.6.17dfsg-4+deb7u4 -- debconf information: redmine/instances/default/passwords-do-not-match: redmine/instances/default/db/basepath: redmine/instances/default/pgsql/changeconf: false redmine/default-language: ${defaultLocale} redmine/instances/default/pgsql/no-empty-passwords: redmine/instances/default/pgsql/manualconf: redmine/instances/default/pgsql/authmethod-admin: ident redmine/instances/default/pgsql/admin-user: postgres redmine/instances/default/pgsql/authmethod-user: password redmine/old-instances: redmine/instances/default/upgrade-error: abort redmine/instances/default/upgrade-backup: true redmine/instances/default/mysql/admin-user: root redmine/instances/default/mysql/method: unix socket redmine/instances/default/remove-error: abort redmine/instances/default/dbconfig-remove: redmine/instances/default/remote/port: * redmine/instances/default/dbconfig-install: true redmine/instances/default/remote/newhost: redmine/instances/default/missing-db-package-error: retry redmine/instances/default/pgsql/method: unix socket * redmine/instances/default/database-type: pgsql redmine/missing-redmine-package: redmine/instances/default/dbconfig-reinstall: false redmine/instances/default/db/app-user: redmine redmine/instances/default/default-language: nl redmine/notify-migration: redmine/instances/default/db/dbname: redmine_default redmine/instances/default/purge: false redmine/current-instances: default redmine/instances/default/remote/host: redmine/instances/default/dbconfig-upgrade: true redmine/instances/default/internal/reconfiguring: false redmine/instances/default/install-error: retry redmine/instances/default/internal/skip-preseed: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#715381: libpam-ldap: config=pam_custom_ldap.conf does not use pam_custom_ldap.secret file
Package: libpam-ldap Version: 184-8.6 Severity: normal Dear Maintainer, after upgrading from squeeze to wheezy, pam_ldap behaviour changed. in the squeeze setup the pam file for pure-ftpd contained: auth sufficient pam_ldap.so config=/etc/pam_ldap_pureftpd.conf auth required pam_deny.so account sufficient pam_ldap.so config=/etc/pam_ldap_pureftpd.conf account required pam_deny.so session optional pam_ldap.so config=/etc/pam_ldap_pureftpd.conf and also a pam_ldap_pureftdp.secret existed after the upgrade to wheezy, a pam_ldap.secret is needed, which i did not have before; hence it is more difficult (how?) to use different ldap servers for different services and it feels consistent with this pam setup error messages: .. pure-ftpd: pam_ldap: could not open secret file /etc/pam ldap.secret (No such file or directory) Jul 8 14:55:11 pure-ftpd: pam_ldap: ldap_search_s Operations error.. so a link (pam_ldap.secret) to pam_ldap_pureftpd.secret fixed it, but cf comments supra hth, Wim -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=nl_BE@euro, LC_CTYPE=nl_BE@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages libpam-ldap depends on: ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38 ii libldap-2.4-2 2.4.31-1+nmu2 ii libpam-runtime 1.1.3-7.1 ii libpam0g 1.1.3-7.1 libpam-ldap recommends no packages. Versions of packages libpam-ldap suggests: ii libnss-ldap 264-2.5 -- debconf information man added * shared/ldapns/base-dn: dc=intranet,dc=somedomain,dc=org * libpam-ldap/dbrootlogin: false * libpam-ldap/override: true * shared/ldapns/ldap-server: ldaps://ad.someworkingldapadserver.org:636 libpam-ldap/pam_password: crypt libpam-ldap/binddn: cn=proxyuser,dc=example,dc=net libpam-ldap/rootbinddn: cn=manager,dc=example,dc=net * shared/ldapns/ldap_version: 3 * libpam-ldap/dblogin: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705533: redmine: html escape? problem in the administration/settings dialog, projects and repositories tab
Could you upgrade to wheezy now? :) This bug persists in oldstable (squeeze), but doesnt seem be present in the current stable branch (squeeze); so it can be fixed #705533 redmine/1.4.4+dfsg1-2 mvg, Wim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705533: redmine: html escape? problem in the administration/settings dialog, projects and repositories tab
check: a downgrade of the following packages to squeeze7 (stable has squeeze8) fixed the problem: libactionmailer-ruby1.8_2.3.5-1.2+squeeze7_all.deb .. libactivesupport-ruby_2.3.5-1.2+squeeze7_all.deb So indeed the problem persists in the upgrade to latest stable packages. So if if u need a quick patch: # get files $ wget -r -l1 --no-parent -A.deb http://snapshot.debian.org/archive/debian-security/20130212T211154Z/pool/updates/main/r/rails/ # then cd to dir where deb files just downloaded are # install files $ ls *squeeze7* | xargs dpkg -i # logout of redmine # restart apache # everything should be fine now, security? after checking the differences between squeeze7 and 8: unfortunately the security update http://www.debian.org/security/2013/dsa-2655 fixes a lot a problems, downgrading to squeeze7 is not safe. other suggestions for a better solution? mvg, Wim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705533: redmine: html escape? problem in the administration/settings dialog, projects and repositories tab
On Tue, 2013-04-16 at 12:03 +0200, Ondřej Surý wrote: Could it be the same as #705466? Can you check if the patch attached to #705466 fix your problem? I checked this patch, doesn't work for this problem. the behaviour stays the same. mvg, Wim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705533: redmine: html escape? problem in the administration/settings dialog, projects and repositories tab
Package: redmine Version: 1.0.1-2 Severity: normal Tags: upstream problem occured after safe-upgrade As an administrator for redmine, u can use the webinterface for the administration/settings dialog. In this dialog the projects and repositories tab have a a problem with listing checkboxes rendering them useless, it is impossible to use them, so u cannot choose a scm or set the default project settings anymore (workaround for the advanced, directly edit the redmine database, settings table) an example: this the html that is shown: Enabled SCMlabel class=blockinput checked=checked id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Subversion /Subversion/labellabel class=blockinput id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Darcs /Darcs/labellabel class=blockinput id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Mercurial /Mercurial/labellabel class=blockinput id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Cvs /Cvs/labellabel class=blockinput id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Bazaar /Bazaar/labellabel class=blockinput id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Git /Git/labellabel class=blockinput id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Filesystem /Filesystem/label where one would expect the actual check boxes to be chown, the html source code on this page for this is: plabelEnabled SCM/labelinput id=settings_enabled_scm_ name=settings[enabled_scm][] value= type=hiddenlt; label class=blockgt;lt;input checked=checked id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Subversion /gt; Subversionlt;/labelgt;lt;label class=blockgt;lt;input id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Darcs /gt;Darcslt;/labelgt;lt; label class=blockgt;lt;input id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Mercurial /gt;Mercuriallt;/labelgt;lt; label class=blockgt;lt;input id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Cvs /gt;Cvslt;/labelgt;lt;label class=blockgt;lt; input id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Bazaar /gt;Bazaarlt;/labelgt;lt;label class=blockgt;lt; input id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Git /gt;Gitlt;/labelgt;lt;label class=blockgt;lt; input id=settings_enabled_scm_ name=settings[enabled_scm][] type=checkbox value=Filesystem /gt;Filesystemlt;/labelgt;/p so the code that is shown to the user should be the html source code possible causes: unlike utf8, sql_ascii encoding database, i already tested this with different encodings, no change most likely: ruby related packages upgrade, i could recreate the problem i a virtual environment, the problem occurs right after the upgrade upgraded packages: acpid apache2 apache2-mpm-prefork apache2-suexec apache2-utils apache2.2-bin apache2.2-common at base-files bind9-host bogofilter bogofilter-bdb bogofilter-common browser-plugin-gnash bzip2 cpufrequtils cups cups-bsd cups-client cups-common cups-pk-helper cups-ppdc cvs dbus dbus-x11 debian-archive-keyring dnsutils dpkg dpkg-dev evince evince-common evolution-data-server evolution-data-server-common exim4 exim4-base exim4-config exim4-daemon-heavy file foomatic-filters fusionforge-standard gforge-common gforge-db-postgresql gforge-lists-mailman gforge-mta-exim4 gforge-plugin-scmcvs gforge-plugin-scmgit gforge-plugin-scmsvn gforge-shell-postgresql gforge-web-apache2 ghostscript ghostscript-cups gimp gimp-data gir1.0-json-glib-1.0 gnash gnash-common gnupg gpgv gzip host hpijs hplip hplip-cups hplip-data iceweasel imagemagick initscripts isc-dhcp-client isc-dhcp-common libactionmailer-ruby libactionmailer-ruby1.8 libactionpack-ruby libactionpack-ruby1.8 libactiverecord-ruby1.8 libactiveresource-ruby libactiveresource-ruby1.8 libactivesupport-ruby libactivesupport-ruby1.8 libapache2-mod-fcgid libapache2-mod-perl2 libapache2-mod-php5 libapr1 libarchive1 libavcodec52 libavformat52 libavutil49 libbind9-60 libbrlapi0.5 libbz2-1.0 libc-bin libc-dev-bin libc6 libc6-dev libc6-i686 libcamel1.2-14 libconfig-inifiles-perl libcpufreq0 libcups2 libcupscgi1 libcupsdriver1 libcupsimage2 libcupsmime1 libcupsppdc1 libcurl3-gnutls libdbd-pg-perl libdbus-1-3 libdbus-glib-1-2 libdns69 libdpkg-perl libebackend1.2-0 libebook1.2-9 libecal1.2-7 libedata-book1.2-2 libedata-cal1.2-7 libedataserver1.2-13 libedataserverui1.2-8 libegroupwise1.2-13 libevince2 libexif12 libexpat1 libfreetype6 libgc1c2 libgdata-common libgdata-google1.2-1 libgdata1.2-1 libgdata7 libgimp2.0 libgnutls26 libgs8 libgssapi-krb5-2 libgssrpc4 libhpmud0 libicu44 libisc62 libisccc60 libisccfg62 libjasper1 libjson-glib-1.0-0 libk5crypto3 libkadm5clnt-mit7 libkadm5srv-mit7
Bug#705533: redmine: html escape? problem in the administration/settings dialog, projects and repositories tab
On Tue, 2013-04-16 at 11:34 +0200, Jérémy Lal wrote: On 16/04/2013 11:19, Wim Bertels wrote: Package: redmine Version: 1.0.1-2 Severity: normal Tags: upstream problem occured after safe-upgrade As an administrator for redmine, u can use the webinterface for the administration/settings dialog. In this dialog the projects and repositories tab have a a problem with listing checkboxes rendering them useless, it is impossible to use them, so u cannot choose a scm or set the default project settings anymore (workaround for the advanced, directly edit the redmine database, settings table) Can you downgrade rails security updates from 2.3.5-1.2+squeeze8 to 2.3.5-1.2+squeeze7, then 2.3.5-1.2+squeeze6, etc... until you find at which version it works again ? There is a good chance the culprit is the latest rails security update, since nobody reported that bug before and 2.3.5-1.2+squeeze8 was made available this month. check: a downgrade of the following packages to squeeze7 (stable has squeeze8) fixed the problem: libactionmailer-ruby1.8_2.3.5-1.2+squeeze7_all.deb libactiverecord-ruby1.8_2.3.5-1.2+squeeze7_all.deb libactiveresource-ruby_2.3.5-1.2+squeeze7_all.deb rails_2.3.5-1.2+squeeze7_all.deb libactionmailer-ruby_2.3.5-1.2+squeeze7_all.deb libactiverecord-ruby1.9.1_2.3.5-1.2+squeeze7_all.deb libactivesupport-ruby1.8_2.3.5-1.2+squeeze7_all.deb rails-doc_2.3.5-1.2 +squeeze7_all.deb libactionpack-ruby1.8_2.3.5-1.2+squeeze7_all.deb libactiverecord-ruby_2.3.5-1.2+squeeze7_all.deb libactivesupport-ruby1.9.1_2.3.5-1.2+squeeze7_all.deb rails-ruby1.8_2.3.5-1.2+squeeze7_all.deb libactionpack-ruby_2.3.5-1.2+squeeze7_all.deb libactiveresource-ruby1.8_2.3.5-1.2+squeeze7_all.deb libactivesupport-ruby_2.3.5-1.2+squeeze7_all.deb So indeed the problem persists in the upgrade to latest stable packages. So if if u need a quick patch: # get files $ wget -r -l1 --no-parent -A.deb http://snapshot.debian.org/archive/debian-security/20130212T211154Z/pool/updates/main/r/rails/ # then cd to dir where deb files just downloaded are # install files $ ls *squeeze7* | xargs dpkg -i # logout of redmine # restart apache # everything should be fine now, security? have to plant some flowers now, Wim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705533: redmine: html escape? problem in the administration/settings dialog, projects and repositories tab
On Tue, 2013-04-16 at 12:03 +0200, Ondřej Surý wrote: Could it be the same as #705466? Can you check if the patch attached to #705466 fix your problem? it's not necessarily the same bug (but could be related, since the output behaviour is similar): cf#705466= The problem is, that an option list rendered by add_options with an initial empty option leads to escaped option tags. (backports redmine) in this case (#705533) - The initial doens't have to be empty, the problem occurs right after the upgrade. - it's a stable debian with redmine installed out of the stable repository mvg, Wim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org