Bug#783929: [mnemosyne-proj-devel] SM-2 bug with patch
Dear Peter, On Sun, May 03, 2015 at 07:50:44AM +0200, Peter Bienstman wrote: It is rule 5 of the SM2 algorithm that is not being executed at all for cards graded 0 or 1 But rule 6 says not to apply rule 5 for failed cards: If the quality response was lower than 3 then start repetitions for the item from the beginning without changing the E-Factor It doesn't say that. It says that rule 6 applies only to cards with grades 0 and 1. It doesn't and shouldn't say anything about the applicability of rule 5 in rule 6! That information belongs in rule 5, which says nothing about treating differently graded cards differently, apart from the value of the EF increment. In fact, the page with the algorithm that you linked to has a link at the bottom to an example implementation. In that implementation, rule 5 is applied to all cards, regardless of the grade. Mnemosyne is really not using rule 5 correctly. I guess the reasoning behind this was that after a lot a repetitions, increasing the difficulty as well as resetting the interval was considered too big of a penalty. I agree in the corner case you mention (immediately failure), this seams suboptimal, but remember that this is not an exact science, and the idea is that after many repetitions and corrections by the user, the intervals and easiness factors converge to something which is roughly OK. Failing to recall it after a lot of repetitions indicates that the intervals were too long. Starting again without decreasing the easiness will just repeat this. Since the intervals grow very rapidly anyway (exponentially), an EF that is a bit too low is not very problematic. However, a failure to recall a card is very serious and carries a very serious penalty: the interval is reset to 1 day. That's much worse than a slightly lower EF. So learning will be more efficient if a card is rated a bit too difficult, and never forgotten, rather than a bit too easy, and occasionally forgotten. Since, as you say, the EF should converge to a roughly OK value in the very long term anyway, the penalty to the EF that is incurred by a failure to recall has no serious consequences for the interval lengths in the very long term. But, after 0 or 1, the card has to be learned again from scratch. Once the intervals have grown again, the EF will converge. The EF penalty that goes with the reset therefore will only affect the short and intermediate term intervals. And that is where it improves the learning efficiency. I'm hesitant to change the scheduler now after so many years without detailed statistical analysis to back up any change. The data is there in the collected learning logs, but analyzing it has not yet made it to the top of my list. By fixing the scheduler now and implementing the algorithm as designed, you could actually get some interesting statistics for a comparison. Of course, putting a comment in the Mnemosyne documentation to explain the situation is much easier than analysing the data. With the current scheduler you really cannot claim that you are using SM2 as you are doing now in the docs, and you cannot make that claim either in any scientific publication based on the data that comes out of Mnemosyne. But if that is ok, because the precise algorithm is not important for what you want to do with this data, then there is no reason not to fix the scheduler now. Best regards, Astrid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783929: [mnemosyne-proj-devel] SM-2 bug with patch
On Sun, May 03, 2015 at 10:04:55AM +0200, Peter Bienstman wrote: But rule 6 says not to apply rule 5 for failed cards: If the quality response was lower than 3 then start repetitions for the item from the beginning without changing the E-Factor It doesn't say that. It says that rule 6 applies only to cards with grades 0 and 1. It doesn't and shouldn't say anything about the applicability of rule 5 in rule 6! As I see it, it does, because rule 6 says not to change the easiness for failed cards, and changing the easiness is what rule 5 is all about. Ergo, rule 6 says to ignore rule 5 in this case. But I think we can at least agree that this description is worded awkwardly and confusingly, especially if it contradicts code snippets! I agree that the wording of the SM2 algorithm is a bit confusing. A description for an algorithm like this is not just a set of rules, it's a set of steps to take, including the order to take them in. What it says on careful reading is that you should not change the easiness while executing step/rule 6. That's not the same as retroactively taking back step 5. So the admittedly somewhat obfuscated formulation and the example code from the website in your link are in fact consistent. But, the current mnemosyne scheduler is not consistent with the intended algorithm or the misinterpretation, because it also does something weird when the new grade of a reviewed card is 2. But if that is ok, because the precise algorithm is not important for what you want to do with this data, then there is no reason not to fix the scheduler now. I agree. Excellent! I look forward to the update. Best regards, Astrid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783929: [mnemosyne-proj-devel] SM-2 bug with patch
On Sun, May 03, 2015 at 06:30:03PM +0200, Peter Bienstman wrote: But if that is ok, because the precise algorithm is not important for what you want to do with this data, then there is no reason not to fix the scheduler now. I agree. Excellent! I look forward to the update. Oops, I misread your mail as there is no reason to fix the scheduler now :-) Anyway, I'd be happy to tweak the scheduler, but I'd like to back it up with statistical data analysis first, especially since this behavior has been in place for almost 10 years, and people are used to it. People are also used to programs doing what it says in the documentation. If you aren't going to fix the scheduler, then at least mention this difference with SM2 in the docs. It is a pretty major deviation, and one sentence is easy to write. Or, better yet, you could create an option. Best regards, Astrid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783929: [mnemosyne-proj-devel] SM-2 bug with patch
Dear Peter, On Sat, May 02, 2015 at 08:04:09PM +0200, Peter Bienstman wrote: Worse, cards that the user reviews precisely on time, but fails to recall (grade 0 or 1) end up with higher easiness scores than cards that the user can recall, but barely or with serious effort (grades 2 and 3). Are you really sure that is what you intended? It is a pretty major deviation from the original SM2 algorithm. If you fail to recall the card (grade 0 or 1), the easiness stays the same, but the interval gets reset to zero. A similar thing happens in the original SM2. See rule 6 in http://www.supermemo.com/english/ol/sm2.htm It is rule 5 of the SM2 algorithm that is not being executed at all for cards graded 0 or 1, and incorrectly for cards graded 2. Let me give you an example: 2 cards, A and B are memorised for the first time. They are then reviewed for the first time. The user forgot card A, and grades the answer 0 or 1. The easiness is not updated, and remains 2.5, but the interval is reset. For the other card, the user grades their answer 3. The easiness is updated and becomes 2.36. The next day, card A has to be learned again. After the second interval of 6 days, assuming the user grades their answer 4 every time, the interval of card A will grow exponentially with a factor of 2.5 each time. Meanwhile, for card B, the interval will grow with only factors of 2.36. So the user performed worse on card A than on card B, and yet the interval of card A grows faster. Moreover, if at some future date both cards are forgotten and have to be learned again, then card B will still repeated more often than card A, even though the user's performance indicates that it is easier for them to remember. This is clearly not the intention of the SM2 algorithm, where card A's easiness should have been updated to 1.7 or 1.96, depending on the grade of the answer. In the real SM2 algorithm, card A would then be repeated more often the next time it has been learned successfully. In the documentation you explain the differences between Mnemosyne and SM2. It states The Mnemosyne algorithm is very similar to SM2 used in one of the early versions of SuperMemo. There are some modifications that deal with early and late repetitions, and also to add a small, healthy dose of randomness to the intervals. The difference in behaviour in this bugreport is not at all covered by that statement. The problem appears also for timely reviews, and it has no randomness. That is why it must be unintentional and why I am not so sure that you understand the nature of this bug. So, why not just fix this by applying my patch? Otherwise, you should really update that comment in the documentation to make it clear what you've changed compared to the actual SM2 algorithm. That way, at least it won't be an undocumented feature anymore. Best regards, Astrid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783929: mnemosyne: easyness not updated according to SM2 algorithm
Package: mnemosyne Version: 2.2.1-2 Severity: normal Tags: upstream patch Dear Maintainer, According to its documentation, mnemosyne follows the SM2 algorithm for determining how to schedule cards (http://www.supermemo.com/english/ol/sm2.htm). When revising a card one scores the answer from 0 to 5, with 0 being a complete blackout and 5 easy and correct answer. According to the SM2 algorithm the easyness score of a card should then be updated depending on the grade of the answer. The interval for revision is adjusted according to this easyness score. I forget some cards repeatedly after one or two revisions, because I find them difficult, so I give them 0 and 1 grades, yet the easyness remains constant. If I give them 2 or 3 grades, which should correspond to better, more correct, answers, the easyness of the cards is decreased. For grades 3, 4, and 5, mnemosyne handles the change in easyness correctly, but for 0, 1, and 2 it does not. For 2 the easyness is updated, but changed too little (increment of -0.16 instead of -0.32 according to the SM2 algorithm). For 0, and 1, where the easyness should be reduced by 0.54 and 0.8 respectively, nothing is done. I am attaching a patch which should be applied to /usr/lib/python2.7/dist-packages/mnemosyne/libmnemosyne/schedulers/SM2_mnemosyne.py -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages mnemosyne depends on: ii libicu52 52.1-7.1 ii libqt4-sql-sqlite 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii python 2.7.8-4 ii python-cherrypy3 3.5.0-1 ii python-matplotlib 1.4.2-3.1 ii python-qt4 4.11.2+dfsg-1 ii python-qt4-sql 4.11.2+dfsg-1 mnemosyne recommends no packages. mnemosyne suggests no packages. -- no debconf information 489a490,493 if new_grade == 1: card.easiness -= 0.54 if new_grade == 0: card.easiness -= 0.8 497c501 card.easiness -= 0.16 --- card.easiness -= 0.32
Bug#684936: qgo: sound settings not remembered
Package: qgo Version: 2~svn764-1 Severity: normal Tags: upstream Dear Maintainer, In the preferences it is possible to switch off sound for observed games globally. However, when I do this, nothing changes. When I start observing a game, the sound is still on. In addition, even when no move is played at that moment, qgo still plays the stone sound. As a result, it is impossible to observe a game without qgo making a sound (unless you just mute sound alltogether). Cheers, Astrid -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages qgo depends on: ii libasound2 1.0.25-3 ii libc6 2.13-34 ii libgcc1 1:4.7.1-3 ii libqt4-network 4:4.8.2-1 ii libqt4-test 4:4.8.2-1 ii libqtcore4 4:4.8.2-1 ii libqtgui4 4:4.8.2-1 ii libstdc++6 4.7.1-3 qgo recommends no packages. Versions of packages qgo suggests: ii gnugo 3.8-5 -- 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#684937: qgo does not update files list in open file dialog at all
Package: qgo Version: 2~svn764-1 Severity: normal Tags: upstream Dear Maintainer, When one tries to open an SGF file with qgo2, the Open file dialog box shows an overview that is not updated when the content of the filesystem changes. A file that is moved, for instance, remains invisible. Opening and closing subdirectories does not help. If I close the dialog, for instance by clicking on Preferences or Go server on the left, and open the dialog again, still nothing changes. In order to open a file that has been moved, I have to restart qgo. Cheers, Astrid -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages qgo depends on: ii libasound2 1.0.25-3 ii libc6 2.13-34 ii libgcc1 1:4.7.1-3 ii libqt4-network 4:4.8.2-1 ii libqt4-test 4:4.8.2-1 ii libqtcore4 4:4.8.2-1 ii libqtgui4 4:4.8.2-1 ii libstdc++6 4.7.1-3 qgo recommends no packages. Versions of packages qgo suggests: ii gnugo 3.8-5 -- 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#684938: qgo: sorting for players and games lists not saved after quitting
Package: qgo Version: 2~svn764-1 Severity: normal Tags: upstream Dear Maintainer, After connecting to a server, one can sort the list of players or games by several variables (rank, name, etc.). However, after quitting qgo2 and starting it again, qgo2 forgets which variable was chosen. It does remember if I only disconnect from the server and then connect again. With the previous version of qgo, 1.5.4, sorting was remembered after quitting. Cheers, Astrid -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages qgo depends on: ii libasound2 1.0.25-3 ii libc6 2.13-34 ii libgcc1 1:4.7.1-3 ii libqt4-network 4:4.8.2-1 ii libqt4-test 4:4.8.2-1 ii libqtcore4 4:4.8.2-1 ii libqtgui4 4:4.8.2-1 ii libstdc++6 4.7.1-3 qgo recommends no packages. Versions of packages qgo suggests: ii gnugo 3.8-5 -- 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#684939: qgo: number of current move not shown anywhere
Package: qgo Version: 2~svn764-1 Severity: normal Tags: upstream Dear Maintainer, When a game board is open, the current move is not shown anywhere. There is a slider at the bottom, which gives the number of the final move. However, when looking at earlier moves in long games, it is impossible to determine the exact number of the current move from this without a ruler. In qgo 1.5.4, the move number was shown at the top right, where it says Black to play or White to play. Komi and several other essential pieces of information are also not shown, which is a bit unusual and inconvenient, but can be viewed at least by opening the game info. This was also different in qgo 1.5.4. Cheers, Astrid -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages qgo depends on: ii libasound2 1.0.25-3 ii libc6 2.13-34 ii libgcc1 1:4.7.1-3 ii libqt4-network 4:4.8.2-1 ii libqt4-test 4:4.8.2-1 ii libqtcore4 4:4.8.2-1 ii libqtgui4 4:4.8.2-1 ii libstdc++6 4.7.1-3 qgo recommends no packages. Versions of packages qgo suggests: ii gnugo 3.8-5 -- no debconf information - ast...@syonax.net ast...@dewijn.eu dew...@fysik.su.se aw...@science.ru.nl - Dr. Astrid S. de Wijn Department of Physics Stockholm University 106 91 Stockholm Sweden Tel: +46855378653 - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623445: xfce4-wmdock-plugin: cannot be installed due to dependency issue
Package: xfce4-wmdock-plugin Version: 0.3.2-1+b1 Severity: grave Justification: renders package unusable The package cannot be installed, because it depends on a version of xfce4-panel which is lower than the one currently in unstable. This is the full output of apt-get install xfce4-wmdock-plugin: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xfce4-wmdock-plugin : Depends: xfce4-panel ( 4.7.0) but 4.8.3-1 is to be installed E: Broken packages -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xfce4-wmdock-plugin depends on: ii libatk1.0-0 2.0.0-1The ATK accessibility toolkit ii libc6 2.11.2-13 Embedded GNU C Library: Shared lib ii libcairo2 1.10.2-6 The Cairo 2D vector graphics libra ii libfontconfig12.8.0-2.2 generic font configuration library ii libfreetype6 2.4.4-1FreeType 2 font engine, shared lib ii libglib2.0-0 2.28.6-1 The GLib library of C routines ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface ii libpango1.0-0 1.28.3-6 Layout and rendering of internatio ii libwnck22 2.30.4-3 Window Navigator Construction Kit ii libx11-6 2:1.4.3-1 X11 client-side library ii libxfce4util4 4.8.1-2Utility functions library for Xfce ii libxfcegui4-4 4.8.1-4Basic GUI C functions for Xfce4 ii xfce4-panel 4.8.3-1panel for Xfce4 desktop environmen xfce4-wmdock-plugin recommends no packages. xfce4-wmdock-plugin suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524280: Same problem on Radeon HD 3200
On Wed, May 06, 2009 at 09:23:02AM +0200, Julien Cristau wrote: On Wed, May 6, 2009 at 01:25:51 +0200, Astrid S. de Wijn wrote: (II) Loading sub module fglrxdrm (II) LoadModule: fglrxdrm (II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so (II) Module fglrxdrm: vendor=FireGL - ATI Technologies Inc. compiled for 1.4.99.906, module version = 8.60.3 This might cause some issues... You probably need to remove anything fglrx-related before testing the radeon driver. Ooops. I didn't realise that was still there. Removing it fixed my problem. And I was so looking forward to helping out... Thanks for the assistance! Astrid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524280: Same problem on Radeon HD 3200
On Sun, Apr 26, 2009 at 11:15:46PM -0400, Alex Deucher wrote: On Thu, Apr 23, 2009 at 5:16 AM, Astrid S. de Wijn Please let me know if you need any more details on my hardware cofiguration. Unfortunately I am not in a position to reboot this computer a lot right now for testing different versions, because it is being used for long simulations. If you get a chance, can you try any versions between 6.9.0 and 6.12.x or do a git bisect between 6.9.0 and some some broken release? Also, did you do anything else like upgrade the amount of ram in the system? I'm afraid I won't be able to do any rebooting untill these simulations finish, which might be a while. The xorg upgrade did not coincide with a hardware upgrade. I did fix some hardware a few days before, and subsequently ran memtest86+, which reported no errors. The machine has 6 Gb of ram, the motherboard is only a few months old, and it has never had any problems with xorg before. Astrid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524280: Same problem on Radeon HD 3200
I have the same problem with the on-board graphics card of a Gigabyte GA-MA78GPM-DS2H motherboard. Lspci output: 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3200 Graphics (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device d000 Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at d000 (32-bit, prefetchable) [size=256M] I/O ports at ee00 [size=256] Memory at fdfe (32-bit, non-prefetchable) [size=64K] Memory at fde0 (32-bit, non-prefetchable) [size=1M] Expansion ROM at unassigned [disabled] Capabilities: [50] Power Management version 3 Capabilities: [a0] MSI: Mask- 64bit+ Count=1/1 Enable- I don't have any more information to add to the extensive test results from Jacek Politowski, except perhaps for my pretty generic xorg.conf (see attachment). I am using unstable with a stock 2.6.29 kernel. Downgrading to 6.9.0 worked for me as well. I can confirm that the image on the screen with the broken driver is some sort of mixup of what the screen looked like just before things broke. At one point during my downgrade things were half fixed and I got almost the entire original image back. I could read most of the text in my terminals. This happened even after a soft reboot. Please let me know if you need any more details on my hardware cofiguration. Unfortunately I am not in a position to reboot this computer a lot right now for testing different versions, because it is being used for long simulations. Astrid # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse EndSection Section InputDevice Driverwacom Identifierstylus OptionDevice/dev/input/wacom #USB ONLY OptionType stylus OptionUSB on #USB ONLY EndSection Section InputDevice Driverwacom Identifiereraser OptionDevice/dev/input/wacom #USB ONLY OptionType eraser OptionUSB on #USB ONLY EndSection Section InputDevice Driverwacom Identifiercursor OptionDevice/dev/input/wacom #USB ONLY OptionType cursor OptionMode relative OptionUSB on #USB ONLY EndSection Section Extensions OptionComposite enable EndSection Section Device Identifier Configured Video Device Driver radeon Option XAANoOffscreenPixmaps true # Option DRI off # Option NoAccel true # Option R4xxATOM true EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard #InputDevice Configured Mouse SendCoreEvents InputDevice stylus SendCoreEvents InputDevice eraser SendCoreEvents InputDevice cursor SendCoreEvents EndSection
Bug#488412: eeepc-acpi-scripts nor ready for 2.6.26 /sys interface
Package: eeepc-acpi-scripts Version: 1.0.3 Severity: wishlist As discussed with SynrG on #debian-eeepc In 2.6.26 kernels the eeepc-acpi-modules are no longer needed and code for interacting with the eeepc specific acpi stuff is in the kernel. The interface is in /sys, though, no longer /proc/acpi/asus. eeepc-acpi-scripts does not use the new interface. wireless control (previously /proc/acpi/asus/wlan, used in /etc/acpi/actions/wireless.sh) moves to: /sys/devices/platform/eeepc/wlan brightness control (previously /proc/acpi/asus/brn, used in /etc/acpi/actions/suspend.sh) moves to: /sys/class/backlight/eeepc/brightness Please rewrite the scripts to autodetect and use the correct interface. Astrid -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488308: xfce4-icon-theme: rodent theme disappears when gnome-icon-theme is installed
Package: xfce4-icon-theme Version: 4.4.2-1 Severity: important I have been using the rodent icon theme. When I install gnome-icon-theme, after the next login, the appearance of my desktop changes spontaneously to the gnome icon theme. Switching the icon theme in the User Interface Preferences back to Rodent does not change anything. In my opinion installing a new theme package should not spontaneously change the appearance of an already configured desktop, only provide more options in the themes menu. It would be strange if the rodent icon theme and the gnome icon theme and packages which depend on it, such as evince, were mutually exclusive. Since I have no idea which package is actually causing this problem, and I have no idea what it's doing, I'm filing this bug against xfce4-icon-theme, as that package is at least involved. Please move this bug to another package if necessary. Kind regards, Astrid de Wijn -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-rc8 (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/bash Versions of packages xfce4-icon-theme depends on: ii hicolor-icon-theme0.10-1 default fallback theme for FreeDes Versions of packages xfce4-icon-theme recommends: ii gtk2-engines-xfce 2.4.2-2A GTK+-2.0 theme engine for Xfce ii librsvg2-common 2.22.2-2 SAX-based renderer library for SVG -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487490: linux-image-2.6.25-2-686: USB_PERSIST is enabled, but does not work
The bug number is 10977. Astrid On Mon, Jun 23, 2008 at 01:20:28AM +0200, maximilian attems wrote: On Mon, Jun 23, 2008 at 01:02:44AM +0200, Astrid S. de Wijn wrote: I've tried it with 2.6.26-rc6. USB_PERSIST works for the card reader, but unfortunately not for the usb stick. Aparently there is another problem. :( Astrid thanks for quick response. please report upstream in bugzilla.kernel.org and let us know the bug number. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487490: linux-image-2.6.25-2-686: USB_PERSIST is enabled, but does not work
] Region 1: I/O ports at 03f4 [size=1] Region 2: I/O ports at 0170 [size=8] Region 3: I/O ports at 0374 [size=1] Region 4: I/O ports at ffa0 [size=16] Capabilities: access denied Kernel driver in use: ata_piix Kernel modules: ahci, ata_piix 00:1f.3 SMBus [0c05]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller [8086:266a] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] 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- Interrupt: pin B routed to IRQ 19 Region 4: I/O ports at 0400 [size=32] Kernel driver in use: i801_smbus Kernel modules: i2c-i801 03:00.0 Ethernet controller [0200]: Attansic Technology Corp. L2 100 Mbit Ethernet Adapter [1969:2048] (rev a0) Subsystem: ASUSTeK Computer Inc. Device [1043:8233] 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, Cache Line Size: 16 bytes Interrupt: pin A routed to IRQ 220 Region 0: Memory at fbfc (64-bit, non-prefetchable) [size=256K] Expansion ROM at fbfa [disabled] [size=128K] Capabilities: access denied Kernel driver in use: atl2 Kernel modules: atl2 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (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/bash Versions of packages linux-image-2.6.25-2-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92b tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.25-2-686 recommends: ii libc6-i6862.7-12 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.25-2-686/preinst/abort-install-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/overwriting-modules-2.6.25-2-686: true linux-image-2.6.25-2-686/prerm/would-invalidate-boot-loader-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/elilo-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/bootloader-test-error-2.6.25-2-686: linux-image-2.6.25-2-686/postinst/depmod-error-initrd-2.6.25-2-686: false linux-image-2.6.25-2-686/preinst/bootloader-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.25-2-686/prerm/removing-running-kernel-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-initrd-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/bootloader-error-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/initrd-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/lilo-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-system-map-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/create-kimage-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-dir-initrd-link-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/abort-overwrite-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/failed-to-move-modules-2.6.25-2-686: linux-image-2.6.25-2-686/postinst/kimage-is-a-directory: linux-image-2.6.25-2-686/postinst/depmod-error-2.6.25-2-686: false - [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] - Dr. Astrid S. de Wijn Theory of Condensed Matter (TCM) Institute for Molecules and Materials (IMM) Faculty of Science Radboud University Nijmegen P.O. Box 9010 6500 GL Nijmegen The Netherlands Tel: +31(0)243652849 - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487490: linux-image-2.6.25-2-686: USB_PERSIST is enabled, but does not work
On Sun, Jun 22, 2008 at 01:18:50PM +0200, maximilian attems wrote: On Sun, Jun 22, 2008 at 10:28:55AM +0200, Astrid S. de Wijn wrote: Package: linux-image-2.6.25-2-686 Version: 2.6.25-5 Severity: normal In 2.6.25 debian kernels, USB_PERSIST has been enabled, to make it possible to suspend with mounted usb storage filesystems which lose power during suspend. Even though the interface in /sys exists, and I write 1 to every device's persist file, I still lose the usb storage devices after resume as if I had suspended without USB_PERSIST. The result is journal commit I/O errors and risk of filesystem corruption. The storage devices in question are a usb SD card reader and a usb stick attached to a usb hub, which contains my / filesystem. I've done a little bit of digging and found someone who reported a suspiciously similar problem. In the thread a patch is mentioned: http://article.gmane.org/gmane.linux.usb.general/2031/match=usb+persist+issue The patch was supposed to be submitted for 2.6.25, but the 2.6.25 debian-patched kernel sources don't seem to have it. I have not been able to test yet wether this patch fixes my problem. Kind regards, Astrid please checkout 2.6.26-rcX kernels. they have got patches for it see apt trunk lines http://wiki.debian.org/DebianKernel (beware to blacklist snd-pcsp ) -- maks I've tried it with 2.6.26-rc6. USB_PERSIST works for the card reader, but unfortunately not for the usb stick. Aparently there is another problem. :( Astrid - [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] - Dr. Astrid S. de Wijn Theory of Condensed Matter (TCM) Institute for Molecules and Materials (IMM) Faculty of Science Radboud University Nijmegen P.O. Box 9010 6500 GL Nijmegen The Netherlands Tel: +31(0)243652849 - signature.asc Description: Digital signature
Bug#485396: acpi is broken with my kernel
Package: acpi Version: 0.09-7 Severity: important Acpi just broken for my kernel, 2.6.22 kernel. It claims: No support for device type: power_supply No support for device type: thermal while it was working perfectly before. The kernel has not changed. On another machine with a 2.6.25 kernel, where it wasn't working for the battery before, it works fine now. It would be nice if it could work everywhere, if necessary with a switch. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22.19 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages acpi depends on: ii libc6 2.7-12 GNU C Library: Shared libraries acpi recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449349: May be fixed
Hi Simon, This bug looks similar to the problem where compression happens to expand data, and that problem was fixed in v2.0.4. Could you please try a later version? The problem appears to be gone with the lftp and gnutls currently in unstable: LFTP | Version 3.6.3 | Copyright (c) 1996-2008 Alexander V. Lukyanov Libraries used: Readline 5.2, GnuTLS 2.2.2, zlib 1.2.3.3 Astrid -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460867: linux-image-2.6.23-1-amd64: kernel BUG at block/cfq-iosched.c:1147!
Package: linux-image-2.6.23-1-amd64 Version: 2.6.23-2 Severity: important *** Please type your report below this line *** I seem to have run into some sort of io kernel bug. I connected a usb drive (trekstor datastation pocket x.u), mounted a partition, juggled data around (tens of GB), and umounted it. When i removed the drive from the usb port, I ran into a kernel bug. I have used this disk and enclosure combo with this machine and kernel before without any problem, also shuffling lots of data, though maybe not quite as much. An e2fsck on the mounted partition turned up no errors. Astrid Here is the relevant part of the dmesg output: usb 5-2: new high speed USB device using ehci_hcd and address 14 usb 5-2: configuration #1 chosen from 1 choice Initializing USB Mass Storage driver... scsi4 : SCSI emulation for USB Mass Storage devices usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usb-storage: device found at 14 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi 4:0:0:0: Direct-Access WDC WD16 00BEVE-00UYT0 PQ: 0 ANSI: 0 sd 4:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB) sd 4:0:0:0: [sdb] Write Protect is off sd 4:0:0:0: [sdb] Mode Sense: 27 00 00 00 sd 4:0:0:0: [sdb] Assuming drive cache: write through sd 4:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB) sd 4:0:0:0: [sdb] Write Protect is off sd 4:0:0:0: [sdb] Mode Sense: 27 00 00 00 sd 4:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 4:0:0:0: [sdb] Attached SCSI disk kjournald starting. Commit interval 5 seconds EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on sdb1, internal journal EXT3-fs: mounted filesystem with ordered data mode. usb 5-2: USB disconnect, address 14 [ cut here ] kernel BUG at block/cfq-iosched.c:1147! invalid opcode: [1] SMP CPU 0 Modules linked in: usb_storage iwl3945 mac80211 usbhid hid e1000 hci_usb bluetooth xt_TCPMSS xt_tcpmss xt_tcpudp iptable_filter ip_tables x_tables ppp_deflate zlib_deflate zlib_inflate bsd_comp pppoatm ppp_generic slhc tun tcp_diag inet_diag ipv6 acpi_cpufreq cpufreq_stats cpufreq_powersave cpufreq_ondemand cpufreq_conservative freq_table cpufreq_userspace fuse loop pcmcia snd_hda_intel joydev snd_pcm_oss snd_mixer_oss irtty_sir snd_pcm sir_dev yenta_socket rsrc_nonstatic cfg80211 battery ac pcmcia_core snd_timer video output nsc_ircc snd button irda i2c_i801 crc_ccitt iTCO_wdt psmouse i2c_core speedtch usbatm ieee80211 ieee80211_crypt serio_raw soundcore snd_page_alloc firmware_class intel_agp tsdev pcspkr thinkpad_acpi evdev nvram ext3 jbd mbcache ide_cd cdrom ata_generic sd_mod piix ahci libata scsi_mod generic ide_core ehci_hcd uhci_hcd thermal processor fan Pid: 181, comm: khubd Not tainted 2.6.23-1-amd64 #1 RIP: 0010:[802fa752] [802fa752] cfq_put_queue+0x12/0x89 RSP: 0018:8100bd1d3bb0 EFLAGS: 00010046 RAX: 0004 RBX: 8100ba5ab498 RCX: 8100bbe96088 RDX: 0003 RSI: 810079238c28 RDI: 8100ba5ab498 RBP: 8100bac64c00 R08: 1bdb R09: 8100013e9950 R10: 810086b67580 R11: 8100bbe96088 R12: 8100bbe96088 R13: 810079238c28 R14: R15: 8100bad55000 FS: () GS:804f6000() knlGS: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: 2b89b34aa000 CR3: b267f000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process khubd (pid: 181, threadinfo 8100bd1d2000, task 8100bd1b7850) Stack: 8100bbe96088 8100bac64c00 0001 802fa97a fff8100b579b080 8100b579b100 810069a51800 802f06da 810079d20190 8100bbe96690 8100bbe96088 802f3efb Call Trace: [802fa97a] cfq_exit_queue+0x92/0xbe [802f06da] elevator_exit+0x2c/0x48 [802f3efb] blk_cleanup_queue+0x37/0x42 [880879ca] :scsi_mod:scsi_device_dev_release_usercontext+0xe9/0x137 [80243ad5] execute_in_process_context+0x23/0x57 [802fe8e5] kobject_cleanup+0x52/0x70 [802fe903] kobject_release+0x0/0x9 [802ff6af] kref_put+0x5d/0x68 [88084ba3] :scsi_mod:scsi_forget_host+0x39/0x5b [8807f767] :scsi_mod:scsi_remove_host+0x75/0xf6 [882a98a3] :usb_storage:quiesce_and_remove_host+0xbf/0xce [882a9989] :usb_storage:storage_disconnect+0x10/0x19 [803758c4] usb_unbind_interface+0x59/0xb6 [80367526] __device_release_driver+0x8e/0xb0 [8036790f] device_release_driver+0x2c/0x45 [80366e1c] bus_remove_device+0x89/0x9c [80365265] device_del+0x22a/0x2b6 [80372f57] usb_disable_device+0x6f/0xe8 [8036f1eb] usb_disconnect+0x9b/0x148 [8036f9e0] hub_thread+0x403/0xbc0
