Bug#999426: lxdm: tcp_listen config options is broken
Package: lxdm Version: 0.5.3-4 Severity: normal X-Debbugs-Cc: gennady.kup...@gmail.com enabling tcp_listen=1 removes 'nolisten tcp' optin from X server, but modern Xorg seems require explicit '-listen' option to actually listen on tcp port, so it is very hard to pass it. Hopefully trivial to fix. -- System Information: Debian Release: bookworm/sid APT prefers oldoldstable APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-3-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxdm depends on: ii debconf [debconf-2.0] 1.5.79 ii gtk2-engines 1:2.20.2-5+b1 ii gtk2-engines-pixbuf2.24.33-2 ii iso-codes 4.8.0-1 ii libc6 2.32-4 ii libcairo2 1.16.0-5 ii libgdk-pixbuf-2.0-02.42.6+dfsg-2 ii libglib2.0-0 2.70.0-3 ii libgtk2.0-02.24.33-2 ii libpam-modules 1.4.0-10 ii libpam-runtime 1.4.0-10 ii libpam0g 1.4.0-10 ii libpango-1.0-0 1.48.10+ds1-1 ii libpangocairo-1.0-01.48.10+ds1-1 ii librsvg2-common2.50.7+dfsg-2 ii libx11-6 2:1.7.2-2+b1 ii libxcb11.14-3 ii lsb-base 11.1.0 ii x11-utils 7.7+5 Versions of packages lxdm recommends: ii desktop-base 11.0.3 Versions of packages lxdm suggests: ii lxde-common 0.99.2-4 -- Configuration Files: /etc/lxdm/lxdm.conf changed: [base] greeter=/usr/lib/lxdm/lxdm-greeter-gtk [server] tcp_listen=1 [display] gtk_theme=Clearlooks bg=/usr/share/images/desktop-base/login-background.svg bottom_pane=1 lang=1 keyboard=0 theme=Industrial [input] [userlist] disable=0 white= black= -- debconf information: * shared/default-x-display-manager: lxdm
Bug#998108: Acknowledgement (firefox freezes shortly after start)
On Wed, 10 Nov 2021 00:59:02 +0100 Christoph Anton Mitterer wrote: > Not sure if this is related, but since a while I've noted even bigger > than the usual performance problems of firefox... > > Crackling sound is something I've heard for a month now... but since > about FF93 came out CPU utilisation seems to be much higher. > I just load simple webpages and may CPU goes up to 70-80°C. > > Anyone else seen this, too? > This is offtopic for the bug, but: Other way round for me. some version around 92 i see huge speed up, at least for youtube. seems before that it was sotwareish (typically 1080p took around 300% cpu) now it is around 130% for all processes. Firefox for the first time in 6 years on same hw could play 4k on intel. I spent some time investigating my 300% before, and learned a lot - that they enabling va-api and etc. slowness/fastness seems depend on the content you trying, configuration of your hardware, etc etc discussion would be way out of scope of this bug.
Bug#998108: Rebuild w/ new toolchain
On Mon, 8 Nov 2021 12:58:54 +0100 Simon Frei wrote: > On 08/11/2021 12:21, Jakob Haufe wrote: > > On Mon, 8 Nov 2021 10:25:24 +0100 > > Matthias Urlichs wrote: > > > >> Looks like the problem is a toolchain matter and requires a rebuild with > >> Rust 1.56. > >> > >> https://bugzilla.opensuse.org/show_bug.cgi?id=1192067 > > According to the build log, 94.0-1 has been built with 1.56. > > > > I read that bug as saying that 1.56 does not have any changes compared > to 1.55 that are likely to change anything. They talk about 1.55 > requiring llvm12, not llvm13. As far as I understand their fix was to go > back to rust 1.55 with llvm12. > When I look at the dependencies of firefox, it does depend on rust 1.56, > which in turn was built with llvm13, so that's fine. However firefox > also depends on libgl1-mesa-dri and mesa-va-drivers, which depend on > llvm12. Maybe this discrepancy is the culprit? > Note that with lichess page I posted above it should be very easy to reproduce. Open page, refresh once.
Bug#998108: having same issue here
Since I recently dist-upgraded sid. Tried to: 1) run with empty profile 2) do apt-get dist-upgrade just now, restart - doesn't help it seems to be freezing during rendering of the websites, seems like eventually running out of some resource and java-script heavy sites freeze it very soon. For example, if i open https://lichess.org/eTyPxe44EoQs (chess game analysis on lichess) first it opens fine, but hitting refresh certainly hungs whole firefox and only way to is kill it.
Bug#919533: python3-oauthlib: New version available
Package: python3-oauthlib Version: 2.1.0-1 Severity: wishlist Dear Maintainer, oauthlib has new version released, that supports openid connect. Please update if it possible. Thanks! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-oauthlib depends on: ii python3 3.7.1-3 ii python3-blinker 1.4+dfsg1-0.2 ii python3-cryptography 2.3-1 ii python3-jwt 1.7.0-2 python3-oauthlib recommends no packages. python3-oauthlib suggests no packages. -- no debconf information
Bug#767388: gdm3: (with default=kdm) gdm.service gives failed status
I am also affected by this problem. During boot quite a large amount of error messages are generated about gdm3 failing to start. signature.asc Description: OpenPGP digital signature
Bug#740885: Severity
Severity shouldn't be grave - it's still possible to use the application - you can specify the update interval manually, in the command line. Package still usable and many users use it, I don't want it to be excluded form archive!
Bug#726671: Upgrade solved the bug
The latest upgrade to libgtk-3-0 3.8.6-1 solved the problem. Bye! signature.asc Description: This is a digitally signed message part
Bug#726671: similar bug in Fedora
I found a similar bug in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1005613#c16 It's the same version of gnome-shell and it is due to an incompatibility with a gtk-3.8.5. I think that this warrants a breaks. I am trying now to upgrade gtk3 to the version in experimental. I'll if this helps. Gennady signature.asc Description: This is a digitally signed message part
Bug#726671: Didn't help.
Well, upgrading to the experimental version of libgtk-3 didn't help. As a matter of fact https://bugzilla.redhat.com/show_bug.cgi?id=1005613#c16 suggests downgrading... signature.asc Description: This is a digitally signed message part
Bug#726671: A stack trace
Hey guys! I installed the debugging symbols and I am providing a stack trace attached. The problem is still there and is reproducible as ever. Starting program: /usr/bin/gnome-shell --replace warning: Could not load shared library symbols for linux-vdso.so.1. Do you need set solib-search-path or set sysroot? [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffe3b91700 (LWP 10511)] [New Thread 0x7fffe1c1d700 (LWP 10533)] [New Thread 0x7fffe1215700 (LWP 10534)] [New Thread 0x7fffe0a14700 (LWP 10537)] [New Thread 0x7fffcf2ff700 (LWP 10542)] [New Thread 0x7fffcd4ff700 (LWP 10561)] [New Thread 0x7fffa1262700 (LWP 10562)] [New Thread 0x7fffa0a61700 (LWP 10563)] [New Thread 0x7fff9bfff700 (LWP 10564)] [New Thread 0x7fff9b7fe700 (LWP 10565)] [Thread 0x7fff9bfff700 (LWP 10564) exited] [Thread 0x7fffa0a61700 (LWP 10563) exited] [Thread 0x7fffa1262700 (LWP 10562) exited] [Thread 0x7fffcd4ff700 (LWP 10561) exited] [Thread 0x7fffcf2ff700 (LWP 10542) exited] [New Thread 0x7fffcf2ff700 (LWP 10704)] [New Thread 0x7fffcd4ff700 (LWP 10705)] [New Thread 0x7fffa1262700 (LWP 10706)] [Thread 0x7fffcf2ff700 (LWP 10704) exited] [Thread 0x7fffcd4ff700 (LWP 10705) exited] [Thread 0x7fffa1262700 (LWP 10706) exited] [New Thread 0x7fffa1262700 (LWP 10707)] [New Thread 0x7fffcd4ff700 (LWP 10708)] [New Thread 0x7fffcf2ff700 (LWP 10709)] [New Thread 0x7fffa0a61700 (LWP 10710)] [New Thread 0x7fffa5af8700 (LWP 10711)] [New Thread 0x7fffa52f7700 (LWP 10712)] [New Thread 0x7fffa4af6700 (LWP 10713)] Program received signal SIGSEGV, Segmentation fault. magazine_chain_pop_head (magazine_chunks=0x609660) at /tmp/buildd/glib2.0-2.36.4/./glib/gslice.c:532 532 /tmp/buildd/glib2.0-2.36.4/./glib/gslice.c: No such file or directory. Thread 21 (Thread 0x7fffa4af6700 (LWP 10713)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7fffeeafd5f5 in g_cond_wait_until (cond=cond@entry=0x1bd9cf8, mutex=mutex@entry=0x1bd9cf0, end_time=end_time@entry=4022145021) at /tmp/buildd/glib2.0-2.36.4/./glib/gthread-posix.c:865 #2 0x7fffeea94941 in g_async_queue_pop_intern_unlocked (queue=0x1bd9cf0, wait=wait@entry=1, end_time=4022145021) at /tmp/buildd/glib2.0-2.36.4/./glib/gasyncqueue.c:424 #3 0x7fffeea94f08 in g_async_queue_timeout_pop_unlocked (queue=optimized out, timeout=timeout@entry=50) at /tmp/buildd/glib2.0-2.36.4/./glib/gasyncqueue.c:572 #4 0x7fffeeae2b68 in g_thread_pool_wait_for_new_task (pool=0x1bd9c90) at /tmp/buildd/glib2.0-2.36.4/./glib/gthreadpool.c:264 #5 g_thread_pool_thread_proxy (data=optimized out) at /tmp/buildd/glib2.0-2.36.4/./glib/gthreadpool.c:298 #6 0x7fffeeae21d5 in g_thread_proxy (data=0x32818a0) at /tmp/buildd/glib2.0-2.36.4/./glib/gthread.c:798 #7 0x7fffee861e0e in start_thread (arg=0x7fffa4af6700) at pthread_create.c:311 #8 0x7fffee5969ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 20 (Thread 0x7fffa52f7700 (LWP 10712)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7fffeeafd5f5 in g_cond_wait_until (cond=cond@entry=0x1bd9cf8, mutex=mutex@entry=0x1bd9cf0, end_time=end_time@entry=4022150277) at /tmp/buildd/glib2.0-2.36.4/./glib/gthread-posix.c:865 #2 0x7fffeea94941 in g_async_queue_pop_intern_unlocked (queue=0x1bd9cf0, wait=wait@entry=1, end_time=4022150277) at /tmp/buildd/glib2.0-2.36.4/./glib/gasyncqueue.c:424 #3 0x7fffeea94f08 in g_async_queue_timeout_pop_unlocked (queue=optimized out, timeout=timeout@entry=50) at /tmp/buildd/glib2.0-2.36.4/./glib/gasyncqueue.c:572 #4 0x7fffeeae2b68 in g_thread_pool_wait_for_new_task (pool=0x1bd9c90) at /tmp/buildd/glib2.0-2.36.4/./glib/gthreadpool.c:264 #5 g_thread_pool_thread_proxy (data=optimized out) at /tmp/buildd/glib2.0-2.36.4/./glib/gthreadpool.c:298 #6 0x7fffeeae21d5 in g_thread_proxy (data=0x7fff94007a30) at /tmp/buildd/glib2.0-2.36.4/./glib/gthread.c:798 #7 0x7fffee861e0e in start_thread (arg=0x7fffa52f7700) at pthread_create.c:311 #8 0x7fffee5969ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 19 (Thread 0x7fffa5af8700 (LWP 10711)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7fffeeafd5f5 in g_cond_wait_until (cond=cond@entry=0x1bd9cf8, mutex=mutex@entry=0x1bd9cf0, end_time=end_time@entry=4022147494) at /tmp/buildd/glib2.0-2.36.4/./glib/gthread-posix.c:865 #2 0x7fffeea94941 in g_async_queue_pop_intern_unlocked (queue=0x1bd9cf0, wait=wait@entry=1, end_time=4022147494) at /tmp/buildd/glib2.0-2.36.4/./glib/gasyncqueue.c:424 #3 0x7fffeea94f08 in g_async_queue_timeout_pop_unlocked (queue=optimized out, timeout=timeout@entry=50) at /tmp/buildd/glib2.0-2.36.4/./glib/gasyncqueue.c:572 #4 0x7fffeeae2b68 in
Bug#726151:
Just upgraded the kernel and the same exact thing is still there for kernel 3.11! signature.asc Description: This is a digitally signed message part
Bug#726336: [gnome-power-manager] Gnome thinks I am on Battery when I am on AC
I found some sort of clue. Updating the system through aptitude I once got this error: setterm: cannot (un)set powersave mode: Inappropriate ioctl for device I do not know what package was concerned (updated quite a few). Maybe it is not a problem of gnome after all. I tried searching google but people complained about this error on servers and they wanted to disable power management completely. This is not my case, however so just adding acpi=off to the boot command will not do. In any case shouldn't gnome power manager at least say something in .xsessionerrors if it encounters a problem setting powermanagement settings? Gennady On Mon, 2013-10-14 at 15:00 -0400, Emilio Pozuelo Monfort wrote: On 14/10/13 13:10, Gennady Uraltsev wrote: Package: gnome-power-manager Version: 3.8.2-1 Severity: important Dear developers, Starting from some time ago I noticed that my Gnome 3 thinks that I am on battery even when I am on AC. In particular it brightens down my screen and sleeps the laptop (Thinkpad W520) after some time of inactivity even though these settings are enabled (through dconf) only for battery powered operation. This worked some time ago (several weeks) and got broke at some point (I cannot pin down when since it took some time to notice). What does `acpi' say when gnome thinks you're on battery while you're not? signature.asc Description: This is a digitally signed message part
Bug#726671: [gnome-shell] Gnome shell segfaults and restarts when going to applications - all
Package: gnome-shell Version: 3.8.4-4 Severity: important Dear Maintainers, Gnome 3.8.4-4 crashes segfaults and restarts when going to Show applications and clicking All To debug I have these messages: .cache/gdm/session.log: gnome-session[15101]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 JS LOG: GNOME Shell started at Fri Oct 18 2013 00:32:38 GMT+0200 (CEST) journalctl -ab: Oct 18 00:32:37 halen kernel: traps: gnome-shell[16359] general protection ip:7fc440cf86a0 sp:7fff8a529f88 error:0 in libglib-2.0.so.0.3600.4[7fc440c94000+fc000] Oct 18 00:32:37 halen polkitd(authority=local)[2267]: Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session11 (system bus name :1.248, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.utf8) (disconnected from bus) Oct 18 00:32:37 halen gnome-session[15101]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 Oct 18 00:32:38 halen dbus-daemon[2195]: dbus[2195]: [system] Rejected send message, 2 matched rules; type=method_call, sender=:1.252 (uid=1000 pid=17441 comm=/usr/bin/gnome-shell ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.16 (uid=0 pid=2888 comm=/usr/sbin/console-kit-daemon --no-daemon ) Oct 18 00:32:38 halen dbus[2195]: [system] Rejected send message, 2 matched rules; type=method_call, sender=:1.252 (uid=1000 pid=17441 comm=/usr/bin/gnome-shell ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destination=:1.16 (uid=0 pid=2888 comm=/usr/sbin/console-kit-daemon --no-daemon ) Oct 18 00:32:38 halen polkitd(authority=local)[2267]: Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session11 (system bus name :1.252 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.utf8) Oct 18 00:32:39 halen nautilus[17474]: [N-A] Nautilus-Actions Tracker 3.2.2 initializing... Oct 18 00:32:39 halen nautilus[17474]: [N-A] Nautilus-Actions Menu Extender 3.2.2 initializing... dmesg: [ 4196.999551] gnome-shell[14639]: segfault at 20001 ip 7f3020fa9507 sp 7fffd5fbf7e0 error 4 in libglib-2.0.so.0.3600.4[7f3020f46000+fc000] [ 4389.744487] traps: gnome-shell[15231] general protection ip:7feab5400507 sp:7fffec78c950 error:0 in libglib-2.0.so.0.3600.4[7feab539d000+fc000] [ 4590.313281] traps: gnome-shell[16359] general protection ip:7fc440cf86a0 sp:7fff8a529f88 error:0 in libglib-2.0.so.0.3600.4[7fc440c94000+fc000] The only way to start programs that are not in the recently used section is by starting typing... I tried to remove .local .cache .gconf .config and all this to no avail! It crashes anyway. Please let me know if I can help more. Sincerely, Gennady --- System information. --- Architecture: amd64 Kernel: Linux 3.10-3-amd64 Debian Release: jessie/sid 990 unstablewww.deb-multimedia.org 990 unstableftp.de.debian.org 500 stable dl.google.com 1 experimentalftp.debian.org 1 experimentalcdn.debian.net --- Package information. --- Depends (Version) | Installed =-+-== gir1.2-clutter-1.0 (= 1.11.11) | 1.14.4-3 gir1.2-glib-2.0 (= 1.31) | 1.36.0-2+b1 gir1.2-gmenu-3.0 | 3.8.0-2 gir1.2-gtk-3.0 (= 3.8) | 3.8.5-1 gir1.2-mutter-3.0 (= 3.8.3) | 3.8.4-2 gir1.2-networkmanager-1.0 | 0.9.8.0-5 gir1.2-soup-2.4 (= 2.40.1) | 2.42.2-6 gir1.2-telepathyglib-0.12 | 0.22.0-1 dconf-gsettings-backend | 0.16.1-1 OR gsettings-backend | gnome-bluetooth(= 3.0.0) | 3.8.1-2 libatk-bridge2.0-0 (= 2.5.3) | 2.10.0-1 libatk1.0-0 (= 1.12.4) | libc6 (= 2.14) | libcairo-gobject2 (= 1.10.0) | libcairo2 (= 1.10.0) | libcamel-1.2-43 | libcanberra-gtk3-0 (= 0.25) | libcanberra0 (= 0.2) | libclutter-1.0-0 (= 1.13.4) | libcogl-pango12(= 1.7.4) | libcogl12 (= 1.10.0) | libcroco3 (= 0.6.2) | libdbus-1-3(= 1.0.2) | libdbus-glib-1-2(= 0.78) | libecal-1.2-15(= 3.5.91) | libedataserver-1.2-17 (= 3.5.91) | libegl1-mesa (= 7.8.1) | OR libegl1
Bug#726336: [gnome-power-manager] Gnome thinks I am on Battery when I am on AC
This is the output of $ acpi -V Battery 0: Charging, 90%, 00:24:44 until charged Battery 0: design capacity 7800 mAh, last full capacity 6863 mAh = 87% Adapter 0: on-line Thermal 0: ok, 38.0 degrees C Thermal 0: trip point 0 switches to mode critical at temperature 99.0 degrees C Cooling 0: LCD 0 of 15 Cooling 1: LCD 0 of 15 Cooling 2: Processor 0 of 10 Cooling 3: Processor 0 of 10 Cooling 4: Processor 0 of 10 Cooling 5: Processor 0 of 10 Cooling 6: Processor 0 of 10 Cooling 7: Processor 0 of 10 Cooling 8: Processor 0 of 10 Cooling 9: Processor 0 of 10 I have tried studying the phenomenon a bit more. Maybe the problem is actually that gnome-power-manager doesn't respect the settings in dconf. My current settings are given by: $ dconf dump /org/gnome/settings-daemon/plugins/power/ [/] button-power='interactive' critical-battery-action='shutdown' idle-dim-time=60 sleep-inactive-ac-type='blank' sleep-inactive-battery-timeout=300 lid-close-ac-action='blank' idle-dim-ac=false idle-dim-battery=true idle-brightness=30 sleep-display-battery=180 lid-close-battery-action='suspend' sleep-inactive-ac-timeout=600 use-time-for-policy=true Even though it is told not to dim on ac idle-dim-ac=false it does so and even tough sleep-inactive-ac-type='blank' it suspends when the battery timeout is reached. I will try to experiment more. I am now trying to reset and then configure all the values using dconf command line tool and not dconf-editor. Lets see how it goes. Thanks! Gennady. On Mon, 2013-10-14 at 15:00 -0400, Emilio Pozuelo Monfort wrote: On 14/10/13 13:10, Gennady Uraltsev wrote: Package: gnome-power-manager Version: 3.8.2-1 Severity: important Dear developers, Starting from some time ago I noticed that my Gnome 3 thinks that I am on battery even when I am on AC. In particular it brightens down my screen and sleeps the laptop (Thinkpad W520) after some time of inactivity even though these settings are enabled (through dconf) only for battery powered operation. This worked some time ago (several weeks) and got broke at some point (I cannot pin down when since it took some time to notice). What does `acpi' say when gnome thinks you're on battery while you're not? signature.asc Description: This is a digitally signed message part
Bug#726336: [gnome-power-manager] Gnome thinks I am on Battery when I am on AC
Package: gnome-power-manager Version: 3.8.2-1 Severity: important Dear developers, Starting from some time ago I noticed that my Gnome 3 thinks that I am on battery even when I am on AC. In particular it brightens down my screen and sleeps the laptop (Thinkpad W520) after some time of inactivity even though these settings are enabled (through dconf) only for battery powered operation. This worked some time ago (several weeks) and got broke at some point (I cannot pin down when since it took some time to notice). Thanks! Gennady --- System information. --- Architecture: amd64 Kernel: Linux 3.10-3-amd64 Debian Release: jessie/sid 990 unstablewww.deb-multimedia.org 990 unstableftp.de.debian.org 500 stable dl.google.com 1 experimentalftp.debian.org 1 experimentalcdn.debian.net --- Package information. --- Depends(Version) | Installed -+-= libc6 (= 2.4) | libcairo2 (= 1.2.4) | libglib2.0-0(= 2.31.18) | libgtk-3-0 (= 3.3.16) | libpango-1.0-0 (= 1.18.0) | libpangocairo-1.0-0 (= 1.14.0) | libupower-glib1 (= 0.9.1) | dconf-gsettings-backend | OR gsettings-backend| notification-daemon | dbus-x11 | upower | gnome-settings-daemon (= 3.2) | Package's Recommends field is empty. Suggests (Version) | Installed ==-+-=== policykit-1| 0.105-3+nmu1 signature.asc Description: This is a digitally signed message part
Bug#726151: [openvpn] openVPN connection breaks power management
Package: openvpn Version: 2.3.2-5 Severity: normal Dear Developers, Once a openvpn connection is established my laptop starts to believe strange things about the power status. In particular the whole DE starts working as though it is on battery power and not on AC (dimming screen and sleeping after some inactivity). However this doesn't depend on the DE (Gnome 3) specifically. Normally running powertop as root gives these debug messages: Loaded 190 prior measurements RAPL device for cpu 0 RAPL device for cpu 0 RAPL device for cpu 0 and then it starts. If the openvpn connection is present the program doesn't start up and gives these debug messages: Loaded 190 prior measurements RAPL device for cpu 0 RAPL device for cpu 0 RAPL device for cpu 0 BUG: requesting unregistered parameter 61 BUG: requesting unregistered parameter 66 ... where the two BUG messages get repeated thousands of times. This behavior is the same regardless is I connect via the nm-applet of GNOME 3 or form a root shell by running openvpn --config login--bonn.ovpn For completeness I am attaching the ovpn file. I inspected syslog and found nothing relevant to power management, ACPI, or such. The only messages that appear during/after a vpn connection are: Oct 12 22:09:51 halen NetworkManager[3416]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/tun0, iface: tun0) Oct 12 22:09:51 halen NetworkManager[3416]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found. Oct 12 22:09:51 halen NetworkManager[3416]: warn /sys/devices/virtual/net/tun0: couldn't determine device driver; ignoring... in /var/log/syslog. I am also attaching the file vpn.log that contains all that vpn outputs when running from terminal. Please let me know if there is anything else I can tell you to help. Sincerely, Gennady --- System information. --- Architecture: amd64 Kernel: Linux 3.10-3-amd64 Debian Release: jessie/sid 990 unstablewww.deb-multimedia.org 990 unstableftp.de.debian.org 500 stable dl.google.com 1 experimentalftp.debian.org 1 experimentalcdn.debian.net --- Package information. --- Depends (Version) | Installed ===-+-== debconf (= 0.5) | 1.5.51 OR debconf-2.0 | libc6 (= 2.15) | liblzo2-2 | libpam0g (= 0.99.7.1) | libpkcs11-helper1 (= 1.05) | libssl1.0.0 (= 1.0.0) | initscripts (= 2.88dsf-13.3) | iproute2| Recommends (Version) | Installed =-+-=== easy-rsa | 2.2.0-1 Suggests(Version) | Installed =-+-=== openssl | 1.0.1e-3 resolvconf| 1.74 remote vpn.stw-bonn.de 1195 udp dev tun persist-tun persist-key ca ca--bonn.crt remote-random resolv-retry infinite tls-remote vpn.stw-bonn.de auth-user-pass client nobind pull verb 4 redirect-gateway def1 Sat Oct 12 22:13:07 2013 DEPRECATED OPTION: --tls-remote, please update your configuration Sat Oct 12 22:13:07 2013 us=921549 Current Parameter Settings: Sat Oct 12 22:13:07 2013 us=921560 config = 'login--bonn.ovpn' Sat Oct 12 22:13:07 2013 us=921568 mode = 0 Sat Oct 12 22:13:07 2013 us=921574 persist_config = DISABLED Sat Oct 12 22:13:07 2013 us=921581 persist_mode = 1 Sat Oct 12 22:13:07 2013 us=921587 show_ciphers = DISABLED Sat Oct 12 22:13:07 2013 us=921593 show_digests = DISABLED Sat Oct 12 22:13:07 2013 us=921599 show_engines = DISABLED Sat Oct 12 22:13:07 2013 us=921605 genkey = DISABLED Sat Oct 12 22:13:07 2013 us=921611 key_pass_file = '[UNDEF]' Sat Oct 12 22:13:07 2013 us=921617 show_tls_ciphers = DISABLED Sat Oct 12 22:13:07 2013 us=921623 Connection profiles [default]: Sat Oct 12 22:13:07 2013 us=921630 proto = udp Sat Oct 12 22:13:07 2013 us=921636 local = '[UNDEF]' Sat Oct 12 22:13:07 2013 us=921642 local_port = 0 Sat Oct 12 22:13:07 2013 us=921648 remote = 'vpn.stw-bonn.de' Sat Oct 12 22:13:07 2013 us=921654 remote_port = 1195 Sat Oct 12 22:13:07 2013 us=921660 remote_float = DISABLED Sat Oct 12 22:13:07 2013 us=921666 bind_defined = DISABLED Sat Oct 12 22:13:07 2013 us=921672 bind_local = DISABLED Sat Oct 12 22:13:07 2013 us=921678 connect_retry_seconds = 5 Sat Oct 12 22:13:07 2013 us=921685 connect_timeout = 10 Sat Oct 12 22:13:07 2013 us=921691 connect_retry_max = 0 Sat Oct 12 22:13:07 2013 us=921697 socks_proxy_server = '[UNDEF]' Sat Oct 12 22:13:07 2013 us=921703 socks_proxy_port = 0 Sat Oct 12 22:13:07 2013 us=921709 socks_proxy_retry = DISABLED Sat Oct 12 22:13:07 2013 us=921715 tun_mtu = 1500 Sat Oct 12 22:13:07 2013 us=921721 tun_mtu_defined = ENABLED Sat Oct 12 22:13:07
Bug#720297: [gnome-core] Freeze on startup since 1:3.8+3
Package: gnome-core Version: 1:3.8+3 Followup-For: Bug #720297 I have the same problem, however it appears not immediately on login but after the first interaction with gnome shell. programs that I start automatically work fine but as soon as I go to Activities, or try to run Alt+F2, or click the network icon or anything else Gnome Shell freezes. I think that it maybe due to a version mismatch because gnome-core is at 1:3.8+3 and gnome-shell is at 3.4.2-12+b1. This is the standard way things are in Sid. I will try to downgrade to gnome-core 1:3.8+2 and upgrade gnome-shell to 3.8.3-1 in experimental to see if the bug remains. I am attaching .xsession-errors that has some serious JS errors by gnome shell that are probably responsible. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-core depends on: ii at-spi2-core 2.9.5-1 ii baobab 3.8.2-1 ii brasero3.8.0-2 ii caribou0.4.4-1 ii caribou-antler 0.4.4-1 ii dconf-gsettings-backend0.16.1-1 ii dconf-tools0.16.1-1 ii empathy3.4.2.3-4+b1 ii eog3.8.2-1 ii evince 3.4.0-3.1+b1 ii evolution-data-server 3.4.4-4 ii fonts-cantarell0.0.13-1 ii gconf2 3.2.6-1 ii gdm3 3.4.1-9 ii gkbd-capplet 3.6.0-1 ii glib-networking2.36.1-2 ii gnome-backgrounds 3.8.1-1 ii gnome-bluetooth3.8.1-2 ii gnome-calculator 3.8.2-1 ii gnome-contacts 3.4.1-2 ii gnome-control-center 1:3.4.3.1-5+b2 ii gnome-dictionary 3.6.0-1 ii gnome-disk-utility 3.0.2-3 ii gnome-font-viewer 3.8.0-1 ii gnome-icon-theme 3.8.2-2 ii gnome-icon-theme-extras3.6.2-2 ii gnome-icon-theme-symbolic 3.8.2.2-2 ii gnome-keyring 3.8.2-2 ii gnome-menus3.8.0-2 ii gnome-online-accounts 3.8.2-1 ii gnome-packagekit 3.8.2-4 ii gnome-panel3.4.2.1-5 ii gnome-power-manager3.8.2-1 ii gnome-screensaver 3.6.0-1+b1 ii gnome-screenshot 3.8.2-1 ii gnome-session 3.4.2.1-4 ii gnome-session-fallback 3.4.2.1-4 ii gnome-settings-daemon 3.4.2+git20121218.7c1322-6+b2 ii gnome-shell3.4.2-12+b1 ii gnome-sushi0.4.1-5+b2 ii gnome-system-log 3.8.1-1 ii gnome-system-monitor 3.8.2.1-2 ii gnome-terminal 3.8.3-1 ii gnome-themes-standard 3.8.3-1 ii gnome-user-guide 3.8.2-1 ii gnome-user-share 3.8.0-2+b1 ii gsettings-desktop-schemas 3.4.2-3 ii gstreamer1.0-plugins-base 1.0.9-1 ii gstreamer1.0-plugins-good 1.0.9-1 ii gstreamer1.0-pulseaudio1.0.9-1 ii gtk2-engines 1:2.20.2-2 ii gucharmap 1:3.8.2-2 ii gvfs-backends 1.16.3-1 ii gvfs-bin 1.16.3-1 ii iceweasel 24.0~b3-1 ii libatk-adaptor 2.9.5-1 ii libcanberra-pulse 0.30-2 ii libcaribou-gtk-module 0.4.4-1 ii libcaribou-gtk3-module 0.4.4-1 ii libgtk-3-common3.8.2-3 ii libpam-gnome-keyring 3.8.2-2 ii metacity 1:2.34.13-1 ii mousetweaks3.8.0-1 ii nautilus 3.4.2-2 ii notification-daemon0.7.6-1 ii policykit-1-gnome 0.105-2 ii pulseaudio 4.0-6 ii sound-theme-freedesktop0.8-1 ii tracker-gui0.16.1-2 ii vino 3.8.1-1 ii yelp 3.8.1-2 ii zenity 3.8.0-1 Versions of packages gnome-core recommends: ii network-manager-gnome 0.9.8.2-1+b1 Versions of packages gnome-core suggests: ii gnome 1:3.8+3 /etc/gdm3/Xsession: Beginning session setup... localuser:guraltsev being added to access control list openConnection: connect: No such file or directory cannot connect to brltty at :0 /etc/gdm3/Xsession: 45: /etc/X11/Xsession.d/98vboxadd-xclient: /usr/bin/VBoxClient: not found /etc/gdm3/Xsession: 46: /etc/X11/Xsession.d/98vboxadd-xclient: /usr/bin/VBoxClient: not found /etc/gdm3/Xsession: 48: /etc/X11/Xsession.d/98vboxadd-xclient: /usr/bin/VBoxClient: not found /etc/gdm3/Xsession: 50: /etc/X11/Xsession.d/98vboxadd-xclient: /usr/bin/VBoxClient: not found /etc/gdm3/Xsession: 52: /etc/X11/Xsession.d/98vboxadd-xclient: /usr/bin/VBoxClient: not found GNOME_KEYRING_CONTROL=/home/guraltsev/.cache/keyring-kgTkAl SSH_AUTH_SOCK=/home/guraltsev/.cache/keyring-kgTkAl/ssh
Bug#720297: [gnome-core] Freeze on startup since 1:3.8+3
Package: gnome-core
Version: 1:3.8+3
I continued playing around with downgrading and changing versions and have
these results:
1) Downgrading gnome-shell to 3.4.2-12 from testing solves the problem with
gnome shell.
This downgrade can be accomplished by doing
[INSTALL, DEPENDENCIES] libcogl-pango0:amd64 1.10.2-7
[INSTALL, DEPENDENCIES] libcogl9:amd64 1.10.2-7
[DOWNGRADE] gir1.2-clutter-1.0:amd64 1.14.4-2 - 1.10.8-2
[DOWNGRADE] gnome-shell:amd64 3.4.2-12+b1 - 3.4.2-12
[DOWNGRADE] libclutter-1.0-0:amd64 1.14.4-2 - 1.10.8-2
However this solution introduces a new problem: Empathy and Evolution do
not start giving out this message to the terminal:
Empathy:
Clutter-CRITICAL **: Unable to initialize Clutter: Failed to connected to any
renderer:
Evolution:
Failed to connected to any renderer:
This happens independently of the version of Empathy and Evolution (I tried
downgrading them...)
2) From situation (1), if one chooses to upgrade gnome-shell this is what
happens:
[REMOVE, DEPENDENCIES] libcogl-pango0:amd64
[REMOVE, DEPENDENCIES] libcogl9:amd64
[UPGRADE] gir1.2-clutter-1.0:amd64 1.10.8-2 - 1.14.4-2
[UPGRADE] gnome-shell:amd64 3.4.2-12 - 3.4.2-12+b1
[UPGRADE] libclutter-1.0-0:amd64 1.10.8-2 - 1.14.4-2
Gnome shell stops working but Evolution and Empathy START working.
Furthermore I managed to get the attached .xessions-errors file. It has
a curious entry that says:
(gnome-shell:7716): Cogl-WARNING **: Failed to compile GLSL program:
src:
#version 110
uniform sampler2D tex;
uniform float fraction;
uniform float height;
const float c = -0.2;
const float border_max_height = 60.0;
mat4 contrast = mat4 (1.0 + c, 0.0, 0.0, 0.0,
0.0, 1.0 + c, 0.0, 0.0,
0.0, 0.0, 1.0 + c, 0.0,
0.0, 0.0, 0.0, 1.0);
vec4 off = vec4(0.633, 0.633, 0.633, 0);
void main()
{
vec4 color = texture2D(tex, cogl_tex_coord_in[0].xy);
float y = height * cogl_tex_coord_in[0].y;
// To reduce contrast, blend with a mid gray
cogl_color_out = color * contrast - off * c * color.a;
// We only fully dim at a distance of BORDER_MAX_HEIGHT from the top and
// when the fraction is 1.0. For other locations and fractions we linearly
// interpolate back to the original undimmed color, so the top of the window
// is at full color.
cogl_color_out = color + (cogl_color_out - color) * max(min(y /
border_max_height, 1.0), 0.0);
cogl_color_out = color + (cogl_color_out - color) * fraction;
}
error:
0:23(1): error: syntax error, unexpected VERSION_TOK, expecting $end
(gnome-shell:7716): Cogl-WARNING **: Failed to link GLSL program:
error: linking with uncompiled shader
3) Finally there is also this bug report that probably is filed against the
right package:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720283
Hope this helps.
Gennady
--- System information. ---
Architecture: amd64
Kernel: Linux 3.10-2-amd64
Debian Release: jessie/sid
990 unstablewww.deb-multimedia.org
990 unstableftp.ru.debian.org
500 testing ftp.ru.debian.org
500 stable dl.google.com
500 experimentalmozilla.debian.net
1 experimentalftp.debian.org
1 experimentalcdn.debian.net
--- Package information. ---
Depends (Version) | Installed
==-+-=
libatk-adaptor(= 2.4) | 2.9.5-1
at-spi2-core (= 2.4) | 2.9.5-1
baobab(= 3.4) | 3.8.2-1
brasero (= 3.4) | 3.8.0-2
caribou (= 0.4.2) | 0.4.4-1
caribou-antler (= 0.4.2) | 0.4.4-1
libcaribou-gtk-module (= 0.4.2) | 0.4.4-1
libcaribou-gtk3-module (= 0.4.2) | 0.4.4-1
dconf-gsettings-backend (= 0.12) | 0.16.1-1
dconf-tools (= 0.12) | 0.16.1-1
empathy (= 3.4) | 3.4.2.3-4+b1
eog (= 3.4) | 3.8.2-1
evince(= 3.4) | 3.4.0-3.1+b1
evolution-data-server (= 3.4) | 3.4.4-4
fonts-cantarell (= 0.0.8) | 0.0.13-1
sound-theme-freedesktop| 0.8-1
gnome-calculator (= 3.8) | 3.8.2-1
gconf2 (= 3.2.5) | 3.2.6-1
gdm3 (= 3.4) | 3.4.1-9
glib-networking (= 2.32) | 2.36.1-2
gnome-backgrounds (= 3.4) | 3.8.1-1
gnome-bluetooth (= 3.4) | 3.8.1-2
gnome-contacts(= 3.4) | 3.4.1-2
gnome-control-center(= 1:3.4) | 1:3.4.3.1-5+b2
gnome-dictionary (= 3.4) | 3.6.0-1
gnome-disk-utility(= 3.0) | 3.0.2-3
gnome-font-viewer (= 3.4) | 3.8.0-1
gnome-icon-theme (= 3.4) | 3.8.2-2
gnome-icon-theme-extras (= 3.4) | 3.6.2-2
gnome-icon-theme-symbolic (= 3.4) | 3.8.2.2-2
gnome-keyring
Bug#720283: gnome-shell fails to start, clutter problems
Package: gnome-shell Version: 3.4.2-12+b1 I have the same situation as described here. Gnome-shell starts but any action causes it to hang. I have also found a bug filed against gnome-core that is due to the same problem (I suppose). It is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720297 Before finding this bug I posted some info and diagnoses I have done there. If someone is trying to solve this, please take a look. In particular I have managed to get this .xsession-errors file (that I attached there) that seems to give some info... Good luck! --- System information. --- Architecture: amd64 Kernel: Linux 3.10-2-amd64 Debian Release: jessie/sid 990 unstablewww.deb-multimedia.org 990 unstableftp.ru.debian.org 500 testing ftp.ru.debian.org 500 stable dl.google.com 500 experimentalmozilla.debian.net 1 experimentalftp.debian.org 1 experimentalcdn.debian.net --- Package information. --- Depends (Version) | Installed =-+-== gir1.2-clutter-1.0(= 1.9.16) | 1.14.4-2 gir1.2-folks-0.6 | 0.6.9-1+b1 gir1.2-glib-2.0 (= 1.31) | 1.36.0-2+b1 gir1.2-gmenu-3.0 | 3.8.0-2 gir1.2-gtk-3.0| 3.8.2-3 gir1.2-mutter-3.0 (= 3.4.1) | 3.4.1-7+b1 gir1.2-networkmanager-1.0 | 0.9.8.0-5 gir1.2-soup-2.4 | 2.42.2-6 gir1.2-telepathyglib-0.12 | 0.20.4-1 gir1.2-telepathylogger-0.2| 0.4.0-1 dconf-gsettings-backend | 0.16.1-1 OR gsettings-backend | gconf-service | 3.2.6-1 gnome-bluetooth(= 3.0.0) | 3.8.1-2 libatk1.0-0 (= 1.12.4) | 2.8.0-2 libc6 (= 2.14) | libcairo-gobject2 (= 1.10.0) | libcairo2 (= 1.10.0) | libcanberra0 (= 0.2) | libclutter-1.0-0 (= 1.10.0) | libcogl-pango12(= 1.7.4) | libcogl12 (= 1.7.4) | libcroco3 (= 0.6.2) | libdbus-1-3(= 1.0.2) | libdbus-glib-1-2(= 0.78) | libebook-1.2-13(= 3.4.4) | libecal-1.2-11 (= 3.4.4) | libedataserver-1.2-16 (= 3.4.4) | libedataserverui-3.0-1 (= 3.4.4) | libegl1-mesa (= 7.8.1) | OR libegl1-x11 | libfolks25 (= 0.6.0) | libgck-1-0(= 2.91.1) | libgconf-2-4 (= 3.2.5) | libgcr-base-3-1(= 3.8.0) | libgcr-ui-3-1 (= 3.8.0) | libgdk-pixbuf2.0-0(= 2.22.0) | libgee2(= 0.5.0) | libgirepository-1.0-1 (= 0.9.2) | libgjs0-libmozjs185-1.0 | libgjs0c (= 1.36.1) | libgl1-mesa-glx | OR libgl1| libglib2.0-0 (= 2.35.9) | libgnome-keyring0 (= 3.2.2-2~) | libgnome-menu-3-0 (= 3.4.2-3~) | libgstreamer0.10-0 (= 0.10.20) | libgtk-3-0 (= 3.3.9) | libical0(= 0.31) | libjson-glib-1.0-0(= 0.13.2) | libmozjs185-1.0 (= 1.8.5-1.0.0+dfsg) | libmutter0 (= 3.4) | libmutter0 ( 3.5) | libnm-glib4 (= 0.8.998) | libnm-util2 (= 0.8.998) | libnspr4 (= 2:4.9-2~) | OR libnspr4-0d (= 1.8.0.10) | libp11-kit0 (= 0.2) | libpango-1.0-0(= 1.14.0) | libpangocairo-1.0-0 (= 1.14.0) | libpolkit-agent-1-0 (= 0.99) | libpolkit-gobject-1-0 (= 0.94) | libpulse-mainloop-glib0 (= 0.99.1) | libpulse0 (= 0.99.1) | libsoup2.4-1 (= 2.4.0) | libstartup-notification0(= 0.11) | libtelepathy-glib0(=
Bug#673705: [Pkg-utopia-maintainers] Bug#673705: Bug#673705: network-manager: Network Manager doesn't connect to wifi (greyed out) when device cannot report signal strength
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry for the ambiguity. I filed a bug against the kernel in Debian about this problem. Here it is: 673703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673703 Anyhow they said it was a hardware/firmware issue and that they wouldn't fix it themselves. They forwarded the issue upstream, to linux-wireless. On 05/20/2012 11:43 PM, Michael Biebl wrote: On 20.05.2012 23:36, Gennady N. Uraltsev wrote: 02:02.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) and the driver is the kernel module ipw2100 I already told them about this and they say it is a hardware/firmware ^ who is them? limitation and they aren't sure it is fixable. I thought this was kernel/driver issue and affected drivers were ipw2100/ipw2200 CCing Dan, maybe he can his insight on this issue. On 05/20/2012 11:06 PM, Michael Biebl wrote: On 20.05.2012 22:55, Gennady N. Uraltsev wrote: There are many cards that have this problem, and I do not see any reason to Which card and driver do you use? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPugW4AAoJEO4X3lPe3Y0xEA8P/32gZVko9cxq+9JGHNVnuBoQ quYSfu0RmekTw5jKMaaFe/nfRJFqgPZA6Smv6Z/bKps0hf36UmPMJQJ2Oi/ZOxKi uTgK3CJ5BuZpy9BUrRSOhjdxhLE5eHEI99VLDPehoQ2fio0AzwfKmc1ZtPMh8985 c5G1cqm4loiULEfF+jtjD7+rnDAm8BhyqS0JfVbhSCgJopr0QMpm7YhvTPb2/JeL TyG/Jodt6eRYENjclIqmmEghgCucm95EV8fw3FjWIWbeG4o4IHgE5aU8FkGBqeUu ecJr1Yby3FcQeFsYadivxqOqGc5g9Va5A0gaRPhYk6WATFgJTaWX2WmDUdVX5BZD 7TukNIn3B+scLAtMf9x0XVwkcAZzSr6VLog47TjdNckdzIvgSlnMxHw/yfjcxjU4 V0jvbsjDGxdo+yy+hlPk2L7GHUNAN+WV/UKNKKT1bhR4iYvypF3rd9cfP8v2QGTl kZvmH80HWLbWSNRlUKX2J4ebF/fJMToi8UBEDAu2rHx7FGkNtAn/m09eJDmVj3C0 89zM/ME82bq9l7DKOt+f+CTrGz/tbcOX8C2siEH3QtWvwdw7/nT+uraEig1CsaAp vfakRaYkWzVqFLn95hRi1qQ3jDDsRpFvitRPXfPYF/Ck9+wfLQCK2+//KmGXPxSQ /dbKMN1jvF4kfUZS+KLV =rd3h -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673703: linux-image-3.2.0-2-686-pae: module ipw2100 doesn't report signal strength
Package: linux-2.6 Version: 3.2.17-1 Severity: important Tags: upstream The ipw2100 module fails to report signal strength. With a Intel 2100 3B mini card this makes it impossible to use standard tools for wireless. As a matter of fact roaming decisions and many others of standard software are based on these values. To illustrate what I am talking about. The command #iwlist eth1 scan outputs: eth1 Scan completed : Cell 01 - Address: 02:18:F8:7A:4E:5E ESSID:eduroam Protocol:IEEE 802.11bg Mode:Master Frequency:2.412 GHz (Channel 1) Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Quality:64 Signal level:0 Noise level:0 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x Extra: Last beacon: 248ms ago Cell 02 - Address: 02:18:39:D4:13:B3 ESSID:eduroam Protocol:IEEE 802.11bg Mode:Master Frequency:2.412 GHz (Channel 1) Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Quality:35 Signal level:0 Noise level:0 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x Extra: Last beacon: 252ms ago Look at the field labeled signal level I do not know how related is the line that sometimes appears in syslog: wpa_supplicant[1826]: bgscan simple: Failed to enable signal strength monitoring Should I file the bug somewhere else? Signal strength monitoring on other wifi cards like usb ones works flawlessly... -- Package-specific info: ** Version: Linux version 3.2.0-2-686-pae (Debian 3.2.17-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 SMP Sun May 13 07:51:23 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-686-pae root=UUID=5a0ffa6d-f75b-430d-af8d-a77bfe7214e8 ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [7.603608] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: clean. [7.603652] pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: clean. [7.603695] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: [7.604118] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1f0-0x1f7 0x2f8-0x2ff 0x370-0x377 [7.605167] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff: excluding 0x3f0-0x3ff 0x4d0-0x4d7 [7.605614] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x820-0x8ff: clean. [7.605989] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcf7: clean. [7.606403] pcmcia_socket pcmcia_socket1: cs: memory probe 0x0c-0x0f: excluding 0xc-0xc 0xdc000-0xf [7.606446] pcmcia_socket pcmcia_socket1: cs: memory probe 0xa000-0xa0ff: clean. [7.606489] pcmcia_socket pcmcia_socket1: cs: memory probe 0x6000-0x60ff: clean. [7.606532] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa00-0xaff: clean. [7.607649] clean. [7.649423] lib80211: common routines for IEEE802.11 drivers [7.649428] lib80211_crypt: registered algorithm 'NULL' [7.818737] libipw: 802.11 data/management/control stack, git-1.1.13 [7.818742] libipw: Copyright (C) 2004-2005 Intel Corporation jketr...@linux.intel.com [7.906101] snd_intel8x0m :00:1f.6: PCI INT B - Link[LNKB] - GSI 5 (level, low) - IRQ 5 [7.906126] snd_intel8x0m :00:1f.6: setting latency timer to 64 [7.958170] snd_intel8x0 :00:1f.5: PCI INT B - Link[LNKB] - GSI 5 (level, low) - IRQ 5 [7.958206] snd_intel8x0 :00:1f.5: setting latency timer to 64 [7.967983] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2 [7.967987] ipw2100: Copyright(c) 2003-2006 Intel Corporation [7.968149] ipw2100 :02:02.0: PCI INT A - Link[LNKC] - GSI 11 (level, low) - IRQ 11 [7.968982] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection [8.380944] cfg80211: failed to add phy80211 symlink to netdev! [8.884045] intel8x0_measure_ac97_clock: measured 55399 usecs (2669 samples) [8.884050] intel8x0: clocking to 48000 [9.030209] cfg80211: World regulatory domain updated: [9.030215] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [
Bug#673705: network-manager: Network Manager doesn't connect to wifi (greyed out) when device cannot report signal strength
Package: network-manager Version: 0.9.4.0-4 Severity: normal If a wireless network card isn't able to report signal strength Network Manager no longer allows connectiong to wifi networks. This was not so in previous versions. All available wireless networks are greyed out. This is due to the fact that the wifi adapter doesn't know how to report signal strength. Connecting through other adapters (external USB) is possible. In particular #iwlist eth1 scan eth1 Scan completed : Cell 01 - Address: 02:18:F8:7A:4E:5E ESSID:eduroam Protocol:IEEE 802.11bg Mode:Master Frequency:2.412 GHz (Channel 1) Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Quality:64 Signal level:0 Noise level:0 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x Extra: Last beacon: 248ms ago and /var/log/syslog has the following line: wpa_supplicant[1826]: bgscan simple: Failed to enable signal strength monitoring There are many cards that have this problem, and I do not see any reason to grey out wifi networks that are reported by iwlist eth1 scan. If a network is reported one can want to try to connect to it. Greying out is useless, IMHO. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages network-manager depends on: ii adduser3.113+nmu2 ii dbus 1.5.12-1 ii dpkg 1.16.3 ii isc-dhcp-client4.2.2.dfsg.1-5 ii libc6 2.13-32 ii libdbus-1-31.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libgcrypt111.5.0-3 ii libglib2.0-0 2.32.3-1 ii libgnutls262.12.19-1 ii libgudev-1.0-0 175-3.1 ii libnl-3-2003.2.7-2 ii libnl-genl-3-200 3.2.7-2 ii libnl-route-3-200 3.2.7-2 ii libnm-glib40.9.4.0-4 ii libnm-util20.9.4.0-4 ii libpolkit-gobject-1-0 0.105-1 ii libuuid1 2.20.1-4 ii lsb-base 4.1+Debian4 ii udev 175-3.1 ii wpasupplicant 1.0-2 Versions of packages network-manager recommends: ii crda 1.1.2-1 ii dnsmasq-base 2.61-1 ii iptables 1.4.13-1.1 ii modemmanager 0.5.2.0-1 ii policykit-1 0.105-1 ii ppp 2.4.5-5.1 Versions of packages network-manager suggests: ii avahi-autoipd 0.6.31-1 -- Configuration Files: /etc/NetworkManager/NetworkManager.conf changed: [main] plugins=ifupdown,keyfile no-auto-default=00:0d:60:89:e5:28, [ifupdown] managed=false -- 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#673705: [Pkg-utopia-maintainers] Bug#673705: network-manager: Network Manager doesn't connect to wifi (greyed out) when device cannot report signal strength
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 02:02.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) and the driver is the kernel module ipw2100 I already told them about this and they say it is a hardware/firmware limitation and they aren't sure it is fixable. On 05/20/2012 11:06 PM, Michael Biebl wrote: On 20.05.2012 22:55, Gennady N. Uraltsev wrote: There are many cards that have this problem, and I do not see any reason to Which card and driver do you use? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPuWP0AAoJEO4X3lPe3Y0x8U4P/jt+3uLpm+WyXgLs/7si8S/T WwZ66Rdf/CTEFxx7yBYKefY8ym0P0JDtakpo71ckn6jVkY8/2cBFizU5cNLkWQIF juAndmvy/7p/NBLvFkx3F8k8kD+JP6wk2HZx+XuQzDQopAQtp1/vcnSmdUfWSkTU rNFP9xCcTIbPksFFhIz9XO/7cWFlsUEvwCsgxiXlViMf5Bt+vMd9acFdJlK6WnZ1 FvOtSXIwv+TfQvC4yMzuK5QRDFnckY6ecnU4Kif8O2JOiZRJvl/R/6vROAgFmuvj 4RWuU1Vm1qSJEHxVP1uouBrrU/6vpX6qLF4RrshuYNaRkWxiY2D0054xjZX+ETq+ CgEw9CASjfmMRuH35OUia19y3D7q+v923Iwyd23WWLUGMGjl+BaA7+M+3xlD/7M9 eRAn5vA4+H+lqaITNkDGLGavJakWH7BYBrtrXZhUDeKWK/NX6BEGLOH22Xzrtkjm XgyRuwhu0p0Q0ZlY4WM3vxT63CHmmuO7QghAvtJaslDPOSFBu+d7jJ8GU/Jt//CR UdP22zoqEl0nzEcpQIcUvexpM2LbQg5OR1vk3yP6IQFiVOeR1dO5lxuXwUBEVPOe 91T6eAkqRZuqgcgOF6v+yQCSCVEOTGj0nppvywlzjaE14DcKF9/RSmWkp4sjDNkw 5lBsIOqWVF9UDXUpmVgC =rnK/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578668:
This one may be closed because keys are working now. Ridiculous approach to reproduction. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668422: patchutils: manual page for editdiff is not displayed
Package: patchutils Version: 0.3.2-1.1 Severity: minor LANG=C man editdiff doesn't display man page: gena@work:~$ LANG=C man editdiff man: can't open /usr/share/man/rediff.1: No such file or directory man: can't open /usr/share/man/rediff.1: No such file or directory man: can't open /usr/share/man/rediff.1: No such file or directory No manual entry for editdiff See 'man 7 undocumented' for help when manual pages are not available. While man rediff working well. work:/home/gena# dpkg -S `which man` man-db: /usr/bin/man work:/home/gena# dpkg -l man-db|grep man-db ii man-db 2.6.1-2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-rc7XMin-00103-g0c4d067 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages patchutils depends on: ii debianutils 4.2.1 ii libc62.13-27 ii patch2.6.1-3 ii perl 5.14.2-9 patchutils recommends no packages. patchutils suggests no packages. -- no debconf information With best regards, Gennady -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664725: Info received (linux-image-3.2.0-2-rt-686-pae: Real-time kernel freezes immediately at boot most of the time)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello everyone, Sorry for the delay but I have not yet found a way to get the debug messages. I disabled the quiet option but there are some problems with saving the debug messages. Netconsole starts too late and I do not have a serial port. I will try to take a photo and to copy the info that gets displayed. However I wanted to tell you that I found out that the problem disappears if the grub option set gfxpayload=keep is removed, aka the framebuffer mode is not used. Will write more about this tomorrow. BTW I upgraded the kernel to the latest one available in sid: Package: linux-image-3.2.0-2-rt-686-pae New: yes State: installed Automatically installed: yes Version: 3.2.14-1 and the problem is still there. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPhhq4AAoJEO4X3lPe3Y0xlrYQANon/yxooIHjAZanAdA+7juz Lt9NOWAr9jAiNGoG9EQq2Xp6eBYle4ludC/rOKN9U45ZPip7cpUklB7lZ5wGvJZ+ TWe098RZ/cDNq/oTTjHfN7wmgu31ldLkMGYJQi42DIr94DAWlGKgEDqB8e3egiaD 3NGn9r0iO2v9oc5xIoBOyCVgHJZqFecemWBrNZHeBOZUMENTHihvWoa3W08bw/PG pTIhK3sHTnM4tgzvW1Y8416TkXYQoGXuN76vAFgMqKjS9la02QWxHxDJ998hG9GR LDLDnQMNFLY8OEiBZ6kZvJO6f7zenLp395ta41ptAPnJEVox/FrPVwIzANOl2dV9 HAaAoOzqLbbjYkL7lKotb9nvXBZ3Gktyab4acmjNCHTKNfEU1anxbdD75Lfwx5oe JfWrFxqY7yYj2KUTmGlH+AXLks90oSicPwI91W2SG0Ewz+E4BCMcZs+r7spRSGOx umDX1E5Psy0RWgVuzJaiAg3fD1PuY8LNyuOx7gHC6kuw/AhceB0nNB1fj4nI5/ae 6IBvD6XZSKha8Xir7qcsPRuchibk4Psv8s3+y3EPTpUzSvkP0Ryvb2q4AWmbeH+D mJtwePSYQSRhPGxE6rKze1D4jlCoa0H4BXbUrTI4gnQNmAXcqvI3YQ7TDLl1Tt4X nnYntJCRvL1U2wJXLzJI =8WDT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667729: network-manager-gnome: Protected wireless networks are greyed out. Unable to connect through applet.
Package: network-manager-gnome Version: 0.9.4.1-1 Severity: important When clicking on the nm applet the wireless networks whose signal is present are presented in a list but all the entries for protected networks are greyed out and thus unclickable. The only way I found to connect to a protected network is to manually go to Edit Connections and add a wireless connection with the correct SSID and password. This does NOT make the list entry clickable, no matter what settings one chooses for the option make available to all users. Finally, after setting up a connection this way, from root I do: /etc/init.d/network-manager restart then the network-manager restarts and by default connects to the wireless network. However this is a very dirty workaround and because of this network- manager is essentially unusable for managing wireless networks. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages network-manager-gnome depends on: ii dbus-x11 1.5.12-1 ii dpkg 1.16.2 ii gconf-service3.2.3-4 ii gconf2 3.2.3-4 ii gnome-icon-theme 3.4.0-2 ii libatk1.0-0 2.4.0-2 ii libc62.13-27 ii libcairo-gobject21.12.0-2 ii libcairo21.12.0-2 ii libdbus-1-3 1.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libfontconfig1 2.8.0-3.1 ii libfreetype6 2.4.9-1 ii libgconf-2-4 3.2.3-4 ii libgdk-pixbuf2.0-0 2.26.0-2 ii libglib2.0-0 2.32.0-3 ii libgnome-bluetooth8 3.2.2-1 ii libgnome-keyring03.4.0-1 ii libgtk-3-0 3.2.3-1 ii libnm-glib-vpn1 0.9.4.0-3 ii libnm-glib4 0.9.4.0-3 ii libnm-gtk0 0.9.4.1-1 ii libnm-util2 0.9.4.0-3 ii libnotify4 0.7.5-1 ii libpango1.0-01.30.0-1 ii network-manager 0.9.4.0-3 ii policykit-1-gnome0.105-2 Versions of packages network-manager-gnome recommends: ii gnome-bluetooth3.2.2-1 ii iso-codes 3.34-1 ii libpam-gnome-keyring [libpam-keyring] 3.2.2-2 ii mobile-broadband-provider-info 20120402-1 ii notification-daemon0.7.4-1 ii xfce4-notifyd [notification-daemon]0.2.2-1 Versions of packages network-manager-gnome suggests: ii network-manager-openvpn-gnome 0.9.4.0-1 ii network-manager-pptp-gnome 0.9.4.0-2 ii network-manager-vpnc-gnome 0.9.4.0-1 -- 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#667729: [Pkg-utopia-maintainers] Bug#667729: network-manager-gnome: Protected wireless networks are greyed out. Unable to connect through applet.
This is the output of ck-list-sessions: Session6: unix-user = '1000' realname = 'Gennady N. Uraltsev' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2012-04-06T12:42:41.925371Z' login-session-id = '' On 04/06/2012 02:20 PM, Michael Biebl wrote: On 06.04.2012 12:08, Gennady N. Uraltsev wrote: When clicking on the nm applet the wireless networks whose signal is present are presented in a list but all the entries for protected networks are greyed out and thus unclickable. The only way I found to connect to a protected network is to manually go to Edit Connections and add a wireless connection with the correct SSID and password. This does NOT make the list entry clickable, no matter what settings one chooses for the option make available to all users. Finally, after setting up a connection this way, from root I do: /etc/init.d/network-manager restart then the network-manager restarts and by default connects to the wireless network. However this is a very dirty workaround and because of this network- manager is essentially unusable for managing wireless networks. What's the output of ck-list-sessions? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664725: linux-image-3.2.0-2-rt-686-pae: Real-time kernel freezes immediately at boot most of the time
Package: linux-2.6 Version: 3.2.10-1 Severity: important Tags: lfs When trying to boot the 3.2.0-2-rt-686 kernel on my machine it freezes most of the time. In particular just after grub finishes loading the kernel and the initrd and proceeds to boot the kernel the message Loading Linux or something of that sort appears, the cursor blinks a couple of times (so far everything as usual) but then the cursor stops blinking and disappears completely and the system is completely unresponsive. Caps Lock, alt+sysrq+... and other keys don't have any effect. Normally, the message that appears immediately after this on my pc, when a normal kernel is run, is a debug message from udev (I think) described in: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654282 but that is NOT fatal and is present on all kernels (even the non rt ones). However in this case nothing of the sort is displayed. This problem seems very similar to the one in bug report 63269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663269 that has been said to be fixed. As a matter of fact I have noticed one difference: with version 3.2.10-1 (current), if I load a normal, non-rt kernel first then restart my pc and load the rt kernel the machine usually starts and doesn't hang and works perfectly, while normally (for example running the rt kernel for two times in a row) causes the machine to freeze. On the other hand, with version 3.2.9-1 there was absolutely nothing to be done to make the machine boot with the rt-kernel. This strange behaviour makes me suspect that something may depend on the way grub is booting the kernel (maybe some options that persist across boots). However I have no idea how to debug this. If someone gives me some hints I would be willing to provide any additional information. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O Controller [8086:3340] (rev 03) Subsystem: IBM Thinkpad T40 series [1014:0529] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Region 0: Memory at d000 (32-bit, prefetchable) [size=256M] Capabilities: access denied Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP Controller [8086:3341] (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 96 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 I/O behind bridge: 3000-3fff Memory behind bridge: c010-c01f Prefetchable memory behind bridge: e000-e7ff Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01) (prog-if 00 [UHCI]) Subsystem: IBM ThinkPad [1014:052d] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 4: I/O ports at 1800 [size=32] Kernel driver in use: uhci_hcd 00:1d.1 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01) (prog-if 00 [UHCI]) Subsystem: IBM ThinkPad [1014:052d] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 11 Region 4: I/O ports at 1820 [size=32] Kernel driver in use: uhci_hcd 00:1d.2 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 01) (prog-if 00 [UHCI]) Subsystem: IBM ThinkPad [1014:052d] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin C routed to IRQ 11 Region 4: I/O ports at 1840 [size=32] Kernel driver in use: uhci_hcd 00:1d.7
Bug#578668: [Pkg-alsa-devel] Bug#578668: alsa-utils: most of volume management keys in alsamixer are not working
В Птн, 23/04/2010 в 19:19 +0200, Elimar Riesebieter пишет: * Gennady Kupava [100423 01:36 +0400] [added buglog to recepients again] ?? ??, 22/04/2010 ?? 19:03 +0200, Elimar Riesebieter ??: Urgh... because: Yes, this may be related to pulseaudio. But I (as a user) can see this as a regression in alsamixer. Even amixer works well. What happens if you do: mv ~/.asoundrc ~/.asoundrc.bak I have no sound card except pulseaudio one. FYI pulseaudio is _not_ a sound driver but a sound server. You should hear sound with every ALSA soundcard with out any pulseaudio participation. So, if i'll do that you suggest I just get system without sound card at all and alsamixer would not start. I don't. Your soundcard will work. If i'll do this and install snd-dummy sound card alsamixer will perform well and in expected way. All this is written in my previous post. Not needed. It seems to be more a problem of that pulsaudio thingi. Mb alsamixer, mb libasound, mb libpulse, mb pulseserver, mb alsa on server side. But I see regression in alsamixer - downgraded only alsa-utils and alsamixer works well. Also I see that this is reproducible. What does Mb and mb mean? Well it is not reproducible for me as a user. Please remove unreproducible tag if you can reproduce this following my instructions. No, I can't reproduce and won't test pulseaudio. Please change bug title to 'most of volume management keys in alsamixer are not working with pulseaudio sink' to make it more descriptive. You can file this as a pulseaudio bug then. I won't ;-) Thanks, Gennady. Elimar FYI pulseaudio is _not_ a sound driver but a sound server. You should hear sound with every ALSA soundcard with out any pulseaudio participation. FYI I am software developer and use Linux for more than 10 years. I even have 1 my patch in libasound. I know how exactly things are working. This report is not against 'sound driver'. It's about alsamixer. In this case you may consider pulseaudio client side as 'driver'. alsamixer name it 'sound card' - why not? I don't. Your soundcard will work. I have no sound card. I have no speakers connected to machine. what do you think will work on that system? Read bug report, I spend much time writing it to make reproduction as easy as possible and problem as clean as possible. What does Mb and mb mean? Well it is not reproducible for me as a user. MB=may be. No, I can't reproduce and won't test pulseaudio. If you do not want to reproduce this problem - no problem, but remove tag. Because your unwilling to reproduce do not mean it is not reproducible. You can file this as a pulseaudio bug then. I won't ;-) If you think bug is in other package, can you request changing package for this bug? Gennady. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578668: [Pkg-alsa-devel] Bug#578668: alsa-utils: most of volume management keys in alsamixer are not working
[added buglog to recepients again] В Чтв, 22/04/2010 в 19:03 +0200, Elimar Riesebieter пишет: Urgh... because: Yes, this may be related to pulseaudio. But I (as a user) can see this as a regression in alsamixer. Even amixer works well. What happens if you do: mv ~/.asoundrc ~/.asoundrc.bak I have no sound card except pulseaudio one. So, if i'll do that you suggest I just get system without sound card at all and alsamixer would not start. If i'll do this and install snd-dummy sound card alsamixer will perform well and in expected way. All this is written in my previous post. It seems to be more a problem of that pulsaudio thingi. Mb alsamixer, mb libasound, mb libpulse, mb pulseserver, mb alsa on server side. But I see regression in alsamixer - downgraded only alsa-utils and alsamixer works well. Also I see that this is reproducible. Please remove unreproducible tag if you can reproduce this following my instructions. Please change bug title to 'most of volume management keys in alsamixer are not working with pulseaudio sink' to make it more descriptive. Thanks, Gennady. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578668: alsa-utils: most of volume management keys in alsamixer are not working
Package: alsa-utils
Version: 1.0.22-1
Severity: important
In alsamixer, keys q,w,e,z,x,c,[arrow up], [arrow down] are not working for me
(this continues for 1 month), while 1,2,3,4... 0 are ok, amixer sset is ok
also.
This is extermly annoying, as I my sound system is regulated in range of
0.5-10% while 10% is very loud.
Sound card is pulseaudio:
cat ~/.asoundrc
pcm.!default {
type pulse
server 192.168.0.1
}
ctl.!default {
type pulse
server 192.168.0.1
}
g...@work:~$ amixer
Simple mixer control 'Master',0
Capabilities: pvolume pswitch pswitch-joined penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 65536
Mono:
Front Left: Playback 2000 [3%] [on]
Front Right: Playback 2000 [3%] [on]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch cswitch-joined penum
Capture channels: Front Left - Front Right
Limits: Capture 0 - 65536
Front Left: Capture 65536 [100%] [on]
Front Right: Capture 65536 [100%] [on]
g...@work:~$
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32.2XMin (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages alsa-utils depends on:
ii dialog1.1-20100119-2 Displays user-friendly dialog boxe
ii libasound21.0.22-2 shared library for ALSA applicatio
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libncursesw5 5.7+20100313-2 shared libraries for terminal hand
ii linux-sound-base 1.0.21+dfsg-2 base package for ALSA and OSS soun
ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip
ii module-init-tools 3.12~pre2-3tools for managing Linux kernel mo
ii udev 151-3 /dev/ and hotplug management daemo
ii whiptail 0.52.10-8 Displays user-friendly dialog boxe
Versions of packages alsa-utils recommends:
ii alsa-base 1.0.21+dfsg-2 ALSA driver configuration files
ii pciutils 1:3.1.7-3 Linux PCI Utilities
alsa-utils 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#578668: [Pkg-alsa-devel] Bug#578668: alsa-utils: most of volume management keys in alsamixer are not working
[added correct destination]
В Срд, 21/04/2010 в 19:53 +0200, Elimar Riesebieter пишет:
tags 578668 unreproducible
thanks
* Gennady Kupava [100421 19:25 +0400]
Package: alsa-utils
Version: 1.0.22-1
Severity: important
In alsamixer, keys q,w,e,z,x,c,[arrow up], [arrow down] are not
working for me (this continues for 1 month), while 1,2,3,4... 0
are ok, amixer sset is ok also.
This is extermly annoying, as I my sound system is regulated in
range of 0.5-10% while 10% is very loud.
AlsaMixer v1.0.22: Works fine here. I can't reproduce on amd64, i386
and ppc.
BTW the keys are: QWEZXC and not qwezxc
Press F1 in alsaxixer for an overview.
Elimar
Why this is bug not wrong setup: That should i do with alsamixer to have
1,2,3 working (sets 10%, 20% and so volume) and [arrow up] do not?
About keys case: And keys always were in both lower and upper case (also
checked alsamixer 1.0.16 on i386), lower - faster, upper - slower tuning
in 1.0.16.
About reproduction:
I downgraded to 1.0.16-2 and everything started to work. Upgraded back
to 1.0.22-11 and hit bug again.
I setup pulseaudio tcp server on snd-dummy sound card on client machine
and got same problem.
While changing volume on dummy card all keys are working perfectly
[switching with that new F6 key in alsamixer].
HOW TO REPRODUCE:
I think to reproduce it you should setup pulseaudio over network. Mb
some other cases exist.
on server, apt-get install pulseaudio. (i am using debian/stable/i386)
in following description server is 192.168.0.1, client is 192.168.0.2
Use following config for server (only changed parts):
/etc/default/daemon.conf:
system-instance = yes
resample-method = speex-float-3
daemonize = yes
FOR 'STABLE' PULSEAUDIO: /etc/pulse/default.pa (only important parts):
load-module module-alsa-sink plughw:0,0
load-module module-native-protocol-tcp auth-ip-acl=192.168.0.1/24
OR FOR 'TESTING' PULSEAUDIO (notice file name): /etc/pulse/system.pa
(only important parts):
load-module module-alsa-sink plughw:0,0
ADD FOLLOWING: load-module module-native-protocol-tcp
auth-ip-acl=192.168.0.1/24
on server enable daemon in /etc/default/pulseaudio set:
PULSEAUDIO_SYSTEM_START=1
then start server /etc/init.d/pulseaudio restart. wait 1 min and check
if it is still around and on tcp:
work:/home/gena# netstat -atnp |grep pulse
tcp 0 0 0.0.0.0:4713 0.0.0.0:* LISTEN 7923/pulseaudio
if not, run without daemon command-line with --daemonize=no and -v
options to see why he is died.
on client (under any user):
$ cat ~/.asoundrc:
pcm.!default {
type pulse
server 192.168.0.1
}
ctl.!default {
type pulse
server 192.168.0.1
}
this will make remote tcp pulse server default alsa card for playing and
for volume changing.
on client apt-get install libasound2-plugins,
now run alsamixer on client under same user - you should hit bug.
I got this few moths ago, I just didn't report it as i thought it were
already reported.
Hope this way you'll be able to reproduce it.
While testing i also hit other bug on arm/sid, which worked some time
ago, so i unable to test this issue where...
I had to add that this related to pulse to header, but didn't understand
in time that i can simple check if problem exist on dummy card
controls...
And thanks for doing Debian!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505097: pulseaudio: eats CPU. CPU usage increase over time
Paul, If the bug is still present, could you please test the latest upstream version 0.9.21 and this does not help open a ticket upstream [3]. You seem to know OProfile so you can probably find the reason with upstream’s help. I workarounded this problem by pinning old pulseaudio from etch (0.9.5-5etch1), which works fine for me. Retesting each case of this will take some time due to nature of issue. I'll retest issue with 0.9.10-3+lenny1, test backport and upstream version. testing upstream version will take even more time as i have no environment to build packages for lenny. If this issue still exist in upstream/latest, I'll write bugreport to upstream tracking system. All this will take some time, but I have some now. I'll report results to this bug report as they be ready. Gennady. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#490159: update
Can you reproduce this with Lenny? If so, what about latest intel
driver in unstable?
Sorry for delay, mailbox full of spam.
It's ok for a while, I'm on rarely updated unstable/x86 now. Problem
seem fixed.
$ dpkg -l|grep xorg|egrep -v '(video-[^i]|input)'|awk '{print $1 $2 $3}'
iixserver-xorg1:7.4+4
iixserver-xorg-core2:1.6.3.901-1
iixserver-xorg-video-i1281:1.3.2-1
iixserver-xorg-video-i7401:1.3.0-1
iixserver-xorg-video-intel2:2.8.1-1
---
Gennady
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548321: #548321 [xterm] abort() a bit after catting binary file
Verified it here - no more crash. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548321: #548321 [xterm] abort() a bit after catting binary file
Is this running in koi8rxterm (which sets locale to ru_RU.KOI8-R and turns on the -k8 option), or just in xterm by itself? Just in plain xterm. bash shell, wmaker window manager. Farther, catting larger portion of this file abort()s it without resizing. I am running: $xterm -e /bin/dash In new xterm: $zcat ~/Desktop/fail.gz Resize window 1 character right, it aborts. Locale setting is en_US.UTF-8. I get xterm and libutempter0 debs to my nearby debian testing-favor box. With original packages (xterm 235-2 and no libutempter), i got no abort. With newly upgraded xterm I reproduced it where. LANG=ru_RU.UTF-8, xfce window manager where. Mb you didn't extract it? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505097: pulseaudio: eats CPU. CPU usage increase over time
After upgrading my router (old 600Mhz celeron PC), which is also my 24/7 network sound server with pulseaudio from etch to lenny, I've got similar very annoying problem. After few hours (always if router was working overnight), I am getting jerks with any freshly run client, so I have to go router with ssh and manually restart pulseaudio service, after that it works for the next few hours. I can't recall if any connected client get this jerks in middle of it's work, even sometimes I have low volume music or video playing for the long time. Observations on router tell me that just after restart, playing same thing on client (client is different machine with ethernet connection to router) - ape with mplayer takes ~27.4 with freshly restarted pulseaudio, as far as I saw last time jerks happen than cpu usage is too high. So, I far as I can see, pulseaudio CPU usage is increasing over time, and that seem several bug. Also this is somehow related to idle time. Also, it eats CPU while idle. PA is running with CPU limit off. The client system seems were not changed except that it is unstable debian. Up-to-date Lenny setup: Package: pulseaudio Architecture: i386 Version: 0.9.10-3 router2:~# cat /etc/pulse/daemon.conf|egrep -v '(^#|$^|;)' verbose = 0 high-priority = 1 disallow-module-loading = 1 router2:~# cat /etc/pulse/default.pa|egrep -v '(^#|$^|;)' load-module module-alsa-sink device=default .ifexists /usr/lib/pulse-0.9/modules/module-esound-protocol-unix.so .endif load-module module-native-protocol-unix auth-anonymous=1 load-module module-native-protocol-tcp auth-anonymous=1 load-module module-volume-restore load-module module-rescue-streams .nofail I did oprofile some time ago, but this seem not very informative: router2:~# opreport CPU: CPU with timer interrupt, speed 0 MHz (estimated) Profiling through timer interrupt TIMER:0| samples| %| -- 1477 92.1397 no-vmlinux 39 2.4329 libasound.so.2.0.0 34 2.1210 libpulsecore.so.5.0.1 29 1.8091 libc-2.7.so 5 0.3119 module-alsa-sink.so 4 0.2495 libpthread-2.7.so 4 0.2495 ld-2.7.so 3 0.1871 dash 3 0.1871 pulseaudio TIMER:0| samples| %| -- 3 100.000 [vdso] (tgid:18758 range:0xb7f96000-0xb7f97000) 1 0.0624 libproc-3.2.7.so 1 0.0624 gawk 1 0.0624 oprofiled 1 0.0624 top 1 0.0624 sshd TIMER:0| samples| %| -- 1 100.000 [vdso] (tgid:16862 range:0xb7ee8000-0xb7ee9000) router2:~# opcontrol --status Daemon not running Separate options: none vmlinux file: none Image filter: none Call-graph depth: 0 Thank you for debian! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#490159: same here
Package: xserver-xorg-video-intel Version: 2:2.3.2-2+lenny6 I am getting random lookups - once per week or so. Computer is working 24/7. It always freeze than I do something useful - no freeze than idle. Last time I was moving gimp window to be visible in half, leaving other out of screen, upper region, this was second such window. X freezes for a while, than attempts to restart without success. Running X again have no success until reboot, with following error in logs: Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0x0001 getbl_err: 0x ipeir: 0x iphdr: 0x7d06 LP ring tail: 0xf0d0 head: 0xf0ec len: 0x0001f001 start 0x eir: 0x esr: 0x emr: 0x instdone: 0xfa41 instpm: 0x memmode: 0x0306 instps: 0x80007826 hwstam: 0xfffe ier: 0x0002 imr: 0x iir: 0x0080 Ring at virtual 0xa799a000 head 0xf0ec tail 0xf0d0 count 32761 f06c: 0200 f070: 54f6 f074: 03cc2000 f078: 001401d4 f07c: 001801d8 f080: 0100 f084: f088: 0010 f08c: 0200 f090: 54f6 f094: 03cc2000 f098: 001401d8 f09c: 001801dc f0a0: 0100 f0a4: f0a8: 0010 f0ac: 0200 f0b0: 54f6 f0b4: 03cc2000 f0b8: 001401dc f0bc: 001801e0 f0c0: 0100 f0c4: f0c8: 0010 f0cc: 0200 f0d0: 0720 f0d4: f0d8: 0720 f0dc: f0e0: 0720 f0e4: f0e8: 0720 f0ec: Ring end space: 20 wanted 32 (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8e4c000 at 0xb7acb000 (II) intel(0): [drm] Closed DRM master. Fatal server error: lockup g...@kupava:~/prg/camspeed/iman/data/cam_measure$ lspci|grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10) g...@kupava:~/prg/camspeed/iman/data/cam_measure$ less /var/log/Xorg.0.log|head X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-10) Current Operating System: Linux kupava 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 Build Date: 09 January 2009 02:57:16AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Log of normal X run is in attachment Xorg.0.log Description: Binary data
Bug#511190: qemubuilder: builds hang because pseudo-fs are not mounted
I used kernel provided by Nikita and got hangs several times. Once I got in while --update. My main problem was that I got hang then I was tring to package my software. After adding some new packages to depends I got hung on last Setting up ... 0.invalid.0 line, with CPU load of qemu process equal to 100%. All hungs are 100% reproducible, I mean I can rerun qemubuilder with same options for same package or for same image to --update, it always hung in same place. I think that best way to reproduce it is to try to install openssh-server inside qemu with --login option, while running qemu as simple wrapper: file /usr/bin/qemu-system-arm: exec /usr/bin/qemu-system-arm__ $@ -redir tcp:10022::22 and try to connect it as ssh r...@0 -p10022 Without devpts mounted, you get following message: r...@0's password: PTY allocation request failed on channel 0 stdin: is not a tty , and it's impossible to get command promt on ssh, but connection is OK, if you mount devpts, all is OK. I'm not really familiar with devpts, but on my AMD64's with custom kernel and x86 with 2.6.26-1 debian testing kernel devpts seems mounted, and this is done in /etc/init.d/mountdevsubfs.sh:20, which is member of initscripts package. I've rechecked ordinary initrd: work:/tmp/i# LANG=C grep -rnw devpts * Binary file lib/libc.so.6 matches So, it seen anyway mounted in ordinary boot procedure. As you seem skip initscripts, running pbuilder-run instead of init, it seems that it's better to do that mounting job. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#296047: Source
with letter Copyright All http://img444.imageshack.us/img444/4379/5jlaol5.png Related No topics that begin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#333081: indians
jakoci ISO zio zip genius zipfiler http://img444.imageshack.us/img444/5336/5dpmtm9.gif imienia zestawy kina domowego zeta -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407593: mc ask for input while viewing files if it encounts special byte; some KOI8-R symbols viewed as control symbols resulting very pleasant garbage on terminal
Package: mc
Version: 1:4.6.1-6
Severity: normal
I've write following program to help localize this bug:
-
#include sys/types.h
#include sys/stat.h
#include fcntl.h
#include stdio.h
#include stdlib.h
#include string.h
const char* text=AA\n;
int main() {
int fa,fb;
for (fa=0;fa255;fa++)
for (fb=fa;fb255;fb++) {
if (fa'a'fa'z'||fa'A'fa'Z')
break;
if (fb'a'fb'z'||fb'A'fb'Z')
break;
char buf[100];
sprintf(buf,%d_%d.tst,fa,fb);
int fd=creat(buf,O_WRONLY);
unsigned char fc;
for (fc=fa;fcfb;fc++)
write(fd, fc, 1);
write(fd, text, strlen(text));
close (fd);
};
return 0;
}
--
I find that, after running this program,
1. opening the 154_155.tst file
for view (just pressing F3) automagically brings to terminal Enter
regilar expression dialog with 1;2c text pre-entered to it.
Such behavior produces extra pleasure then you open any binary file
(especially that mistakenly open for view), becouse sometimes where is
no way get rid of Enter regular expression dialog with text
preentered except killing mc by pid.
Also, this feature carefully prevents me from using this new bright
version of mc as a hex editor/viewer in normal way - that was my
famous hex editor and viewer.
2.Opening 128_129.tst file give me some garbage on screen. First symbol
seem missing completely.
This bug seem very stable and reproduce itself for several months.
I hope I can help somehow...
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-2-686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Versions of packages mc depends on:
ii libc62.3.6.ds1-4 GNU C Library: Shared
libraries ii libglib2.0-0 2.12.4-1The GLib library
of C routines ii libgpmg1 1.19.6-22 General
Purpose Mouse - shared lib ii libslang22.0.6-4
The S-Lang programming library - r
mc recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
