Package: copyq
Version: 6.4.0-1
Severity: important
X-Debbugs-Cc: valentin.queq...@gmail.com
Dear Maintainer,
I run default configuration of AMD 64-bit Debian 12 Bookworm.
CopyQ doesn't start on session opening under gdm3/Xwayland ; at least the
server is **sometimes** started (using gnome-tweak
ll enabled.
Do you still need that I remove the '/var/lib/alsa/asound.state'
configuration file in between two full boots? I will do, one day, regardless
of your answer, but I make no promise for when I will share my progress.
Still in contact ... co-Debianer, or not?
Deep Though
ault.
Once toggeled, everything functions very fine.
I'm not so sorry for the noise, cause this mis-feature is much of a trap,
indeed; hope you agree with me.
Thanks again, Jonathan.
Kind Regards,
Valentin QUEQUET
-- System Information:
Debian Release: wheezy/sid
APT prefers experim
seful.
Kind Regards,
Valentin QUEQUET
-- Package-specific info:
** Version:
Linux version 3.2.0-1-amd64 (Debian 3.2.7-1) (debian-ker...@lists.debian.org)
(gcc version 4.6.2 (Debian 4.6.2-16) ) #1 SMP Tue Feb 28 15:35:32 UTC 2012
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-1-amd64
root
Kind Regards,
Valentin QUEQUET
-- Package-specific info:
** Version:
Linux version 3.2.0-1-amd64 (Debian 3.2.7-1) (debian-ker...@lists.debian.org)
(gcc version 4.6.2 (Debian 4.6.2-16) ) #1 SMP Tue Feb 28 15:35:32 UTC 2012
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-1-amd64
root=UUID=33f
ot;, this
launches the expected 3.2... version of the Python interpreter.
Any fixup in mind ?
Sincerely,
Valentin QUEQUET
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2
Package: sensors-applet
Version: 2.2.7-3
Severity: normal
Hi co-Linuxiens,
I chose to use the GNOME Sensors Applet which functions almost right.
In fact, if I switch from open-source Radeon (AMD/ATi) driver to proprietary
FGLRX driver, then I loose a sensor, which is not a big trouble and is no
Package: network-manager
Version: 0.8.9997-1
Followup-For: Bug #631150
Hello,
Now that I've used the version of n-m in experimental several times, I have to
tell more about the trouble I had.
Its "experimental" version (0.8.9997-1) sounds rock solid.
The trouble I had with this version (connec
Package: network-manager
Version: 0.8.4.0-2
Followup-For: Bug #631150
Hi!
I just upgraded network-manager from 0.8.4.0-2 (testing/unstable) to
0.8.9997-1 (experimental) in order to get rid of this nasty bug.
Unfortunately, this upgrade didn't help me at all.
In fact, this new n-m version didn
enVPN-powered VPN service to get a broader range of available services
(FTP, NTP, IM, GIT, SSH, Gaming, ...).
Here follows the log of the network-manager service I ran in the foreground.
In hope my report will prove useful.
Sincerely,
Valentin QUEQUET
NetworkManager[6394]: NetworkManager (version 0.
Both versions fail in the exact same manner ; so no need to provide logs
this time.
Do you think there is a solution for me to recover my data ?
I'm hearing from you eagerly.
Sincerely,
Valentin QUEQUET
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT po
dumps if possible and if useful (say me if it's not
a good idea).
In hope my report will prove useful.
Sincerely,
Valentin QUEQUET
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6
Package: libfuse2
Version: 2.8.4-1.3
Severity: important
Hi!
After upgrading FUSE from version 2.8.4-1.3 to 2.8.5-3 , all FUSE-based
filesystems I tried stopped working (i.e. ntfs-3g, sshfs, or zfs).
Example given:
root@valentin-laptop:~# mount -v /dev/sda3 /mnt/sda3 ; echo RESULT=$?
mount: yo
a bug of the
install system? By the time someone has initramfs-tools 0.94.4 , he/she
should have a "COMPRESS=gzip" stanza in the configuration file.
I appologize for not having seen the bug report #586554 before.
Sincerely,
Valentin QUEQUET
-- Package-specific info:
-- initramfs siz
ot;/etc/initramfs-tools/initramfs.conf" before upgrading initramfs-tools from
version 0.94.4 to version 0.97 .
Note that it is strange that initramfs-tools 0.97 depends on the COMPRESS
variable to be set properly in "/etc/initramfs-tools/initramfs.conf", while
the 0.94.4 version d
itramfs-tools to invoke gzip by
default, but apparently, there is a problem now, with 0.97 .
In hope my bug report will prove usefull.
Sincerely,
Valentin QUEQUET
-- Package-specific info:
-- initramfs sizes
lrwxrwxrwx 1 root root 51 Feb 16 12:09
/boot/initrd.img-2.6.29.4-reiser4-um-custo
Hello, the hurd,
davide wrote :
[...]
svn co svn://svn.debian.org/kernel/dists/trunk/linux-kbuild-2.6
Then, fetch the vanilla kernel tarball (important: the 2.6.x version,
no 2.6.x.y version):
wget http://ftp.de.kernel.org/pub/linux/kernel/v2.6/linux-2.6.27.tar.bz2
Now, you can prepare the pack
rg/cgi-bin/bugreport.cgi?bug=513835
which itself refers to a previous bug report of mine:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513095
In hope my report will prove useful.
Sincerely,
Valentin QUEQUET
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
'false bug' since Xen is known not to support ACPI.
However it is embarrassing if keyboard and touchpad functions depend
effectively on proper OS-Side ACPI initialisation while the keyboard
can be used seamlessly to tell the boot loader what to boot.
In hope my report will prove u
Hello again,
I just realized that I've been influenced by a wrong Xen tutorial.
When using the Xen hypervisor, one must replace the 'initrd' grub
keyword by the 'module' keyword.
That's all !
Sorry for the inconvenience if that change turn out to solve my
E Xen Hypervisor.
Furthermore, it always fails whether I use default all gzipped images or
all uncompressed ones. (for Xen Hypervisor, Linux Kernel, and Linux Initrd)
Please, give me some hints of what's wrong on my system.
Thanks in advance.
In hope my report will prove usefu
r to me which kernel version, and precisely which
Debian-packaged kernel version, does Debian sid btrfs-source package
apply to.
In hope you could make things more obvious, or at least more documented.
Sincerely,
Valentin QUEQUET
Here follows my build attempt and failure:
cd /usr/src &&
maximilian attems wrote:
On Mon, Aug 18, 2008 at 01:13:21PM +0200, Valentin QUEQUET wrote:
Package: initramfs-tools
Version: 0.92e
Severity: normal
Hello all,
I witnessed this trouble with initramfs-tools 0.92f :
Boot process freezes on 'Activating swap:' message.
Instead, all is
Activating swap:' message.
Instead, all is fine with previous initramfs-tools version = 0.92e .
Under 0.92e, I can see the message : 'Activating swap: swapon on /dev/sda3'
In hope my report will prove useful.
Sincerely,
Valentin QUEQUET
-- Package-specific info:
-- /proc/cmdline
#x27;Activating swap:' message.
Instead, all is fine with previous initramfs-tools version = 0.92e .
Under 0.92e, I can see the message : 'Activating swap: swapon on /dev/sda3'
In hope my report will prove useful.
Sincerely,
Valentin QUEQUET
-- Package-specific info:
-- /proc/cm
Package: openarena
Version: 0.7.7-1
Severity: normal
Hello all,
I would like OpenArena to be more friendly towards the user and allow this:
- Let [configurable] key combos (i.e. Alt+Tab) leak to the WindowManager,
whether OpenArena is Windowed or FullScreen.
(Or sees only key combo
Package: unclutter
Version: 8-8
Severity: normal
Hello all,
I found that, similarly to already reported bugs #237319 and #413282 ,
package unclutter has too many side effects:
It even mess up with some apps when these apps are in *windowed mode* (i.e.
OpenArena).
In hope my report will prove
Package: lilo
Version: 1:22.8-6
Severity: normal
Hello All,
I noticed that upgrading lilo from 1:22.8-5 to 1:22.8-6 got rid of bug #487421
on i386
architecture.
However, bug #487421 remains on amd64 architecture despite this same lilo
upgrade.
In hope my report will prove useful.
Sincerely,
:
http://bugzilla.kernel.org/show_bug.cgi?id=10997
I also updated things on my WEB site (more log files, .config, ...):
http://pagesperso-orange.fr/mandolosse/
Have a nice W.E.
regards
Valentin QUEQUET
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tro
Least but not last: I still experience bug #427421 (The FAMOUS
Linux/LILO/initRD case) with kernel
2.6.26~rc7-1~experimental.1~snapshot.11693 :-(
Help this report will prove useful.
Yours, sincerely.
Valentin QUEQUET
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of &quo
n early kernel panic with version 2) (see above) of my
initrd for linux-image-2.6.25-2-amd64 (ver 2.6.25-5) which is smaller ?
In hope my report will prove useful.
I'm looking forward to hearing from you.
Sincerely,
Valentin QUEQUET
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
losse/logs/2008-06-23__dmesg__ehci_hcd__died.txt
I also captured 'scanimage', 'lsmod' output and snapshots of '/proc/interrupts'
at different times. I plan to scrutinize all this data, to comment the relevant
parts and to post them later.
In hope my report will pr
t, in the
Linux_Kernel/LILO/Initial_RAM_Disk case, be a moot point.
To your opinion, who's guilty ?
I don't necessarily want to make the case against Linux_Kernel
overflated ;-)
I'm looking forward to hearing from you.
Sincerely,
Valentin QUEQUET
--
To UNSUBSCRIBE, email to [EMAI
#x27;s just that the kernel might not detect the
good filesystem type of the initial RAM disk image.
It's clear that the problem is more complex, and I bet it is a
Kernel+LILO problem (like in the mythology of the Babel Tower).
I'm looking forward to hearing from you.
Sincerely,
prove useful.
Sincerely,
Valentin QUEQUET
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR
s, try
something else. The basic themes are provided by the xpenguins package
(this is the xpenguins-applet package), so you'll have to install that
before xpenguins-applet will work.
[EMAIL PROTECTED]:~$
We can see clearly that this new version (2.1.1-6) still depends on
scrollkeeper
previously ran iceweasel 2.0.0.13xxx and I think (though not sure)
this version didn't have this bug.
In hope this report will prove usefull.
Sincerely,
Valentin QUEQUET
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
,
seems to me a better and safer idea.
Help my report will prove useful.
Sincerely,
Valentin QUEQUET
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-tuned (SMP w/2 CPU cores; PREEMPT)
Lo
forward to hearing from you.
Sincerely,
Valentin QUEQUET
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-tuned-toi (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-
f make-kpkg to 'ship' these
modules, instead of
further module-assistant invokation (I always used m-a)?
Help this report will prove useful.
Sincerely,
Valentin QUEQUET
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
wning packages (under Lenny):
splashy splashy-themes libsplashy1 uswsusp
And idea to recover the normal startup process where my display manager
(gdm) is launched automagically?
Hope this will be usefull to get a REAL (and curative) fix to this problem.
Sincerely,
Valentin QUEQUET
-- S
nt?
I highly suggest this be a bug (discrepancy of packages' expectations) of
initscripts, lsb-base and *splashy* . Or is 'gdm' mis-registered?
Sincerely,
Valentin QUEQUET
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing&
enny)
Then, any hint?
I highly suggest this be a bug (discrepancy of packages' expectations) of
initscripts, initscripts and *splashy* . Or is 'gdm' mis-registered?
Sincerely,
Valentin QUEQUET
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy:
enny)
Then, any hint?
I highly suggest this be a bug (discrepancy of packages' expectations) of
initscripts, lsb-base and *splashy* . Or is 'gdm' mis-registered?
Sincerely,
Valentin QUEQUET
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, '
44 matches
Mail list logo