prompt
ioncore.get_hook(tiling_placement_alt):add(function(tbl) return false end)
- open a new window (eg. F2)
My idea was that returning false from the handler should behave as if
the handler was not there.
regards, ingo
here follows the backtrace:
obj_cast (obj=0xc, descr=0x8081a28) at obj.c
://bugs.debian.org/458149 .
Anyway, this is not a sane way of failing on a bad rules files.
ingo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
causes a variety of followup failures on boot) .
This happens also for other rules that place devices in subdirectories
(eg. /dev/input/mice).
Everything went fine until a recent upgrade but unfortunately
i am not able to determine what exactly caused the breakage.
regards, ingo
-- output of some
for a while and eventually crash
The backtrace looks certainly wrong.
If anyone anyone can point out how to do better
(or how to use gdb to debug x on a single machine)
i would be willing to help.
regards, ingo
Backtrace:
0: X(xf86SigHandler+0x7e) [0x80c632e]
1: [0xb7fa7420]
2: /usr/lib/libpixman
On Tue, Sep 18, 2007 at 03:41:37PM +0200, ingo wrote:
Package: xserver-xorg
Version: 1:7.3+2
Severity: important
since upgrading to 7.3 i got crashes of the xserver with the folling
backtrace.
- happen with VESA and ATI (below is the stripped down vesa
configuration)
- xdm runs fine
On Tue, Sep 18, 2007 at 05:24:33PM +0200, Steinar H. Gunderson wrote:
On Tue, Sep 18, 2007 at 04:53:56PM +0200, ingo wrote:
the switch to the new configuration format is mentioned in NEWS.Debian. I
don't know a better place to write such information. If you have a
suggestion, please let
)
?xml version=1.0 encoding=UTF-8?
pam_mount
volume
user=ingo
path=/home/ingo:crypt.img
mountpoint=/home/ingo/crypt
fstype=crypt
options=fsck,nodev,loop,nosuid
fskeycipher
recompiled libpixman with gcc 4.1 as suggested by other
and this just works fine.
regards, ingo
sudo apt-get build-dep libpixman-1-0
apt-get source libpixman-1-0
cd pixman-0.9.5
export CC=gcc-4.1
dpkg-buildpackage -us -uc -b -rfakeroot
sudo dpkg -i ../libpixman-1-0_0.9.5-1_i386.deb
Package: libpam-mount
Version: 0.21-3
Severity: normal
hi,
depending on what is debian policy, this should either be done
automatically, or stated in NEWS.Debian.
regards, ingo
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1
Package: libpam-mount
Version: 0.21-3
Severity: normal
should be .pam_mount.conf.xml i suppose.
regards, ingo
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.22.5
Locale
this (some time ago)
it was not possible to distinguish between
- username wrong
- password wrong
- username and password wrong
Regards, ingo
Here a screen dump of a successful and a failed attempt:
Ctrl-Alt-Delete for system halt
Linux 2.6.22.5 (tty2)
noo login: ingo
:607) waiting for umount
pam_mount(pam_mount.c:620) unmount of failed
pam_mount(pam_mount.c:617) going to unmount
pam_mount(mount.c:1049) getpwnam(ingo) failed: Success
The source of this does not seem to be libpam-mount itself,
but rather some other upgraded package
Package: libpam-mount
Version: 0.20-1
Severity: normal
Hi,
when using the convert_pam_mount_conf.pl utility to convert my user
configuration in ~/.pam_mount.conf to ~/.pam_mount.conf.xml
volume ingo crypt - /home/ingo:crypt.img /home/ingo/crypt
fsck,nodev,loop,nosuid - -
the empty
the xml based configuration.
After having converted my user configuration everything worked fine again.
Maybe a notice somewhere about convert_pam_mount_conf.pl will make
life easier for the less curious :)
Best, Ingo
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT
Package: libpam-mount
Version: 0.20-1
Severity: normal
Hi,
when attempting to use the convert_pam_mount_conf.pl utility to convert my user
configuration in ~/.pam_mount.conf to ~/.pam_mount.conf.xml
volume ingo crypt - /home/ingo:crypt.img /home/ingo/crypt
fsck,nodev,loop,nosuid
Package: libpam-mount
Version: 0.18-6
Severity: normal
Hi,
i have a luks encrypted file /home/ingo:crypt.img mounted on
/home/ingo/crypt with the following line in my .pam_mount.conf
volume ingo crypt - /home/ingo:crypt.img /home/ingo/crypt
fsck,nodev,loop,nosuid - -
but with the default
hi, bastian,
On Wed, Aug 29, 2007 at 02:44:25PM +0200, Bastian Kleineidam wrote:
Am Sonntag, 26. August 2007 19:23:19 schrieb ingo:
What seems to happen in the former case is that 'mount' creates a first
loop device and only after that passes this loop device to mount.crypt
which creates
:586) received order to close things
pam_mount(misc.c:55) Session close: (uid=1000, euid=1000, gid=1000,
egid=1000)
pam_mount(misc.c:284) command: /usr/sbin/pmvarrun [-u] [ingo] [-o] [-1]
pam_mount(misc.c:55) set_myuidpre: (uid=1000, euid=1000, gid=1000,
egid=1000
On Sat, Sep 29, 2007 at 03:38:11PM +0200, Bastian Kleineidam wrote:
Am Freitag, 28. September 2007 14:24:39 schrieb ingo:
when logging in as root and then su-ing to a user account everything works
fine. But at logout the su-command seems to have dropped root privileges,
Yep, pam_mount
Unbelievable but true, a recent update of a single package in Etch (I cannot
recall which) appears to have fixed all problems.
I have commented out the ehci_hcd from my /etc/modules/blacklist file and here
is my latest dmesg:
usb 3-1: new high speed USB device using ehci_hcd and address 2
usb
Here is a link for the Ubuntu bug
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746
Attached is also the result of lshw for my system (in case it helps).
dicker
description: Computer
width: 32 bits
*-core
description: Motherboard
physical id: 0
Package: zsh
Version: 4.3.3-1
Severity: normal
Tags: patch
hi,
when compiling the function in /usr/share/zsh/4.3.3/functions/Misc
add-zsh-hook fails. the attached patch fixes this
regards,
ingo
--- /usr/share/zsh/4.3.3/functions/Misc/add-zsh-hook.orig 2007-04-20
13:38:46.0 +0200
Got the same error:
# lvextend -L +16.8G -r -v /dev/smvg/movies
Finding volume group smvg
Rounding up size to full physical extent 16.80 GB
Executing: fsadm check /dev/smvg/movies (null)
fsadm: execlp failed: No such file or directory
fsadm failed: 2
Even without using the -r
Package: sagemath
Version: 3.0.5dfsg-1
Followup-For: Bug #513853
Had the same problem and it went away after installing libsingular-dev.
If /usr/lib/libsingular.so from that package is moved away, the crash reappears.
Regards, ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
Package: sagemath
Version: 3.0.5dfsg-1
Followup-For: Bug #513853
oops, please ignore that subject line of the previous message.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
session excerpt).
Unfortunately, i can not remember which package update started this.
Thanks,
Ingo
gdb session excerpt (empty lines added for readablility):
Breakpoint 6, 0xb7c94ca6 in xcb_get_wm_hints_from_reply () from
/usr/lib/libxcb-icccm.so.1
(gdb) bt
#0
suppose that hardcoding is not really necessary anyway as 'pcsp'
should be included when all cards are looped over (which is the case
when running from init. And giving a specific card on the command line
one would not expect this to operate on a different card.
regards, ingo
-- System Information
pcsp
which was not always present, but at least in the most
recent alsa-utils packages is.
Regards, Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Sun, Jun 14, 2009 at 06:59:53PM +0200, Elimar Riesebieter wrote:
Everything hinges on the line /etc/init.d/alsa-utils:175
mute_and_zero_levels_on_card pcsp
What happens if you remove this line?
Everythings seems fine with this line commented out.
Regards, ingo
updated the kernel to 3.4.4-1 from
experimental ...
Meanwhile the author has updated to kernel 3.5.5-1-amd64 and all appears
still fine.
Just my 2 cents,
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
I am back and join the injured.
today I again had the known freeze after 3 weeks of freedom with 256MB
GPU-RAM BIOS setting. So my remedy did not cure the root cause. I now
installed kernel 3.5.5-1 from experimental - let's see.
--
To UNSUBSCRIBE, email to
to 'modinfo i915'
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am 03.11.2012 22:11, schrieb Jonathan Nieder:
Jonathan Nieder wrote:
Hi Ingo,
[...]
There seem to be some differences in symptoms here, so please file a
separate bug. We can merge them later if they turn out to have the
same cause.
I've assigned you bug#692234.
Many thanks
Please
Am 04.11.2012 08:46, schrieb Jonathan Nieder:
Ingo wrote:
-- Package-specific info:
[...]
Thanks much.
BOOT_IMAGE=/vmlinuz root=/dev/sda2 ro i915_enable_rc6=0 drm.debug=0x2
There's a spelling mistake here: the kernel parameter disabling
rc6 should be spelled i915.i915_enable_rc6=0
I am currently running kernel 3.2.32-1 from Sid and intend to run till I
get freezes.
That happened already 1 hour ago. I was watching a HTML5 video on
YouTube when machine froze totally, even SysRq doesn't work. Sound was
looping the last fraction of a second endlessly. Power consumtion up at
as
/devices/pci:00/:00:1b.0/sound/card0/input13
input: HDA Intel PCH Line Out Front as
/devices/pci:00/:00:1b.0/sound/card0/input14
I'll report as soon as I get any freeze,
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
Am 07.11.2012 22:53, schrieb intrigeri:
Hi Laurent,
Ingo Steiner wrote (05 Jul 2012 14:09:46 GMT) :
When booted via systemd I am unable to launch applications requiring
authentication, like synaptic from the desktop.
Ingo Steiner wrote (06 Jul 2012 16:30:36 GMT) :
After today's (July 6
without proper fan
regulation.
Regards,
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
GB Video Memory with 4 GB and above system memory
configuration
So these 1.7GB probably exceeds what the driver (or PAT) is capable?
Regards,
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
.
Probably it ist worth to try this kernel parameter with Wheezy's
standard kernel:
enable_mtrr_cleanup
to allow kernel to re-arrange them and see if it has any influence in
your case?
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
(in case the motherboard offeres
it), while mine i5-3570K does not support VT-d (like all K-CPU's).
Worth to try to switch off VT-d in the BIOS, Per?
Ingo
P.S.: I am still assuming that Per's and mine obeservations have the
same root cause: some mismatch of I/O-memory areas caused by whatever,
BIOS-bug
Am 21.10.2012 14:20, schrieb Per Foreby:
[22.177] (II) VESA(0): Total Memory: 1023 64KB banks (65472kB)
[22.200] (II) VESA(0): VESA VBE Total Mem: 65472 kB
Note that this is 1023 memory banks, not 1024, so it's not exactly 64 MB
(65536 kB). Maybe the reason why it almost works with
Problems still persist in xfce4-sensors-plugin (version 1.2.5-1+b1) in
Wheezy, maybe showing up in a different way.
For some reason package 'hddtemp' is installed automatically, despite I
do not need it. My PC does not have any rotational HD, just an Intel
520series SSD which does not contain any
Am 08.11.2012 16:55, schrieb Jonathan Nieder:
Ingo wrote:
I have now been running kernel 3.3.0-rc6-amd64 for 4 days. I did even
try with different BIOS settings for IGD DVMT Memory especially with
Maximum DVMT which according to the manual corresponds to 1.7GB. With
this configuration I
Some additional information, probably it helps:
As stated above, when system freezes power consumption rises by some 30
watts. I now checked under normal operating conditions and it turns out
that this value is precisely the same when 2 cores (out of 4) run under
full load (checked with
/dev/null 21 to the command line.
/Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: lxde
Version: 4+nmu1
Severity: normal
I did install Wheezy from netinstall-image, choosing LXDE as desktop
environment. All went fine until yesterday:
A security-update (kernel) was available, but there was no notification
on the desktop. This is working under Gnome3 and XFCE (which
Addition:
Package update-notifier cannot be installed directly with apt-get,
instead you have to:
'apt-get install update-notifier-core'
which also pulls in python-vte and update-manager-gnome.
This adds the essential configuration file
/etc/apt/apt.conf.d/10periodic and 99update-notifier.
--
package /update-notifier-common is also required.
This supplies the configuration for /etc/apt/apt.conf.d/.
/
I can confirm this bug here too and found a temporarly workaround.
Ivy-Bridge i5-3570K on Intel DH77EB MoBo (H77 chipset), latest BIOS
EB0089.BIO.
These freezes happend most of the time when hitting a link in Iceweasel.
They are so severe that even the MoBo reset button does not respond
But since then I have never obseved any cras/freeze for days now.
Keeping my fingers crossed for the same outcome.
/Per
Still ok here - good luck.
Me came up another thing which probably relates to that. As far as I
could extract from internet searches regarding this issue, I concluded:
by the i915 module.
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
setups (/proc/mtrr) are still identical with both
kernels. Seems the write-combining area has become obsolete - or
still not implemented in i915?
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
it be that in the
Debian-kernel either the hangs are not detected securely, or that it
just fails to reset the module?
/Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
@ colliar
I just checked with your syslog and found that system has resumed from
hibernate just a few minutes before the crash happened.
I did see also random cashes/freezes in Wheezy when system was suspended
before (s2ram). Since I no longer use suspend all the troubles have gone
away.
I must
Am 26.01.2013 19:06, schrieb Debian Bug Tracking System:
Processing commands for cont...@bugs.debian.org:
severity 689268 important
Bug #689268 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge)
graphics freeze
Bug #692234 [src:linux] Intel DH77EB (H77): sporadic freeze and
.
/Ingo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlEFDI8ACgkQx2YcFfrwLxMAUACfQ/9YomlVoJk1V1+YBfrMo+Op
AckAnA1XiU/xGlRnoT+LV3cGhOtpK6XV
=I+mX
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email
/dkms/virtualbox/4.1.18/build] Fehler 2
make[1]: *** [sub-make] Fehler 2
make: *** [all] Fehler 2
make: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64'
I am back on kernel 3.2.39-2 and all works as expected.
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
I checked the package from
http://ftp.debian.org/debian/pool/main/l/linux/linux-headers-3.2.0-4-common_3.2.41-1_amd64.deb
it is just 209k and almost empty, whereas it usually is 3-4M.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
I have now been running vanilla 3.4 from kernel.org for 4 weeks.
Starting with 3.4.18 I have continuosly updated as new builds were
released - recently 3.4.21 and now 3.4.23.
All versions ran smoothly without any problems. Also no
incompatibilities with other Wheezy packages have been noticed.
Am 15.12.2012 20:33, schrieb Ingo:
All versions ran smoothly without any problems. Also no
incompatibilities with other Wheezy packages have been noticed.
CORRECTION:
with vanilla kernel 3.4.23, I now had 2 freezes within 6 days!
I now switched back to 3.4.21 (which ran 8 days without
kernel - power consumption remained normal
and reset button responded immediately.
I am now with vanilla kernel 3.4.24 from kernel.org and all is fine.
/Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
I did contact the author and he kindly has fixed this bug in December 2012.
The new package can be downloaded from:
http://www.photofilmstrip.org/builds/photofilmstrip_1.9.92-1_all.deb
However Jens stated that this build would need some more testing before
it is released. Here, on Wheezy-amd64
I now tested Julien's kernel for 4 days under various conditions and all
ist solid so far. No freezes, everything works fine. I'll keep on
testing and report finally in bug #687442.
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe
to
standard Wheezy-kernel without beeing scared for my hardware.
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Many THANKS to Julien and Ben for fixing this (and pending) bugs.
I have immediately switched from vanilla 3.4 kernel to Debian's
3.2.0-39-1 from unstable.
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Since 2 weeks I an running kernel 3.4 from kernel.org. I used config from
Debian's 3.4.4-1~experimental.1 with make silentoldconfig and accepted
defaults fo 5 new items. This is a long term kernel as well and thus
still maintained.
I started with 3.4.18, updated to 3.4.19 and now using 3.4.20.
I do need my PC for daily work with VirtualBox. However
that site does not supply any matching header packages, so it won't
support VBox.
Regards,
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
on 11.2.202.291.
Kind regards,
Ingo
Subject: flashplugin-nonfree: Update of plugin to 11.2.202.297 fails
Package: flashplugin-nonfree
Version: 1:3.2
Severity: important
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation
According to my tests this nasty bug (which I observed mainly with
VirtualBox and OS/2 guest) has been fixed with the recent kernel update
in Wheezy to 3.2.0-51.
My guess is this commit which cured the freezes:
commit 884020bf3d2a3787a1cc6df902e98e0eec60330b upstream.
After any soft gfx
According to my tests this nasty bug (which I observed mainly with
VirtualBox and OS/2 guest) has been fixed with the recent kernel update
in Wheezy to 3.2.0-51.
My guess is this commit which cured the freezes:
commit 884020bf3d2a3787a1cc6df902e98e0eec60330b upstream.
After any soft gfx
I do hope we get the fix backported to Wheezy soon.
/Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
with version 0.7.4-4 my weather-plugin is alive again, thanks for the
quick fix.
/Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I only have configured a local mailbox (mbox).
It appears that if the mailwatch-plugin fails to fetch the local system
mail (forwarded from root - my user account) or has another problem, it
generates another mail and thus ends up in a dead loop. This happens
quite seldom, maybe once par 2 weeks
I now can definitely confirm that it is virtualbox 4.1.18-dfsg-2+deb7u1
which causes the hangs.
During an uptime of 1 week I performed 22x s2ram including 7x over night
*without any VM up and running*. I did not notice any problems or glitches.
The VM is running OS/2 as a guest with 1 CPU and
I just installed the Wheezy packages:
update-notifier
update-notifier-common
and its dependencies. Then purged packagekit and ...
Now apt-pin above 2 packages and you are done for the time beeing.
Uptdate-notification works fine as before.
It is sad to see how Gnome invades the whole system
I just installed following packages from Wheezy using 'dpkg -i':
libgdu0_3.0.2-3_amd64.deb (same version also in Jessie)
python-vte_0.28.2-5_amd64.deb (same version also in Jessie)
update-manager-core_0.200.5-2.1_all.deb
update-manager-gnome_0.200.5-2.1_all.deb
installed.
/Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
://lkml.org/lkml/2013/7/11/661
/Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
/7/11/661
/Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Delete me
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Today I tried to gather further information and found:
before s2ram:
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq
160
160
160
160
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq
380
380
380
380
after resume from s2ram:
cat
Just installing build-dep xfce4-weather-plugin in Wheezy and getting
source tarballs from Jessi is all you need. It smoothly builds with
dpkg-buildpackage -us -uc.
Works fine without any glitches here in Wheezy-amd64.
I also tried compiling from original sources
On Wed, Jan 22, 2014 at 05:18:39PM +0100, Alad Wenter wrote:
With the new version, it doesn't crash anymore, but some of the
prediction data are missing (location: Belgium)
The same here in Germany - all high temperatures are now NA as the
patch is supposed to do. However this applies to all
Am 26.01.2014 23:17, schrieb Yves-Alexis Perez:
It's in stable-proposed-updates right now, and should be available
in the next point release.
As posted before in message #50, that version from proposed is missing
*all* maximum/high temperatures in the forecast tab. First patch from
Christoph
Package: hugin
Version: 2014.0.0~rc2+dfsg-1
Severity: important
Dear Maintainer,
I just started Hugin and following the introduchtion hit I wanted to load 3
photos. Clicking on the step 1 button opens the usual file selection window
and after marking/selecting 3 *.jpg pictures to load pressing
Once Jessie is frozen, this will be a security issue for XFCE-desktop users:
*Not getting any notification on pending (security)-updates.*
The proposed solution as described in the previous message still works
perfectly.
Just using Gtk2-versions of update-manager and update-notifier should
also
Package: xfce4-weather-plugin
Version: 0.8.3-1
Severity: important
Tags: upstream
Dear Maintainer,
due to the crippled functionality of v7.4-5 in Wheezy I am using the
version 0.8.3-1~bpo70+1 from wheezy-backports. However since a few days
the old API stopped working and thus the applet does not
Package: gedit
Version: 3.12.2-2
Severity: normal
Tags: upstream
Dear Maintainer,
when trying to open (even to just read) a plain text file containing a
zero byte gedit is unable to display it correctly and does not allow to
edit and save it. zero bytes are not forbidden in plain text files and
Datum/Uhrzeit Meldung
30.09.2014 15:21:59 192.168.33.12 Anmeldung erfolgreich. (G101)
30.09.2014 15:10:47 Die IPv6 Systemzeit wurde erfolgreich aktualisiert. (NT101)
30.09.2014 14:40:45 DNSv6-Fehler: Der angegebene Domainname kann nicht von 2003:180:2:8000::53 aufgelöst werden. Fehler: Timeout
Package: pk-update-icon
Version: 1.0.0-1
Severity: important
Dear Maintainer,
* What led up to the situation?
Testing pk-update-icon (instead of update-manager + -notifier) in jessie with
XFCE4
* What exactly did you do (or not do) that was effective (or
ineffective)?
Puged
Am 19.11.2014 um 18:39 schrieb Matthias Klumpp:
Control: reassign -1 gnome-packagekit 3.14.0-1
Hi!
The network-interface issue is a problem of GNOME-PackageKit (and a
pretty stupid one...).
That the notifier does not notify after the Apt cronjob was run is
another bug, can you please
I just checked the timestamps in following directory (Jessie):
ls -l /var/lib/apt/periodic
insgesamt 0
-rw-r--r-- 1 root root 0 Nov 16 13:07 update-stamp
-rw-r--r-- 1 root root 0 Nov 17 12:47 update-success-stamp
These are outdated despite I installed the updates with packagekit GUI.
Seems that
be immediately for security reasons.
If more help is needed: I have done this in a VM and taken a snapshot
before, so I can repeat any time.
Cheers,
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I digged into documentation of PK and found in
/usr/share/doc/packagekit/README.Debian
The following components of PackageKit aren't shipped in the packages:
- cron job: APT does this already, no need for doubling the functionality
The following components of PackageKit aren't shipped in
Package: pk-update-icon
Version: 1.0.0-1
Severity: important
Dear Maintainer,
* What led up to the situation?
Today a dbus update for Jessie was available. During install
gnome-packagekit indicated by a computer symbol for package dbus the
necessarry reboot?
(don't know if thats the purpose
://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/sound/usb/mixer.c?id=e182534d4bd3a779941f2868f35e1f66a8d36cea
Jessie kernel works fine and has the patched version of /sound/usb/mixer.c.
Please include the patch in next update of Wheezy kernel.
Regards,
Ingo
--
To UNSUBSCRIBE, email
/default.pa.
(Command not documented in 'man pactl')
The message Unlikely big volume range in syslog is just cosmetic.
Ingo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Just prevent installation by apt-pinning:
/etc/apt/preferences
Package: libxrender*
Pin: version 1:0.9.7-1+deb7u1+b1
Pin-Priority: -1
Hope it gets fixed soon.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Whatever piece of volume I mount from fstab creates an entry in
/var/log/messages (can nicely be monitored with tail -f).
Be it a partitition, a NFS-export ...
And even a local partition which is declared in fstab to be mounted at
boot time:
UUID=279cee0c-5a0 /home/ingo/data ext4 errors
1 - 100 of 566 matches
Mail list logo
