control: severity 736612 normal Hi,
FYI: I do not have any problem here .... On Sat, Jan 25, 2014 at 05:14:29PM +0200, Juhapekka Tolvanen wrote: > Package: im-config > Version: 0.24-1 This is sid/testing version > Severity: grave This should not be used to indicate you are extremely annoyed. > When I use im-config, it writes these to console: Can you elaborate how you started X. (Or are you in X) Which desktop.... > % im-config > > ** (zenity:2238): WARNING **: Couldn't register with accessibility > bus: Did not receive a reply. Possible causes include: the remote > application did not send a reply, the message bus security policy > blocked the reply, the reply timeout expired, or the network > connection was broken. I would say "What the h***" too. But problem seems to be not im-config but "zenity" in your environment. > ** (zenity:3354): WARNING **: Couldn't register with accessibility > bus: Did not receive a reply. Possible causes include: the remote > application did not send a reply, the message bus security policy > blocked the reply, the reply timeout expired, or the network > connection was broken. > head: virhe luettaessa tiedostoa ”Asiakirjat”: On hakemisto > tail: virhe luettaessa tiedostoa ”Asiakirjat”: On hakemisto > E: Configuration in Asiakirjat is manually managed. Doing nothing. In order to make problem cleaner, can you change Desktop locale to be en_US.UTF-8. I would like to see exactly what happens under reproducible environment from my side. > "virhe luettaessa tiedostoa ”Asiakirjat”: On hakemisto" means: "error > reading file ”Asiakirjat”: Is directory". Asiakirjat happens to be the > first file or directory in my home directory, when running running > command "ls". Meaning is one thing but we need to track the code where these strings are living in. The program is written in English strings while they get translated with gettext mechanism. So, please. > Why on earth it tries to do something in that directory ~/Asiakirjat ? > Where is the current configuration of im-config? I do not know. but to identify issues and forward to zenity with meaningful message, we need more data from you. At least, I do not have problem like yours here on sid. > -- System Information: > Debian Release: jessie/sid > APT prefers stable > APT policy: (990, 'stable'), (500, 'testing-proposed-updates'), (500, > 'oldstable-updates'), (500, 'oldstable-proposed-updates'), (102, 'testing'), > (101, 'unstable') Hmmmm... this make me think .... Why are you reporting sid/testing version bug with such system. Why put aggressive testing-proposed-updates in 500 while keeping testing in 102. This seems to indicate you tend to believe library from any repo can be mixed. (Debian's package version dependency description is getting better on handling odd combinations but this is like playing with fire.) For your case, upgrade to testing seems right thing to do if you can. Please make sure you have consistent library from a single set of repo unless you know extremely well on this library ABI issue. To me, you have broken library ABI issue by using unsupported combination of packages. Hmmm... unless you have a clean rational report as follow-up in a week or so, I will close this bug. (I consider this to be user mis-configuration at this moment.) Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
