[Bug 228550] Re: aspect ratio crop tool hangs
Changing few variables in aspect ratio crop tool "fixed" the problem. Now works as expected. -- aspect ratio crop tool hangs https://bugs.launchpad.net/bugs/228550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 228550] Re: aspect ratio crop tool hangs
see last comment ** Changed in: digikam (Ubuntu) Status: New => Invalid -- aspect ratio crop tool hangs https://bugs.launchpad.net/bugs/228550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324071] [NEW] [jaunty] Digikam crashes under Gnome but not under KDE
Public bug reported: On startup Digikam (and 2 days ago Amarok 2) crashes under Gnome, while it works just fine under KDE. $ lsb_release -rd Description:Ubuntu jaunty (development branch) Release:9.04 $ apt-cache policy digikam digikam: Installed: 2:0.10.0~rc1-0ubuntu1 Candidate: 2:0.10.0~rc1-0ubuntu1 Version table: *** 2:0.10.0~rc1-0ubuntu1 0 500 http://ftp.kfki.hu jaunty/universe Packages 100 /var/lib/dpkg/status I have a stack trace, (KDE states that it's probably useless): This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb477f700 (LWP 20458)] [New Thread 0xb19ffb90 (LWP 20476)] [New Thread 0xb2610b90 (LWP 20475)] [New Thread 0xb3162b90 (LWP 20459)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7f7b424 in __kernel_vsyscall () [Current thread is 0 (LWP 20458)] Thread 4 (Thread 0xb3162b90 (LWP 20459)): #0 0xb7f7b424 in __kernel_vsyscall () #1 0xb54960e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb559827d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0xb5783792 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0x08292d61 in ?? () #5 0xb578274e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb54924ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb55893fe in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 3 (Thread 0xb2610b90 (LWP 20475)): #0 0xb7f7b424 in __kernel_vsyscall () #1 0xb54960e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb559827d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0xb5783792 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb7195232 in Digikam::LoadSaveThread::run () from /usr/lib/libdigikamcore.so.1 #5 0xb578274e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb54924ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb55893fe in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 2 (Thread 0xb19ffb90 (LWP 20476)): #0 0xb7f7b424 in __kernel_vsyscall () #1 0xb54960e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb559827d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0xb5783792 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb7195232 in Digikam::LoadSaveThread::run () from /usr/lib/libdigikamcore.so.1 #5 0xb578274e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb54924ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb55893fe in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb477f700 (LWP 20458)): #0 0xb7f7b424 in __kernel_vsyscall () #1 0xb5544746 in nanosleep () from /lib/tls/i686/cmov/libc.so.6 #2 0xb554455e in sleep () from /lib/tls/i686/cmov/libc.so.6 #3 0xb68d1c02 in ?? () from /usr/lib/libkdeui.so.5 #4 0xb68d2604 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5 #5 #6 0xb58889a7 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #7 0xb7f0dfd3 in ?? () from /usr/lib/libphonon.so.4 #8 0xb7ef7216 in ?? () from /usr/lib/libphonon.so.4 #9 0xb7ef84aa in ?? () from /usr/lib/libphonon.so.4 #10 0xb7ef6b85 in ?? () from /usr/lib/libphonon.so.4 #11 0xb7f074b5 in ?? () from /usr/lib/libphonon.so.4 #12 0xb7f077a0 in Phonon::VideoPlayer::VideoPlayer () from /usr/lib/libphonon.so.4 #13 0x08285557 in ?? () #14 0x08235a93 in ?? () #15 0x0826037a in ?? () #16 0x08252aa3 in ?? () #17 0x082548bb in ?? () #18 0x082b62ef in ?? () #19 0xb54bb775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #20 0x0808d6b1 in _start () #0 0xb7f7b424 in __kernel_vsyscall () Some
[Bug 324071] Re: [jaunty] Digikam crashes under Gnome but not under KDE
Installed. The stack trace is: Application: digiKam (digikam), signal SIGSEGV [Current thread is 0 (LWP 28924)] Thread 4 (Thread 0xb3150b90 (LWP 28943)): #0 0xb7f69424 in __kernel_vsyscall () #1 0xb54840e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb558627d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0xb5771792 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0x08292d61 in Digikam::ScanController::run (this=0xa215d10) at /build/buildd/digikam-0.10.0~rc1/digikam/scancontroller.cpp:412 #5 0xb577074e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb54804ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb55773fe in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 3 (Thread 0xb25f2b90 (LWP 29184)): #0 0xb7f69424 in __kernel_vsyscall () #1 0xb54840e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb558627d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0xb5771792 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb7183232 in Digikam::LoadSaveThread::run (this=0xa53b9d8) at /build/buildd/digikam-0.10.0~rc1/libs/threadimageio/loadsavethread.cpp:129 #5 0xb577074e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb54804ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb55773fe in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 2 (Thread 0xb19ffb90 (LWP 29185)): #0 0xb7f69424 in __kernel_vsyscall () #1 0xb54840e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb558627d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0xb5771792 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb7183232 in Digikam::LoadSaveThread::run (this=0xa4899f0) at /build/buildd/digikam-0.10.0~rc1/libs/threadimageio/loadsavethread.cpp:129 #5 0xb577074e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb54804ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb55773fe in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb476d700 (LWP 28924)): [KCrash Handler] #6 0xb58769a7 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #7 0xb7efbfd3 in Phonon::AudioOutputAdaptor::outputDeviceIndexChanged (this=0x0, _t1=0) at /build/buildd/phonon-4.3.0/obj-i486-linux-gnu/phonon/moc_audiooutputadaptor_p.cpp:185 #8 0xb7ee5216 in Phonon::AudioOutputPrivate::handleAutomaticDeviceChange (this=0xa5b6520, devic...@0xbfd86814, type=Phonon::AudioOutputPrivate::FallbackChange) at /build/buildd/phonon-4.3.0/phonon/audiooutput.cpp:366 #9 0xb7ee64aa in Phonon::AudioOutputPrivate::setupBackendObject (this=0xa5b6520) at /build/buildd/phonon-4.3.0/phonon/audiooutput.cpp:269 #10 0xb7ee4b85 in Phonon::AudioOutputPrivate::init (this=0xa5b6520, c=Phonon::VideoCategory) at /build/buildd/phonon-4.3.0/phonon/audiooutput.cpp:85 #11 0xb7ef54b5 in Phonon::VideoPlayerPrivate::init (this=0xa5b62d0, q=0xa5b6180, category=Phonon::VideoCategory) at /build/buildd/phonon-4.3.0/phonon/videoplayer.cpp:59 #12 0xb7ef57a0 in VideoPlayer (this=0xa5b6180, category=Phonon::VideoCategory, parent=0xa5b5e60) at /build/buildd/phonon-4.3.0/phonon/videoplayer.cpp:75 #13 0x08285557 in MediaPlayerView (this=0xa5b40e8, parent=0xa28f808) at /build/buildd/digikam-0.10.0~rc1/digikam/mediaplayerview.cpp:108 #14 0x08235a93 in AlbumWidgetStack (this=0xa28f808, parent=0xa489d80) at /build/buildd/digikam-0.10.0~rc1/digikam/albumwidgetstack.cpp:115 #15 0x0826037a in DigikamView (this=0xa545fc0, parent=0xa2ed218) at /build/buildd/digikam-0.10.0~rc1/digikam/digikamview.cpp:196 #16 0x08252aa3 in Digikam::DigikamApp::setupView (this=0xa2ed218) at /build/buildd/digikam-0.10.0~rc1/digikam/digikamapp.cpp:400 #17 0x082548bb in DigikamApp (this=0xa2ed218) at /build/buildd/digikam-0.10.0~rc1/digikam/digikamapp.cpp:191 #18 0x082b62ef in main (argc=5, argv=0xbfd86ef4) at /build/buildd/digikam-0.10.0~rc1/digikam/main.cpp:167 -- [jaunty] Digikam crashes under Gnome but not under KDE https://bugs.launchpad.net/bugs/324071 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324071] Re: [jaunty] Digikam crashes under Gnome but not under KDE
Maybe in conjunction with this: 1. Gwenview work normally but there is no window decoration at all. 2. I had a case when digikam started, but I could only see the main window part, the thumbnail list. No window decoration, and nothing else. As there were no way to quit the app, I had to kill it with xkill. After it the error from above occurred. 3. checked k3b (as another kde app): everything is fine, window decoration, etc... -- [jaunty] Digikam crashes under Gnome but not under KDE https://bugs.launchpad.net/bugs/324071 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to digikam in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 324071] Re: [jaunty] Digikam crashes under Gnome but not under KDE
After an update today, everything works as expected on first start. After closing and restarting Digikam crashes, just as before. -- [jaunty] Digikam crashes under Gnome but not under KDE https://bugs.launchpad.net/bugs/324071 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324071] Re: [jaunty] Digikam crashes under Gnome but not under KDE
I found out that pulse is the source of the trouble. When pulse killed digikam, amarok, etc. starts and restarts normally each time. I don't know if this is a pulse or a "kde-pulse bridge" bug. -- [jaunty] Digikam crashes under Gnome but not under KDE https://bugs.launchpad.net/bugs/324071 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 228550] [NEW] aspect ratio crop tool hangs
Public bug reported: Binary package hint: digikam After some kde packages upgraded (about 1 week ago ~ may 4) when choosing aspect ratio crop tool X hangs. I tried it with xorg and xgl too. In both cases X became non-responsive. (alt+ctrl+1 multiple times brings up console). The system recovers after a while (about 3 minutes). For that time X uses 100% of CPU. In the Xorg log I see a lots of lines like this: -- cut -- mieqEnequeue: out-of-order valuator event; dropping. tossed event which came in late -- cut -- When the system recovers the aspect ratio crop appears and works as normally. Packages: digikam2:0.9.3-2ubuntu1 xserver-xorg 1:7.3+10ubuntu10 xserver-xorg-core 2:1.4.1~git20080131-1ubuntu9 kdebase-bin4:3.5.9-0ubuntu7.2 kdebase-bin-kde3 4:3.5.9-0ubuntu7.2 kdebase-bin-kde4 4:4.0.4-0ubuntu1~hardy3 System: 32 bit, Ubuntu Hardy (8.04) 2.6.24-17-generic ** Affects: digikam (Ubuntu) Importance: Undecided Status: New -- aspect ratio crop tool hangs https://bugs.launchpad.net/bugs/228550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324071] Re: Digikam crashes under Gnome but not under KDE (Phonon::AudioOutputAdaptor::outputDeviceIndexChanged)
Confirmed. Works with Karmic (9.10). Thank you! -- Digikam crashes under Gnome but not under KDE (Phonon::AudioOutputAdaptor::outputDeviceIndexChanged) https://bugs.launchpad.net/bugs/324071 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 775401] [NEW] package postgresql-8.4 8.4.8-0ubuntu0.10.04 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Public bug reported: Binary package hint: postgresql-8.4 automatic update ProblemType: Package DistroRelease: Ubuntu 10.04 Package: postgresql-8.4 8.4.8-0ubuntu0.10.04 ProcVersionSignature: Ubuntu 2.6.32-31.61-generic-pae 2.6.32.32+drm33.14 Uname: Linux 2.6.32-31-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon May 2 09:46:29 2011 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: postgresql-8.4 Title: package postgresql-8.4 8.4.8-0ubuntu0.10.04 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 ** Affects: postgresql-8.4 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/775401 Title: package postgresql-8.4 8.4.8-0ubuntu0.10.04 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 775401] Re: package postgresql-8.4 8.4.8-0ubuntu0.10.04 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/775401 Title: package postgresql-8.4 8.4.8-0ubuntu0.10.04 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
