Bug#749695: [Pkg-xfce-devel] Bug#749695: xfce4: Password required for shutdown

2014-05-31 Thread Robert Gomulka
-sysv (No, I haven't proceed further) (I provide this info inspired by your question about init - discard it if unrelated) Regards, Robert On 31 May 2014 16:11, Yves-Alexis Perez cor...@debian.org wrote: On jeu., 2014-05-29 at 10:19 +0200, Robert Gomulka wrote: Package: xfce4 Version

Bug#749695: [Pkg-xfce-devel] Bug#749695: xfce4: Password required for shutdown

2014-05-31 Thread Robert Gomulka
-systemd:i386 (204-7, 204-10), libsystemd-journal 0:i386 (204-7, 204-10) Remove: sysvinit-core:i386 (2.88dsf-51) End-Date: 2014-05-31 20:55:27 things started working and the bug is no longer present. Regards, Robert On 31 May 2014 20:50, Robert Gomulka r.gom1...@gmail.com wrote: Thank you for your

Bug#749695: [Pkg-xfce-devel] Bug#749695: xfce4: Password required for shutdown

2014-05-31 Thread Robert Gomulka
/systemd Regards, Robert On 31 May 2014 21:10, Robert Gomulka r.gom1...@gmail.com wrote: Quick update. After upgrading systemd: Start-Date: 2014-05-31 20:54:43 Commandline: apt -t unstable install systemd Install: systemd-sysv:i386 (204-10, automatic) Upgrade: libsystemd-daemon0:i386 (204-7

Bug#749695: xfce4: Password required for shutdown

2014-05-29 Thread Robert Gomulka
Package: xfce4 Version: 4.10.1 Severity: normal Dear Maintainer, recently (few days ago, after another dist-upgrade) I've discovered that I'm required to enter my password to perform shutdown, which I find extremely annoying and useless. I don't know if this is the correct package, reassign if

Bug#679693: linux: 3.2.0-2 - 3.2.0-3 upgrade resulted in unbootable system

2012-07-04 Thread Robert Gomulka
On 4 July 2012 18:51, Jonathan Nieder jrnie...@gmail.com wrote: Hi again, Robert Gomulka wrote: I've upgraded from 3.2.0-2 to 3.2.0-3. That wasn't the only upgrade, [...] After the upgrade system stopped booting. Right after trying to display Grub boot menu, system was rebooting

Bug#679693: How to debug

2012-07-02 Thread Robert Gomulka
I'd like to help with this issue, but don't know how. I'd like to avoid bisecting grub config, as it's my production machine and it could be time-consuming. Is there a way to have any grub logs? Maybe it's a grub issue, which manifested itself after kernel upgrade? Regards, Robert -- To

Bug#440495: xserver-xorg-input-synaptics: Keyboard doesn't work after turning touchpad off and on

2011-01-01 Thread Robert Gomulka
[cut] Hi all, For me the issue is to some extent still present. While I can't reproduce keyboard stealing (well, for the short period of time, like in Ove's description) and help popup is not coming up, the three sub-issues are present. While switching input back on: 1. There's temporary freeze

Bug#511322: libkcal2b: Wrong Polish working days

2009-01-09 Thread Robert Gomulka
Package: libkcal2b Version: 4:3.5.9-5 Severity: normal Tags: l10n *** Please type your report below this line *** When looking at korganizer calendar I have found that some bank holiday dates are reported incorrectly. I have found this page: http://pim.kde.org/components/korganizer/holidays.php

Bug#511322: Patch

2009-01-09 Thread Robert Gomulka
This patch should fix the problem. --- holiday_pl 2005-09-10 10:24:19.0 +0200 +++ /tmp/holiday_pl 2009-01-09 15:24:33.0 +0100 @@ -3,29 +3,29 @@ : by Krzysztof P. Jasiutowicz kp...@promail.pl : -small Nowy Rok on 1.1. -small Trzech Króli weekend

Bug#472406: Workaround

2008-05-20 Thread Robert Gomulka
Please try to execute: $ cd /usr $ widelands In my case it helped. How? I have run strace and grepped for locale string: $ strace -o /tmp/widelands.txt widelands $ grep locale widelands.txt open(/home/user/share/games/widelands/locale/pl_PL/LC_MESSAGES/widelands.mo, O_RDONLY) = -1 ENOENT (No

Bug#479742: kbabel: Very long window refreshing on long files

2008-05-06 Thread Robert Gomulka
Package: kbabel Version: 4:3.5.9-1 Severity: normal When changing virtual desktops in KDE and going back to KBabel's one it takes reasonable amount of time (a few seconds, e.g 10s) to redraw KBabel window, during which KBabel is just frozen. Steps to reproduce: 1. Run KBabel 2. Open a .po file 3.

Bug#476217: libqt4-core: PSI crashes after qt upgrade

2008-04-15 Thread Robert Gomulka
Package: libqt4-core Version: 4.4.0~rc1-3 Severity: normal *** Please type your report below this line *** After last qt4 upgrade with psi (0.11-3 to 0.11-6) PSI started crashing. Reverting to 0.11-3 did not help. It crashes often, randomly. I have recorded backtrace, which suggested me it may be

Bug#469332: Possible dependency problem

2008-04-06 Thread Robert Gomulka
After installing the following packages reportbug-ng starts fine: python-sip4 python-dev python-sip4-dev python2.4-dev sip4 I'm not sure which exact package fixed this problem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#445078: More info

2008-03-17 Thread Robert Gomulka
Ok, what I have discovered so far: - when I put laptop_mode force invocation to Xstartup: #! /bin/sh # Xstartup - run as root before session starts DPMS settings are not applied, because who command, used in script, gives no results (log previously attached) - when I put sudo laptop_mode force

Bug#445078: Additional information

2008-03-15 Thread Robert Gomulka
Hello, Finally I have managed to collect more data, which may be helpful to track down the problem. For the debugging purposes I have modified laptop_mode script to log all messages to file instead of standard output. Then I added /usr/sbin/laptop_mode force invocation to /etc/kde3/kdm/Xstartup

Bug#445078: Additional info - log

2008-03-15 Thread Robert Gomulka
I had no time to check it this time - I assume it contains correct information. Please let me know if it works for you. Regards, Robert verbose1.txt.bz2 Description: BZip2 compressed data

Bug#445078: laptop-mode-tools: No DPMS settings applied on startup

2007-10-09 Thread Robert Gomulka
2007/10/9, Bart Samwel [EMAIL PROTECTED]: Hi Robert, Thanks for reporting. A problem similar to this is documented in the laptop-mode.conf(8) manual page, in the section about CONTROL_DPMS_STANDBY. It's not so easy to control the DPMS settings for a not-logged-in terminal, but at least you

Bug#445723: wlassistant: network not working because routing is not set

2007-10-07 Thread Robert Gomulka
Package: wlassistant Version: 0.5.7-2 Severity: normal First - steps to reproduce: $ sudo wlassistant Loaded application options. All interfaces: eth0, wlan0 Wireless interface(s): wlan0 Permissions checked. DHCP Client: dhclient All executables found. scan: /sbin/iwlist wlan0 scan Networks

Bug#445078: laptop-mode-tools: No DPMS settings applied on startup

2007-10-02 Thread Robert Gomulka
Package: laptop-mode-tools Version: 1.34-1 Severity: normal DPMS settings are not applied on system startup. Reproducible: always Steps to reproduce: 1. Disconnect power on turned off laptop. 2. Turn on laptop. 3. Check `xset q` output. In my case it was: $ xset q Keyboard Control: auto repeat:

Bug#444810: uswsusp: s2both does not do s2ram

2007-10-01 Thread Robert Gomulka
Package: uswsusp Version: 0.7-1 Severity: normal My s2disk works perfectly. My s2both works exactly in the same way as s2disk, shutting down computer after creating image. My s2ram doesn't work without -f switch: $ sudo s2ram Machine is unknown. This machine can be identified by: sys_vendor

Bug#443953: kdebase: autostart order unreliable

2007-09-28 Thread Robert Gomulka
What I have discovered so far. I have added debugs to xmms-xf86audio, to functions registering keys: if ((sym = XStringToKeysym(keystring)) == NoSymbol) { g_warning(_(XStringToKeysym returned NoSymbol for %s), keystring); return 0; } if

Bug#443938: wlassistant: Crash when some options set

2007-09-26 Thread Robert Gomulka
It occured only the first time when I changed the options. Problematic option was group networks with the same name. When I removed it from config file, it started. When I re-added, it crashed again upon startup. However, it seems that the problem vanished after reboot - I can't reproduce it even

Bug#443953: kdebase: autostart order unreliable

2007-09-25 Thread Robert Gomulka
You could try using the KDE environment extender mechanism instead. For this you create a file with .sh extension and put it into .kde/env/ It will be read (sourced) by the KDE startup script startkde. It might also work with a different autostart phase, see /usr/share/autostart for

Bug#443953: kdebase: autostart order unreliable

2007-09-25 Thread Robert Gomulka
Update: my xmodmap.sh from .kde/env is being called during startup (verified with debugs). But still then after logging in my modifier map looks as not modified. Executing script for the second time makes things work. I have no idea why. Other application modifying keys? KDE itself? Regards,

Bug#443938: wlassistant: Crash when some options set

2007-09-24 Thread Robert Gomulka
Package: wlassistant Version: 0.5.7-2 Severity: normal I use wlassistant successfully. Today I've selected two new options (after connecting to a network): 1. group networks with the same name 2. automatically reconnect when disconnected Then I quit wlassistant and tried to start it again. After

Bug#443953: kdebase: autostart order unreliable

2007-09-24 Thread Robert Gomulka
Package: kdebase Version: 4:3.5.7-2 Severity: normal I use xmms for playing music. I also use xmodmap for registering multimedia keys for my laptop. xmms is started by automatic session restore, while for xmms I put desktop file in .kde/Autostart: $ cat .kde/Autostart/xmodmap.desktop [Desktop

Bug#443755: wlassistant: Fake fail when connecting

2007-09-23 Thread Robert Gomulka
Package: wlassistant Version: 0.5.7-2 Severity: normal Currently I use wlassistant to connect to my hotel's wireless network. It reports fail when everything is fine. Steps to reproduce: 1. modprobe ndiswrapper (I insert my card driver) 2. start wlassistant 3. list of detected networks appear. I

Bug#440495: xserver-xorg-input-synaptics: Keyboard steal after stopping touchpad

2007-09-02 Thread Robert Gomulka
2007/9/2, Mattia Dongili [EMAIL PROTECTED]: Hi Peter, one more bugreport that's now hitting a couple of people. I'm really sorry but again I'm lacking the necessary time to properly investigate... On Sat, Sep 01, 2007 at 07:47:04PM -0600, Robert Gomulka wrote: Package: xserver-xorg-input

Bug#440495: xserver-xorg-input-synaptics: Keyboard steal after stopping touchpad

2007-09-01 Thread Robert Gomulka
Package: xserver-xorg-input-synaptics Version: 0.14.7~git20070517-2 Severity: normal *** Please type your report below this line *** Hardware: Compaq Presario F500 Reproducible: very often Steps to reproduce: 1. Turn touchpad off below keyboard 2. Turn it on again 3. Repeat 1-2 if needed

Bug#426171: Confirmation

2007-08-28 Thread Robert Gomulka
Hello, I would like to confirm this problem on my Compaq Presario F572US. It may be the same as in: http://lkml.org/lkml/2007/6/3/138 I can reproduce it with 2.6.22 Debian kernel: ii linux-image-2.6.22-1-amd64 2.6.22-3 Linux 2.6.22 image on AMD64 and ii util-linux

Bug#419789: digikam: Crash on exit

2007-04-17 Thread Robert Gomulka
Package: digikam Version: 2:0.9.1-2 Severity: normal It happened once, when I finished my work with Digikam and wanted to exit (I don't remember if it was a menu entry or window close), it crashed. Callstack follows: (no debugging symbols found) Using host libthread_db library