Bug#666272: [keepnote] You can not change language.
It may be duplicated with #572. A locale env is '*.UTF-8' and resources are named '*.UTF8' on Python 2.7 environment, Debian wheezy. Yes, I confirm this bug: cd /usr/lib/python2.7/dist-packages/keepnote/rc/locale cp -r de_DE.UTF8 de_DE.UTF-8 (and all other languages) After start language is accepted and working!! Please fix it somehow!
Bug#750659: [foomatic-db-gutenprint] Upgrade from 5.2.9 to 5.2.10~pre2-2 breaks printing (Epson 525wd)
Package: foomatic-db-gutenprint Version: 5.2.10~pre2-2 Severity: normal NOTE: I have sent a similar bugreport to upstream, however because this might (very likely) be caused by packaging problem, I report it also here. Hello! Printer: Epson SX525WD Driver used: Epson Stylus SX525 Foomatic/gutenprint-ijs.5.2 (en) I do not use, and never used Epson Esc/P-R driver, because its extremely primitive and Foomatic driver worked exceptionally well. Packages installed: printer-driver-gutenprint 5.2.10~pre2-2 -- note, these provide only primitive epson esc/p-r driver. foomatic-db-gutenprint 5.2.10~pre2-2 -- this look to have the actual driver, epson foomatic/gutenprint ijs. foomatic-db 5.2.10~pre2-2 ijsgutenprint 5.2.10~pre2-2 escputil 5.2.10~pre2-2 After global update to current state of Debian Testing yesterday, 5.2.9 to 5.2.10-pre2, I can't print anymore: 1) First when printing over, CUPS responds with usual Rendering completed, but the document stays in queque. Logging into localhost:631, I tried to remove the printer and reinstall it. 2) When reinstalling, the driver usual name is listed. Copy of screen: http://imgur.com/Zs3CWux 3) When clicking Add printer, I get the error message: Unable to add printer Unable to copy PPD file. 4) I have set CUPS to LogLevel debug and these are the relevant snippets: D [05/Jun/2014:13:13:45 +0200] CUPS-Add-Modify-Printer ipp://localhost/printers/SX525WD D [05/Jun/2014:13:13:45 +0200] cupsdIsAuthorized: username=root D [05/Jun/2014:13:13:45 +0200] SX525WD device-uri: OK I [05/Jun/2014:13:13:45 +0200] Setting SX525WD device-uri to lpd://192.168.2.104:515/PASSTHRU (was file:///dev/null.) I [05/Jun/2014:13:13:45 +0200] Setting SX525WD printer-is-accepting-jobs to 1 (was 0.) D [05/Jun/2014:13:13:45 +0200] cupsdMarkDirty(S) D [05/Jun/2014:13:13:45 +0200] cupsdSetBusyState: newbusy=Active clients and dirty files, busy=Active clients D [05/Jun/2014:13:13:45 +0200] cupsdDeregisterPrinter(p=0x7fce2810fae0(SX525WD), removeit=1) I [05/Jun/2014:13:13:45 +0200] Setting SX525WD printer-is-shared to 0 (was 1.) I [05/Jun/2014:13:13:45 +0200] Setting SX525WD printer-state to 3 (was 5.) D [05/Jun/2014:13:13:45 +0200] cupsdMarkDirty(S) D [05/Jun/2014:13:13:45 +0200] cupsdSetBusyState: newbusy=Active clients and dirty files, busy=Active clients and dirty files D [05/Jun/2014:13:13:45 +0200] copy_model: Running cups-driverd cat foomatic:Epson-Stylus_SX525-gutenprint-ijs.5.2.ppd... E [05/Jun/2014:13:13:45 +0200] [CGI] Could not determine driver name for Epson-Stylus_SX525-gutenprint-ijs.5.2.ppd! E [05/Jun/2014:13:13:45 +0200] copy_model: empty PPD file D [05/Jun/2014:13:13:45 +0200] CUPS-Add-Modify-Printer server-error-internal-error: Unable to copy PPD file. E [05/Jun/2014:13:13:45 +0200] [Client 11] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://localhost/printers/SX525WD) from localhost D [05/Jun/2014:13:13:45 +0200] [Client 11] Content-Length: 118 D [05/Jun/2014:13:13:45 +0200] PID 2458 (/usr/lib/cups/daemon/cups-driverd) stopped with status 255 (Unknown error 155) D [05/Jun/2014:13:13:45 +0200] cupsd is not idle any more, canceling shutdown. D [05/Jun/2014:13:13:45 +0200] [Client 11] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=118, response=0x7fce2810f660(IPP_IDLE), pipe_pid=0, file=-1 D [05/Jun/2014:13:13:45 +0200] [Client 11] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0 D [05/Jun/2014:13:13:45 +0200] [Client 11] bytes=0, http_state=0, data_remaining=0 D [05/Jun/2014:13:13:45 +0200] [Client 11] Waiting for request. D [05/Jun/2014:13:13:45 +0200] cupsdSetBusyState: newbusy=Active clients and dirty files, busy=Active clients and dirty files D [05/Jun/2014:13:13:45 +0200] cupsd is not idle any more, canceling shutdown. D [05/Jun/2014:13:13:45 +0200] [CGI] cgiSetVariable: TITLE=Drucker hinzufügen D [05/Jun/2014:13:13:45 +0200] [CGI] cgiSetVariable: SERVER_NAME=localhost D [05/Jun/2014:13:13:45 +0200] [CGI] cgiSetVariable: REMOTE_USER=root D [05/Jun/2014:13:13:45 +0200] [CGI] cgiSetVariable: CUPS_VERSION=CUPS v1.7.2 D [05/Jun/2014:13:13:45 +0200] [Client 15] CGI data ready to be sent. D [05/Jun/2014:13:13:45 +0200] PID 2457 (/usr/lib/cups/cgi-bin/admin.cgi) exited with no errors. D [05/Jun/2014:13:13:45 +0200] cupsd is not idle any more, canceling shutdown. D [05/Jun/2014:13:13:45 +0200] [CGI] cgiSetVariable: MESSAGE=Unable to add printer D [05/Jun/2014:13:13:45 +0200] [CGI] cgiSetVariable: ERROR=Unable to copy PPD file. D [05/Jun/2014:13:13:45 +0200] [Client 11] HTTP_STATE_WAITING Closing on EOF D [05/Jun/2014:13:13:45 +0200] [Client 11] Closing connection. Full log: http://paste.ubuntu.com/7594231/ I have also done a grep SX525 /usr/share/foomatic/* -R, this is the result: http://paste.ubuntu.com/7594371/ It looks like Epson-Stylus_SX525-gutenprint-ijs.5.2.ppd is referenced in the database, but has been moved away; or the system
Bug#750659: [foomatic-db-gutenprint] Upgrade from 5.2.9 to 5.2.10~pre2-2 breaks printing (Epson 525wd)
UPDATE: Version: 5.2.10-1 Le jeudi, 5 juin 2014, 17.07:07 lct a écrit : Driver used: Epson Stylus SX525 Foomatic/gutenprint-ijs.5.2 (en) I do not use, and never used Epson Esc/P-R driver, because its extremely primitive and Foomatic driver worked exceptionally well. (…) It looks like Epson-Stylus_SX525-gutenprint-ijs.5.2.ppd is referenced in the database, but has been moved away; or the system can't extract or generate PPD anymore. This was fixed in the 5.2.10-1 packages; please try to install the 5.2.10-2 packages from unstable, they fix this problem. The package migrated to testing by mistake but this should be fixed in few days. Cheers, OdyX Thanks a lot, OdyX! Now this confirms everything. I will post this post to the debian mailing list for those affected to find my messages and solve them too. Perhaps, it would be wise to force newer foomatic packages out of unstable, so that newer bugs (such as these) don't polute the system and save people the trouble? Thanks! I will report back how this works out and close the issue, which I opened, in upstream. -- Older response below, fresh response is above this line: 1) I have just discovered that the issue is even more serious and might be something to do with Debian only. UPDATE: This indeed is a debian issue, as below. I started by looking at /usr/share/foomatic/db/source/printer/Epson-SX525WD_Series.xml I see that this driver is compatible with workforce 635, 60, nx625. Trying all these drivers fails with similar error. Trying then any other epson driver fails too! So, when adding *any* other foomatic ijs printer driver, this includes other models and simplified driver version, installation breaks with similar issue. Note, that I have already tried removing all relevant (foomatic, foomatic-db, ijs, gutenprint) packages from the system and made sure all the files were physically purged from system. Then I rebooted the machine and reinstalled them. Problem persists. My machine has a flawless SMART on disks and problem started exactly on the next day after upgrade. So, its very unlikely the issue is caused by something else... 2) The wine subsystem seems to make a copy of existing PPDs in system. locate 525|grep -i ppd has reported: /home/lct/.PlayOnLinux/wineprefix/d2/drive_c/windows/system32/spool/drivers/w32x86/3/Netzwerk__Epson_SX525WD.ppd Direct installation of this PPD into CUPS via graphical interface was successfull, BUT the printing is not possible. When printing, there is an error: The PPD version (5.2.9) is not compatible with Gutenprint 5.2.10-pre2. Thanks!
Bug#750659: [foomatic-db-gutenprint] Upgrade from 5.2.9 to 5.2.10~pre2-2 breaks printing (Epson 525wd)
Hello! Upgrading from 5.2.10~pre2-2 to 5.2.10-2 from sid does NOT resolve the issue. I have added sid sources and commented out testing sources, then upgraded to sid version the following packages (and pinned them): escputil 5.2.10-2 foomatic-db-gutenprint 5.2.10-2 gimp-gutenprint 5.2.10-2 gutenprint-locales 5.2.10-2 ijsgutenprint 5.2.10-2 The following packages are (double checked) same in testing and sid: foomatic-db 20140325-1 foomatic-db-engine 4.0.11-1 1) After that I restarted cups and tried to add a printer. Exactly same error came out: Unable to add printer Unable to copy PPD file. 2) After reboot, the situation is same Perhaps it is advisable to rollback to 5.2.9 versions of packages in testing? Because this issue *essentially breaks* the package. I will now 1) remove all the affected packages from system, make sure they are physically gone and reinstall them from sid, then recheck. If it does not work: 2) test a rollback to 5.2.9 of the five packages above now, must find it somewhere first... 3) will try to find previous deb of foomatic-db, and retest. Perhaps the issue is there. I will report back. Please reopen the bug. Thanks!
Bug#750659: [foomatic-db-gutenprint] Upgrade from 5.2.9 to 5.2.10~pre2-2 breaks printing (Epson 525wd)
Hello, dear maintainer, I have spent six hours in a hope to figure out the situation. I have polled three incremental groups of packages...over three distributions, and tested each case individually: x.1) printer-driver-gutenprint, libgutenprint2 x.2) (1) + foomatic-db x.3) (2) + foomatic-db-gutenprint, ijsgutenprint over 1.x) wheezy 2.x) testing 3.x) sid Between groups, I have been restarting cups. And between releases, I have removed every related package before switching source lists. Every single case has been tested and screenshoted (for me). I found out, that there are actually THREE different drivers, that appear *in CUPS driver selection dialogue* if certain conditions meet: 1)- Epson Esc/P-R, a primitive one. Shows up and works over all three distros. 2)- CUPS+Gutenprint v5.2.9(wheezy); 5.2.10(sid). Its broken in Testing, does not appear there. Nothing foomatic is needed for this one to work. 3)- Foomatic/Gutenprint -5.2/-simplified. Initially, I though that I used this (3) driver, but correctly I used (2). The driver (3) appears in CUPS dialog, when foomatic-db-engine package is installed. And it appeared because I started experimenting when printer stopped working. Image: http://imgur.com/l59PIbu I think it should *NOT* appear in CUPS printer driver selection dialog, and should be part of foomatic-filters, package that replaces CUPS? Because its broken in all three releases: Every release, one tries to install driver (3) of any printer that has no drivers installed, there is a message about inability to copy PPD. My previous reports actually consist of a mix of this issue and original issue of testing/(2) For reference, the corresponding versions of packages over three releases: escputil foomatic-db-gutenprint gimp-gutenprint ijsgutenprint - with each sid: 5.2.10-2, testing: 5.2.10~pre2-2, wheezy: 5.2.9-1, and foomatic-db (sid, testing: 20140325-1, wheezy: 20120523-1) Thanks!
Bug#717613: Re[2]: [Pkg-utopia-maintainers] Bug#717613: systemd-udevd failes to execute /lib/udev/socket:@/org/freedesktop/hal/udev_event
@lct: If you run apt-get autoremove, is hal uninstalled? I can only *assume* it is *not*. I always use autoremove after upgrades (I upgrade via apt-get) and the situation with tons and tons of warning messages persisted up till now, that is, until I explicitly checked for existing bug, tried to remove hal (synaptic) and hal-info, no package disagreed, no messages after boot up anymore. But because I did not awarenessly issued autoremove *prior* to directly purging hal, I can't guarantee for that, but my assumption above about HAL's volatility and injection is very strong. I did not believe it has to do anything with outdated HAL, nor I was aware of its presence in the system, because I thought that, this was temporary issue due to switch or integration (as in compatibility to) with systemd. That said, I don't understand why would anyone still support the possibility to have HAL installed in current Debian Testing system. It was deprecated from upstream, it was deprecated from current software stack, it is far less energy efficient, it is harder to configure and so on. Thanks!
Bug#717613: systemd-udevd failes to execute /lib/udev/socket:@/org/freedesktop/hal/udev_event
This is crazy and scary. Affects me too. The system is hardly a year old, first Wheezy then dist-upgraded to Testing. Hal was NOT manually installed. I know what prehistoric artifact HAL is, but the thing is - it was pulled as dependency at some regular update. Indeed, the hal somehow was in the system...! Thanks a lot for reporting and pointing it out. Why doesn't Debian have clear distinction between must-keep/relevant packages and the rest/non-relevant? It sure has manually installed group, but user could manually install because it was dependency of one must-keep package and can be safely purged if must-keep is gone. Apt-pinning isn't the case, because we don't want to pin version, we want to pin the package in system, as explicitly to stay in the system as of relevance to the user. Manually installed is also very vague definition, as displayed earlier. I am not debian developer, nor can code. I wish someone proposed something like that. Thanks!
Bug#714285: Epdfview: When printing, does not scale/honor the page size settings
Package: epdfview Version: 0.1.8 Severity: normal Tested with Gutenprint opensource driver on Epson SX-525wd (NOT epson driver). CUPS and all underlying system is from Debian Testing branch, current state. Open PDF (any) and have any A4 and A5 capable printer ready. Make sure your printing system (CUPS etc) has default page size set to A4. Load A5 blank page in printer (or you can load A4, just note A5 printout size should be visually half of A4), set File-Print-Page size A5 and print. Result: The document will be printed in A4 size, however it is centered as if its for A5. Expected result: The document should be printed in A5 size (scaled down). If you go to your printing system (global) settings (cups: localhost:631) and change default to A5 now, save and then just go back to File-Print-Page size - A5 and print: you will have perfectly sized A5. This means epdfview simply either ignores or can't supply the page size settings in its dialogs to the printing system. If I open the very same document with Evince and set there Page size - A5, automatically scale, then I get perfect page sizes as specified within Evince print dialog regardless of what is set globally default. The problem is - this machine has only XFCE and epdfview is perfect small software for it :(
Bug#705088: Re[4]: Bug#705088: amd64: due to missing lib32asound2-plugins:i386, i386 applications output is broken on pulseaudio-enabled system.
In this case I will reinstall everything from scratch via Debian Netinst and will then post if this bug will be happening on clean install. I will respond in two business days. Thank you! Hello! The clean install machine does not show this issue anymore. This case should remain closed/worksforme. Thank you, Elimar, for your patience and willingless to help! Best regards
Bug#705088: amd64: due to missing lib32asound2-plugins:i386, i386 applications output is broken on pulseaudio-enabled system.
Please show us the output of: apt-show-versions | grep experimental Hello, thanks, sure: root@linux:/tmp# apt-show-versions | grep experimental libgl1-mesa-dri-experimental/testing uptodate 8.0.4-2
Bug#705088: Re[2]: Bug#705088: amd64: due to missing lib32asound2-plugins:i386, i386 applications output is broken on pulseaudio-enabled system.
Please show us the output of: apt-show-versions | grep experimental Hello, thanks, sure: root@linux:/tmp# apt-show-versions | grep experimental libgl1-mesa-dri-experimental/testing uptodate 8.0.4-2 Well, according to the packages apt wants to remove, you have a version mix of packages. There are versions whicht aren't available in Debian testing nor sid. Just from where did you get packages like ffmpeg libavcodec54 libavdevice54 libavfilter3 libavformat54 vlc vlc-nox vlc-plugin-notify vlc-plugin-pulse? It seems that your installation is all but unmaintainable situation. Hello! It was Linux Mint Debian Edition installation (which is just cut of raw Debian testing packages), which I later upgraded to pure Debian testing by changing sources and dist-upgrading. I made sure configs were transfered fine and nothing broke. There is nothing more than custom kernel, unbranded firefox and theme in it. Maybe exactly these packages were not transfered fine. If you insist that your amd64 installation does not have this behaviour and is WORKSFORME, then I suggest we leave this bug closed. In this case I will reinstall everything from scratch via Debian Netinst and will then post if this bug will be happening on clean install. I will respond in two business days. Thank you!
Bug#705088: Re[4]: Bug#705088: amd64: due to missing lib32asound2-plugins:i386, i386 applications output is broken on pulseaudio-enabled system.
Here: apt-get install --no-install-recommends libasound2-plugins:i386 Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: libasound2:i386 libasyncns0:i386 libattr1:i386 libavcodec53:i386 libavutil51:i386 libcap2:i386 libdbus-1-3:i386 libdirac-encoder0:i386 libflac8:i386 libgsm1:i386 libice6:i386 libjack-jackd2-0:i386 libjson0:i386 libmp3lame0:i386 libogg0:i386 libopenjpeg2:i386 liborc-0.4-0:i386 libpulse0:i386 libsamplerate0:i386 libschroedinger-1.0-0:i386 libsm6:i386 libsndfile1:i386 libspeex1:i386 libspeexdsp1:i386 libtheora0:i386 libuuid1:i386 libva1:i386 libvorbis0a:i386 libvorbisenc2:i386 libvpx1:i386 libwrap0:i386 libx11-xcb1:i386 libx264-123:i386 libxtst6:i386 libxvidcore4:i386 Suggested packages: jackd2:i386 pulseaudio:i386 speex:i386 Recommended packages: uuid-runtime:i386 The following NEW packages will be installed: libasound2:i386 libasound2-plugins:i386 libasyncns0:i386 libattr1:i386 libavcodec53:i386 libavutil51:i386 libcap2:i386 libdbus-1-3:i386 libdirac-encoder0:i386 libflac8:i386 libgsm1:i386 libice6:i386 libjack-jackd2-0:i386 libjson0:i386 libmp3lame0:i386 libogg0:i386 libopenjpeg2:i386 liborc-0.4-0:i386 libpulse0:i386 libsamplerate0:i386 libschroedinger-1.0-0:i386 libsm6:i386 libsndfile1:i386 libspeex1:i386 libspeexdsp1:i386 libtheora0:i386 libuuid1:i386 libva1:i386 libvorbis0a:i386 libvorbisenc2:i386 libvpx1:i386 libwrap0:i386 libx11-xcb1:i386 libx264-123:i386 libxtst6:i386 libxvidcore4:i386 0 upgraded, 36 newly installed, 0 to remove and 0 not upgraded. Thank you very much, thats exactly that I would be expecting.
Bug#705088: amd64: due to missing lib32asound2-plugins:i386, i386 applications output is broken on pulseaudio-enabled system.
Package: libasound2-plugins Version:1.0.25-2 Referencing bug (now archived): #663715 Hello. I don't understand how you fixed that guys. The problem clearly still persists. The basic problem is.. - libasound2-plugins:i386 contains additional sinks for i386 applications to output to.. pulseaudio(i386 and amd64). however it is not possible to install this library in amd64 build. This results in wine:i386 (running 32bit applications) is unable to output to pulseaudio:amd64. So they will try to grab raw ALSA, which they will succeed ( if pulse is not used) This is because there is no i386 sink available. How to test: - stock amd64 wheezy build, wine:i386, pulseaudio, pavucontrol, any audio application linux amd64(totem, vlc etc) Start pulse volume control. Start playing something with linux audio application(amd64) // one can notice pavucontrol display new volume control for this application. Sound comes out. Execute wine-cfg, Audio Tab, press Test sound You will NOT hear wine test sound nor you see wine volume control If you close the playing audio application (amd64), then execute pulseaudio --kill !! wine-cfg will be able to output Test sound Why this is happening: --- libasound2-plugins package provides pulse audio sink. amd64 version of plugins provides sinks for amd64 audio applications. i386 version of plugins provides sinks for i386 audio applications that execute on am64 system. If this library is not present on amd64 system, amd64 audio application will not be able to route sound ALSA DIRECT(1)-PULSE(mix)(2)-ALSA(3). It will fail at step 2, because there is no pulse sink seen from i386. So the sound of all i386 applications will be ONLY available via RAW ALSA. amd64 applications will be not affected, because they have libasound2-plugins:amd64. How debian should fix this: - provide libasound2-plugins:i386 for amd64 system please! However, make sure that libasound2-plugins:i386 does NOT depend on packages that pull further i386 libraries. Nothing more than that. Current situation: --- it is impossible to install libasound2-plugins:i386 package on amd64 system. Attempt to pull libasound2-plugins:i386 results in: -- root@linux:/tmp# apt-get install --no-install-recommends libasound2-plugins:i386 Reading package lists... Done Building dependency tree Reading state information... Done libasound2-plugins:i386 is already the newest version. You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: libasound2-plugins:i386 : Depends: libavcodec53:i386 (= 6:0.8.2-2) but it is not going to be installed or libavcodec-extra-53:i386 (= 6:0.8.2-2) but it is not going to be installed Depends: libavutil51:i386 (= 6:0.8.2-2) but it is not going to be installed Depends: libspeexdsp1:i386 (= 1.2~beta3.2-1) but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). If one explicitly adds all missing, but not going to be installed dependecies, we get following: -- (Notice how apt wants to delete whole amd64 audio system with applications) root@linux:/tmp# apt-get install --no-install-recommends libasound2-plugins:i386 libavcodec-extra-53:i386 libavutil51:i386 libmp3lame0:i386 libxvidcore4:i386 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apache2-utils audacity-data libboost-filesystem1.49.0 libboost-program-options1.49.0 libboost-system1.49.0 libboost-thread1.49.0 libdlrestrictions1 libgettextpo0:i386 libgtkglext1 libkdecore5 libmlt-data libportsmf0 libpython3.2 libtiff-tools libtiff5 libunistring0:i386 libvamp-hostsdk3 openshot-doc Use 'apt-get autoremove' to remove them. The following extra packages will be installed: libavcodec-extra-53 libdirac-encoder0:i386 libopencore-amrnb0:i386 libopencore-amrwb0:i386 libopenjpeg2:i386 libschroedinger-1.0-0:i386 libspeex1:i386 libspeexdsp1:i386 libtheora0:i386 libva1:i386 libvo-aacenc0:i386 libvo-amrwbenc0:i386 libvpx1:i386 libx264-123:i386 Suggested packages: speex:i386 The following packages will be REMOVED: audacity blender browser-plugin-gnash browser-plugin-vlc ffmpeg frei0r-plugins gimp gimp-dcraw gimp-dimage-color gimp-gap gimp-gmic gimp-plugin-registry gimp-resynthesizer gimp-texturize gnash gnash-common libavcodec53 libavcodec54 libavdevice53 libavdevice54 libavfilter2 libavfilter3 libavformat53 libavformat54 libgegl-0.2-0 libmjpegtools-2.0-0 libmlt++3 libmlt5 libopencv-calib3d2.3 libopencv-contrib2.3 libopencv-features2d2.3 libopencv-highgui2.3 libopencv-legacy2.3 libopencv-objdetect2.3 libquicktime2 lightspark lightspark-common melt openshot
Bug#705088: Workaround script
Ok, I tried manuall extraction and installation. Simple library copy worked. This is tested bash script to workaround of this bug (its not solution, obviously) Save and run as root: #!/bin/bash cd /tmp mkdir tempalsa cd tempalsa mkdir /usr/lib/i386-linux-gnu/alsa-lib wget http://ftp.us.debian.org/debian/pool/main/a/alsa-plugins/libasound2-plugins_1.0.25-2_i386.deb dpkg -x libasound2-plugins_1.0.25-2_i386.deb . cd usr/lib/i386-linux-gnu/alsa-lib/ mv libasound_module_*pulse* /usr/lib/i386-linux-gnu/alsa-lib/ ldconfig
Bug#692607: linux-image-3.2.0-4-686-pae: Kernel crash when coming out of screen saver
Hello here! I am experiencing exactly this kernel panic on exactly this kernel image version that is right now in DEBIAN TESTING with xfce, absolutely vanilla everything. The panic happens when entering Xorg after login manager (slim). I guess it is also somehow bound to that I use xfwm4 in composite mode. I have P4 with IGP i845, using 915 driver. I suppose the patch was not backported? Please do this, please. Thank you!
Bug#677725: thunar: deleting files on removable media uses a trash with no command to empty it
I have exactly same problem! This is how to track it: You must have at least ONE partition, that is not listed in /etc/fstab or any REMOVABLE disk. Insert disk or pick unmounted partition and access it, entering password. Create a file. Delete a file with Remove option. The directory .Trash is created on current disk/partition (correct behavior). However, the Trash icon does not change from empty to full. If you try to empty trash, it won't be available, because Thunar thinks its empty. If you go inside .Trash however, you will find your deleted file. I confirm this! Thunar: 1.2.3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
