Bug#1020276: Fwd: Bug#1020276: linux-image-5.19.0-1-amd64: NFC device not detected
Thanks Mark, I worked my way through these build instruction and got successfully to Step 15: There, I don't know to do. What is my target platform? Is it "custom"? If so, what are the correct values to set? I also wonder whether that part is optional. In 8./9. I make and install the software. Then I modify the code (in 15.) and make/install again (16./17.) That's a bit confusing. Running the demo after the first make/install also doesn't work: ~/linux_libnfc-nci(master)> sudo nfcDemoApp nfcDemoApp: error while loading shared libraries: libnfc_nci_linux-1.so.0: cannot open shared object file: No such file or directory ~/linux_libnfc-nci(master)> echo $LD_LIBRARY_PATH /usr/local/lib/ ~/linux_libnfc-nci(master)> ls $LD_LIBRARY_PATH libnfc_nci_linux-1.so.0 libnfc_nci_linux.la pkgconfig python3.10 python3.9 libnfc_nci_linux-1.so.0.0.0 libnfc_nci_linux.so python2.7 python3.8 That may be me doing something stupid, though. smime.p7s Description: S/MIME Cryptographic Signature
Bug#1020276: linux-image-5.19.0-1-amd64: NFC device not detected
Package: src:linux Version: 5.19.6-1 Severity: normal I have a ThinkPad X1 Yoga (4th gen). It has an NFC device built in. The NFC device appears in the BIOS, and it is enabled there. However, I cannot see it from Debian at all. Neither lsusb nor lspci show anything ressembling an NFC device. I would gladly help to debug this, but I don't know what to do in such a situation. -- Package-specific info: ** Version: Linux version 5.19.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 11.3.0-5) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.6-1 (2022-09-01) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-1-amd64 root=UUID=1a64cfce-790c-4909-943a-4b0eae472280 ro quiet ** Tainted: W (512) * kernel issued warning ** Kernel log: [50279.964287] usb 1-2.3.3.2: SerialNumber: [50280.044948] input: Lenovo ThinkPad USB-C Dock Gen2 USB Audio as /devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3.3/1-2.3.3.2/1-2.3.3.2:1.3/0003:17EF:A396.0008/input/input35 [50280.103999] hid-generic 0003:17EF:A396.0008: input,hidraw5: USB HID v1.11 Device [Lenovo ThinkPad USB-C Dock Gen2 USB Audio] on usb-:00:14.0-2.3.3.2/input3 [50280.183667] usb 1-2.3.3.4: new full-speed USB device number 22 using xhci_hcd [50280.290956] usb 1-2.3.3.4: New USB device found, idVendor=0b0e, idProduct=0422, bcdDevice= 2.31 [50280.290962] usb 1-2.3.3.4: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [50280.290964] usb 1-2.3.3.4: Product: Jabra SPEAK 510 USB [50280.290965] usb 1-2.3.3.4: SerialNumber: 3050752CC7E7021F00 [50280.576445] input: Jabra SPEAK 510 USB as /devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3.3/1-2.3.3.4/1-2.3.3.4:1.3/0003:0B0E:0422.0009/input/input36 [50280.634984] usb 1-2.3.3.4: 1:1: cannot set freq 48000 to ep 0x3 [50280.635890] jabra 0003:0B0E:0422.0009: input,hiddev1,hidraw6: USB HID v1.11 Device [Jabra SPEAK 510 USB] on usb-:00:14.0-2.3.3.4/input3 [50280.669158] usbcore: registered new interface driver snd-usb-audio [50280.842220] wlp0s20f3: authenticate with f4:4e:05:b5:37:dd [50280.843533] wlp0s20f3: send auth to f4:4e:05:b5:37:dd (try 1/3) [50280.939101] wlp0s20f3: authenticated [50280.943667] wlp0s20f3: associate with f4:4e:05:b5:37:dd (try 1/3) [50280.945310] wlp0s20f3: RX AssocResp from f4:4e:05:b5:37:dd (capab=0x111 status=0 aid=11) [50280.946668] wlp0s20f3: associated [50281.051857] wlp0s20f3: Limiting TX power to 17 dBm as advertised by f4:4e:05:b5:37:dd [50281.051931] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready [50281.085188] input: Lenovo ThinkPad USB-C Dock Gen2 USB Audio as /devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3.3/1-2.3.3.2/1-2.3.3.2:1.3/0003:17EF:A396.000A/input/input37 [50281.147813] hid-generic 0003:17EF:A396.000A: input,hidraw5: USB HID v1.11 Device [Lenovo ThinkPad USB-C Dock Gen2 USB Audio] on usb-:00:14.0-2.3.3.2/input3 [50281.162696] usbhid 1-2.3.3.1:1.1: can't add hid device: -32 [50281.162704] usbhid: probe of 1-2.3.3.1:1.1 failed with error -32 [50281.360066] usb 1-2.3.3.1: USB disconnect, device number 20 [50281.623686] usb 1-2.3.3.1: new full-speed USB device number 23 using xhci_hcd [50281.731344] usb 1-2.3.3.1: New USB device found, idVendor=04b4, idProduct=521a, bcdDevice= 0.00 [50281.731347] usb 1-2.3.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [50281.731348] usb 1-2.3.3.1: Product: USB-I2C Bridge [50281.731349] usb 1-2.3.3.1: Manufacturer: Cypress Semiconductor [50284.799365] IPv6: ADDRCONF(NETDEV_CHANGE): enx482ae3771609: link becomes ready [50284.799711] r8152 4-1.1:1.0 enx482ae3771609: carrier on [50312.180563] wlp0s20f3: disconnect from AP f4:4e:05:b5:37:dd for new auth to f4:4e:05:ae:21:ed [50312.247452] wlp0s20f3: authenticate with f4:4e:05:ae:21:ed [50312.257584] wlp0s20f3: send auth to f4:4e:05:ae:21:ed (try 1/3) [50312.296792] wlp0s20f3: authenticated [50312.299718] wlp0s20f3: associate with f4:4e:05:ae:21:ed (try 1/3) [50312.301711] wlp0s20f3: RX ReassocResp from f4:4e:05:ae:21:ed (capab=0x111 status=0 aid=2) [50312.305238] wlp0s20f3: associated [50312.337849] wlp0s20f3: Limiting TX power to 17 dBm as advertised by f4:4e:05:ae:21:ed [50631.655067] wlp0s20f3: disconnect from AP f4:4e:05:ae:21:ed for new auth to f4:4e:05:b5:37:dd [50631.702978] wlp0s20f3: authenticate with f4:4e:05:b5:37:dd [50631.712151] wlp0s20f3: send auth to f4:4e:05:b5:37:dd (try 1/3) [50631.751766] wlp0s20f3: authenticated [50631.754022] wlp0s20f3: associate with f4:4e:05:b5:37:dd (try 1/3) [50631.755982] wlp0s20f3: RX ReassocResp from f4:4e:05:b5:37:dd (capab=0x111 status=0 aid=12) [50631.759006] wlp0s20f3: associated [50631.798424] wlp0s20f3: Limiting TX power to 17 dBm as advertised by f4:4e:05:b5:37:dd [50631.799678] wlp0s20f3: disconnect from AP f4:4e:05:b5:37:dd for new auth to f4:4e:05:ae:21:ed [50631.849425] wlp0s20f3: authenticate with f4:4e:05:ae:21:ed [50631.857225] wlp0s20f3: send auth to f4:4e:05:ae:21:ed (try 1/3)
Bug#1000150: Spurious message 'cannot open folder tags:/'
I found an upstream bugreport: https://bugs.kde.org/show_bug.cgi?id=437176 The workaround mentioned there (balooctl purge) worked for me. Thanks for your work on Debian. smime.p7s Description: S/MIME Cryptographic Signature
Bug#1000150: Spurious message 'cannot open folder tags:/'
I forgot to mention that the following message are printed at the command line when the message widget opens: [17::40:54.472] unknown: PostingDB::open MDB_NOTFOUND: No matching key/data pair found [17::40:54.472] unknown: PositionDB::open MDB_NOTFOUND: No matching key/data pair found [17::40:54.472] unknown: DocumentDB::open docterms MDB_NOTFOUND: No matching key/data pair found [17::40:54.472] unknown: DocumentDB::open docfilenameterms MDB_NOTFOUND: No matching key/data pair found [17::40:54.472] unknown: DocumentDB::open docxatrrterms MDB_NOTFOUND: No matching key/data pair found [17::40:54.472] unknown: IdTreeDB::open MDB_NOTFOUND: No matching key/data pair found [17::40:54.472] unknown: IdFilenameDB::open MDB_NOTFOUND: No matching key/data pair found [17::40:54.472] unknown: DocumentTimeDB::open MDB_NOTFOUND: No matching key/data pair found [17::40:54.472] unknown: DocumentDataDB::open MDB_NOTFOUND: No matching key/data pair found [17::40:54.472] unknown: DocumentIdDB::open indexingleveldb MDB_NOTFOUND: No matching key/data pair found [17::40:54.472] unknown: DocumentIdDB::open failediddb MDB_NOTFOUND: No matching key/data pair found [17::40:54.472] unknown: MTimeDB::open MDB_NOTFOUND: No matching key/data pair found [17::40:54.472] unknown: dbis is invalid [17::40:54.472] unknown: tag fetch failed: "Failed to open the database" [17::40:54.472] unknown: "tags:/" list() invalid url [17::40:54.472] unknown: "Ordner tags:/ lässt sich nicht öffnen." smime.p7s Description: S/MIME Cryptographic Signature
Bug#1000150: Spurious message 'cannot open folder tags:/'
Subject: kate: Spurious message 'cannot open folder tags:/' Package: kate Version: 4:21.08.2-1 Severity: normal Disclaimer: this is most likely not a bug in kate, but I don't know what package to assign this bug report to. Please reassign appropriately. Every time I open the 'file open' dialog in kate or a number of other KDE apps such as kile or okular, I get a little error widget saying 'Cannot open folder tags:/' (My own translation: My German GUI actually says 'Ordner tags:/ lässt sich nicht öffnen.' ) If I click on the OK button the 'file open' dialog appears, and there are no further problems. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-4-amd64 (SMP w/8 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kate depends on: ii kate5-data 4:21.08.2-1 ii kio 5.86.0-1 ii ktexteditor-katepart 5.86.0-1 ii libc62.32-4 ii libkf5bookmarks5 5.86.0-1 ii libkf5completion55.86.0-1 ii libkf5configcore55.86.0-1 ii libkf5configgui5 5.86.0-1 ii libkf5configwidgets5 5.86.0-1 ii libkf5coreaddons55.86.0-1 ii libkf5crash5 5.86.0-1 ii libkf5dbusaddons55.86.0-1 ii libkf5guiaddons5 5.86.0-1 ii libkf5i18n5 5.86.0-1 ii libkf5iconthemes55.86.0-1 ii libkf5kiocore5 5.86.0-1 ii libkf5kiofilewidgets55.86.0-1 ii libkf5kiogui55.86.0-1 ii libkf5kiowidgets55.86.0-1 ii libkf5newstuff5 5.86.0-3 ii libkf5parts5 5.86.0-1 ii libkf5plasma55.86.0-1 ii libkf5service-bin5.86.0-1 ii libkf5service5 5.86.0-1 ii libkf5syntaxhighlighting55.86.0-1 ii libkf5texteditor55.86.0-1 ii libkf5textwidgets5 5.86.0-1 ii libkf5wallet-bin 5.86.0-1 ii libkf5wallet55.86.0-1 ii libkf5widgetsaddons5 5.86.0-1 ii libkf5windowsystem5 5.86.0-1 ii libkf5xmlgui55.86.0-1 ii libkuserfeedbackcore11.0.0-3 ii libkuserfeedbackwidgets1 1.0.0-3 ii libqt5concurrent55.15.2+dfsg-12 ii libqt5core5a 5.15.2+dfsg-12 ii libqt5dbus5 5.15.2+dfsg-12 ii libqt5gui5 5.15.2+dfsg-12 ii libqt5sql5 5.15.2+dfsg-12 ii libqt5widgets5 5.15.2+dfsg-12 ii libqt5xml5 5.15.2+dfsg-12 ii libstdc++6 11.2.0-10 ii plasma-framework 5.86.0-1 ii qml-module-org-kde-kquickcontrolsaddons 5.86.0-1 ii qml-module-qtquick-layouts 5.15.2+dfsg-8 ii qml-module-qtquick2 5.15.2+dfsg-8 Versions of packages kate recommends: ii sonnet-plugins 5.86.0-1 Versions of packages kate suggests: pn darcs pn exuberant-ctags ii git 1:2.33.0-1 ii khelpcenter 4:21.08.0-1 ii konsole-kpart4:21.08.2-1 pn mercurial ii subversion 1.14.1-3+b1 -- no debconf information smime.p7s Description: S/MIME Cryptographic Signature
Bug#996670: Enable compositor on startup switched off
>> But I guess you had, or some cosmic radiation induced bit switch did it >> for you on your hard disk ;-) The default for all installations is being >> on. > yeah, then lets say "maybe" or "probably" I did that, nevertheless, at least it was a couple of years ago and I cannot remeber ;-) This sounds familiar. Wasn't "Enable compositor..." being disabled also the cause of this week's #998216 ? And I checked: On my system the setting is also disabled, with me not remembering ever having disabled it. My original installation happened many years ago. Did the default maybe change afterwards? Best, Oliver smime.p7s Description: S/MIME Cryptographic Signature
Bug#950604: gitg crashes even at startup
I get the same crash, but at every start of the program (i.e. without clicking at a specific commit). This makes gitg completely unusable for me. smime.p7s Description: S/MIME Cryptographic Signature
Bug#979622: Wayland: No image on external display when reconnecting
I still see this with current Testing, but now I sometimes have the same problem with X11 too. So I guess it is likely that this is not a Plasma problem but rather a kernel one. Please feel free to close this. Thanks for your work on Debian. smime.p7s Description: S/MIME Cryptographic Signature
Bug#983442: QT_SCREEN_SCALE_FACTORS erroneously set in Wayland session
Package: plasma-desktop Version: 4:5.20.5-3 Severity: normal When I boot and start a Plasma session, the environment variable QT_SCREEN_SCALE_FACTORS is set: ~> echo $QT_SCREEN_SCALE_FACTORS eDP-1=1.5;DP-1=1.5;HDMI-1=1.5;DP-2=1.5;DP-1-1=1.5;DP-1-2=1.5;DP-1-3=1.5; AFAIU this is correct: I did select 1.5 screen scaling via the GUI earlier. When I boot and start a Plasma Wayland session, the same variable is not set. Again, the seems to be correct: Wayland apparently communicates the screen scaling by other means. However, when I boot, and then 1) start a Plasma session 2) log out without reboot 3) start a Plasma Wayland session then QT_SCREEN_SCALE_FACTORS *is* set. And this leads to all sorts of dubious effects, because now the X11 and Wayland scaling mechanisms interfere. Apologies if I am reporting this for the wrong package. Please correct me. Likewise if this is really an upstream problem that should be reported there. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-desktop depends on: ii accountsservice 0.6.55-3 ii breeze 4:5.20.5-2 ii kactivitymanagerd5.20.5-1 ii kde-cli-tools4:5.20.5-2 ii kded55.78.0-2 ii kio 5.78.0-4 ii kpackagetool55.78.0-3 ii libaccounts-qt5-11.16-2 ii libc62.31-9 ii libcrypt11:4.4.17-1 ii libglib2.0-0 2.66.7-1 ii libibus-1.0-51.5.23-2 ii libkaccounts24:20.12.1-1 ii libkf5activities55.78.0-2 ii libkf5activitiesstats1 5.78.0-2 ii libkf5authcore5 5.78.0-2 ii libkf5baloo5 5.78.0-2 ii libkf5codecs55.78.0-2 ii libkf5completion55.78.0-3 ii libkf5configcore55.78.0-4 ii libkf5configgui5 5.78.0-4 ii libkf5configwidgets5 5.78.0-2 ii libkf5coreaddons55.78.0-2 ii libkf5crash5 5.78.0-3 ii libkf5dbusaddons55.78.0-2 ii libkf5declarative5 5.78.0-2 ii libkf5globalaccel-bin5.78.0-2 ii libkf5globalaccel5 5.78.0-2 ii libkf5guiaddons5 5.78.0-3 ii libkf5i18n5 5.78.0-2 ii libkf5iconthemes55.78.0-2 ii libkf5itemviews5 5.78.0-2 ii libkf5kcmutils5 5.78.0-3 ii libkf5kdelibs4support5 5.78.0-2 ii libkf5kiocore5 5.78.0-4 ii libkf5kiofilewidgets55.78.0-4 ii libkf5kiogui55.78.0-4 ii libkf5kiowidgets55.78.0-4 ii libkf5notifications5 5.78.0-2 ii libkf5notifyconfig5 5.78.0-2 ii libkf5package5 5.78.0-3 ii libkf5plasma55.78.0-3 ii libkf5plasmaquick5 5.78.0-3 ii libkf5quickaddons5 5.78.0-2 ii libkf5runner55.78.0-3 ii libkf5service-bin5.78.0-2 ii libkf5service5 5.78.0-2 ii libkf5solid5 5.78.0-2 ii libkf5sonnetcore55.78.0-2 ii libkf5sonnetui5 5.78.0-2 ii libkf5wallet-bin 5.78.0-2 ii libkf5wallet55.78.0-2 ii libkf5widgetsaddons5 5.78.0-2 ii libkf5windowsystem5 5.78.0-2 ii libkf5xmlgui55.78.0-2 ii libkworkspace5-5 4:5.20.5-3 ii libnotificationmanager1 4:5.20.5-3 ii libphonon4qt5-4 4:4.11.1-3 ii libprocesscore9 4:5.20.5-1 ii libqt5concurrent55.15.2+dfsg-4 ii libqt5core5a 5.15.2+dfsg-4 ii libqt5dbus5 5.15.2+dfsg-4 ii libqt5gui5 5.15.2+dfsg-4 ii libqt5network5 5.15.2+dfsg-4 ii libqt5qml5 5.15.2+dfsg-4 ii libqt5quick5
Bug#981704: Attempting to use Wacom stylus freezes system
I saw this, too. The latest kernel from unstable fixed it. smime.p7s Description: S/MIME Cryptographic Signature
Bug#979622: Wayland: No image on external display when reconnecting
Package: kscreen Version: 4:5.20.5-1 Severity: normal Apologies if I am not reporting this for the correct package. I try the following steps: 1) Reboot my laptop (ThinkPad X1 Yoga) with external monitor plugged in. The external monitor works as expected. 2) At the SDDM prompt, log into Plasma Wayland. The external monitor still works as it should. 3) Disconnect the external monitor Still everything appears to work as it should. 4) Reconnect the monitor -- it remains black and tells me 'no signal' Nevertheless, the system settings dialog shows me that the external display is correctly recognized. From looking at that dialog everything seems to be in order. 5) Log out of Plasma Wayland, and log back in. 6) The external display is back! This does not happen with Plasma X11. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kscreen depends on: ii kde-cli-tools 4:5.20.5-2 ii libc6 2.31-9 ii libkf5configcore5 5.77.0-2 ii libkf5coreaddons5 5.77.0-2 ii libkf5dbusaddons5 5.77.0-2 ii libkf5declarative5 5.77.0-2 ii libkf5globalaccel-bin 5.77.0-3 ii libkf5globalaccel5 5.77.0-3 ii libkf5i18n55.77.0-2 ii libkf5plasma5 5.77.0-2 ii libkf5plasmaquick5 5.77.0-2 ii libkf5quickaddons5 5.77.0-2 ii libkf5screen-bin 4:5.20.5-1 ii libkf5screen7 4:5.20.5-1 ii libkf5xmlgui5 5.77.0-2 ii libqt5core5a 5.15.2+dfsg-2 ii libqt5dbus55.15.2+dfsg-2 ii libqt5gui5 5.15.2+dfsg-2 ii libqt5qml5 5.15.2+dfsg-2 ii libqt5quick5 5.15.2+dfsg-2 ii libqt5sensors5 5.15.2-2 ii libqt5widgets5 5.15.2+dfsg-2 ii libstdc++6 10.2.1-3 ii plasma-framework 5.77.0-2 ii qml-module-qtgraphicaleffects 5.15.2-2 Versions of packages kscreen recommends: ii upower 0.99.11-2 kscreen suggests no packages. -- no debconf information smime.p7s Description: S/MIME Cryptographic Signature
Bug#973677: Confirmed even in 5.19.5-2
I (apparently) solved the problem by updating a few plasma packages to 5.19, in particular plasma-workspace plasma-desktop (and possibly one or two more). They are still at 5.17 in unstable. smime.p7s Description: S/MIME Cryptographic Signature
Bug#973677: Confirmed even in 5.19.5-2
I'm seeing the same thin even with libkscreenlocker5 5.19.5-2 from experimental. The locked screen is completely black, and wiggling the mouse shows the cursor but nothing else. My workaround to unlocking the session is to switch to a TTY shell by ctrl-shift-2, and using 'loginctl unlock-session'. smime.p7s Description: S/MIME Cryptographic Signature
Bug#927063: closed by saul...@legtux.org (libreoffice-writer: Writer aborts with 'unexpected error' when opening one particular docx file)
Hi Stéphane, thanks for caring about my bug report. However, you wrote: > This kind of bug is not specific to Debian. I recommend you register on the > bugtracker of LO and follow it. This is indeed what I did before filing the Debian report. In particular, my Debian report says: > I filed an upstream bug: > https://bugs.documentfoundation.org/show_bug.cgi?id=124607 > but upstream cannot reproduce it. So could this be a packaging bug... And later in that bugreport I note that I get the bug with the Debian package of LO but not with the same LO version downloaded directly from the Document Foundation site. So I am not convinced yet that this is not a Debian issue. Best regards, Oliver On 13.05.19 14:21, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the libreoffice-writer package: > > #927063: libreoffice-writer: Writer aborts with 'unexpected error' when > opening one particular docx file > > It has been closed by saul...@legtux.org. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact saul...@legtux.org by > replying to this email. > > signature.asc Description: OpenPGP digital signature
Bug#927063: The problematic file
Here is the problematic file. 2_Document_cannot_be_opened.docx Description: MS-Word 2007 document signature.asc Description: OpenPGP digital signature
Bug#927063: libreoffice-writer: Writer aborts with 'unexpected error' when opening one particular docx file
Package: libreoffice-writer Version: 1:6.1.5-2 Severity: normal The following problem happens with LO Writer 6.1.5.2 from Debian, but not with the same version downloaded from https://www.libreoffice.org/download/ I filed an upstream bug: https://bugs.documentfoundation.org/show_bug.cgi?id=124607 but upstream canno reproduce it. So could this be a packaging bug... Opening the attached file gives me a textbox saying "Due to an expected error LO crashed" (my translation of a German text). If I then click 'ok', the document recuperation dialog starts, but when I click on "start recuperation", I get a hard segfault with the screen message attached below. My LO version is Version: 6.1.5.2 Build-ID: 1:6.1.5-1 CPU-Threads: 4; BS: Linux 4.19; UI-Render: Standard; VCL: gtk3; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group threaded Here is the backtrace. I have tried the libreoffice-writer-dbgsym package, but that did not make the backtrace more helpful. ~/tmp> lowriter 2_Document_cannot_be_opened.docx (soffice:17598): GLib-GObject-WARNING **: 13:38:40.702: ../../../gobject/gsignal.c:3492: signal name 'selection_changed' is invalid for instance '0x562015104ed0' of type 'OOoAtkObjCompTxt' Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d693)[0x7f28b3639693] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d8a3)[0x7f28b36398a3] /lib/x86_64-linux-gnu/libc.so.6(+0x37940)[0x7f28b3429940] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f28b34298bb] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f28b3414535] /usr/lib/libreoffice/program/libmergedlo.so(+0x11e6746)[0x7f28b4840746] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x88427)[0x7f28abbcc427] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f28b2921dd8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4e1c8)[0x7f28b29221c8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f28b292225c] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x89963)[0x7f28abbcd963] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7f28b6493b9e] /usr/lib/libreoffice/program/libmergedlo.so(_ZN6Dialog7ExecuteEv+0x6e)[0x7f28b61e2d7e] /usr/lib/libreoffice/program/libmergedlo.so(+0x237d15f)[0x7f28b59d715f] /usr/lib/libreoffice/program/libmergedlo.so(+0x1efbac5)[0x7f28bac5] /usr/lib/libreoffice/program/libmergedlo.so(+0x1efc239)[0x7f28b5556239] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e3ec8b)[0x7f28b6498c8b] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x17772)[0x7f28b3613772] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d76f)[0x7f28b363976f] /lib/x86_64-linux-gnu/libc.so.6(+0x37940)[0x7f28b3429940] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f28b34298bb] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f28b3414535] /usr/lib/libreoffice/program/libmergedlo.so(+0x11e6746)[0x7f28b4840746] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x88427)[0x7f28abbcc427] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f28b2921dd8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4e1c8)[0x7f28b29221c8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f28b292225c] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x89963)[0x7f28abbcd963] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7f28b6493b9e] /usr/lib/libreoffice/program/libmergedlo.so(_ZN6Dialog7ExecuteEv+0x6e)[0x7f28b61e2d7e] /usr/lib/libreoffice/program/libmergedlo.so(+0x237d32c)[0x7f28b59d732c] /usr/lib/libreoffice/program/libmergedlo.so(+0x1efbac5)[0x7f28bac5] /usr/lib/libreoffice/program/libmergedlo.so(+0x1effe77)[0x7f28b5559e77] /usr/lib/libreoffice/program/libmergedlo.so(+0x1f0062a)[0x7f28b555a62a] /usr/lib/libreoffice/program/libmergedlo.so(+0x2c1e098)[0x7f28b6278098] /usr/lib/libreoffice/program/libmergedlo.so(_ZN16SalUserEventList18DispatchUserEventsEb+0x187)[0x7f28b64758e7] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x88669)[0x7f28abbcc669] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f28b2921dd8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4e1c8)[0x7f28b29221c8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f28b292225c] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x89963)[0x7f28abbcd963] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7f28b6493b9e] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f28b6495315] /usr/lib/libreoffice/program/libmergedlo.so(+0x1f01a96)[0x7f28b555ba96] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e40416)[0x7f28b649a416] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f28b649a510] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x91)[0x7f28b5577e41] /usr/lib/libreoffice/program/soffice.bin(+0x107b)[0x56201332e07b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f28b341609b]
Bug#900364: paraview: Paraview viewer mishandles fractional Qt screen scaling
Package: paraview Version: 5.4.1+dfsg4-3 Severity: normal I use a KDE desktop with fractional screen scaling enabled, more specifically, on my system ~> echo $QT_SCREEN_SCALE_FACTORS eDP-1=1.5;DP-1=1.5;HDMI-1=1.5;HDMI-2=1.5; As a result, only parts of the Paraview rendering window are actually used for rendering---the rest remains black. I'll attach a screenshot. The problem disappears when I set export QT_SCREEN_SCALE_FACTORS=eDP-1=1 The problem also disappears when I switch the Paraview window to full-screen mode. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages paraview depends on: ii libavcodec57 7:3.4.2-2+b1 ii libavformat57 7:3.4.2-2+b1 ii libavutil557:3.4.2-2+b1 ii libc6 2.27-3 ii libcgns3.3 3.3.0-6 ii libexpat1 2.2.5-3 ii libfreetype6 2.8.1-2 ii libgcc11:8.1.0-3 ii libgl1 1.0.0+git20180308-2 ii libgl2ps1.41.4.0+dfsg1-2 ii libglew2.0 2.0.0-5 ii libhdf5-1001.10.0-patch1+docs-4+b1 ii libjpeg62-turbo1:1.5.2-2+b1 ii libjsoncpp11.7.4-3 ii libnetcdf131:4.6.1-1 ii libogg01.3.2-1+b1 ii libopenmpi33.0.1.real-3 ii libpng16-161.6.34-1 ii libprotobuf10 3.0.0-9.1 ii libpython2.7 2.7.15-1 ii libqt5core5a 5.10.1+dfsg-6+b1 ii libqt5gui5 5.10.1+dfsg-6+b1 ii libqt5help55.10.1-2 ii libqt5network5 5.10.1+dfsg-6+b1 ii libqt5widgets5 5.10.1+dfsg-6+b1 ii libqt5x11extras5 5.10.1-2 ii libstdc++6 8.1.0-3 ii libswscale47:3.4.2-2+b1 ii libtheora0 1.1.1+dfsg.1-14+b1 ii libtiff5 4.0.9-5 ii libx11-6 2:1.6.5-1 ii libxml22.9.4+dfsg1-6.1 ii libxt6 1:1.1.5-1 ii python-autobahn17.10.1+dfsg1-2 ii python-matplotlib 2.1.1-2 ii python-mpi4py 2.0.0-3+b1 ii python-six 1.11.0-2 ii python-twisted 17.9.0-2 ii tcl [tclsh]8.6.0+9 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages paraview recommends: ii mpi-default-bin 1.13 ii paraview-doc 5.4.1+dfsg4-3 pn paraview-python Versions of packages paraview suggests: pn h5utils pn hdf5-tools -- no debconf information
Bug#860086: Unreproducible, moreinfo
Thanks for asking. In fact, the problem disappeared automatically during some Qt update (sorry, I don't know which one). So the bug can be fixed. smime.p7s Description: S/MIME Cryptographic Signature
Bug#867566: texlive-latex-extra: pdfcomment tacitly redefines \C
Package: texlive-latex-extra
Version: 2017.20170629-1
Severity: normal
The pdfcomment packages appears to redefine \C, without that being
mentioned in the documentation. This is unfortunate, as \C is a
standard way to typeset the complex numbers. To reproduce the problem,
use the following small test program:
\documentclass{book}
\usepackage{pdfcomment}
\newcommand{\C}{Hallo Welt!}
\begin{document}
\C
\end{document}
It fails to build unless the second line is removed.
-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource.
In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.
*** The Debian TeX Team is *not* a LaTeX Help Desk ***
If you report an error when running one of the TeX-related binaries
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.
Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.
Don't forget to also include minimal examples of other files that are
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!
If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at
http://www.minimalbeispiel.de/mini-en.html (english)
or
http://www.minimalbeispiel.de/mini.html (german)
##
minimal input file
##
other files
##
List of ls-R files
-rw-rw-r-- 1 root staff 80 Oct 12 2015 /usr/local/share/texmf/ls-R
-rw-r--r-- 1 root root 1246 Jul 4 16:17 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Jun 24 14:20 /usr/share/texmf/ls-R ->
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Jun 29 04:30 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Jun 29 04:30 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
##
Config files
lrwxrwxrwx 1 root root 40 Jun 29 04:30 /usr/share/texmf/web2c/texmf.cnf ->
../../texlive/texmf-dist/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Jun 29 04:30 /usr/share/texmf/web2c/fmtutil.cnf ->
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Jun 29 04:30 /usr/share/texmf/web2c/updmap.cfg ->
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2982 Jul 4 16:17
/var/lib/texmf/tex/generic/config/language.dat
##
Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Sep 3 2015 mktex.cnf
-rw-r--r-- 1 root root 475 Jul 4 16:14 texmf.cnf
##
md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages texlive-latex-extra depends on:
ii preview-latex-style11.90-1
ii tex-common 6.07
ii texlive-base 2017.20170629-1
ii texlive-binaries 2017.20170613.44572-2
ii texlive-latex-recommended 2017.20170629-1
ii texlive-pictures 2017.20170629-1
Versions of packages texlive-latex-extra recommends:
ii texlive-fonts-recommended 2017.20170629-1
ii texlive-latex-extra-doc2017.20170629-1
ii texlive-plain-generic 2017.20170629-1
Versions of packages texlive-latex-extra suggests:
ii libfile-which-perl 1.21-1
pn libspreadsheet-parseexcel-perl
ii python-pygments 2.2.0+dfsg-1
Versions of packages tex-common depends on:
ii dpkg 1.18.24
ii ucf 3.0036
Versions of packages tex-common suggests:
ii debhelper 10.2.5
Versions of packages texlive-latex-extra is related to:
ii tex-common6.07
ii texlive-binaries 2017.20170613.44572-2
-- no debconf information
Bug#866013: /usr/bin/krunner: krunner always appears on first virtual desktop under wayland
Package: plasma-workspace Version: 4:5.8.7-1 Severity: normal File: /usr/bin/krunner I am trying the Plasma Wayland desktop. I can start krunner by pressing Alt+F2. However, no matter which one of my four virtual desktops I start it from, it always switches back to the first desktop, and then starts there. Instead, it should start on the current desktop. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plasma-workspace depends on: ii dbus-x11 1.10.18-1 ii frameworkintegration 5.28.0-1 ii gdb 7.12-6 ii iso-codes3.75-1 ii kactivitymanagerd5.8.4-1 ii kde-cli-tools4:5.8.7-1 ii kded55.28.0-1 ii kinit5.28.0-1 ii kio 5.28.0-2 ii kpackagetool55.28.1-1 ii libc62.24-12 ii libcln6 1.3.4-2+b1 ii libdbusmenu-qt5-20.9.3+16.04.20160218-1 ii libgcc1 1:7.1.0-7 ii libgps22 3.16-4 ii libice6 2:1.0.9-2 ii libkf5activities55.28.0-1 ii libkf5auth5 5.28.0-2 ii libkf5baloo5 5.28.0-2 ii libkf5bookmarks5 5.28.0-1 ii libkf5calendarevents55.28.0-1 ii libkf5completion55.28.0-1 ii libkf5configcore55.28.0-2 ii libkf5configgui5 5.28.0-2 ii libkf5configwidgets5 5.28.0-2 ii libkf5coreaddons55.28.0-2 ii libkf5crash5 5.28.0-1 ii libkf5dbusaddons55.28.0-1 ii libkf5declarative5 5.28.0-1 ii libkf5globalaccel-bin5.28.0-1 ii libkf5globalaccel5 5.28.0-1 ii libkf5guiaddons5 5.28.0-1 ii libkf5holidays5 16.04.2-1 ii libkf5i18n5 5.28.0-2 ii libkf5iconthemes55.28.0-2 ii libkf5idletime5 5.28.0-1 ii libkf5itemviews5 5.28.0-1 ii libkf5jobwidgets55.28.0-2 ii libkf5js55.28.0-1 ii libkf5jsembed5 5.28.0-1 ii libkf5kdelibs4support5 5.28.0-2 ii libkf5kiocore5 5.28.0-2 ii libkf5kiofilewidgets55.28.0-2 ii libkf5kiowidgets55.28.0-2 ii libkf5networkmanagerqt6 5.28.0-2 ii libkf5newstuff5 5.28.0-1 ii libkf5notifications5 5.28.0-1 ii libkf5notifyconfig5 5.28.0-1 ii libkf5package5 5.28.1-1 ii libkf5plasma55.28.0-2 ii libkf5plasmaquick5 5.28.0-2 ii libkf5quickaddons5 5.28.0-1 ii libkf5runner55.28.0-1 ii libkf5service-bin5.28.0-1 ii libkf5service5 5.28.0-1 ii libkf5solid5 5.28.0-4 ii libkf5texteditor55.28.0-2 ii libkf5textwidgets5 5.28.0-1 ii libkf5wallet-bin 5.28.0-3 ii libkf5wallet55.28.0-3 ii libkf5waylandclient5 4:5.28.0-1 ii libkf5widgetsaddons5 5.28.0-3 ii libkf5windowsystem5 5.28.0-2 ii libkf5xmlgui55.28.0-1 ii libkf5xmlrpcclient5 5.28.0-1 ii libkscreenlocker55.8.7-1 ii libksgrd74:5.8.7-1 ii libkworkspace5-5 4:5.8.7-1 ii libphonon4qt5-4 4:4.9.0-4 ii libplasma-geolocation-interface5 4:5.8.7-1 ii libprocesscore7 4:5.8.7-1 ii libprocessui74:5.8.7-1 ii libqalculate5v5 0.9.7-9.2 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5dbus5 5.7.1+dfsg-3+b1 ii libqt5gui5 5.7.1+dfsg-3+b1 ii libqt5network5 5.7.1+dfsg-3+b1 ii
Bug#860086: qtbase5-dev: QApplication does not receive QEvent::TabletEnterProximity
Package: qtbase5-dev Version: 5.7.1+dfsg-3+b1 Severity: normal I'm using a Lenovo ThinkPad Yoga 2, which has a touch screen and a stylus. The stylus triggers Qt tablet events. Trying to fix a problem in Okular [0], I noticed that the QApplication class does not receive the events TabletEnterProximity and TabletLeaveProximity, even though it should, according to the Qt documentation [1]. To test this, try the example tablet application from [1]. It should change the cursor shape whenever the stylus comes near the screen, but the cursor never changes. Adding a debug line into TabletApplication::event (which inherits from QApplication) shows that QApplication actually receives very few events at all. Basically only QApplicationStateChangeEvents and QTimerEvents. On the other hand, my system does know about the stylus being close to the screen. xev sees it, and in the example from [1] the cursor moves to the correct position when I move the stylus close to, but not onto the screen. This is a regression. It used to work with a Debian testing installation from about six month ago when I first wrote the patch in [0]. Has there been some change to Qt in the meantime that could trigger this? What can I do to debug this further? Thanks for your help! [0]: https://git.reviewboard.kde.org/r/128858/ [1]: http://doc.qt.io/qt-5/qtwidgets-widgets-tablet-example.html -- System Information: Debian Release: 9.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qtbase5-dev depends on: ii libgl1-mesa-dev [libgl-dev]13.0.6-1 ii libglu1-mesa-dev [libglu-dev] 9.0.0-2.1 ii libqt5concurrent5 5.7.1+dfsg-3+b1 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5dbus55.7.1+dfsg-3+b1 ii libqt5gui5 5.7.1+dfsg-3+b1 ii libqt5network5 5.7.1+dfsg-3+b1 ii libqt5printsupport55.7.1+dfsg-3+b1 ii libqt5sql5 5.7.1+dfsg-3+b1 ii libqt5test55.7.1+dfsg-3+b1 ii libqt5widgets5 5.7.1+dfsg-3+b1 ii libqt5xml5 5.7.1+dfsg-3+b1 ii libxext-dev2:1.3.3-1+b2 ii qt5-qmake 5.7.1+dfsg-3+b1 ii qtbase5-dev-tools 5.7.1+dfsg-3+b1 ii qtchooser 63-g13a3d08-1 Versions of packages qtbase5-dev recommends: ii libqt5opengl5-dev 5.7.1+dfsg-3+b1 Versions of packages qtbase5-dev suggests: ii default-libmysqlclient-dev 1.0.2 pn firebird-dev pn libegl1-mesa-dev ii libgl1-mesa-dev 13.0.6-1 ii libpq-dev 9.6.2-2 ii libsqlite3-dev 3.16.2-3 ii unixodbc-dev2.3.4-1 -- no debconf information
Bug#857478: texlive: lualatex does not compile document that uses algorithm2e package
Package: texlive
Version: 2016.20170123-4
Severity: normal
lualatex does not build documents that use the algorithm2e package.
Minimal working example:
\documentclass{article}
\usepackage{algorithm2e}
\begin{document}
\section{Hallo Welt!}
\end{document}
The error message is
(/usr/share/texlive/texmf-dist/tex/latex/algorithm2e/algorithm2e.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
! String contains an invalid utf-8 sequence.
l.1311 \renewcommand{\algorithmcflinename}{
�izizgi}%
Indeed, line 1311 of algorithm2e.sty does contain some 'nonstandard'
letters. They look okay in an editor, but I don't know enough
about encodings to investigate further.
-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource.
In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.
*** The Debian TeX Team is *not* a LaTeX Help Desk ***
If you report an error when running one of the TeX-related binaries
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.
Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.
Don't forget to also include minimal examples of other files that are
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!
If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at
http://www.minimalbeispiel.de/mini-en.html (english)
or
http://www.minimalbeispiel.de/mini.html (german)
##
minimal input file
##
other files
##
List of ls-R files
-rw-r--r-- 1 root root 1246 Mar 8 16:30 /var/lib/texmf/ls-R
-rw-rw-r-- 1 root staff 80 Oct 12 2015 /usr/local/share/texmf/ls-R
lrwxrwxrwx 1 root root 29 Jan 17 03:45 /usr/share/texmf/ls-R ->
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Feb 20 05:37 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Feb 20 05:37 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
##
Config files
-rw-r--r-- 1 root root 475 Jan 30 11:43 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Feb 20 05:37 /usr/share/texmf/web2c/fmtutil.cnf ->
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Feb 20 05:37 /usr/share/texmf/web2c/updmap.cfg ->
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2982 Mar 8 16:30
/var/lib/texmf/tex/generic/config/language.dat
##
Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Sep 3 2015 mktex.cnf
-rw-r--r-- 1 root root 475 Jan 30 11:43 texmf.cnf
##
md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf
-- System Information:
Debian Release: 9.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages texlive depends on:
ii texlive-fonts-recommended 2016.20170123-4
ii texlive-latex-base 2016.20170123-4
ii texlive-latex-recommended 2016.20170123-4
texlive recommends no packages.
texlive suggests no packages.
Versions of packages tex-common depends on:
ii dpkg 1.18.22
ii ucf 3.0036
Versions of packages tex-common suggests:
ii debhelper 10.2.5
Versions of packages texlive is related to:
ii tex-common6.06
ii texlive-binaries 2016.20160513.41080.dfsg-1
-- no debconf information
Bug#834595: mate-desktop: cursor doesn't follow finger on the touchscreen if second display is attached
control: reassign -1 xserver-xorg-input-all I have a ThinkPad Yoga 12, which has a touchscreen. In a normal session, I can move my finger on the touchscreen, and the cursor will follow the finger. Just like it is supposed to. However, I now plug in an external display. By default, it is supposed to be physically located to the right of my primary display, i.e., my desktop is now twice as wide; the left part is on my built-in display, the right part on the external one. In this situation, the code that computes the cursor position from my finger position on the touchscreen is wrong: when I move my finger from the left edge to to the right edge of my primal display, the cursor moves from the left boundary to the right boundary of the entire virtual desktop. In particular, if I touch the screen in the right half, the cursor appears on the other display. As it turns out, this is not a Mate issue: I see the same effect with a KF5 Plasma desktop. +++--=--= un xserver-xorg-input(keine Beschreibung vorhanden) un xserver-xorg-input-2 (keine Beschreibung vorhanden) un xserver-xorg-input-2.1(keine Beschreibung vorhanden) un xserver-xorg-input-4 (keine Beschreibung vorhanden) un xserver-xorg-input-7 (keine Beschreibung vorhanden) ii xserver-xorg-input-all 1:7.7+16 amd64X.Org X server -- input driver metapackage ii xserver-xorg-input-evdev 1:2.10.2-1amd64X.Org X server -- evdev input driver un xserver-xorg-input-evtouch(keine Beschreibung vorhanden) un xserver-xorg-input-joystick (keine Beschreibung vorhanden) ii xserver-xorg-input-libinput 0.19.0-1 amd64X.Org X server -- libinput input driver ii xserver-xorg-input-mouse 1:1.9.1-1+b1 amd64X.Org X server -- mouse input driver ii xserver-xorg-input-synaptics 1.8.3-2 amd64Synaptics TouchPad driver for X.Org server un xserver-xorg-input-tslib (keine Beschreibung vorhanden) ii xserver-xorg-input-vmmouse 1:13.1.0-1+b1 amd64X.Org X server -- VMMouse input driver to use with VMWare ii xserver-xorg-input-wacom 0.30.0-1+b1 amd64X.Org X server -- Wacom input driver signature.asc Description: OpenPGP digital signature
Bug#834593: plasma-workspace: Plasma fails to load: "all shell packages missing"
Interesting -- I didn't. And installing it pulled in so much stuff that I am really surprised now that plasma ever worked for me. Anyway. With the plasma-desktop package I have my shell back, and the bug can be closed. Gracias, Maximiliano! signature.asc Description: OpenPGP digital signature
Bug#834593: plasma-workspace: Plasma fails to load: "all shell packages missing"
¡Hola Maximiliano! > Can you check the value of the XDG_DATA_DIRS? it's /usr/share:/usr/share:/usr/local/share (I got a konsole using krunner) signature.asc Description: OpenPGP digital signature
Bug#834595: mate-desktop: cursor doesn't follow finger on the touchscreen if second display is attached
I have plasma installed along with Mate, but I can't even login right now because of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834593 Is there another way to test whether this is in Mate or in the layers below? signature.asc Description: OpenPGP digital signature
Bug#834595: mate-desktop: cursor doesn't follow finger on the touchscreen if second display is attached
... or try the login manager? In fact, I also see the same effect after a reboot in sddm, before even loggin into Mate. So if it is not Mate, what's the correct pacakge for this bug? Can you please reassign it? Thanks. signature.asc Description: OpenPGP digital signature
Bug#834595: mate-desktop: cursor doesn't follow finger on the touchscreen if second display is attached
Package: mate-desktop Version: 1.14.1-1 Severity: normal I am not quite sure what package to report this bug against. Apologies if I picked the wrong one. I have a ThinkPad Yoga 12, which has a touchscreen. In a normal MATE session, I can move my finger on the touchscreen, and the cursor will follow the finger. Just like it is supposed to. However, I now plug in an external display. By default, it is supposed to be physically located to the right of my primary display, i.e., my desktop is now twice as wide; the left part is on my built-in display, the right part on the external one. In this situation, the code that computes the cursor position from my finger position on the touchscreen is wrong: when I move my finger from the left edge to to the right edge of my primal display, the cursor moves from the left boundary to the right boundary of the entire virtual desktop. In particular, if I touch the screen in the right half, the cursor appears on the other display. -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mate-desktop depends on: ii hicolor-icon-theme0.15-1 ii libatk1.0-0 2.20.0-1 ii libc6 2.23-4 ii libcairo-gobject2 1.14.6-1+b1 ii libcairo2 1.14.6-1+b1 ii libgdk-pixbuf2.0-02.34.0-1 ii libglib2.0-0 2.48.1-2 ii libgtk-3-03.20.7-1 ii libmate-desktop-2-17 1.14.1-1 ii libpango-1.0-01.40.1-1 ii libpangocairo-1.0-0 1.40.1-1 ii libstartup-notification0 0.12-4 ii libxrandr22:1.5.0-1 ii mate-desktop-common 1.14.1-1 ii mate-user-guide 1.14.0-1 ii python2.7.11-2 ii python-requests 2.10.0-2 mate-desktop recommends no packages. mate-desktop suggests no packages. -- no debconf information
Bug#834593: plasma-workspace: Plasma fails to load: "all shell packages missing"
Package: plasma-workspace Version: 4:5.6.5.1-1 Severity: normal I am not quite sure what package to report this bug against. Apologies if I picked the wrong one. After a recent update, I cannot log into the KF5 plasma shell anymore. After entering the password, the screen becomes black, and I get a window saying "All shell packages missing. This is an installation issue, please contact your distribution" The same issue has been reported for Ubuntu systems, e.g., here: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1576500 However, in that report snapd appears to be the culprit, which I don't have installed. -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plasma-workspace depends on: ii dbus-x11 1.10.8-1 ii frameworkintegration 5.23.0-1 ii gdb-minimal [gdb]7.11.1-2 ii kde-cli-tools4:5.7.0-1 ii kded55.23.0-1 ii kinit5.23.0-1 ii kio 5.23.0-1 ii libc62.23-4 ii libcln6 1.3.4-1 ii libdbusmenu-qt5-20.9.3+16.04.20160218-1 ii libgcc1 1:6.1.1-11 ii libgps22 3.16-2 ii libice6 2:1.0.9-1+b1 ii libkf5activities55.23.0-1 ii libkf5auth5 5.23.0-1 ii libkf5baloo5 5.23.0-1 ii libkf5bookmarks5 5.23.0-1 ii libkf5completion55.23.0-1 ii libkf5configcore55.23.0-1 ii libkf5configgui5 5.23.0-1 ii libkf5configwidgets5 5.23.0-1 ii libkf5coreaddons55.23.0-1 ii libkf5crash5 5.23.0-1 ii libkf5dbusaddons55.23.0-1 ii libkf5declarative5 5.23.0-1 ii libkf5globalaccel-bin5.23.0-1 ii libkf5globalaccel5 5.23.0-1 ii libkf5guiaddons5 5.23.0-1 ii libkf5i18n5 5.23.0-1 ii libkf5iconthemes55.23.0-1 ii libkf5idletime5 5.23.0-1 ii libkf5itemviews5 5.23.0-1 ii libkf5jobwidgets55.23.0-1 ii libkf5js55.23.0-1 ii libkf5jsembed5 5.23.0-1 ii libkf5kdelibs4support5 5.23.0-1 ii libkf5kiocore5 5.23.0-1 ii libkf5kiofilewidgets55.23.0-1 ii libkf5kiowidgets55.23.0-1 ii libkf5networkmanagerqt6 5.23.0-1 ii libkf5newstuff5 5.23.0-1 ii libkf5notifications5 5.23.0-1 ii libkf5notifyconfig5 5.23.0-1 ii libkf5package5 5.23.0-1 ii libkf5plasma55.23.0-1 ii libkf5plasmaquick5 5.23.0-1 ii libkf5quickaddons5 5.23.0-1 ii libkf5runner55.23.0-1 ii libkf5screen-bin 4:5.7.0-1 ii libkf5screen74:5.7.0-1 ii libkf5service-bin5.23.0-1 ii libkf5service5 5.23.0-1 ii libkf5solid5 5.23.0-1 ii libkf5su55.23.0-1 ii libkf5texteditor55.23.0-1 ii libkf5textwidgets5 5.23.0-1 ii libkf5wallet-bin 5.23.0-3 ii libkf5wallet55.23.0-3 ii libkf5waylandclient5 4:5.23.0-1 ii libkf5widgetsaddons5 5.23.0-1 ii libkf5windowsystem5 5.23.0-1 ii libkf5xmlgui55.23.0-1 ii libkf5xmlrpcclient5 5.23.0-1 ii libkscreenlocker55.7.0-1 ii libksgrd74:5.7.0-1 ii libkworkspace5-5 4:5.6.5.1-1 ii libphonon4qt5-4 4:4.9.0-4 ii libplasma-geolocation-interface5 4:5.6.5.1-1 ii libprocesscore7 4:5.7.0-1 ii libprocessui74:5.7.0-1 ii libqalculate5v5 0.9.7-9.1+b1 ii libqt5core5a 5.6.1+dfsg-3+b1 ii
Bug#787095: texlive-latex-extra: Example tex file for pdfcomment.sty does not build
The upstream maintainer has commented on the issue: the root of the issue seems to be some unfortunate interaction with the microtype and zref packages. Not loading the microtype package (which is not used anyway) will fix the issue. The maintainer promised to do this for some upcoming bugfix release. signature.asc Description: OpenPGP digital signature
Bug#787095: texlive-latex-extra: Example tex file for pdfcomment.sty does not build
Hi Norbert, thanks for the quick reply. Upstream bug report is https://bitbucket.org/kleberj/pdfcomment/issue/16/exampletex-does-not-build Thanks, Oliver signature.asc Description: OpenPGP digital signature
Bug#787095: texlive-latex-extra: Example tex file for pdfcomment.sty does not build
Package: texlive-latex-extra Version: 2014.20141024-1 Severity: normal Dear Maintainer, [caveat: I am not sure whether to report this here or upstream, in particular since I am not sure whether pdfcomment contains the bug or triggers the bug. I will gladly report the bug upstream if you consider that more appropriate.] The pdfcomment package that comes as part of texlive-latex-extra includes a few example documents as part of its documentation. However, the main one, called 'example.tex' cannot be build using texlive. Here is what happens: ~/tmp/foo cp /usr/share/doc/texlive-doc/latex/pdfcomment/example.tex.gz . ~/tmp/foo ls example.tex.gz ~/tmp/foo gunzip example.tex.gz ~/tmp/foo ls example.tex ~/tmp/foo pdflatex example.tex This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2015/dev/Debian) (preloaded format=pdflatex) restricted \write18 enabled. entering extended mode (./example.tex LaTeX2e 2014/05/01 Babel 3.9l and hyphenation patterns for 7 languages loaded. (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrartcl.cls Document Class: scrartcl 2013/12/19 v3.12 KOMA-Script document class (article) (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrkbase.sty (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrbase.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile.sty Package scrlfile, 2013/12/19 v3.12 KOMA-Script package (loading files) Copyright (C) Markus Kohm ))) (/usr/share/texlive/texmf-dist/tex/latex/koma-script/tocbasic.sty) (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrsize11pt.clo) (/usr/share/texlive/texmf-dist/tex/latex/koma-script/typearea.sty Package typearea, 2013/12/19 v3.12 KOMA-Script package (type area) Copyright (C) Frank Neukam, 1992-1994 Copyright (C) Markus Kohm, 1994- )) (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def))) (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def)) (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def)) (/usr/share/texmf/tex/latex/lm/lmodern.sty) (/usr/share/texlive/texmf-dist/tex/latex/microtype/microtype.sty (/usr/share/texlive/texmf-dist/tex/latex/microtype/microtype-pdftex.def) (/usr/share/texlive/texmf-dist/tex/latex/microtype/microtype.cfg)) (/usr/share/texlive/texmf-dist/tex/latex/lipsum/lipsum.sty) (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/color.cfg) (/usr/share/texlive/texmf-dist/tex/latex/pdftex-def/pdftex.def (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)) (/usr/share/texlive/texmf-dist/tex/latex/xcolor/svgnam.def)) (/usr/share/texlive/texmf-dist/tex/latex/textpos/textpos.sty Package: textpos 2014/01/03 1.7j, absolute positioning of text on the page (/usr/share/texlive/texmf-dist/tex/latex/ms/everyshi.sty) Grid set 16 x 16 = 37.34424pt x 52.81543pt TextBlockOrigin set to 0pt x 0pt ) (/usr/share/texlive/texmf-dist/tex/latex/pgf/frontendlayer/tikz.sty (/usr/share/texlive/texmf-dist/tex/latex/pgf/basiclayer/pgf.sty (/usr/share/texlive/texmf-dist/tex/latex/pgf/utilities/pgfrcs.sty (/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfutil-common.tex (/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfutil-common-lists.t ex)) (/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfutil-latex.def ) (/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfrcs.code.tex)) (/usr/share/texlive/texmf-dist/tex/latex/pgf/basiclayer/pgfcore.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg))) (/usr/share/texlive/texmf-dist/tex/latex/pgf/systemlayer/pgfsys.sty (/usr/share/texlive/texmf-dist/tex/generic/pgf/systemlayer/pgfsys.code.tex (/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfkeys.code.tex (/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfkeysfiltered.code.t ex)) (/usr/share/texlive/texmf-dist/tex/generic/pgf/systemlayer/pgf.cfg) (/usr/share/texlive/texmf-dist/tex/generic/pgf/systemlayer/pgfsys-pdftex.def (/usr/share/texlive/texmf-dist/tex/generic/pgf/systemlayer/pgfsys-common-pdf.de f))) (/usr/share/texlive/texmf-dist/tex/generic/pgf/systemlayer/pgfsyssoftpath.code. tex) (/usr/share/texlive/texmf-dist/tex/generic/pgf/systemlayer/pgfsysprotocol.code. tex)) (/usr/share/texlive/texmf-dist/tex/generic/pgf/basiclayer/pgfcore.code.tex (/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmath.code.tex
Bug#771222: adolc: ADOLC computes wrong second derivatives of the log function in vector mode
Source: adolc Version: 2.5.2 Severity: important Tags: patch Dear Maintainer, ADOL-C computes wrong second derivatives for the log function in vector mode. I consider this bug 'important', because you may not even notice right away that your results are wrong. The bug has been fixed upstream in commit 1fd1caefc8d6874162463a9f7123f54ed5f05964 after the 2.5.2 release (which is the one in Debian). The trivial patch is appended below. Please consider applying it to the version that will be in Jessie. Thanks. commit 1fd1caefc8d6874162463a9f7123f54ed5f05964 Author: kulshres kulshres@94ac48a7-3327-4b6a-8511-9a4036a20e83 Date: Fri Aug 29 06:47:22 2014 + increment the correct pointer in log_op reverse mode this op has no use for Targ2 but Targ is used in the statements above so incrementing Targ2 is the silliest mistake I've seen so far. Signed-off-by: Kshitij Kulshreshtha kshi...@math.upb.de git-svn-id: https://projects.coin-or.org/svn/ADOL-C/trunk@568 94ac48a7-3327-4b6a-8511-9a4036a20e83 diff --git a/ADOL-C/src/ho_rev.c b/ADOL-C/src/ho_rev.c index 28591e5..a5d5c03 100644 --- a/ADOL-C/src/ho_rev.c +++ b/ADOL-C/src/ho_rev.c @@ -1688,7 +1688,7 @@ int hov_ti_reverse( HOV_INC(Ares, k) HOV_INC(Aarg, k) - HOS_OV_INC(Targ2, k) + HOS_OV_INC(Targ, k) } } break; -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: OpenPGP digital signature
Bug#703439: H5Cpp.h missing in libhdf5-openmpi-dev and libhdf5-mpich2-dev?
I had a quick look at the package, since the hdf5 FAQ says: If the build completes properly and the tests pass, then the installation should be okay. You need two options for 'configure': --enable-unsupported and --enable-cxx. Somewhat surprisingly, the first one is already set in debian/rules. I added --enable-cxx and tried to build the package on my Debian Jessie machine. The build fails with make[2]: Entering directory `/home/sander/hdf5/hdf5-1.8.12/debian/build-openmpi/c++' Making all in src make[3]: Entering directory `/home/sander/hdf5/hdf5-1.8.12/debian/build-openmpi/c++/src' CXX H5Exception.lo In file included from ../../../../src/hdf5.h:24:0, from ../../../../c++/src/H5Include.h:17, from ../../../../c++/src/H5Exception.cpp:18: ../../../../src/H5public.h:63:20: fatal error: mpi.h: No such file or directory # include mpi.h ^ compilation terminated. make[3]: *** [H5Exception.lo] Fehler 1 make[3]: Leaving directory `/home/sander/hdf5/hdf5-1.8.12/debian/build-openmpi/c++/src' make[2]: *** [all-recursive] Fehler 1 make[2]: Leaving directory `/home/sander/hdf5/hdf5-1.8.12/debian/build-openmpi/c++' make[1]: *** [all-recursive] Fehler 1 make[1]: Leaving directory `/home/sander/hdf5/hdf5-1.8.12/debian/build-openmpi' make: *** [build-stamp-openmpi] Fehler 2 dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules build war 2 Any ideas? signature.asc Description: OpenPGP digital signature
Bug#703439: H5Cpp.h missing in libhdf5-openmpi-dev and libhdf5-mpich2-dev?
Any chance of having the C++ interface enabled in Debian, even though its 'at our own risk'? My problem is the following: I use gmsh a lot, which depends on libhdf5-openmpi. Hence I am stuck with the parallel version of hdf5, even though I don't actually use any of its parallel features. Now as a consequence of this bug I cannot build any programs that use the hdf5 C++ interface. It's either gmsh or C++ hdf5, but I need both. Thanks, Oliver signature.asc Description: OpenPGP digital signature
Bug#684064: coinor-libipopt-dev: Missing ATL_*** symbols when linking to libipopt
Hi Roberto, it does indeed sound related. I have been getting warnings like may conflict with libblas.so.3 or similar in other occasions too, but I don't know enough about the background to really tell. Feel free to merge the bugs and do whatever you find appropriate. Thanks, Oliver signature.asc Description: OpenPGP digital signature
Bug#706514: RFS: dcraw/9.17-1
Hi Anton, Problem is, I don't understand how much these rules apply to me, since the actual upload to unstable will not be done by me. That case is not covered by the text. It does not matter, who physically uploads the package e.g. sponsors it. In this case you are the author of changes. Thanks, that fills a long-standing gap in my knowledge. But then it is a NMU (unless I become maintainer first), and should have a NMU number? I would upload it into, for example, 14-DAY queue, if: 1) you will continue to maintain it; 2) original maintainer will not react. 3) the package technically be OK. I start to feel a little like the famous donkey with the carot held in front. Everytime I do something to improve the package there are new requirements that pop up. I usually upload the package, even there are some minor problems, which would be good to fix. But from my point of view, the current status of the package is not enough good to be uploaded in Debian. The package is way better than the current one in Debian. Please recall that I did not start from scratch, but from the package currently in stable/testing/unstable. Is there a rule in Debian saying that improving one thing in a package can only be done when all other known problems are fixed at the same time as well? Please, fix patch-issues. Patch should be minimal and clear. if you do not understand, what the patch does - just remove it and check the package functionality. I pointed already the problems with .badpixels and gpg_key file. See above. The actual maintainer added those files to the package, and I don't really know what they do. But just because _I_ don't know what they do that doesn't mean they don't serve a purpose. That's why I kept them in. Also it is very important to decide, whether you want to (co)-maintain the package. If not - who will fix the possible problems after the uploading of new version? That's why my original intention was to change the package only minimally, and _only_ exchange the single source file with a newer one. But somehow I got coerced into rewriting the entire package... Cheers, Oliver @Steve, please, clarify, whether you want to maintain the package further. Cheers, Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706514: RFS: dcraw/9.17-1
Am 11.07.2013 22:45, schrieb Anton Gladky: 2013/7/11 Oliver Sandersan...@igpm.rwth-aachen.de: I don't understand. I am not the maintainer, hence what I am doing is a NMU, hence the NMU number? Please tell me the version number you want and I'll use it. Hmm, please, read, when you are allowed to do NMUs. http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu I kind of knew these rules, but it's good to now the details anyway. Problem is, I don't understand how much these rules apply to me, since the actual upload to unstable will not be done by me. That case is not covered by the text. I was thinking, you want to (co-)maintain the package (CC-ing original maintainer again). I do consider doing so, but so far I have not even managed to get anything uploaded at all. (no offense) Best, Oliver Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706514: RFS: dcraw/9.17-1
Add to description something like: Fixing lintiant warnings in manpages. I will do that, but please comment on my questions below first. Plus, we are now at dcraw-9.19-1.1, because upstream has made two new releases in the meantime. ,,,1.1 is not correct version number. You are not doing NMU, so the last number should be integer. See the Debian Policy. I don't understand. I am not the maintainer, hence what I am doing is a NMU, hence the NMU number? Please tell me the version number you want and I'll use it. I still do not understand, what are you doing with patch. import_from_old_1.0_format.diff: a) why do you add gpg_key? What is that? I have no clue. It is not from upstream, but must have been added by the package maintainer instead. I didn't want to remove it without knowing why it is there. b) why do you add badpixel, if it is shipped by upstream? Same here: I am just keeping what the actual package currently in Debian does. In this case, upstream ships a file .badpixels (note the leading dot), and the packaging renames it to badpixels (without the dot). No idea why. best, Oliver Patches are only to fix some problems, in the source code. No need to add there everything. Please, look also into Debian Developer's reference, if you find time. Cheers, Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706514: RFS: dcraw/9.17-1
Thanks for the hints, I just uploaded a new version. That's a thing that I still don't understand. In an AutoTools environment all you need is configure.in and Makefile.in. The files configure and Makefile are then created automatically. However when I remove configure and Makefile from the patch, nothing is built at all. You shoud, probably, use autoreconf. See an attachment. That is what I was looking for. The files 'configure' and 'Makefile' have now been removed from the patch. use DEP-5 for copyright, Done. use dcraw.manpages and dcraw.exapmles instead of putting them into the override_*. Done. Thanks for the explanation. I am getting one new lintian warning: I: dcraw source: quilt-patch-missing-description remove_LO_line_from_manpage.diff I split that patch off from the remaining ones, because it was obviously a separate thing. But not knowing manpage syntax at all I have no clue what the patch actually does. Hence I cannot provide a patch description. Plus, we are now at dcraw-9.19-1.1, because upstream has made two new releases in the meantime. Best, Oliver -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706514: RFS: dcraw/9.17-1
Hi Anton, I finally got around to looking at the package again. Currently getsource doesn't run due to some minor upstream format change. Can you fix that? I fixed the first bug it runs into. It still doesn't seem to work, though. No idea what is missing. Yes, but in the previous uploaded version there are in patch-section only Makefile, badpixels and manpages. You have now also configure, Makefile.in etc. That's a thing that I still don't understand. In an AutoTools environment all you need is configure.in and Makefile.in. The files configure and Makefile are then created automatically. However when I remove configure and Makefile from the patch, nothing is built at all. Please, add into the patch only Makefile and badpixels. Manpages can be stored somewhere in debian-directory (debian/manpages, for example). All non-upstream manpages are in debian/manpages now. I have now uploaded dcraw-9.17-1.1, which contains all my fixes and cleanups in a single changelog entry. Ok, looks good. Please, clean patches, see above: The manpages have been removed, but configure and Makefile are still there. try to fix watch-file, Beyond my time/skill resources. Besides, the getsource script is not a real watch file. use DEP-5 for copyright, The standard says this is optional. http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ check README.debian (update or remove it, if the info is outdated), Done. use dcraw.manpages and dcraw.exapmles instead of putting them into the override_*. I don't understand what you mean here. Best, Oliver Thanks for your work, Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706514: RFS: dcraw/9.17-1
Hi Anton, I finally found the time to look at the dcraw package again. lintian reports three problems with this package, which I don't know how to fix: P: dcraw: no-upstream-changelog There really is no upstream changelog. What to do? Id upstream does not ship it, you can do nothing with that. Okay. W: dcraw source: package-needs-versioned-debhelper-build-depends 9 The lintian documentation says the following about this: Note if you are using a compat level, which is marked as experimental, such as compat 9 in debhelper 8.1.3, then please override this tag. But I'd rather not override anything without explicitly being told to do so by a sponsor. in control file: debhelper (=9) Done. I: dcraw source: debian-watch-file-is-missing Upstream doesn't really have a precise location to watch. The individual files that make up the orig.tar.gz appear separately on the upstream homepage. What to do? If the upstream does not ship tarballs systematically, you can unlikely create a working watch-file. There is getsource script in the tarball. Did you check it, whether it works? Currently getsource doesn't run due to some minor upstream format change. There are two more problems I have with this package: a) The quilt patch contains the files Makefile and configure, even though those should be created automatically during package building from Makefile.in and configure.in (which are also in the patch file). However when I remove Makefile and/or configure from the patch, then the binaries do not get build at all. I'm afraid I don't really know where to look further for the problem, here. The patch is really terrible. It is what you get when following the official Debian instructions for switching from source format 1.0 to 3.0 (quilt). http://www.debian.org/doc/manuals/maint-guide/update.de.html (see 9.4). I would suggest you to use cmake instead of it. See an attachment. You just need to add all other binaries and test them. Actually, I'd rather not. First of all I don't think you can't make it nice with the AutoTools. Also, I've never worked with CMake before. Finally, I used the AutoTools because you implicitly recommended them (by giving me the admesh package for guidance). b) I know I messed up the versioning, but before messing it up further I'd like to get advice on how to proceed. What should the version of my final upload be? current in sid + 1. I have now uploaded dcraw-9.17-1.1, which contains all my fixes and cleanups in a single changelog entry. Best, Oliver Cheers, Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707635: ThinkPad X230: right touchpad button functions as left button when touchpad is touched
Package: src:linux Version: 3.8.11-1 Severity: minor Dear Maintainer, I have a Lenovo ThinkPad X230, running Wheezy and the 3.8.11 kernel from today's unstable. The touchpad works okay, in particular the two buttons do what they are supposed to do. Unless, that is, I have a finger resting on the touchpad. Then the right button triggers the same actions as the left button, until I remove my finger from the touchpad again. This can be reproduced all the time. It has behaved that way for all kernels I tried between 3.2 and the current one. -- Package-specific info: ** Version: Linux version 3.8-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.8.11-1 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.8-1-amd64 root=UUID=64517d02-ab77-4577-9b35-cf21c25cb293 ro quiet ** Not tainted ** Kernel log: [ 7214.785370] Freezing user space processes ... (elapsed 0.01 seconds) done. [ 7214.799730] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [ 7214.815693] PM: Entering mem sleep [ 7214.815737] Suspending console(s) (use no_console_suspend to debug) [ 7214.944815] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 7214.947356] sd 0:0:0:0: [sda] Stopping disk [ 7215.220319] e1000e :00:19.0: System wakeup enabled by ACPI [ 7215.461905] ACPI: Cannot transition to non-D0 state from D3 [ 7215.529859] PM: suspend of devices complete after 715.862 msecs [ 7215.529959] PM: late suspend of devices complete after 0.098 msecs [ 7215.545793] ehci-pci :00:1d.0: System wakeup enabled by ACPI [ 7215.561626] ehci-pci :00:1d.0: power state changed by ACPI to D3hot [ 7215.561711] ehci-pci :00:1a.0: System wakeup enabled by ACPI [ 7215.577582] ehci-pci :00:1a.0: power state changed by ACPI to D3hot [ 7215.593603] xhci_hcd :00:14.0: System wakeup enabled by ACPI [ 7215.609500] xhci_hcd :00:14.0: power state changed by ACPI to D3hot [ 7215.609562] PM: noirq suspend of devices complete after 79.804 msecs [ 7215.610158] ACPI: Preparing to enter system sleep state S3 [ 7215.781100] PM: Saving platform NVS memory [ 7215.782526] Disabling non-boot CPUs ... [ 7215.884811] smpboot: CPU 1 is now offline [ 7215.886311] smpboot: CPU 2 is now offline [ 7215.887712] smpboot: CPU 3 is now offline [ 7215.888010] Extended CMOS year: 2000 [ 7215.888997] ACPI: Low-level resume complete [ 7215.889035] PM: Restoring platform NVS memory [ 7215.889413] Extended CMOS year: 2000 [ 7215.890003] microcode: CPU0 updated to revision 0x17, date = 2013-01-09 [ 7215.890019] Enabling non-boot CPUs ... [ 7215.890107] smpboot: Booting Node 0 Processor 1 APIC 0x1 [ 7215.903962] microcode: CPU1 updated to revision 0x17, date = 2013-01-09 [ 7215.982038] CPU1 is up [ 7215.982137] smpboot: Booting Node 0 Processor 2 APIC 0x2 [ 7215.995984] microcode: CPU2 updated to revision 0x17, date = 2013-01-09 [ 7216.073797] CPU2 is up [ 7216.073896] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 7216.087758] microcode: CPU3 updated to revision 0x17, date = 2013-01-09 [ 7216.165568] CPU3 is up [ 7216.168716] ACPI: Waking up from system sleep state S3 [ 7216.357034] ACPI: \_SB_.PCI0.LPC_.EC__.BAT1: docking [ 7216.384952] ACPI: \_SB_.PCI0.LPC_.EC__.BAT1: Unable to dock! [ 7216.516670] i915 :00:02.0: power state changed by ACPI to D0 [ 7216.532568] xhci_hcd :00:14.0: power state changed by ACPI to D0 [ 7216.548586] xhci_hcd :00:14.0: System wakeup disabled by ACPI [ 7216.596417] ehci-pci :00:1a.0: power state changed by ACPI to D0 [ 7216.612383] ehci-pci :00:1a.0: System wakeup disabled by ACPI [ 7216.628570] ehci-pci :00:1d.0: power state changed by ACPI to D0 [ 7216.644305] ehci-pci :00:1d.0: System wakeup disabled by ACPI [ 7216.676489] sdhci-pci :02:00.0: MMC controller base frequency changed to 50Mhz. [ 7216.692687] PM: noirq resume of devices complete after 176.536 msecs [ 7216.692776] PM: early resume of devices complete after 0.065 msecs [ 7216.692802] i915 :00:02.0: setting latency timer to 64 [ 7216.692805] xhci_hcd :00:14.0: setting latency timer to 64 [ 7216.692849] mei :00:16.0: irq 41 for MSI/MSI-X [ 7216.692862] e1000e :00:19.0: System wakeup disabled by ACPI [ 7216.692885] ehci-pci :00:1a.0: setting latency timer to 64 [ 7216.692912] ehci-pci :00:1d.0: setting latency timer to 64 [ 7216.692954] ahci :00:1f.2: setting latency timer to 64 [ 7216.692971] snd_hda_intel :00:1b.0: irq 43 for MSI/MSI-X [ 7216.693124] e1000e :00:19.0: irq 46 for MSI/MSI-X [ 7216.748103] tpm_tis 00:09: TPM is disabled/deactivated (0x6) [ 7216.748562] Extended CMOS year: 2000 [ 7216.923718] usb 3-1.6: reset high-speed USB device number 5 using ehci-pci [ 7217.035297] ata2: SATA link down (SStatus 0 SControl 300) [ 7217.035349] ata5: SATA link down (SStatus 0 SControl 300) [ 7217.043306] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7217.043986] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 7217.043991]
Bug#706514: RFS: dcraw/9.17-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package dcraw * Package name: dcraw Version : 9.17-1 Upstream Author : Dave Coffin, dcoffin a cybercom period net * URL : http://www.cybercom.net/~dcoffin/dcraw/ * License : GPL v2 Section : graphics It builds those binary packages: dcraw - decode raw digital camera images To access further information about this package, please visit the following URL: http://mentors.debian.net/package/dcraw Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/d/dcraw/dcraw_9.17-1.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * New upstream release (Closes: #617543) * Build-depend on libjasper-dev Regards, Oliver Sander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706514: RFS: dcraw/9.17-1
Hi Anton, thanks for the quick reply. You are right: I should have asked the maintainers before. My apologies. I needed the package for myself, and then figured why not learn how to upload? I'm not surprised that the packaging is old. I basically just took the last package und stuffed in the new upstream code. I can try to improve it a little, but let's hear what Steve says first. Thanks, Oliver Am 01.05.2013 17:55, schrieb Anton Gladky: Hi Oliver, thanks for providing the new version of the package! But to do such uploads you should be or (co)maintainer of the package or at least to get a permission from the current maintainer (CC-ing him), as the package has not been orphaned. From the technical point of view the package needs to be fixed before uploading into the archive: see the list of errors/warnings [1]. The last package uploading was 3 years ago and it really requires some work on it. It would be good to know the opinion of the current maintainer, whether he interested to continue it. Thank you, Anton [1] http://mentors.debian.net/package/dcraw On 05/01/2013 08:42 AM, Oliver Sander wrote: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package dcraw * Package name: dcraw Version : 9.17-1 Upstream Author : Dave Coffin, dcoffin a cybercom period net * URL : http://www.cybercom.net/~dcoffin/dcraw/ * License : GPL v2 Section : graphics It builds those binary packages: dcraw - decode raw digital camera images To access further information about this package, please visit the following URL: http://mentors.debian.net/package/dcraw Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/d/dcraw/dcraw_9.17-1.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * New upstream release (Closes: #617543) * Build-depend on libjasper-dev Regards, Oliver Sander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617543: New upstream release 9.17 packaged
A package for the current release 9.19 can now be found at mentors.debian.net https://mentors.debian.net/package/dcraw -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592943: Feel free to close
I have gotten rid of this hardware. Feel free to close the bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693698: latexmk: Typo in German package description (letexmk instead of latexmk)
Package: latexmk Version: 1:4.24-1 Severity: minor Tags: l10n Dear Maintainer, The German description of the latexmk package contains a typo. aptitude show latexmk prints text starting with Letexmk führt LaTex in ... It should obviously be Latexmk führt LaTex in ... -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages latexmk depends on: ii perl5.14.2-15 ii texlive-latex-base 2012.20120611-5 Versions of packages latexmk recommends: ii acroread [pdf-viewer]9.5.1-0.1 ii evince [postscript-viewer] 3.4.0-3 ii ghostscript [postscript-viewer] 9.05~dfsg-6.2 ii okular [postscript-viewer] 4:4.8.4-2 Versions of packages latexmk suggests: pn gs-common none -- 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#593477: Fixed in KDE 4.10
This bug has been fixed upstream, the fix will be in KDE 4.10: https://bugs.kde.org/show_bug.cgi?id=300051 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684062: coinor-libipopt-dev: stddef-related flag missing
Package: coinor-libipopt-dev Version: 3.10.2-1.1 Severity: important Dear Maintainer, I have code using IPOpt which I ran up until recently with an old (3.5.5) hand-compiled version of IPOpt. Now I am trying to use the one in Debian (thanks for packaging, btw!), but I run into a problem: compiling a simple test problem gives me g++ -std=c++0x -DHAVE_CONFIG_H -I. -I../../.. -I/home/sander/dune/dune-common -I/home/sander/dune/dune-geometry -I/home/sander/dune/dune-grid -I/home/sander/dune/dune-istl -I/home/sander/dune/dune-localfunctions -I../../..-g -MT quadraticipoptsolvertest-quadraticipoptsolvertest.o -MD -MP -MF .deps/quadraticipoptsolvertest-quadraticipoptsolvertest.Tpo -c -o quadraticipoptsolvertest-quadraticipoptsolvertest.o `test -f 'quadraticipoptsolvertest.cc' || echo './'`quadraticipoptsolvertest.cc In file included from /usr/include/coin/IpJournalist.hpp:15:0, from /usr/include/coin/IpException.hpp:13, from /usr/include/coin/IpTNLP.hpp:14, from ../../../dune/solvers/solvers/quadraticipopt.hh:22, from quadraticipoptsolvertest.cc:18: /usr/include/coin/IpSmartPtr.hpp:18:4: error: #error don't have header file for stddef make: *** [quadraticipoptsolvertest-quadraticipoptsolvertest.o] Fehler 1 The code snippet around the error line is #ifdef HAVE_CSTDDEF # include cstddef #else # ifdef HAVE_STDDEF_H # include stddef.h # else # error don't have header file for stddef # endif #endif Indeed, neither HAVE_CSTDDEF nor HAVE_STDDEF_H is set by a compiler flag. I would expect it to be given by pkg-config, but pgk-config says only sander@igel:~/dune/dune-grid$ pkg-config --cflags ipopt -I/usr/include/coin Apologies if this is my own fault and not a bug. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages coinor-libipopt-dev depends on: ii coinor-libipopt1 3.10.2-1.1 coinor-libipopt-dev recommends no packages. coinor-libipopt-dev 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#684064: coinor-libipopt-dev: Missing ATL_*** symbols when linking to libipopt
Package: coinor-libipopt-dev Version: 3.10.2-1.1 Severity: normal Dear Maintainer, I have written an m4 tests that looks for an installation of ipopt. While it has worked with hand-installed older versions of IPOpt (=3.5.5), it doesn't work with the one in Debian, because it fails to link a test program. I attach the relevant snippet from my config.log. I'll be happy to provide more information if needed. PS: I am hacking my way around http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684062 for this one. configure:38257: checking for IPOPT configure:38264: $PKG_CONFIG --exists --print-errors ipopt configure:38267: $? = 0 configure:38281: $PKG_CONFIG --exists --print-errors ipopt configure:38284: $? = 0 configure:38326: result: yes configure:38377: g++ -std=c++0x -o conftest -g -I/home/sander/include conftest.cpp -lm -lipopt -ldmumps -lblas -lm -ldl 5 conftest.cpp:83:0: warning: HAVE_BOOST redefined [enabled by default] conftest.cpp:82:0: note: this is the location of the previous definition /usr/bin/ld: warning: libblas.so.3gf, needed by /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libdmumps.so, may conflict with libblas.so.3 /usr/lib/liblapack.so.3: undefined reference to `ATL_zptgemm' /usr/lib/liblapack.so.3: undefined reference to `ATL_scopy' /usr/lib/liblapack.so.3: undefined reference to `ATL_stpsv' /usr/lib/liblapack.so.3: undefined reference to `ATL_dtrsv' /usr/lib/liblapack.so.3: undefined reference to `ATL_sptgemm' /usr/lib/liblapack.so.3: undefined reference to `ATL_zgemv' /usr/lib/liblapack.so.3: undefined reference to `ATL_cher' /usr/lib/liblapack.so.3: undefined reference to `ATL_ssbmv' /usr/lib/liblapack.so.3: undefined reference to `ATL_caxpy' /usr/lib/liblapack.so.3: undefined reference to `ATL_sptsymm' /usr/lib/liblapack.so.3: undefined reference to `ATL_cgerc' /usr/lib/liblapack.so.3: undefined reference to `ATL_dnrm2' /usr/lib/liblapack.so.3: undefined reference to `ATL_dsyreflect' /usr/lib/liblapack.so.3: undefined reference to `ATL_sdsdot' /usr/lib/liblapack.so.3: undefined reference to `ATL_zrotg' /usr/lib/liblapack.so.3: undefined reference to `ATL_strsv' [...] collect2: error: ld returned 1 exit status configure:38377: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME dune-solvers | #define PACKAGE_TARNAME dune-solvers | #define PACKAGE_VERSION 0.10 | #define PACKAGE_STRING dune-solvers 0.10 | #define PACKAGE_BUGREPORT san...@mi.fu-berlin.de | #define PACKAGE_URL | #define PACKAGE dune-solvers | #define VERSION 0.10 | #define DUNE_SOLVERS_VERSION 0.10 | #define DUNE_SOLVERS_VERSION_MAJOR 0 | #define DUNE_SOLVERS_VERSION_MINOR 10 | #define DUNE_SOLVERS_VERSION_REVISION 0 | #define PACKAGE dune-solvers | #define VERSION 0.10 | #define STDC_HEADERS 1 | #define HAVE_SYS_TYPES_H 1 | #define HAVE_SYS_STAT_H 1 | #define HAVE_STDLIB_H 1 | #define HAVE_STRING_H 1 | #define HAVE_MEMORY_H 1 | #define HAVE_STRINGS_H 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_STDINT_H 1 | #define HAVE_UNISTD_H 1 | #define HAVE_DLFCN_H 1 | #define LT_OBJDIR .libs/ | #define HAVE_BLAS 1 | #define HAVE_LAPACK 1 | #define FC_FUNC(name,NAME) name ## _ | #define FC_FUNC_(name,NAME) name ## _ | #define HAVE_STATIC_ASSERT 1 | #define HAVE_NULLPTR 1 | #define HAVE_TYPE_TRAITS 1 | #define HAVE_TR1_TYPE_TRAITS 1 | #define HAVE_TUPLE 1 | #define HAVE_TR1_TUPLE 1 | #define HAVE_ARRAY 1 | #define HAVE_MEMORY 1 | #define HAVE_TR1_MEMORY 1 | #define HAVE_BOOST_SHARED_PTR_HPP 1 | #define SHARED_PTR_NAMESPACE std | #define SHARED_PTR_HEADER memory | #define HAVE_MAKE_SHARED 1 | #define HAS_ATTRIBUTE_DEPRECATED 1 | #define HAS_ATTRIBUTE_DEPRECATED_MSG 1 | #define HAS_ATTRIBUTE_UNUSED 1 | #define DUNE_MINIMAL_DEBUG_LEVEL 4 | #define HAVE_RPC_RPC_H 1 | #define HAVE_STDLIB_H 1 | #define HAVE_MALLOC 1 | #define HAVE_MALLOC_H 1 | #define HAVE_STRING_H 1 | #define HAVE_LIBM 1 | #define HAVE_SQRT 1 | #define HAVE_STRCHR 1 | #define HAVE_DUNE_COMMON 1 | #define DUNE_COMMON_VERSION 2.3-svn | #define DUNE_COMMON_VERSION_MAJOR 2 | #define DUNE_COMMON_VERSION_MINOR 3 | #define DUNE_COMMON_VERSION_REVISION 0 | #define HAVE_DUNE_GEOMETRY 1 | #define DUNE_GEOMETRY_VERSION 2.3-svn | #define DUNE_GEOMETRY_VERSION_MAJOR 2 | #define DUNE_GEOMETRY_VERSION_MINOR 3 | #define DUNE_GEOMETRY_VERSION_REVISION 0 | #define HAVE_PTHREAD 1 | #define HAVE_ALBERTA ENABLE_ALBERTA | #define DUNE_ALBERTA_VERSION 0x200 | #define HAVE_UG ENABLE_UG | #define HAVE_AMIRAMESH 1 | #define PSURFACE_NAMESPACE psurface:: | #define HAVE_PSURFACE 1 | #define HAVE_ALUGRID_SERIAL_H 1 | #define HAVE_ALUGRID_PARALLEL_H 1 | #define HAVE_ALUGRID ENABLE_ALUGRID | #define HAVE_DUNE_GRID 1 | #define DUNE_GRID_VERSION 2.3-svn | #define DUNE_GRID_VERSION_MAJOR 2 | #define DUNE_GRID_VERSION_MINOR 3 | #define DUNE_GRID_VERSION_REVISION 0 | #define HAVE_BOOST /**/ | #define HAVE_BOOST ENABLE_BOOST | #define HAVE_BOOST_FUSION /**/ | #define HAVE_DUNE_ISTL 1 | #define DUNE_ISTL_VERSION 2.3-svn | #define DUNE_ISTL_VERSION_MAJOR 2 | #define
Bug#684065: plasma-widgets-workspace: Plasma clock is badly rendered on vertical taskbar
Package: plasma-widgets-workspace Version: 4:4.8.4-3 Severity: minor Dear Maintainer, I am using a vertical taskbar to save some space on a wide screen. The plasma clock in that taskbar is rendered badly. There is about 10 cm vertical screen space between time and date, and the font for the date is too large for the date to fit on the bar. I'll attach a screenshot in a second. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plasma-widgets-workspace depends on: ii libc6 2.13-33 ii libkdecore5 4:4.8.4-3 ii libkdeui5 4:4.8.4-3 ii libkdewebkit5 4:4.8.4-3 ii libkio5 4:4.8.4-3 ii libkunitconversion4 4:4.8.4-3 ii libkworkspace4abi14:4.8.4-3 ii libplasma34:4.8.4-3 ii libplasmaclock4abi3 4:4.8.4-3 ii libqt4-dbus 4:4.8.2-1 ii libqt4-network4:4.8.2-1 ii libqt4-xml4:4.8.2-1 ii libqtcore44:4.8.2-1 ii libqtgui4 4:4.8.2-1 ii libqtwebkit4 2.2.1-4+b1 ii libsolid4 4:4.8.4-3 ii libstdc++64.7.1-2 ii libx11-6 2:1.5.0-1 ii libxcomposite11:0.4.3-2 ii libxdamage1 1:1.1.3-2 ii libxfixes31:5.0-4 ii libxrender1 1:0.9.7-1 ii plasma-dataengines-workspace 4:4.8.4-3 plasma-widgets-workspace recommends no packages. plasma-widgets-workspace 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#679203: dune-common-dev: Wish: have a meta package 'dune-dev'
Package: libdune-common-dev Version: 2.2.0-1 Severity: wishlist File: dune-common-dev Dear Maintainer, it would be great if there was a meta-package 'dune-dev' (or similarly named), which pulled in all dune-related modules. That would make dune installation easier. Thanks! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libdune-common-dev depends on: ii dpkg 1.16.4.2 ii libdune-common-2.2.0 2.2.0-1 Versions of packages libdune-common-dev recommends: ii autoconf2.69-1 ii automake1:1.11.5-2 ii libtool 2.4.2-1.1 ii pkg-config 0.26-1 Versions of packages libdune-common-dev suggests: pn libdune-common-dbg none -- 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#675148: texlive-extra: Please ship current file movie15.sty from ctan
Source: texlive-extra
Severity: wishlist
Dear Maintainer,
please consider uploading the current movie15.sty file from ctan
with the Wheezy release. That file differs only minimally from the
one currently in testing:
--- /usr/share/texlive/texmf-dist/tex/latex/movie15/movie15.sty 2012-03-29
01:00:05.0 +0200
+++ movie15.sty 2012-05-30 09:55:12.0 +0200
@@ -9,7 +9,7 @@
%
\NeedsTeXFormat{LaTeX2e}
-\ProvidesPackage{movie15}[2012/03/16]
+\ProvidesPackage{movie15}[2012/05/16]
\RequirePackage{keyval}
\RequirePackage{ifthen}
\RequirePackage{ifpdf}
@@ -1788,6 +1788,7 @@
/F 2%
\@MXV@@repeat\@MXV@@volume\@MXV@@ctrls%
/D /S /F%
+ \if@MXV@autoplay/A true\else/A false\fi%
%
%
}\edef\@MXV@mediarendition{\the\pdflastobj}\pdfrefobj\pdflastobj%
@@ -1968,6 +1969,7 @@
%annotation rectangle
\@MXV@@repeat\@MXV@@volume\@MXV@@ctrls%
/D /S /F%movie remains opened
+ \if@MXV@autoplay/A true\else/A false\fi%
%
%
%
This fix sets the autostart flag for embedded movies correctly in pdf files.
Without it movies always start automatically when viewing pdfs in okular
(use poppler 0.20 and a development version of okular if you want to try this).
Thanks.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593478: Okular shows black rectangle instead of first frame of a movie
This issue has been fixed upstream in poppler 0.20 and Okular from KDE 4.9. Is that reason enough to close this issue? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669199: latex-beamer: New upstream releases
Yes, that would be much appreciated. They are now up to 3.19, and the recent changes are very interesting to me. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671753: paraview: pvpython doesn't start
Package: paraview Version: 3.14.1-1 Severity: normal Dear Maintainer, when starting pvpython I get the error message sander@igel:~$ pvpython Error converting executable file /usr/bin/../lib/paraview/pvpython to real path: No such file or directory And that's all. This is on an up-to-date Debian Testing machine. I'd be happy to provide further information and more testing on request. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages paraview depends on: ii libavcodec53 5:0.10.2-0.3 ii libavformat53 5:0.10.2-0.3 ii libavutil51 5:0.10.2-0.3 ii libc6 2.13-30 ii libexpat1 2.1.0-1 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.0-3 ii libgl1-mesa-glx [libgl1] 7.11.2-1 ii libglu1-mesa [libglu1]7.11.2-1 ii libhdf5-7 [libhdf5-7] 1.8.8-9 ii libice6 2:1.0.8-2 ii libjpeg8 8d-1 ii libmysqlclient16 5.1.61-3 ii libogg0 1.2.2~dfsg-1 ii libopenmpi1.3 1.4.3-2.1 ii libpng12-01.2.49-1 ii libpq59.1.3-2 ii libpython2.7 2.7.3~rc2-2.1 ii libqt4-help 4:4.7.4-3 ii libqt4-network4:4.7.4-3 ii libqt4-sql4:4.7.4-3 ii libqt4-xml4:4.7.4-3 ii libqt4-xmlpatterns4:4.7.4-3 ii libqtcore44:4.7.4-3 ii libqtgui4 4:4.7.4-3 ii libqtwebkit4 2.2.0-3 ii libsm62:1.2.1-2 ii libsqlite3-0 3.7.11-2 ii libstdc++64.7.0-3 ii libswscale2 5:0.10.2-0.3 ii libtheora01.1.1+dfsg.1-3 ii libtiff4 3.9.6-5 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.1-2 ii libxml2 2.7.8.dfsg-9 ii libxt61:1.1.3-1 ii qt4-dev-tools 4:4.7.4-3 ii tcl8.4 [tclsh]8.4.19-4 ii tcl8.5 [tclsh]8.5.11-1 ii zlib1g1:1.2.6.dfsg-2 Versions of packages paraview recommends: ii mpi-default-bin 1.0.1 ii paraview-doc 3.14.1-1 ii paraview-python 3.14.1-1 Versions of packages paraview suggests: pn h5utils none pn hdf5-tools none -- 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#671753: paraview: pvpython doesn't start
Great, looking forward to the next upload then. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592943: still no network with 2.6.38 from squeeze-backports
Hi! I just tried the 2.6.38 kernel in squeeze-backports, to no avail. From http://wireless.kernel.org/en/users/Drivers/orinoco I learned that this is a known issue, and that I should set the wpa_supplicant parameter ap_scan to 2. However I can only do that if I stop using networkmanager, because networkmanager ignores the wpa_supplicant conf files. So I guess I could start trying out alternatives to networkmanager, but I don't really like the idea. First, nm is the default and I would expect it to just work. Secondly the machine in question is not mine, and I'd rather not fool around with it too much. I am stuck: is this a kernel bug? A nm bug? Will someone with more skills than me fix this properly sometime in the future? Can I help? Thanks for your time, Oliver -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605566: Same patch, this time with diff -u
Same patch, this time with diff -u, hope this eases things. --- xine.1.in 2009-12-19 01:15:31.0 +0100 +++ xine.1.in.patched 2011-05-17 22:33:23.0 +0200 @@ -41,12 +41,12 @@ Setze Stufe der `Geschwätzigkeit'. .TP .BI \-\-config\ Datei -Benutze \fIDatei\fP anstatt anstatt der normalen \fBconfig\fP Datei. +Benutze \fIDatei\fP anstatt der normalen \fBconfig\fP Datei. .TP .BI \-a,\ \-\-audio\-channel\ Zahl Wählt die angegebene Tonspur. \fIZahl\fP ist die Nummer der Tonspur, normalerweise \fB0\fP. .br -Xine 0.5 und neuer versucht, möglichst viele gültige Tonspuren (ac3, mpeg audio, avi audio, ...) des Titels zu sammeln und ordnet diese sogenannten Virtuelen Kanälen zu, die von \fB0\fP an beginnend durchnummeriert sind. +Xine 0.5 und neuer versucht, möglichst viele gültige Tonspuren (ac3, mpeg audio, avi audio, ...) des Titels zu sammeln und ordnet diese sogenannten Virtuellen Kanälen zu, die von \fB0\fP an beginnend durchnummeriert sind. .TP .BI \-V,\ \-\-video\-driver\ Treiber Wählt den Video\-Treiber aus. \fIxine \-\-help\fP zeigt eine Liste der Video\-Treiber an, die auf diesem System verfügbar sind. Diese Auswahl wird automatisch in \fI~/.xine/config\fP gespeichert, so daß der Video\-Treiber nur einmalig gewählt werden braucht. @@ -65,9 +65,9 @@ .br `\fIF\fP' Xinerama Vollbildmodus, .br -`\fIh\fP' GUI (Steuerfenster, etc...) ausbelnden, +`\fIh\fP' GUI (Steuerfenster, etc...) ausblenden, .br -`\fIw\fP' Videoausgabefenster ausbelnden, +`\fIw\fP' Videoausgabefenster ausblenden, .br `\fIq\fP' Programm nach Abspielen beenden, .br @@ -75,7 +75,7 @@ Dafür gibt es inzwischen die allgemeinere Option \fI\-\-auto\-scan\fP, mehr dazu siehe weiter unten. .TP .BI \-s,\ \-\-auto\-scan\ plugin -Titelliste automatisch vom Input\-Plugin erstellen. Viele Plugins erlauben es, eine standard Titelliste zu erstellen, die alles enthält. Dies Funktioniert zum Beispiel gut mit DVDs und VCDs. Das Benutzen dieser Option hat die gleiche Wirkung, als wenn der zugehörige Knopf im xine\-Hauptfenster gedrückt wird. +Titelliste automatisch vom Input\-Plugin erstellen. Viele Plugins erlauben es, eine Standard-Titelliste zu erstellen, die alles enthält. Dies funktioniert zum Beispiel gut mit DVDs und VCDs. Das Benutzen dieser Option hat die gleiche Wirkung, als wenn der zugehörige Knopf im xine\-Hauptfenster gedrückt wird. Diese Option ist besonders nützlich im Zusammenhang mit auto\-play. Durch Starten von \fIxine \-\-auto\-play \-\-auto\-scan dvd\fP kann eine gesamte DVD abgespielt werden, ohne einen weiteren Knopf zu betätigen. @@ -98,7 +98,7 @@ Position und Größe des Video\-Fensters als X-Geometrie angeben (siehe \fIX\fP(7)). Position \fBX\fP und \fBY\fP sind optional. .TP .B \-B,\ \-\-borderless -Rahmen von Video\-Fenster entfernen (Nur im Fenster\-Modus). +Rahmen vom Video\-Fenster entfernen (Nur im Fenster\-Modus). .TP .BI \-N,\ \-\-animation\ mrl Eine oder mehrere MRLs zum Abspielen, falls kein Videoanteil vorhanden ist. @@ -115,13 +115,13 @@ .br `\fIshuffle\fP': Zufälligen Eintrag aus noch nicht gespielter Wiedergabeliste auswählen. .br -`\fIshuffle+\fP': Das Selbe wie shuffle, nur wird die Playliste unendlichoft wiederholt. +`\fIshuffle+\fP': Dasselbe wie shuffle, nur wird die Playliste unendlich oft wiederholt. .TP .BI \-\-skin\-server\-url\ url Definiert die URL für den Skin-Server. .TP .BI \-\-enqueue\ mrl -Eine oder mehrere MRLs an laufenden Sitzung (Sitzung 0) anhängen. +Eine oder mehrere MRLs an laufende Sitzung (Sitzung 0) anhängen. .br Wenn eine andere Sitzung verwendet werden soll, kann diese mit \fB\-S session=\fP\fIx\fP angegeben werden. .TP @@ -212,7 +212,7 @@ Zeigt die Tastenbelegung an. Optionen sind: .br -`\fBdefault\fP' Zeigt die standard Tastenbelegung an, +`\fBdefault\fP' Zeigt die Standard-Tastenbelegung an, .br `\fBlirc\fP' Zeigt die Tastenbelegung aus der \fI~/.lircrc\fP-Konfigurationsdatei an, .br @@ -224,18 +224,18 @@ .TP .B \-n, \-\-network Aktiviert netzwerkbasierte Fernsteuerung. -Für die Benutzung der netzwerkbasierte Fernsteuerung wird eine Passwortdatei benötigt. +Für die Benutzung der netzwerkbasierten Fernsteuerung wird eine Passwortdatei benötigt. Wenn xine diese nicht finden kann, wird der Server gestoppt. -Der Syntax der Passwortdatei folgt dem (bekannten) Schema \fIIdentifikation\fP:\fIPasswort\fP. +Die Syntax der Passwortdatei folgt dem (bekannten) Schema \fIIdentifikation\fP:\fIPasswort\fP. Weil Kryptographie in einigen Ländern gesetzlichen Beschränkungen unterliegt, wird das Passwort unverschlüsselt gespeichert und übertragen, weshalb Netzwerkverbindungen besonders zu beachten sind. -Zusätzlichen stehen zwei (optionale) allgemeine Regeln stehen zur Verfügung, die sich gegenseitig ausschließen +Zusätzlichen stehen zwei (optionale) allgemeine Regeln zur Verfügung, die sich gegenseitig ausschließen .nf \fBALL:ALLOW\fP oder \fBALL:DENY\fP .fi Im ersten Fall können alle Klienten alle
Bug#605566: Typos in German xine manpage -- here is a patch
I happened to have a look at that man page again. It turns out there are lots of language errors. I checked upstream and the errors exist there too. So I prepared a patch and sent it to the xine-bugs mailing list, and now two weeks later I am still waiting moderator approval. Anyways, here is the patch for the file xine.1.in. cheers, Oliver 44c44 Benutze \fIDatei\fP anstatt anstatt der normalen \fBconfig\fP Datei. --- Benutze \fIDatei\fP anstatt der normalen \fBconfig\fP Datei. 49c49 Xine 0.5 und neuer versucht, möglichst viele gültige Tonspuren (ac3, mpeg audio, avi audio, ...) des Titels zu sammeln und ordnet diese sogenannten Virtuelen Kanälen zu, die von \fB0\fP an beginnend durchnummeriert sind. --- Xine 0.5 und neuer versucht, möglichst viele gültige Tonspuren (ac3, mpeg audio, avi audio, ...) des Titels zu sammeln und ordnet diese sogenannten Virtuellen Kanälen zu, die von \fB0\fP an beginnend durchnummeriert sind. 68c68 `\fIh\fP' GUI (Steuerfenster, etc...) ausbelnden, --- `\fIh\fP' GUI (Steuerfenster, etc...) ausblenden, 70c70 `\fIw\fP' Videoausgabefenster ausbelnden, --- `\fIw\fP' Videoausgabefenster ausblenden, 78c78 Titelliste automatisch vom Input\-Plugin erstellen. Viele Plugins erlauben es, eine standard Titelliste zu erstellen, die alles enthält. Dies Funktioniert zum Beispiel gut mit DVDs und VCDs. Das Benutzen dieser Option hat die gleiche Wirkung, als wenn der zugehörige Knopf im xine\-Hauptfenster gedrückt wird. --- Titelliste automatisch vom Input\-Plugin erstellen. Viele Plugins erlauben es, eine Standard-Titelliste zu erstellen, die alles enthält. Dies funktioniert zum Beispiel gut mit DVDs und VCDs. Das Benutzen dieser Option hat die gleiche Wirkung, als wenn der zugehörige Knopf im xine\-Hauptfenster gedrückt wird. 101c101 Rahmen von Video\-Fenster entfernen (Nur im Fenster\-Modus). --- Rahmen vom Video\-Fenster entfernen (Nur im Fenster\-Modus). 118c118 `\fIshuffle+\fP': Das Selbe wie shuffle, nur wird die Playliste unendlichoft wiederholt. --- `\fIshuffle+\fP': Dasselbe wie shuffle, nur wird die Playliste unendlich oft wiederholt. 124c124 Eine oder mehrere MRLs an laufenden Sitzung (Sitzung 0) anhängen. --- Eine oder mehrere MRLs an laufende Sitzung (Sitzung 0) anhängen. 215c215 `\fBdefault\fP' Zeigt die standard Tastenbelegung an, --- `\fBdefault\fP' Zeigt die Standard-Tastenbelegung an, 227c227 Für die Benutzung der netzwerkbasierte Fernsteuerung wird eine Passwortdatei benötigt. --- Für die Benutzung der netzwerkbasierten Fernsteuerung wird eine Passwortdatei benötigt. 229c229 Der Syntax der Passwortdatei folgt dem (bekannten) Schema \fIIdentifikation\fP:\fIPasswort\fP. --- Die Syntax der Passwortdatei folgt dem (bekannten) Schema \fIIdentifikation\fP:\fIPasswort\fP. 231c231 Zusätzlichen stehen zwei (optionale) allgemeine Regeln stehen zur Verfügung, die sich gegenseitig ausschließen --- Zusätzlichen stehen zwei (optionale) allgemeine Regeln zur Verfügung, die sich gegenseitig ausschließen 236c236 Im zweiten Fall können keine Klienten irgendwelche Kommandoa ausführen, außer identifizierten Benutzern (durch das \fBidentify\fP-Kommando). --- Im zweiten Fall können keine Klienten irgendwelche Kommandos ausführen, außer identifizierten Benutzern (durch das \fBidentify\fP-Kommando). 238c238 Wenn ein Passworteintrag mit einem Stern `\fB*\fP' beginnt, ider der Benutzer blockiert. --- Wenn ein Passworteintrag mit einem Stern `\fB*\fP' beginnt, wird der Benutzer blockiert. 278c278 MRLs sind ähnlich wir URLs im Web\-Browser und beschreiben die zu spielenden Titel. Gültige MRLs können einfache Dateinamen sein oder folgendermaßen aussehen: --- MRLs sind ähnlich wie URLs im Web\-Browser und beschreiben die zu spielenden Titel. Gültige MRLs können einfache Dateinamen sein oder folgendermaßen aussehen: 355c355 Die standard Tastaturbelegung ist: --- Die Standard-Tastaturbelegung ist: 363c363 Mediamark für aktuelle Apspielposition der Wiedergabeliste hinzufügen. --- Mediamarke für aktuelle Abspielposition der Wiedergabeliste hinzufügen. 453c453 Menü 2 (insbesondere Titlemenü) --- Menü 2 (insbesondere Titelmenü) 505c505 Die Zifferntasten können zur Eingabe von Zahlen verwendet werden, aber aus Rückwärtskompatibilitätsgründen sind die Zifferntasten nicht mit den korrespondirenden Zahlen belegt. Vielmehr sind sie mit Symbolen belegt, die normalerweise nicht mit der Tastatur erzeugt werden können. Deshalb ist die numerische Eingabe standardmäßig deaktiviert. --- Die Zifferntasten können zur Eingabe von Zahlen verwendet werden, aber aus Rückwärtskompatibilitätsgründen sind die Zifferntasten nicht mit den korrespondierenden Zahlen belegt. Vielmehr sind sie mit Symbolen belegt, die normalerweise nicht mit der Tastatur erzeugt werden können. Deshalb ist die numerische Eingabe standardmäßig deaktiviert.
Bug#618422: linux-image-2.6.32-5-amd64: HP DM1-2160la with ALPS toucpad wasn't detect very well
I had the same symptoms with an ALPS touchpad in a Dell Latitude E6510.
I found a patch in the following list:
https://bugzilla.redhat.com/show_bug.cgi?id=590880,
which I attach for your convenience. The patch applies cleanly to the
current stable
kernel. It enabled vertical scrolling for me. Also, by a trivial tweak
of the patch
(look at the code, it really is trivial) I was able to disable
click-on-tap, which was
way to sensitive on my machine.
I'm not quite sure how Dell-specific the patch is, but it may be worth a
try.
diff --git a/drivers/input/mouse/alps.c b/drivers/input/mouse/alps.c
index a9f461e..27ec20e 100644
--- a/drivers/input/mouse/alps.c
+++ b/drivers/input/mouse/alps.c
@@ -29,15 +29,17 @@
#define dbg(format, arg...) do {} while (0)
#endif
-#define ALPS_DUALPOINT 0x01
-#define ALPS_WHEEL 0x02
-#define ALPS_FW_BK_1 0x04
-#define ALPS_4BTN 0x08
-#define ALPS_OLDPROTO 0x10
-#define ALPS_PASS 0x20
-#define ALPS_FW_BK_2 0x40
-#define ALPS_PS2_INTERLEAVED 0x80 /* 3-byte PS/2 packet interleaved with
+#define ALPS_DUALPOINT 0x001
+#define ALPS_WHEEL 0x002
+#define ALPS_FW_BK_1 0x004
+#define ALPS_4BTN 0x008
+#define ALPS_OLDPROTO 0x010
+#define ALPS_PASS 0x020
+#define ALPS_FW_BK_2 0x040
+#define ALPS_PS2_INTERLEAVED 0x080 /* 3-byte PS/2 packet interleaved with
6-byte ALPS packet */
+#define ALPS_EC_PROTO 0x100 /* EC memory access protocol */
+#define ALPS_IMPS 0x200 /* IMPS emulation */
static const struct alps_model_info alps_model_data[] = {
{ { 0x32, 0x02, 0x14 }, 0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT }, /* Toshiba Salellite Pro M10 */
@@ -64,6 +66,7 @@ static const struct alps_model_info alps_model_data[] = {
{ { 0x73, 0x02, 0x50 }, 0xcf, 0xcf, ALPS_FW_BK_1 }, /* Dell Vostro 1400 */
{ { 0x52, 0x01, 0x14 }, 0xff, 0xff,
ALPS_PASS | ALPS_DUALPOINT | ALPS_PS2_INTERLEAVED }, /* Toshiba Tecra A11-11L */
+ { { 0x73, 0x02, 0x64 }, 0x00, 0x00, ALPS_EC_PROTO | ALPS_IMPS }, /* Dell E2 series */
};
/*
@@ -516,6 +519,89 @@ static int alps_absolute_mode(struct psmouse *psmouse)
return ps2_command(psmouse-ps2dev, NULL, PSMOUSE_CMD_SETPOLL);
}
+static int alps_ec_mode(struct psmouse *psmouse, bool enable)
+{
+ struct ps2dev *ps2dev = psmouse-ps2dev;
+ unsigned char param[4];
+
+ if (ps2_command(ps2dev, NULL, PSMOUSE_CMD_SETSTREAM))
+ return -1;
+ if (enable) {
+ /* EC EC EC E9 */
+ if (ps2_command(ps2dev, NULL, PSMOUSE_CMD_RESET_WRAP) ||
+ ps2_command(ps2dev, NULL, PSMOUSE_CMD_RESET_WRAP) ||
+ ps2_command(ps2dev, NULL, PSMOUSE_CMD_RESET_WRAP))
+ return -1;
+ param[0] = param[1] = param[2] = 0xff;
+ if (ps2_command(ps2dev, param, PSMOUSE_CMD_GETINFO))
+ return -1;
+
+ dbg(EC report: %2.2x %2.2x %2.2x, param[0], param[1], param[2]);
+
+ if (param[0] != 0x88 || param[1] != 0x07 || (param[2] != 0x9b param[2] != 0x9d))
+ return -1;
+ }
+
+ return 0;
+}
+
+static int alps_ec_nibble(struct psmouse *psmouse, uint8_t nibble)
+{
+ struct ps2dev *ps2dev = psmouse-ps2dev;
+ unsigned char param;
+ static const int cmds[] = {
+ PSMOUSE_CMD_SETPOLL,
+ PSMOUSE_CMD_RESET_DIS,
+ PSMOUSE_CMD_SETSCALE21,
+ PSMOUSE_CMD_SETRATE,
+ PSMOUSE_CMD_SETRATE,
+ PSMOUSE_CMD_SETRATE,
+ PSMOUSE_CMD_SETRATE,
+ PSMOUSE_CMD_SETRATE,
+ PSMOUSE_CMD_SETRATE,
+ PSMOUSE_CMD_SETRATE,
+ PSMOUSE_CMD_GETINFO,
+ PSMOUSE_CMD_SETRES,
+ PSMOUSE_CMD_SETRES,
+ PSMOUSE_CMD_SETRES,
+ PSMOUSE_CMD_SETRES,
+ PSMOUSE_CMD_SETSCALE11 };
+ static const unsigned char params[] = {
+ 0xff, 0xff, 0xff, 10, 20, 40, 60, 80, 100, 200, 0xff, 0, 1, 2, 3, 0xff };
+
+ nibble = 0xf;
+ param = params[nibble];
+ if (ps2_command(ps2dev, param, cmds[nibble]))
+ return -1;
+
+ return 0;
+}
+
+static int alps_ec_write(struct psmouse *psmouse, uint16_t addr, uint8_t value)
+{
+ struct ps2dev *ps2dev = psmouse-ps2dev;
+
+ /* Select new address: EC addr3 addr2 addr1 addr0 */
+ if (ps2_command(ps2dev, NULL, PSMOUSE_CMD_RESET_WRAP) ||
+ alps_ec_nibble(psmouse, addr 12) ||
+ alps_ec_nibble(psmouse, addr 8) ||
+ alps_ec_nibble(psmouse, addr 4) ||
+ alps_ec_nibble(psmouse, addr))
+ return -1;
+
+ /*
+ * PSMOUSE_CMD_GETINFO can be used to read from the current address,
+ * returning { addr_high, addr_low, value } Useful when working with bit fields.
+ */
+
+ /* Write byte: value1 value0 */
+ if (alps_ec_nibble(psmouse, value 4) ||
+ alps_ec_nibble(psmouse, value))
+ return -1;
+
+ return 0;
+}
+
static int alps_get_status(struct psmouse *psmouse, char *param)
{
struct ps2dev *ps2dev = psmouse-ps2dev;
@@ -602,30 +688,65 @@ static int alps_hw_init(struct psmouse *psmouse, int *version)
if (!priv-i)
return -1;
- if ((priv-i-flags ALPS_PASS)
- alps_passthrough_mode(psmouse, true)) {
+ if (!priv-dev2 !(priv-i-flags ALPS_IMPS)) {
+ /* Because we never initialized dev2 */
+ printk(KERN_ERR alps.c: Failed to reconnect to IMPS emulation mode\n);
return -1;
}
- if (alps_tap_mode(psmouse, true)) {
- printk(KERN_WARNING alps.c: Failed to enable hardware
Bug#592752: closed by robe...@connexer.com (Roberto C. Sanchez) (Bug#592752: fixed in coinor-ipopt 3.9.2-1)
Thanks again! Oliver -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592752: coinor-libipopt-dev: Problems linking libipopt to a sequential program
Hi Roberto! Thanks for the addition to README.Debian. That will be very helpful. Regarding pkg-config support, have a look at the source code of IPOpt 3.9.0 https://projects.coin-or.org/Ipopt/browser/releases/3.9.0#Ipopt There you'll see a file ipopt.pc.in. That together with a few changes in configure.ac, should constitute pkg-config support. thanks, Oliver -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592752: coinor-libipopt-dev: Problems linking libipopt to a sequential program
Hi! I think that this might be the same problem reported in #592324. I am not sure, because 592324 is a problem during linking, and what I reported is a run-time problem. However, in the meantime I moved to a new computer, and now I run into 592324 as well. I can get the missing symbols MPI_Finalize, MPI_Comm_rank, MPI_Init by installing libmumps-4.9.2 and libmumps-seq-4.9.2, but not dmumps_c. Where is it? Thanks for your help, Oliver -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592752: coinor-libipopt-dev: Problems linking libipopt to a sequential program
Okay, nevermind, I figured that one out myself. You need to link against libdmumps-4.9.2 and libdmumps_seq-4.9.2 as well. Hang on. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592752: coinor-libipopt-dev: Problems linking libipopt to a sequential program
I finished testing, and here's the result: I can link successfully by providing either -ldmumps_seq-4.9.2 or -ldmumps-4.9.2. However, in the latter case the programm aborts at run time with the same error message as in my original post. Additionally linking with libmpi does not help. Hence I come the same conclusion as the poster of 592324: MUMPS needs to be dependency, and a hint about the necessary libraries would be helpful. Support for pkg-config would still be greatly appreciated, but I acknowledge that it is probably to late for that in squeeze. Cheers, Oliver -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593389: Duplicate of 564941
As it turns out, this is a duplicate of 564941. A workaround for the latter has been described in the README.Debian of kdebase-workspace 4:4.4.5-6. Hence I'll mark this bug as 'done'. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601558: Still not working with kernel in squeeze
Would it make sense to do a bisection on the kernels from snapshot.debian.org between the one in testing and the one in experimental? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601558: Still not working with kernel in squeeze
Sorry for the delay. I tried the patch and it didn't seem to change anything. Let me know if you're interested in logfiles and such. Best, Oliver -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601558: Still not working with kernel in squeeze
I tried this again after an update to today's squeeze, with kernel 2.6.32-29 and xserver-xorg-video-intel 2:2.13.0-5. Unfortunately, the problem remains unchanged: the screen turns black when the frame buffer is switched on, and there is no way to get a text console let alone X. I also tried with the current kernel from experimental: 2.6.37-rc7. That seems to work nicely. I didn't encounter any serious problems after about an hour of playing around with it. In particular, the X server freezes I reported above with the 2.6.36 kernel appear to have gone. As this bug is not ranked important enough to be fixed in squeeze, and it already is fixed in post-squeeze, feel free to close this bug report. Thank you guys for your help! Oliver
Bug#592943: Confirmed in linux-image-2.6.37-rc7
I just tried linux-image-2.6.37-rc7 from experimental. The problem is still there. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596349: No improvements in xserver-xorg-video-intel 2:2.13.0-5
I tried this again with kernel 2.6.37-rc7 from experimental and xserver-xorg-video intel 2:2.13.0-5, from current squeeze. The bug is still there. With rare exceptions, pressing Fn-arrow up|down makes the mouse pointer disappear. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511463: Bug is gone
I have had this problem for a long time, but it recently got fixed automatically during a dist-upgrade. It may have been the move to 3.3.12, but I am not sure. Can the reporters maybe check if they can still reproduce the bug with an up-to-date installation? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605566: Typos in German xine manpage
Package: xine-ui Version: 0.99.6-1 Severity: minor The German man page for xine contains (at least) twice the word 'ausbelnden'. This is a typo, it should be 'ausblenden'. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xine-ui depends on: ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libcurl3-gnutls 7.21.0-1 Multi-protocol file transfer libra ii liblircclient00.8.3-5infra-red remote control support - ii libpng12-01.2.44-1 PNG library - runtime ii libreadline6 6.1-3 GNU readline and history libraries ii libx11-6 2:1.3.3-4 X11 client-side library ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar ii libxft2 2.1.14-2 FreeType-based font drawing librar ii libxine1 1.1.19-2 the xine video/media player librar ii libxine1-ffmpeg 1.1.19-2 MPEG-related plugins for libxine1 ii libxine1-x1.1.19-2 X desktop video output plugins for ii libxinerama1 2:1.1-3X11 Xinerama extension library ii libxtst6 2:1.1.0-3 X11 Testing -- Record extension li ii libxv12:1.0.5-1 X11 Video extension library ii libxxf86vm1 1:1.1.0-2 X11 XFree86 video mode extension l Versions of packages xine-ui recommends: ii xdg-utils1.0.2+cvs20100307-2 desktop integration utilities from xine-ui 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#592744: Playing from the device manager works now
I updated my system and tried again. dragonplayer does play my DVDs now if it is started from the KDE device manager. When started from the console the behavior is unchanged: clicking on the 'Play CD/DVD' button doesn't appear to do anything. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592746: Seems to be a udev problem
I did some more investigations and it seems to be a udev problem. I'll reassign the bug report. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592746: xine doesn't play dvd because dvd-drive is mounted as /dev/dvd1 instead of /dev/dvd
Here it is:
# This file was automatically generated by the /lib/udev/write_cd_rules
# program, run by the cd-aliases-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and set the $GENERATED variable.
# QSI_CD-RW_DVD-ROM_SBW242U (pci-:00:1f.1)
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:1f.1, SYMLINK+=cdrom, ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:1f.1, SYMLINK+=cdrw, ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:1f.1, SYMLINK+=dvd, ENV{GENERATED}=1
# CDRW_DVD_SBW242U (pci-:00:1f.1-scsi-1:0:0:0)
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:1f.1-scsi-1:0:0:0, SYMLINK+=cdrom1,
ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:1f.1-scsi-1:0:0:0, SYMLINK+=cdrw1,
ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:1f.1-scsi-1:0:0:0, SYMLINK+=dvd1,
ENV{GENERATED}=1
# U3_Cruzer_Micro (pci-:00:1d.7-usb-0:4:1.0-scsi-0:0:0:1)
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:1d.7-usb-0:4:1.0-scsi-0:0:0:1,
SYMLINK+=cdrom2, ENV{GENERATED}=1
# U3_Cruzer_Micro (pci-:00:1d.7-usb-0:4:1.0-scsi-0:0:0:1)
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_SERIAL}==SanDisk_U3_Cruzer_Micro_431711165750868F-0:1,
SYMLINK+=cdrom3, ENV{GENERATED}=1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592746: closed by m...@linux.it (Marco d'Itri) (Re: Bug#592746: xine doesn't play dvd because dvd-drive is mounted as /dev/dvd1 instead of /dev/dvd)
I don't recall ever having had a second dvd drive, but still following your advice gave me the correct link again. Thank you very much! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601558: Working with experimental xserver-xorg-video-intel and kernel
Now that xserver-xorg-video-intel 2.13.0-2 appeared in unstable I tried that package. As was to be expected, together with the squeeze kernel there is still no functioning display. On the other hand, with the 2.6.36-rc6 kernel the display and X appeared to be working property. This seemed like a step forward. Thank you for that. However, after two days of testing a new problem surfaced: it appears that every time the computer is left without input events for a few minutes the X output becomes garbled and the X server freezes. I had to revert the kernel and intel driver packages yet again. I know that this information is not precise enough to be of much help. The problem has been reported to me by the person who uses the machine for work. Please let me know what I can do to help track down the problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601558: closed by Cyril Brulebois k...@debian.org (Re: Bug#601558: SOLVED? CONFIG_FRAMEBUFFER_CONSOLE=y solved the problem)
I don't really see how that solves my problem. I am using the regular squeeze kernel, and both options are set there. Still I don't have a working display. I will follow Cesare Leonardis suggestion in the 600802 thread and try the kernel and x driver from experimental. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601558: [i830] Black screen with kms and i915 again
Of course, but it'll be a few days before I have access to the machine again. Am 29.10.2010 00:14, schrieb Cyril Brulebois: Oliver Sandersan...@mi.fu-berlin.de (27/10/2010): Thanks for the quick response. Here are the X log and the dmesg output. Thanks; could we also get a full dmesg in the same conditions? Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601558: Relation to 593432
I should mention that this bug and 593432 were the same machine. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601558: Acknowledgement ([i830] Black screen with kms and i915 again)
I forgot to mention that I also tried the package xserver-xorg-video-intel-2:2.13.0+git20101017.33133a1d-1 from http://autobuild.ikibiki.org/. Unfortunately that didn't help at all. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601558: [i830] Black screen with kms and i915 again
Thanks for the quick response. Here are the X log and the dmesg output. best, Oliver /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 13. Jul 10:27 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1733468 10. Okt 14:03 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82830 CGC [Chipset Graphics Controller] (rev 04) /etc/X11/xorg.conf does not exist. Kernel version (/proc/version): Linux version 2.6.32-5-686 (Debian 2.6.32-26) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Oct 19 14:40:34 UTC 2010 Xorg X server log files on system: -rw-r--r-- 1 root root 36746 27. Okt 16:50 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.23-dsa-ia32 i686 Debian Current Operating System: Linux baumann 2.6.32-5-686 #1 SMP Tue Oct 19 14:40:34 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=2b4fbfbd-8cd8-4da5-b90c-7b281a41435b ro quiet Build Date: 10 October 2010 11:57:07AM xorg-server 2:1.7.7-8 (Cyril Brulebois k...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Oct 27 16:50:30 2010 (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x81ecca0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:0:2:0) 8086:3577:1028:0122 Intel Corporation 82830 CGC [Chipset Graphics Controller] rev 4, Mem @ 0xe800/134217728, 0xe000/524288 (--) PCI: (0:0:2:1) 8086:3577:1028:0122 Intel Corporation 82830 CGC [Chipset Graphics Controller] rev 0, Mem @ 0xf000/134217728, 0xe008/524288 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: record (II) Loading /usr/lib/xorg/modules/extensions/librecord.so (II) Module record: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension RECORD (II) LoadModule: dri (II) Loading /usr/lib/xorg/modules/extensions/libdri.so (II) Module dri: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: dri2 (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so (II) Module dri2: vendor=X.Org Foundation compiled
Bug#592746: xine doesn't play dvd because dvd-drive is mounted as /dev/dvd1 instead of /dev/dvd
With today's squeeze, the problem is still there. In fact, what precisely is the bug? Should xine find the drive in /dev/dvd1 or should my only dvd drive be mounted in /dev/dvd in the first place? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599171: Kaffeine crashes when trying to play a dvd
Package: kaffeine Version: 1.0-1 Severity: normal Steps to reproduce: 1) enter a dvd 2) start kaffeine from the konsole 3) in the main menu press 'play dvd' For a few seconds the viewer window shows me the movie title, and then the KDE crash handler comes up. Here is what's printed in the konsole during this: san...@haile:~/dune-2.0/richards$ kaffeine san...@haile:~/dune-2.0/richards$ libdvdnav: Using dvdnav version 4.1.3 libdvdread: Using libdvdcss version 1.2.10 for DVD access libdvdnav: DVD Title: TOM_TYKWER_BOX__LOLA_RENNT libdvdnav: DVD Serial Number: 39907591 libdvdnav: DVD Title (Alternative): libdvdnav: Unable to find map file '/home/sander/.dvdnav/TOM_TYKWER_BOX__LOLA_RENNT.map' libdvdnav: DVD disk reports itself with Region mask 0x00fd. Regions: 2 libdvdread: Attempting to retrieve all CSS keys libdvdread: This can take a _long_ time, please be patient libdvdread: Get key for /VIDEO_TS/VIDEO_TS.VOB at 0x0140 libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_01_1.VOB at 0x0001f223 libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_02_1.VOB at 0x0002078f libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_03_1.VOB at 0x0002aca3 libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_04_1.VOB at 0x0003ad45 libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_05_0.VOB at 0x000562ac libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_05_1.VOB at 0x0006623f libdvdread: Elapsed time 0 libdvdread: Get key for /VIDEO_TS/VTS_06_1.VOB at 0x00284d9c libdvdread: Elapsed time 0 libdvdread: Found 6 VTS's libdvdread: Elapsed time 0 demux_wavpack: (open_wv_file:127) open_wv_file: non-seekable inputs aren't supported yet. received X error event: BadMatch (invalid parameter attributes) X Error: BadMatch (invalid parameter attributes) 8 Extension:132 (Uknown extension) Minor opcode: 17 (Unknown request) Resource id: 0x3f KCrash: Application 'kaffeine-xbu' crashing... sock_file=/home/sander/.kde/socket-haile/kdeinit4__0 libdvdread: Can't seek to block 127734 And here is the backtrace: Application: Kaffeine (kaffeine-xbu), signal: Segmentation fault [Current thread is 1 (Thread 0xb5b88930 (LWP 14215))] Thread 9 (Thread 0xb299bb70 (LWP 14217)): #0 0xb78bd424 in __kernel_vsyscall () #1 0xb5fc1482 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179 #2 0xb6186e64 in __pthread_cond_timedwait (cond=0x9cfc4f0, mutex=0x9cfc4d8, abstime=0xb299b320) at forward.c:152 #3 0xb7743bdf in ?? () from /usr/lib/libxine.so.1 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 8 (Thread 0xb2021b70 (LWP 14222)): #0 0xb78bd424 in __kernel_vsyscall () #1 0xb616c696 in *__GI___poll (fds=0xb61efff4, nfds=1, timeout=333) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb181ca5f in ?? () from /usr/lib/xine/plugins/1.29/xineplug_ao_out_alsa.so Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 7 (Thread 0xad01eb70 (LWP 14223)): #0 0xb78bd424 in __kernel_vsyscall () #1 0xb5fc0f7f in __pthread_cond_wait (cond=0x9d3e430, mutex=0x9d3e418) at pthread_cond_wait.c:153 #2 0xb6186e0d in __pthread_cond_wait (cond=0x9d3e430, mutex=0x9d3e418) at forward.c:139 #3 0xb775487e in ?? () from /usr/lib/libxine.so.1 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 6 (Thread 0xad81fb70 (LWP 14224)): #0 0xb78bd424 in __kernel_vsyscall () #1 0xb6173011 in select () at ../sysdeps/unix/syscall-template.S:82 #2 0xb776d4d8 in xine_usec_sleep () from /usr/lib/libxine.so.1 #3 0x in ?? () Thread 5 (Thread 0xb1024b70 (LWP 14225)): [KCrash Handler] #6 0xb2189604 in ?? () from /usr/lib/xine/plugins/1.29/xineplug_vo_out_xv.so Thread 4 (Thread 0xb0656b70 (LWP 14226)): #0 0xb78bd424 in __kernel_vsyscall () #1 0xb5fc0f7f in __pthread_cond_wait (cond=0xa2a37fc, mutex=0xa2a37e4) at pthread_cond_wait.c:153 #2 0xb6186e0d in __pthread_cond_wait (cond=0xa2a37fc, mutex=0xa2a37e4) at forward.c:139 #3 0xb7747196 in ?? () from /usr/lib/libxine.so.1 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 3 (Thread 0xafe55b70 (LWP 14227)): #0 0xb78bd424 in __kernel_vsyscall () #1 0xb5fc0f7f in __pthread_cond_wait (cond=0xa2c13fc, mutex=0xa2c13e4) at pthread_cond_wait.c:153 #2 0xb6186e0d in __pthread_cond_wait (cond=0xa2c13fc, mutex=0xa2c13e4) at forward.c:139 #3 0xb77578d2 in ?? () from /usr/lib/libxine.so.1 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 2 (Thread 0xaf316b70 (LWP 14228)): #0 0xb78bd424 in __kernel_vsyscall () #1 0xb6173011 in select () at ../sysdeps/unix/syscall-template.S:82 #2 0xb776d4d8 in xine_usec_sleep () from /usr/lib/libxine.so.1 #3 0x in ?? () Thread 1 (Thread 0xb5b88930 (LWP 14215)): #0 0xb78bd424 in __kernel_vsyscall () #1 0xb5fc0f7f in __pthread_cond_wait (cond=0x9c07570,
Bug#593507: This seems to be Bug #593432
Hi! This really does seem to be the same as 593432. I have also seen the backlight behavior you describe, and even the problem with 'nomodeset'. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593440: Screen message spelled wrongly during update of openoffice.org
Package: openoffice.org Version: 1:3.2.1-5 Severity: normal When updating today from openoffice.org 1:3.2.1-4 to 1:3.2.1-5 I got the messages revoke component 'file:///usr/lib/openoffice/basis3.2/program/libbf_migratefilterli.so' from registry '/var/lib/openoffice/basis3.2/program/services.rdb' succesful! and register component 'file:///usr/lib/openoffice/basis3.2/program/libbf_migratefilterli.so' in registry '/var/lib/openoffice/basis3.2/program/services.rdb' succesful! The word 'succesful' is misspelled here. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openoffice.org depends on: ii liblucene2-java 2.9.2+ds1-1 Full-text search engine library fo pn openoffice.org-base none (no description available) pn openoffice.org-calc none (no description available) ii openoffice.org-core 1:3.2.1-5 office productivity suite -- arch- pn openoffice.org-draw none (no description available) pn openoffice.org-filter-mobile none (no description available) pn openoffice.org-impress none (no description available) pn openoffice.org-java-common none (no description available) pn openoffice.org-math none (no description available) pn openoffice.org-officebean none (no description available) pn openoffice.org-report-builde none (no description available) pn openoffice.org-writer none (no description available) ii ttf-dejavu 2.31-1 Metapackage to pull in ttf-dejavu- ii ttf-sil-gentium-basic1.1-2 smart Unicode font families (Basic Versions of packages openoffice.org recommends: pn openoffice.org-filter- none(no description available) ii ttf-liberation 1.05.2.20091019-4 Fonts with the same metrics as Tim Versions of packages openoffice.org suggests: ii cups-bsd 1.4.4-2 Common UNIX Printing System(tm) - ii default-jre [java5-runtime 1.6-38Standard Java or Java compatible R pn gstreamer0.10-ffmpeg none(no description available) pn gstreamer0.10-plugins-bad none(no description available) pn gstreamer0.10-plugins-base none(no description available) pn gstreamer0.10-plugins-good none(no description available) pn gstreamer0.10-plugins-ugly none(no description available) ii hunspell-en-us [hunspell-d 20070829-4English_american dictionary for hu ii icedove3.0.6-1 mail/news client with RSS and inte ii iceweasel 3.5.11-1 Web browser based on Firefox ii imagemagick8:6.6.0.4-2.1 image manipulation programs ii libgl1-mesa-glx [libgl1] 7.7.1-4 A free implementation of the OpenG ii libldap-2.4-2 2.4.21-1 OpenLDAP libraries ii libpaper-utils 1.1.24library for handling paper charact ii libsane1.0.21-3 API library for scanners ii libxrender11:0.9.6-1 X Rendering Extension client libra pn menu none(no description available) ii myspell-de-de [myspell-dic 20091006-4.1 German dictionary for myspell pn openclipart-openoffice.org none(no description available) ii openjdk-6-jre [java5-runti 6b18-1.8-1OpenJDK Java runtime, using Hotspo pn openoffice.org-gnome | ope none(no description available) pn openoffice.org-help-3.2 none(no description available) pn openoffice.org-hyphenation none(no description available) ii openoffice.org-l10n-de [op 1:3.2.1-4 office productivity suite -- Germa pn openoffice.org2-thesaurus none(no description available) ii pstoedit 3.50-3+b1 PostScript and PDF files to editab pn unixodbc none(no description available) Versions of packages openoffice.org-core depends on: ii fontconfig 2.8.0-2.1generic font configuration library ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-4 The Cairo 2D vector graphics libra ii libcurl3-gnutls 7.21.0-1 Multi-protocol file transfer libra ii libdb4.84.8.30-1 Berkeley v4.8 Database Libraries [ ii libexpat1 2.0.1-7 XML parsing C library - runtime li ii libfreetype62.4.2-1 FreeType 2 font engine, shared lib ii libgcc1 1:4.4.4-8GCC support library ii libglib2.0-02.24.1-1 The GLib library of C routines ii libgraphite31:2.3.1-0.2 SILGraphite - a smart font rende ii libgstreamer-plugins-ba 0.10.30-1GStreamer libraries from the base ii libgstreamer0.10-0 0.10.30-1
Bug#593432: Black screen with kms and i915
Strange. Last night's update must have changed the default behavior. All of a sudden the content of /etc/modprobe.d/i915-kms.conf doesn't seem to matter anymore: kms is always off. The only way to trigger the problem is to add modeset=1 to the boot options. I guess this makes the problem less grave, because the default behavior works now. For your questions: I installed the machine from scratch using a netinstall cd in late July. From the date, the kernel must have been 2.6.32-15. The bug was there. Before, I had been using Lenny, and that worked fine. However, that's pre-kms anyways, so I don't know whether that really counts as a regression. Here's the dmesg output with kms: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-20) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Thu Aug 12 13:38:27 UTC 2010 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] NSC Geode by NSC [0.00] Cyrix CyrixInstead [0.00] Centaur CentaurHauls [0.00] Transmeta GenuineTMx86 [0.00] Transmeta TransmetaCPU [0.00] UMC UMC UMC UMC [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009e800 (usable) [0.00] BIOS-e820: 0009e800 - 000a (reserved) [0.00] BIOS-e820: 000c - 000d4000 (reserved) [0.00] BIOS-e820: 000e - 0010 (reserved) [0.00] BIOS-e820: 0010 - 176b7000 (usable) [0.00] BIOS-e820: 176b7000 - 176e (ACPI NVS) [0.00] BIOS-e820: 176e - 176f (ACPI data) [0.00] BIOS-e820: 176f - 1770 (ACPI NVS) [0.00] BIOS-e820: 1770 - 1778 (usable) [0.00] BIOS-e820: 1778 - 1800 (reserved) [0.00] BIOS-e820: ff80 - ffc0 (reserved) [0.00] BIOS-e820: fff0 - 0001 (reserved) [0.00] DMI 2.3 present. [0.00] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it. [0.00] e820 update range: - 0001 (usable) == (reserved) [0.00] last_pfn = 0x17780 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C7FFF write-protect [0.00] C8000-E uncachable [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask FF000 write-back [0.00] 1 base 01000 mask FF800 write-back [0.00] 2 base 017F8 mask 8 uncachable [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] PAT not supported by CPU. [0.00] initial memory mapped : 0 - 0180 [0.00] init_memory_mapping: -1778 [0.00] 00 - 40 page 4k [0.00] 40 - 001740 page 2M [0.00] 001740 - 001778 page 4k [0.00] kernel direct mapping tables up to 1778 @ 1-16000 [0.00] RAMDISK: 1113f000 - 1194891c [0.00] ACPI: RSDP 000f6300 00014 (v00 PTLTD ) [0.00] ACPI: RSDT 176ea420 00034 (v01 PTLTDRSDT 0604 LTP ) [0.00] ACPI: FACP 176efdf3 00074 (v01 DELL X200 0604 PTL 004B) [0.00] ACPI: DSDT 176ea454 0599F (v01 DELLX2000604 MSFT 010D) [0.00] ACPI: FACS 176fcfc0 00040 [0.00] ACPI: SSDT 176efe67 000BC (v01 PTLTD ACPICST1 0604 LTP 0001) [0.00] ACPI: SSDT 176eff23 000B5 (v01 PTLTD ACPIPST1 0604 LTP 0001) [0.00] ACPI: BOOT 176effd8 00028 (v01 PTLTD $SBFTBL$ 0604 LTP 0001) [0.00] 0MB HIGHMEM available. [0.00] 375MB LOWMEM available. [0.00] mapped low ram: 0 - 1778 [0.00] low ram: 0 - 1778 [0.00] node 0 low ram: - 1778 [0.00] node 0 bootmap 00012000 - 00014ef0 [0.00] (9 early reservations) == bootmem [00 - 001778] [0.00] #0 [00 - 001000] BIOS data page == [00 - 001000] [0.00] #1 [001000 - 002000]EX TRAMPOLINE == [001000 - 002000] [0.00] #2 [006000 - 007000] TRAMPOLINE == [006000 - 007000] [0.00] #3 [000100 - 00014c6b94]TEXT DATA BSS == [000100 - 00014c6b94] [0.00] #4 [001113f000 - 001194891c] RAMDISK == [001113f000 - 001194891c] [
Bug#593432: Info received (Bug#593432: Black screen with kms and i915)
Forget what I said about the default behavior having changed. This machine is a can full of Heisenbugs! After the fifth reboot, kms came back with a vengeance. Currently not even the conf file won't stop it. The only way I have to use the machine is the kernel from Ubuntu 10.4 that I hand-copied onto it. Apparently they have kms disabled for the i915 by some brute force method. The dmesg output contains the line /i915/ disabling kernel modesetting for known /bad device/.
Bug#592943: Can't connect to WEP network: eth1: Lucent/Agere firmware doesn't support manual roaming
Package: linux-2.6 Version: 2.6.32-18 Severity: normal I cannot connect to a WEP network. The kde network manager keeps asking me for the password. This is after a complete reinstall of Debian Squeeze. Connecting to the very same network worked when the machine was still running Lenny. One other way to connect is to use the kernel shipped with Ubuntu 10.4. The firmware-linux-nonfree package needs to be removed for this---I guess they ship their own firmware. In case you wonder about the linux-base package from experimenal: it was pulled in when I installed the 2.6.35 kernel from experimental. That did not appear to change anything, but I am too scared to downgrade again. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-18) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Sat Jul 24 02:27:10 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=2b4fbfbd-8cd8-4da5-b90c-7b281a41435b ro quiet ** Not tainted ** Kernel log: [7.901738] intel_rng: FWH not detected [7.925838] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [8.036778] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input7 [8.037020] ACPI: Video Device [GRFX] (multi-head: yes rom: yes post: no) [8.100735] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [8.889669] [drm] Initialized drm 1.1.0 20060810 [8.970529] i801_smbus :00:1f.3: PCI INT B - Link[LNKB] - GSI 10 (level, low) - IRQ 10 [9.125816] pci :00:02.0: PCI INT A - Link[LNKA] - GSI 10 (level, low) - IRQ 10 [9.125833] pci :00:02.0: setting latency timer to 64 [9.138369] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [9.412976] yenta_cardbus :02:03.0: CardBus bridge found [1028:0122] [9.541048] yenta_cardbus :02:03.0: ISA IRQ mask 0x00b8, PCI irq 10 [9.541061] yenta_cardbus :02:03.0: Socket status: 3006 [9.541081] yenta_cardbus :02:03.0: pcmcia: parent PCI bridge I/O window: 0xa000 - 0xafff [9.541093] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa000-0xafff: clean. [9.542535] yenta_cardbus :02:03.0: pcmcia: parent PCI bridge Memory window: 0xe020 - 0xe02f [9.542547] yenta_cardbus :02:03.0: pcmcia: parent PCI bridge Memory window: 0x1800 - 0x21ff [9.543151] yenta_cardbus :02:07.0: CardBus bridge found [12a3:ab01] [9.543175] yenta_cardbus :02:07.0: Enabling burst memory read transactions [9.543186] yenta_cardbus :02:07.0: Using CSCINT to route CSC interrupts to PCI [9.543194] yenta_cardbus :02:07.0: Routing CardBus interrupts to PCI [9.543204] yenta_cardbus :02:07.0: TI: mfunc 0x0102, devctl 0x60 [9.773048] yenta_cardbus :02:07.0: ISA IRQ mask 0x, PCI irq 10 [9.773061] yenta_cardbus :02:07.0: Socket status: 3010 [9.773072] pci_bus :02: Raising subordinate bus# of parent bus (#02) from #04 to #07 [9.773097] yenta_cardbus :02:07.0: pcmcia: parent PCI bridge I/O window: 0xa000 - 0xafff [9.773110] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa000-0xafff: clean. [9.774549] yenta_cardbus :02:07.0: pcmcia: parent PCI bridge Memory window: 0xe020 - 0xe02f [9.774560] yenta_cardbus :02:07.0: pcmcia: parent PCI bridge Memory window: 0x1800 - 0x21ff [ 10.234342] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean. [ 10.235355] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7 [ 10.235854] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [ 10.236399] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. [ 10.237180] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [ 10.412083] pcmcia_socket pcmcia_socket1: pccard: PCMCIA card inserted into slot 1 [ 10.528166] Intel ICH :00:1f.5: PCI INT B - Link[LNKB] - GSI 10 (level, low) - IRQ 10 [ 10.528206] Intel ICH :00:1f.5: setting latency timer to 64 [ 10.576068] pcmcia_socket pcmcia_socket1: cs: memory probe 0xe020-0xe02f: excluding 0xe020-0xe020 [ 10.585810] pcmcia 1.0: pcmcia: registering new device pcmcia1.0 [ 10.594737] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: clean. [ 10.595748] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7 [ 10.596585] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x820-0x8ff: clean. [ 10.597015] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcf7: clean. [ 10.597793] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa00-0xaff: clean. [ 10.903008] cfg80211: Using static regulatory domain info [ 10.903016] cfg80211: Regulatory domain: US [ 10.903023] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 10.903032] (2402000 KHz - 2472000 KHz @
Bug#592872: Amarok doesn't play audio cd
Package: amarok Version: 2.3.1-1 Severity: normal Amarok doesn't play my audio CDs. I have tried two ways: a) Open amarok from the device manager which correctly suggests amarok to play the inserted CD. Then amarok shows n tracks, with n being the correct number of tracks on the cd. However, the names of the songs are not recognized, and they all have length 0:00. None of the songs is playable. b) Start amarok from a konsole. Initially, the cd is not mentioned in the playlist. I go to playlist -- add media. The file dialog shows the audio cd and all files on it the way dolphin would (all correct, apparently). However, when I try to select a track, the file dialog closes directly after clicking on the file name, before clicking 'okay'. Needless to say: nothing is played again. The cd plays nicely if I copy it to my harddrive first. In case b), amarok gives out a lot of debugging information, which I put here: QObject::connect: Cannot connect Meta::MediaDeviceHandler::incrementProgress() to (null)::incrementProgress() QObject::connect: Cannot connect Meta::MediaDeviceHandler::endProgressOperation(const QObject*) to (null)::endProgressOperation(const QObject*) QDBusObjectPath: invalid path Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Calling appendChild() on a null node does nothing. QGraphicsLinearLayout::removeAt: invalid index 1 role 0 : ( QVariantList ) : QVariant(QVariantList, (QVariant(QString, Wiedergabelisten-Dateien auf dem Datenträger) , QVariant(QString, Interne Datenbank) ) ) role 1 : ( QVariantList ) : QVariant(QVariantList, (QVariant(QIcon, ) , QVariant(QIcon, ) ) ) role 3 : ( QVariantList ) : QVariant(QVariantList, (QVariant(QString, Wiedergabelisten-Dateien auf dem Datenträger) , QVariant(QString, Interne Datenbank) ) ) QMap((0, QMap((0, QVariant(QString, Wiedergabelisten-Dateien auf dem Datenträger) ) ( 1 , QVariant(QIcon, ) ) ( 3 , QVariant(QString, Wiedergabelisten-Dateien auf dem Datenträger) ) ) ) ) Creating empty group: Wiedergabelisten-Dateien auf dem Datenträger QMap((0, QMap((0, QVariant(QString, Interne Datenbank) ) ( 1 , QVariant(QIcon, ) ) ( 3 , QVariant(QString, Interne Datenbank) ) ) ) ) Creating empty group: Interne Datenbank QMap() Object::connect: No such signal QSortFilterProxyModel::renameIndex( QModelIndex ) amarok(3058)/kdeui (Wallet): The kwalletd service has been disabled amarok(3058)/kdeui (Wallet): The kwalletd service has been disabled amarok(3058)/kdeui (Wallet): The kwalletd service has been disabled amarok(3058)/kdeui (Wallet): The kwalletd service has been disabled amarok(3058)/kdeui (Wallet): The kwalletd service has been disabled amarok(3058)/kdeui (Wallet): The kwalletd service has been disabled role 0 : ( QVariantList ) : QVariant(QVariantList, (QVariant(QString, Lokale Podcasts) ) ) role 1 : ( QVariantList ) : QVariant(QVariantList, (QVariant(QIcon, ) ) ) role 3 : ( QVariantList ) : QVariant(QVariantList, (QVariant(QString, Lokale Podcasts) ) ) QMap((0, QMap((0, QVariant(QString, Lokale Podcasts) ) ( 1 , QVariant(QIcon, ) ) ( 3 , QVariant(QString, Lokale Podcasts) ) ) ) ) Creating empty group: Lokale Podcasts QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::setCompositionMode: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::save: Painter not active QPainter::fillPath: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::translate: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::fillPath: Painter not active QPainter::restore: Unbalanced save/restore QPainter::setClipRegion: Painter not active QPainter::save: Painter not active QPainter::translate: Painter not active QPainter::save: Painter not active QPainter::pen: Painter not active QPainter::setPen: Painter not active QPainter::pen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::restore: Unbalanced save/restore QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::save: Painter not active QPainter::setPen: Painter not active QPainter::translate: Painter not active QPainter::pen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setPen: Painter not active QPainter::translate: Painter not active QPainter::pen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setPen: Painter not active QPainter::translate: Painter not active QPainter::pen: Painter not active QPainter::restore:
Bug#592744: dragonplayer doesn't play dvd
Package: dragonplayer Version: 4:4.4.5-1 Severity: normal When I insert a DVD, the KDE device manager applet suggests that I use dragonplayer to play it. When I pick dragonplayer, the player opens. I click on 'Play CD/DVD' but nothing happens. It's the same when I start the player from the konsole. Then I additionally get the error messages dragonplayer(2421)/kdeui (kdelibs): Attempt to use QAction aspect_ratio_menu with KXMLGUIFactory! dragonplayer(2421)/kdeui (kdelibs): Attempt to use QAction audio_channels_menu with KXMLGUIFactory! dragonplayer(2421)/kdeui (kdelibs): Attempt to use QAction subtitle_channels_menu with KXMLGUIFactory! Please prompt me for more information, if needed. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dragonplayer depends on: ii kdebase-runtime 4:4.4.5-1runtime components from the offici ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-8GCC support library ii libkdecore5 4:4.4.5-1the KDE Platform Core Library ii libkdeui5 4:4.4.5-1the KDE Platform User Interface Li ii libkio5 4:4.4.5-1the Network-enabled File Managemen ii libkparts4 4:4.4.5-1the Framework for the KDE Platform ii libphonon4 4:4.6.0really4.4.2-1 the core library of the Phonon mul ii libqt4-dbus 4:4.6.3-1Qt 4 D-Bus module ii libqtcore4 4:4.6.3-1Qt 4 core module ii libqtgui4 4:4.6.3-1Qt 4 GUI module ii libsolid4 4:4.4.5-1Solid Library for KDE Platform ii libstdc++6 4.4.4-8 The GNU Standard C++ Library v3 ii libxine11.1.19-2 the xine video/media player librar ii libxine1-x 1.1.19-2 X desktop video output plugins for ii phonon 4:4.6.0really4.4.2-1 metapackage for the Phonon multime dragonplayer recommends no packages. dragonplayer 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#592746: xine doesn't play dvd because dvd-drive is mounted as /dev/dvd1 instead of /dev/dvd
Package: xine-ui Version: 0.99.6-1 Severity: normal I am trying to play a dvd using the xine GUI in xine-ui. I start it from a konsole. The GUI comes up, and I press the 'dvd' button there. I get an error window, and, in particular, the message 'libdvdread: Can't stat /dev/dvd' on the konsole. Indeed, my (only) dvd drive is mounted as /dev/dvd1 instead of /dev/dvd. Linking /dev/dvd to /dev/dvd1 let's me play the dvd for this session. Also I guess I could configure xine such as to look for dvds in /dev/dvd1. But as a user I think that the player software should find the drive automatically. I am aware that this is possible not the correct package for the bug report. I didn't know any better. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xine-ui depends on: ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libcurl3-gnutls 7.21.0-1 Multi-protocol file transfer libra ii liblircclient00.8.3-5infra-red remote control support - ii libpng12-01.2.44-1 PNG library - runtime ii libreadline6 6.1-3 GNU readline and history libraries ii libx11-6 2:1.3.3-3 X11 client-side library ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar ii libxft2 2.1.14-2 FreeType-based font drawing librar ii libxine1 1.1.19-2 the xine video/media player librar ii libxine1-ffmpeg 1.1.19-2 MPEG-related plugins for libxine1 ii libxine1-x1.1.19-2 X desktop video output plugins for ii libxinerama1 2:1.1-3X11 Xinerama extension library ii libxtst6 2:1.1.0-3 X11 Testing -- Record extension li ii libxv12:1.0.5-1 X11 Video extension library ii libxxf86vm1 1:1.1.0-2 X11 XFree86 video mode extension l Versions of packages xine-ui recommends: ii xdg-utils1.0.2+cvs20100307-1 desktop integration utilities from xine-ui suggests no packages. -- no debconf information -- * Oliver Sander** email: san...@mi.fu-berlin.de* * Freie Universität Berlin ** phone: + 49 (30) 838 75348 * * Institut für Mathematik ** URL : page.mi.fu-berlin.de/~sander * * Arnimallee 6 ** -* * 14195 Berlin, Germany** Member of MATHEON (www.matheon.de) * -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592752: Problems linking libipopt to a sequential program
Package: coinor-libipopt-dev Version: 3.8.3-2 Severity: normal I have been using a hand-compiled libipopt with a C++ program for a while. The linear solver for ipopt was ma27 (fortran). The C++ program was purely sequential, hence there was no need to mention or have MPI. Now I want to build the same program with libipopt from the new package (thanks for packaging, by the way!). As the linker flags I use -lipopt -llapack -lblas -lgfortran which is what worked before. (As ma27 is not used anymore I guess the -lgfortran is obsolete.) The program compiles and links, however when running it I get symbol lookup error: /usr/lib/libipopt.so.0: undefined symbol: MPI_Init on the first call to libipopt, and the program aborts. Trying to be smart, I add -lmpi to me list of linker flags. Then I get the run time error [haile:4637] *** An error occurred in MPI_Comm_rank [haile:4637] *** on communicator MPI_COMM_WORLD [haile:4637] *** MPI_ERR_COMM: invalid communicator [haile:4637] *** MPI_ERRORS_ARE_FATAL (your MPI job will now abort) Is this a bug or am I using the wrong flags? How can I find out what the correct linker flags are? The ipopt manual mentions a file ipopt_addlibs_cpp.txt with this information, but it is not contained in the Debian package. I guess the most elegant solution would be to use pkg-config. Support for pkg-config seems to have entered the ipopt code shortly after the 3.8.3 release. Maybe it can be backported? -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages coinor-libipopt-dev depends on: ii coinor-libipopt0 3.8.3-2Interior-Point Optimizer, for larg coinor-libipopt-dev recommends no packages. coinor-libipopt-dev 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
