[solved - bug reports filed]python cssselect missing

After today's python updates, I'm getting an error in calibre converting to .mobi. I have the python2-cssutils package installed, am I missing another package?
File "/usr/lib/python2.7/site-packages/lxml/cssselect.py", line 18, in <module>
raise ImportError('cssselect seems not to be installed.
Last edited by Scimmia (2012-10-18 01:02:07)

For a temp solution I recommend changing line 23 in /usr/lib/calibre/calibre/ebooks/oeb/stylizer.py
from:
from lxml.cssselect import css_to_xpath, ExpressionError, SelectorSyntaxError
to:
from cssselect import GenericTranslator
Patch is short so I'm posting it here:
--- stylizer.py 2012-10-18 23:27:41.205984029 +0200
+++ stylizer.py.patched 2012-10-18 23:27:07.442641381 +0200
@@ -20,7 +20,8 @@
from cssutils import (profile as cssprofiles, parseString, parseStyle, log as
cssutils_log, CSSParser, profiles, replaceUrls)
from lxml import etree
-from lxml.cssselect import css_to_xpath, ExpressionError, SelectorSyntaxError
+#from lxml.cssselect import css_to_xpath, ExpressionError, SelectorSyntaxError
+from cssselect import GenericTranslator
from calibre import force_unicode
from calibre.ebooks import unit_convert
from calibre.ebooks.oeb.base import XHTML, XHTML_NS, CSS_MIME, OEB_STYLES

Similar Messages

Bug Report Tool Bar Icon Missing

I'm using the latest version of Safari on 10.7.3. I always kept the bug report icon on the tool bar to have a quick way to send a report when necessary. Today when I had an issue I noticed the icon was gone and when I went to the View menu to customize the tool bar I saw that the icon was missing from there as well. I know that Report Bugs To Apple is under the Sfari menu and I used that but I'm wondering why the icon was removed from this version.

Yes, it seems to be gone.
As for why ...
I don't see how anybody here could know what the developers were thinking.

Zsh modutils completion (solved & bug report)

Hi,
Since last zsh update, I can't get 'modinfo' & 'modprobe' completion, only 'rmmod' & 'modprobe -r' are working actually (easy with '/proc/modules'). It seems that a new caching algorithm was implemented in the last version but I don't understand it . Diff with zsh 4.3.11 _modutils :
--- Sources/zsh-4.3.11/Completion/Linux/Command/_modutils 2009-07-14 10:57:13.000000000 +0200(B
+++ /usr/share/zsh/functions/Completion/Linux/_modutils 2011-06-02 13:02:04.000000000 +0200(B
@@ -1,8 +1,23 @@(B
#compdef lsmod modinfo modprobe rmmod insmod
+_modules_caching_policy()(B
+{(B
+ # Rebuild every week, or if $modules_dir is newer than the cache(B
+ local -a oldp(B
+(B
+ oldp=( "$1"(Nmw+1) )(B
+ (( $#oldp )) || [[ $modules_dir -nt $1 ]](B
+}(B
+(B
local curcontext="$curcontext" expl state line modules ign args ret=1
local -r modules_dir=/lib/modules
+local update_policy(B
+zstyle -s ":completion:*:*:$service:*" cache-policy update_policy(B
+if [[ -z "$update_policy" ]]; then(B
+ zstyle ":completion:*:*:$service:*" cache-policy _modules_caching_policy(B
+fi(B
+(B
args=(
'(-)'{-V,--version}'[print version]'
'(-)'{-h,--help}'[print help text]'
@@ -39,6 +54,7 @@(B
"(-v --verbose $ign)"{-v,--verbose}'[print all commands as executed]' \
'(-C --config)'{-C,--config}'[specify config file]:config file:_files' \
"(-r --remove -l --list -t --type -a --all $ign)"{-r,--remove}'[remove module (stacks)]' \
+ "(-l --list -t --type -a --all $ign)"{'-i[ignore install/remove commands in config file]','--ignore-install[ignore install commands in config file]','--ignore-remove[ignore remove commands in config file]'} \(B
"(* -l --list -r --remove $ign)"{-l,--list}'[list matching modules]' \
"(-c $ign)1:modules:->loadable_modules" \
"(-c -l --list -t --type $ign)*:params:->params" && ret=0
@@ -87,7 +103,13 @@(B
else
kver=$(uname -r)
fi
- modules=( $modules_dir/$kver/(*~(source|build))/**/*(.:t:r) )(B
+ if [[ -z $modules ]] && ! _cache_invalid modules-$kver && \(B
+ ! _retrieve_cache modules-$kver;(B
+ then (B
+ # 2011-01-02 gi1242: Do we need .o files? Or is .ko enough?(B
+ modules=( $modules_dir/$kver/(*~(source|build))/**/*.(o|ko)(.:t:r) )(B
+ _store_cache modules-$kver modules(B
+ fi(B
if [[ $state = loadable_modules ]]; then
modules=( ${modules:#(${(j:|:)~${=loaded_modules//_/-}})} )
Last edited by Drexya (2011-06-13 01:46:34)

Wow, thanks it works, but there's a problem, modules appears with *.ko suffix so
modules=( $modules_dir/$kver/(*~(source|build))/**/*.(o|ko|ko.gz)(.:t:r:r) )
is even better .
taken from http://zsh.sourceforge.net/Guide/zshguide05.html :
print ${p:t:r}
will work for both arrays and scalars: the :t takes only the tail of the filename, stripping the directories, and the :r removes the suffix. These two operators could have slightly unexpected effects in versions of zsh before 4.0.1, removing `suffixes' which contained directory paths, for example (though this is what the pattern forms taken separately do, too).
bug report
Last edited by Drexya (2011-06-13 01:45:45)

Did you know that Google toolbar doesn't work properly in FF rc1? I have filed a bug report to Google about this

The Google toolbar doesn't recognize a left mouse click when selecting a 'suggestion'. It's OK using the keyboard, however. I have filed a bug report with Google, but as this is an important extension thought you should know.

See also: http://forums.adobe.com/message/4662367#4662367
-Noel

[solved] whats the right place for community repository bug reports?

was about to write a bug report, but there was no category for packages:community.. is the forum the correct place for this?
pacman -S freevo
resolving dependencies...
error: cannot resolve "python-pysqlite-legacy", a dependency of "freevo"
error: failed to prepare transaction (could not satisfy dependencies)
:: freevo: requires python-pysqlite-legacy
Last edited by schuay (2008-12-11 18:17:21)

schuay wrote:
was about to write a bug report, but there was no category for packages:community.. is the forum the correct place for this?
pacman -S freevo
resolving dependencies...
error: cannot resolve "python-pysqlite-legacy", a dependency of "freevo"
error: failed to prepare transaction (could not satisfy dependencies)
:: freevo: requires python-pysqlite-legacy
When you go into the bug tracker, there's a drop down list on your left that says "Arch Linux". Go into there, select "Community Packages", and pres the "switch" button right next to it.

[Bug Report] Rhythmbox missing depedency for "tdb"

Here's the bug report:
https://bugs.archlinux.org/task/29310
Just tryed to install Rhythmbox and had to track down that depedency. Just figured I'd post it here to try to give it some more attention. Seems like a pretty easy fix that could save some users some frustration. Go give it a vote on the bug report so the developers will see this.

For Oracle TopLink customers can report bugs using a support request on metalink.oracle.com.
For TopLink Essentials customer can directly file bugs in the GlassFish system.
Doug

Upstream Bug Reporting Etiquette [solved]

I've a question. Some distributions discourage upstream reporting by users so as not to overwhelm upstream developers and to provide a single cohesive point of contact for the distribution. Errors are posted at the distro bug report site and are reported upstream by the maintainer.
I get the distinct impression this does not hold true for Arch. Before I go off promoting my bug reports upstream, is this proper?
If so, the bug reports are likely to have references to Arch when describing the problem and how to reproduce it. Since I am not officially part of the Arch developer / maintainer team, I do not want to represent myself as such. Recommendations?
Thank you.
Last edited by ewaller (2010-07-01 13:00:44)

FWIW, I think relying on package maintainers of a specific distro is unfair for those maintainers. They are already responsible for tracking the statuses of A LOT of packages and updating/patching them as necessary. If they were to go through every single bug reported and forward the relevant ones upstream, it would simply be overwhelming.
Newbie-oriented distros like Ubuntu might have people that simply track user reported bugs. But for Arch, the situation is actually better since most users are proficient enough in Linux so they are more than capable of reporting a bug upstream
Last edited by dcc24 (2010-07-01 07:03:59)

Filing Bug Reports in Configurator

I spend a lot of time looking at the logging in Console that comes from this app, and I have a few uncaught exceptions and Crash Reports that I can recreate consistently. Can I file bug reports with Apple? Where do I file bug reports? I have seen the Apple Bug Reporter, and there is no clear product type that matches Apple Configurator (iPad, iPad SDK, App Store, Other) and I am not sure if this is even seen as official. Anyone does this before?

Please do file bug reports using Apple Bug Reporter and they will be routed to the Configurator engineering team. Provide as much information as you can about the problem, what specific actions you take that cause it to occur, versions of all relevant software (Configurator, OS X, iOS, etc.), and anything else that seems relevant.

Filing Bug Reports With Apple?

I SWEAR Apple is getting more and more like Microsoft.
Can some one PLEASE tell me how to file a BUG REPORT to Apple on the 10.5.3 update? I am getting graphic driver problems again like they were on 10.5.0 and 10.5.1.
Contacting Apple with a direct bug report seems near impossible and the website is of little help in finding this information. I am outside of Apple Care support.
10.5.3 graphic drivers are broken again on a "Dual 2HHz Power PC G5" with the following Graphics Card:
GeForce FX 5200:
Chipset Model: GeForce FX 5200
Type: Display
Bus: AGP
Slot: SLOT-1
VRAM (Total): 64 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0321
Revision ID: 0x00a2
ROM Revision: 2060
Bringing up the Save Dialog for e-mail attachments for Apple Mail 3.3 (924) cause the background to totally go wacko but it is restored when the save dialog disappears.
Message was edited by: Confused7766

Register for a free online developer account with your AppleID you used to sign on this board. http://developer.apple.com/
Then go to http://bugreporter.apple.com/ and login there to file your bug report. Note, any discoveries there you are under a non-disclosure agreement.

Bug Report: Shortcuts for Adjustments in 3.1

I have verified that bug with a brand new test account (Aperture 3.1 and OS 10.6.4 with latest Pro Update):
- Make an adjustment to an NEF-file
- save that adjustment as a preset
- assign a keyboard shortcut to that specific adjustment
Switch to the next NEF-file and make your usual adjustments:
- initiate that shortcut to apply the already saved preset/adjustment
All of a sudden, all already applied adjustments are set back to defaults!!!!
To sum up:
Shortcuts are presently not useable!
Bug Report was filed!
Any observations???

I got it myself. My shortcut combination contained the option key. That causes AP to replace any adjustments already made to the image. You have to use a keyboard short cut combination without the option key.
The question is, why AP 3.1 is not smart enough to refuse such a combination??? In version 3.0.x everything worked fine!!!

BUG REPORT FIRMWARE 5.1.7 PLEASE FORWARD TO SUPERVISOR....

BUG REPORT FIRMWARE 5.1.7 PLEASE FORWARD TO SUPERVISOR.
The spa-3102 has the following two bugs.
When the unit sends a hook-flash to the fxo port it:
a) does not send the hook flash to the fxo port for PSTN Hook Flash Len: Instead it uses a very short pulse of about 100ms or 1/10 of a second. It should honor the PSTN Hook Flash Len configurable parameter of .2 – 1.5 seconds.
b) Does not change the line voltage from –7 (off-hook) to –48(on-hook) during a flash-hook to the fxo port. Instead it varies the voltage only by about 2.5 volts.
This was reported as early as June 07 to linksys support. It is reported they agreed and would fix in the next firmware release. There is info that firmware 5.2 being released and is this fix in 5.2 and how can I get it.

Although the problem is still not solved, at least I now know WHY the problem is happening... and Apple's Firmware Update is NOT to blame!
Through a series of coincidences, I was actually lucky enough to get in touch with the engineers in Apple's Airport firmware division, and they were helping me to nail down this problem.
Turns out that Apple takes great PRIDE in the fact that they are one of the VERY FEW manufacturers who make routers that behave properly in this regards: they SPECIFICALLY test for their Airport Extreme routers to allow you to connect to servers behind the NAT by way of the public WAN IP address of the NAT box. This is the way that apparently the NAT/DHCP specification is SUPPOSED TO WORK! You're SUPPOSED to be able to connect this way, if you so desire.
So what was causing the problem on my network, then?
Something I hadn't thought about... the Vonage Linksys RTP300 router that we're using for our Vonage VoIP service. Turns out that this router does NOT support clients behind the NAT connecting to servers behind the NAT by way of the public WAN IP address.
Linksys is to blame, not Apple!
And apparently, this feature may have actually been working in an earlier
firmware update, but apparently, Vonage AUTOMATICALLY pushes firmware
updates to RTP300's, apparently without user notification:
<http://www.vonage.com/help.php?article=1066&category=90&nav=5>
And a forum thread on vonage-forums.com seems to indicate that the 1.00.60 firmware in the RTP300 started getting pushed to customer units on or before 1/26/06, making it less than a month after Apple shipped the 5.7 firmware update for AirPort Extreme Base Stations:
<http://www.vonage-forum.com/ftopic10915.html>. So if the problem cropped up then, it's possible that I accidentally attributed it to Apple when really the RTP300 got a firmware update around then too which may have broken this feature (assuming it was working before then).
Power Mac G4 QuickSilver Dual 800 MHz Mac OS X (10.4.4)

Sending a bug report on the OS and a sleep mode problem.

I find the bug button in Safari really convenient for sending Apple bug reports. And when other applications crash, you usually get an error dialog with a button to send a bug report. But sometimes problems arise that require reporting, but which don't fall in either of these categories. It would be very handy to have a bug "button" for the OS, or perhaps just a menu selection in the Finder menu bar that invokes a bug report dialog box. I know you can dig around and find the URL for Apple's bug report web page, but I am always forgetting it -- I suppose I could just bookmark it, but then I'd just have to dig around in all the bookmarks to find it. Better would be a utility built-in to the OS for sending bug reports (like Safari's). It could also automatically transfer necessary info about the OS rev and such.
The problem I had was this. I have a script that puts my iMac to sleep. I put the script alias on the task bar and a single click puts the computer to sleep (easier than using the menu). Unfortunately, I sometimes click it by mistake when I am trying to click an adjacent icon in the task bar, and the Mac starts going through its cycle to enter sleep mode and is impervious to anything I do to try and cancel it. I tried pressing the space bar continuously to prevent it from going to sleep, but that did not work. Worse, when it went to sleep and I woke it up again, the task bar would not appear, clicking on app windows did not activate them, Finder menus could not be selected, etc. The cursor would move, but I could not do anything else. (I wish now I had noted if the clock in the menu bar was still advancing, but I didn't think to do that.) I powered down the iMac from the power key and rebooted. Things are working fine now.
I wanted to send a bug report on this, but realized that unlike Safari, there was no button or menu selection for doing that. So here I am.
Any suggestions are welcome.
TIA,
Drake

[email protected]
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Solaris 9 x86 bug report - el_GR.ISO8859-7 & CDE

I'm posting this article here, because I can't find any official Solaris 9 x86 bug report page. I hope the developers will notice it. I'm using Solaris 9 x86 (12/02), with the latest 9_x86_Recommended patch cluster installed, and support for Greek installed too.
It seems there is some kind of problem, when trying to view text files with Greek (el_GR.ISO8859-7) characters, which were created under Windows. To be more specific:
If I boot at CDE with language el_GR.ISO8859-7, and try to view a .txt file (just with a simple double click), which I have created under Windows, with Greek characters,
the screen goes black, and the CDE login screen appears again (restarts). If I keep the Greek language or change the language to US English, I can boot at CDE again, with
no problems. If I try "command line logging", the screen goes off - just like when the computer is powered off, and I can't do anything, (well, except pressing the reset button, that's the sure way). And if I use the "init 6" command, while being logged at CDE, from a terminal, the Graphical Desktop exits, and then, the screen goes off again (just like the computer is powered off), but finally the computer manages to restart.
I'm using the Sun X server, NOT the XFree86 porting kit and I use the entry
:0 Local local_uid@console nobody /usr/openwin/bin/Xsun :0 -dpsfileops
in /usr/dt/config/Xservers file, to start the X server.
Here is the $HOME_DIR/.dt/startlog file:
--- ??? 23 ??? 2003 12:10:51
--- /usr/dt/bin/Xsession starting...
--- starting /usr/openwin/bin/speckeysd
--- Xsession started by dtlogin
--- starting /usr/dt/bin/dtsession_res -load -system
--- sourcing /root/.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
--- sourcing /usr/dt/config/Xsession.d/1000.solregis...
--- could not read /root/.profile
--- starting /usr/dt/bin/dthello &
--- starting /usr/dt/bin/dtsearchpath
--- starting /usr/dt/bin/dtappgather &
--- starting /usr/dt/bin/dsdm &
--- session log file is /root/.dt/sessionlogs/www_DISPLAY=:0
--- DTSOURCEPROFILE is 'true' (see /root/.dtprofile)
--- execing /usr/dt/bin/dtsession with a /sbin/sh login shell ...
--- starting desktop on /dev/pts/3
Sun Microsystems Inc. SunOS 5.9 Generic_112234-03 November 2002
/usr/dt/bin/ttsession[337]: starting
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
I don't know if this is a bug or something, and I'm very curious about the cause. I didn't have much time for any other "experiments".
Anyway, I hope this will help developers solve a problem -if it really exists-.
Angelos Vasilopoulos
Site Security Officer
[email protected]

I'm posting this article here, because I can't find any official Solaris 9 x86 bug report page. I hope the developers will notice it. I'm using Solaris 9 x86 (12/02), with the latest 9_x86_Recommended patch cluster installed, and support for Greek installed too.
It seems there is some kind of problem, when trying to view text files with Greek (el_GR.ISO8859-7) characters, which were created under Windows. To be more specific:
If I boot at CDE with language el_GR.ISO8859-7, and try to view a .txt file (just with a simple double click), which I have created under Windows, with Greek characters,
the screen goes black, and the CDE login screen appears again (restarts). If I keep the Greek language or change the language to US English, I can boot at CDE again, with
no problems. If I try "command line logging", the screen goes off - just like when the computer is powered off, and I can't do anything, (well, except pressing the reset button, that's the sure way). And if I use the "init 6" command, while being logged at CDE, from a terminal, the Graphical Desktop exits, and then, the screen goes off again (just like the computer is powered off), but finally the computer manages to restart.
I'm using the Sun X server, NOT the XFree86 porting kit and I use the entry
:0 Local local_uid@console nobody /usr/openwin/bin/Xsun :0 -dpsfileops
in /usr/dt/config/Xservers file, to start the X server.
Here is the $HOME_DIR/.dt/startlog file:
--- ??? 23 ??? 2003 12:10:51
--- /usr/dt/bin/Xsession starting...
--- starting /usr/openwin/bin/speckeysd
--- Xsession started by dtlogin
--- starting /usr/dt/bin/dtsession_res -load -system
--- sourcing /root/.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
--- sourcing /usr/dt/config/Xsession.d/1000.solregis...
--- could not read /root/.profile
--- starting /usr/dt/bin/dthello &
--- starting /usr/dt/bin/dtsearchpath
--- starting /usr/dt/bin/dtappgather &
--- starting /usr/dt/bin/dsdm &
--- session log file is /root/.dt/sessionlogs/www_DISPLAY=:0
--- DTSOURCEPROFILE is 'true' (see /root/.dtprofile)
--- execing /usr/dt/bin/dtsession with a /sbin/sh login shell ...
--- starting desktop on /dev/pts/3
Sun Microsystems Inc. SunOS 5.9 Generic_112234-03 November 2002
/usr/dt/bin/ttsession[337]: starting
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
I don't know if this is a bug or something, and I'm very curious about the cause. I didn't have much time for any other "experiments".
Anyway, I hope this will help developers solve a problem -if it really exists-.
Angelos Vasilopoulos
Site Security Officer
[email protected]

FAQ: How do I submit a bug report or feature request or otherwise give feedback about Premiere Pro?

The best way to submit a bug report or feature request is to use the bug-report/feature-request form.
The Premiere Pro team doesn’t necessarily see and record every post on every forum and social network, but we do see, record, and track every entry through the the official feature-request/bug-report form.
It also helps a lot if you opt into the Product Improvement Program.
Also, be sure to use the crash reporter.
We really do read all of the bug reports and feature requests, and the software really does get a lot of benefit from detailed crash reports.
Don’t forget about contacting Adobe Technical Support or Customer Service, too. For information on how to contact Adobe Technical Support, see this page. (Note that you must register your product before you can open a technical support case for it.)
If you have tried to get help from our support staff, but the service was inadequate, I can help you to escalate your issue if you send me your case number at kopriva at adobe dot com. You must provide me a case number. I am not offering to solve your problem myself; rather, I am willing to forward your information to someone if you have already hit a dead end with our Technical Support or Customer Service.
If you have feedback about the content of the Premiere Pro Help document, then please add a comment at the bottom of the relevant page. You can add comments to add information, to add links, to make corrections, or to ask for clarification.
If you want to keep up with the Premiere Pro team, then you can follow our blogs, Facebook page, and Twitter feed and so on.
Oh, and I can’t resist this opportunity to remind you to update to the most recent version of the application. Don’t be surprised when the first thing that you hear back from us is that you need to install the latest updates. We fix a lot of things in updates, and we don’t want to go chasing bugs that we’ve already fixed. We’ll keep you posted on our blogs, Facebook page, and Twitter feed about updates as they become available.

Hi qwerty,
Dun tink that creative customer support sucks cos I had been dealing with them in the past and I can say that their service are quite gd and fast. If you wanted a refund, I tink you need to contact the store that sells you the product. Dun tink creative will refund you though.

Bug Report - Some items in your iTunes Library ... because the file could not be found.

10.6 and this is still this is a problem?!?!?!?!
Not like this is an obscure issue only affecting a few noobs. Google returns 11,200 results on this issue!t'
Can we PLEASE at least allow the list of broken files to be dumped as a text file so I can find them manually! guess not,
I'll just have to get out a pencil and write down 100 songs to spend my saturday looking up and fixing. Or I could let my wife purchase 100 songs she already has whenever this comes up...
What's really infurating is that non-technical wife thinks this means she must go to the iTunes store and buy them again. Is it just coincidence that this only happens to songs that we ripped from the CD with iTunes? Hmmmm?....
what follows is for the programmers, please make sure this get's to the development group.
iTunes is the only music library manager, Media player was not even activated.
iTunes is configured to "Keep folder organized", "Copy files to folder when adding"
this has been a recurring issue since iTunes 9.x for us
The issue is persisted accross system and library rebuilds.
some of the same songs recurr but most of the time the list differs.
Library survived transfer to new computer and back for a system rebuild (new hdd) w/o this issue.
I'm guessing 100 songs is an arbitrary limit for error reporting.
Songs seem to get lost for the following reasons.
Track number added to filename
Spelling of some tags like Album, Artist, Title differ in iTunes library and the file path !!!!
Only seems to happen to mp3 files.
My suspicion is that iTunes is downloading meta data from the store and updating the mp3 tags and iTunes Music Library.xml then predicting the new file location without actually moving the file to that new location. I've enabled insert/update auditing on the NTFS folder to see if that provided any new info. I'm also capturing iTunes Music Library.xml so I can compare it to the new one WHEN this happens again and see if there is a pattern there.
Would love a bug number and feedback chanel on this.

The missing file thing happens when files are no longer where iTunes expects to find them. Possible causes are that you or some third party tool has moved, renamed or deleted the files, or that the drive they live on has had a change of drive letter. It is also possible that iTunes has changed from expecting the files to be in the pre-iTunes 9 layout to post-iTunes 9 layout, or vice-versa, and so is looking in slightly the wrong place.
Select a track with an exclamation mark, use Ctrl-I to get info, then cancel when asked to try to locate the track. Look on the summary tab for the location that iTunes thinks the file should be. Now take a look around your hard drive(s). Hopefully you can locate the track in question. If a section of your library has simply been moved, or a drive letter has changed, it should be possible to reverse the actions.
Alternatively, as long as you can find a location holding the missing files in a relatively sensible structure, then you should be able to use my FindTracks script to reconnect them to iTunes .
Although you say you haven't used Media Player it can be raised as a background process by visiting enabled web sites. Possibly worth you reviewing this post: Getting iTunes & Windows Media Player to play nicely
jerunamuck wrote:
...My suspicion is that iTunes is downloading meta data from the store and updating the mp3 tags and iTunes Music Library.xml then predicting the new file location without actually moving the file to that new location. I've enabled insert/update auditing on the NTFS folder to see if that provided any new info. I'm also capturing iTunes Music Library.xml so I can compare it to the new one WHEN this happens again and see if there is a pattern there.
Unlike Windows Media player iTunes doesn't have a feature to automatically update tag data, although it will sometimes spot when a 3rd party program has (say during playback) and then update its own copy of the data. The iTunes (Music) Library xml file is provided for querying by third party software and is rewritten every time there is a change to the library, but is otherwise of no relevance to iTunes. The library is maintained in the iTunes Library.itl file. I suppose what could be happening is that iTunes issues a command to the file system to move a file based upon its tag, updates its knowledge of where the file is supposed to be, but the OS fails to move the file for some reason. Alternatively everything could go as planned, but iTunes could fail to get the updated copy of the library written out to disk so next time you start you get the previously stored locations.
I have ideas of my own about the best way to organise my media, but I'm quite familiar with the way iTunes does it. It might be interesting to see the details of one of the broken tracks, the path iTunes thinks it is at, and the actual path, in case there is anything that can be deduced.
Apple don't run an open bug tracking system so you won't be able to follow reports/progress based on a bug number. You can drop a line to iTunes Feedback or get a free Apple Developer account and submit a bug report report there.
tt2

[solved - bug reports filed]python cssselect missing

Similar Messages

Maybe you are looking for