Re: [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.
Hi I've turned lots of things off so it might take me a while to get this to you. I thought I had nepomuk completely suppressed however I see it is still running. I have attached the output from the command which I just issued. So obviously something is still running. I am still getting corruption of the file system also. I have attached also a list from the Ubuntu sw management tool to show which versions are installed. Thanks for following this up. Regards, Tim Josling On Fri, Mar 1, 2013 at 3:34 PM, Bladud 1053...@bugs.launchpad.net wrote: Thank you, what you did was exactly right, and interestingly there is this suggestive line: 0 D 1000 2198 2108 7 99 - - 32215 sleep_ R 00:00:02 nepomukservices However, I really need ps to not truncate the output...does ps -wweo pid,state,args | grep nepomuk work for you? I only need the results from the first test again. It should look something like: 2487 S /usr/bin/nepomukserver 9797 S /usr/bin/nepomukservicestub nepomukstorage 9857 S /usr/bin/nepomukcontroller -session 10a470623400013606718180005290009_1362030556_932758 9900 S /usr/bin/nepomukservicestub nepomukfileindexer 9901 S /usr/bin/nepomukservicestub nepomukfilewatch but longer. Could you also tell me exactly the version of the nepomuk package installed? Thanks -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1053783 Title: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info. Status in “gnome-session” package in Ubuntu: Confirmed Bug description: In Ubuntu 12.04, the shutdown is stalling - for about 2 minutes - but only on occasions when I have opened - and then quit - KAlarm. A window pops up Stating that, 'A Program is still running'; Unknown (not responding); and, there are 3 buttons to choose: 'Lock Screen', 'Cancel' and 'Shutdown Anyway'. Initial report was Bug #1053779 but had no package information. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27 Uname: Linux 3.2.0-30-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Fri Sep 21 13:22:35 2012 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions ** Attachment added: temp.txt https://bugs.launchpad.net/bugs/1053783/+attachment/3552570/+files/temp.txt ** Attachment added: nepomuk-installed1.png https://bugs.launchpad.net/bugs/1053783/+attachment/3552571/+files/nepomuk-installed1.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1053783 Title: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.
I have no NFS file systems. I never have and I don't even know how to set them up. df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda6 115345448 41550852 67935296 38% / udev 4076624 4 4076620 1% /dev tmpfs1635464 936 1634528 1% /run none5120 0 5120 0% /run/lock none 4088652 2596 4086056 1% /run/shm /dev/sda7 336443396 257672676 61680376 81% /home3 /dev/sdb5 365367160 36495920 310311672 11% /home4 /dev/sdb1 115353540 37911128 71582708 35% /home2 Here is a PS as requested which I ran earlier. This was a ps auxf - as have turned nepo* off I can't readily do the exact command you requested. This particular ps may in fact have been done before the shutdown was requested. tim 14522 1.7 0.3 647640 30540 ?Sl 23:08 0:00 \_ /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder tim 14571 0.2 0.1 230884 11716 ?Sl 23:08 0:00 /usr/bin/nepomukserver tim 14577 5.6 0.4 1255452 37948 ? SNl 23:08 0:00 \_ /usr/bin/nepomukservicestub nepomukstorage tim 14600 2.0 0.3 644180 29452 ?SNl 23:08 0:00 \_ /usr/bin/nepomukservicestub nepomukfileindexer tim 14601 1.3 0.3 475160 25016 ?SNl 23:08 0:00 \_ /usr/bin/nepomukservicestub nepomukqueryservice tim 14602 1.5 0.3 543168 27536 ?SNl 23:08 0:00 \_ /usr/bin/nepomukservicestub nepomukbackupsync tim 14603 6.2 0.3 702476 27396 ?SNl 23:08 0:00 \_ /usr/bin/nepomukservicestub nepomukfilewatch I am willing to turn it on again if needed to get the diagnostic info. Let me know. Tim Josling On Tue, Feb 12, 2013 at 4:42 PM, Bladud 1053...@bugs.launchpad.net wrote: When shutdown is hung, can you find out which nepomuk processes are still running? You can do this by executing 'ps -ef | grep nepomuk' at a terminal. Also, do you have any network filesystems? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1053783 Title: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info. Status in “gnome-session” package in Ubuntu: Confirmed Bug description: In Ubuntu 12.04, the shutdown is stalling - for about 2 minutes - but only on occasions when I have opened - and then quit - KAlarm. A window pops up Stating that, 'A Program is still running'; Unknown (not responding); and, there are 3 buttons to choose: 'Lock Screen', 'Cancel' and 'Shutdown Anyway'. Initial report was Bug #1053779 but had no package information. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27 Uname: Linux 3.2.0-30-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Fri Sep 21 13:22:35 2012 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1053783 Title: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.
I have exactly the same problem. In fact it gets worse. If I force the shut down I find that on restart a full file system check is forced and I am getting file system corruption!!! My workaround is to log off before I shutdown. I log off and get a message that an unknown program is running and I force the logoff. Then I shut down. This seems to avoid the problem of file system corruption. However it means that shutdown has an annoying 2 minute wait (for the program to be terminated during logon) then I have to shut down. Another workaround is to press the restart button on the computer. If I do this there is no annoying 2 minute wait and no file system corruption. It amazes me that hitting the red button is less problematic than doing an orderly shutdown. So there are several problems here 1. I run kalarm and terminate it correctly. This results in a problem shutting the system down and at best a 2 minute delay. Problem #1. 2. The name of the offending program that is delaying the shutdown is not displayed. You only get unknown. Problem number #2. 3. There is a 2 minute delay after you choose to force termination of the program. Problem #3 4. File system check forced on restart. Problem #4. 5. File system corruption detected on restart. Problem #5. This is the flakiest linux install since Slackware with Linux 0.99 which was flaky mainly due to the X driver. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1053783 Title: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.
The file system error/check bug is here http://ubuntuforums.org/showthread.php?t=1973178 This problem is not limited to kalarm. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1053783 Title: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 18510] Re: Rhythmbox Does Not Remember Current Song on Reopen
After 4+ years, this is not solved. May be this is an intentional design? Can the Dev team add an option somewhere to allow people who still want to resume their last played album / playlist and song position ? -- Rhythmbox Does Not Remember Current Song on Reopen https://bugs.launchpad.net/bugs/18510 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 416731] Re: Long filename unreadable by Windows but can be read by Ubuntu
Can you FWD my comment to the people at http://bugzilla.gnome.org/show_bug.cgi?id=589919 ? I have created an account, activated, requested pwd change, etc. By I can never login. Alwyas get The username or password you entered is not valid. I have noticed above that you have rated the Importance of this bug as Low. Upstream, the bug report is rated as Unconfirmed. This is quite a giant bug. I am wondering what is the mechanism behind the rating of the importance of a bug. -- Long filename unreadable by Windows but can be read by Ubuntu https://bugs.launchpad.net/bugs/416731 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 416731] [NEW] Long filename unreadable by WIndows but can be read by Ubuntu
Public bug reported: Binary package hint: brasero Using Ubuntu 9.04 x64. Brasero 2.26.1 I have seen that a similar bug report https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/349096 has been flagged as invalid. I think this is a valid bug report. A quick description of the bug is: Ubuntu can read long file name in a data DVD written by a Windows software. The opposite is not always true. Brasero writes something in the DVD so that Windows only see capitalized 8.3 folder / file name. But when read under Ubuntu, all the log file name are intact. It is not a long file name problem. Brasero can write long file name which is Windows compatible (meaning can be read by Windows and the long filename appears as the original name). Example (without quotes) Ubuntu_0-94 - 64 bits Version.txt. However, when the folder / file name is long and has symbol Example (without quotes) Ubuntu_0-94 - 64 bits Version (April 2009).txt Then when the Burn button is clicked, Brasero UNCHECK the Increase compatibility with Windows System box. If you continue to burn the CD/DVD then the file / folder is transformed into captialized name and truncaeted to 8.3 format. Example: UBUNT_01.TXT. However if the CD/DVD is read using Ubuntu then the file name appears as its original name. This is not not a technical support question, neither nitpicking about a philosophical debate about who is better between Linux Windows. This is an objective report about a simple and provable discrepancy. A file has a name, the file is written in a DVD. The DVD doesn't know which OS is going to read it. When Windows writes that file name in the DVD, Ubuntu can read it. When Brasero writes the same file name in the DVD, Windows can no longer read it. There is no waring on Ubuntu system that states Ubuntu can only read DVD written specifically for Ubuntu. Therefore I assume that the DVD format must be universal and compatible between Windows Ubuntu. To reproduct this bug: 1. Create folder named: Test Brasero Long File name (Aug.2009) 2. Copy any binary file into this folder and rename it to: 01 - Brasero [2.26.1] and Ubuntu 9.04 x64.testBinary Burn the CD/DVD and read it using Windows operating system. The folder and file names above must remain intact. ** Affects: brasero (Ubuntu) Importance: Undecided Status: New -- Long filename unreadable by WIndows but can be read by Ubuntu https://bugs.launchpad.net/bugs/416731 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 416731] Re: Long filename unreadable by Windows but can be read by Ubuntu
** Summary changed: - Long filename unreadable by WIndows but can be read by Ubuntu + Long filename unreadable by Windows but can be read by Ubuntu ** Description changed: Binary package hint: brasero Using Ubuntu 9.04 x64. Brasero 2.26.1 I have seen that a similar bug report https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/349096 has been flagged as invalid. I think this is a valid bug report. A quick description of the bug is: Ubuntu can read long file name in a data DVD written by a Windows software. The opposite is not always true. Brasero writes something in the DVD so that Windows only see capitalized - 8.3 folder / file name. But when read under Ubuntu, all the log file - name are intact. + 8.3 folder / file name. But when read under Ubuntu, all the long file + names are intact. It is not a long file name problem. Brasero can write long file name which is Windows compatible (meaning can be read by Windows and the long - filename appears as the original name). Example (without quotes) + file name appears as the original name). Example (without quotes) Ubuntu_0-94 - 64 bits Version.txt. - However, when the folder / file name is long and has symbol Example + However, when the folder / file name is long and has symbol. Example (without quotes) Ubuntu_0-94 - 64 bits Version (April 2009).txt Then when the Burn button is clicked, Brasero UNCHECK the Increase compatibility with Windows System box. If you continue to burn the CD/DVD then the file / folder is transformed into captialized name and truncaeted to 8.3 format. Example: UBUNT_01.TXT. However if the CD/DVD is read using Ubuntu then the file name appears as its original name. - This is not not a technical support question, neither nitpicking about a + This is not not a technical support question, neither nitpicking a philosophical debate about who is better between Linux Windows. This is an objective report about a simple and provable discrepancy. A file has a name, the file is written in a DVD. The DVD doesn't know which OS - is going to read it. When Windows writes that file name in the DVD, - Ubuntu can read it. When Brasero writes the same file name in the DVD, - Windows can no longer read it. There is no waring on Ubuntu system that - states Ubuntu can only read DVD written specifically for Ubuntu. - Therefore I assume that the DVD format must be universal and compatible - between Windows Ubuntu. + is going to read it. When Windows writes that file / folder name in the + DVD, Ubuntu can read it. When Brasero writes the same file name in the + DVD, Windows can no longer read it. There is no waring on Ubuntu system + that states Ubuntu can only read data DVD written specifically for + Ubuntu. Therefore I assume that the DVD format must be universal and + compatible between Windows Ubuntu. - To reproduct this bug: + To reproduce this bug: 1. Create folder named: Test Brasero Long File name (Aug.2009) 2. Copy any binary file into this folder and rename it to: 01 - Brasero [2.26.1] and Ubuntu 9.04 x64.testBinary Burn the CD/DVD and read it using Windows operating system. The folder and file names above must remain intact. + + Suggestion: remove the Increase compatibility with Windows System + option in Brasero burn dialog. Brasero just writes the file name into + the DVD without transforming its length or casing. The way other CD + burning softwares do. -- Long filename unreadable by Windows but can be read by Ubuntu https://bugs.launchpad.net/bugs/416731 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 407723] [NEW] drag drop files, folder on playlist: must ignore unplayable files
Public bug reported: Binary package hint: totem When drag drop several files (or an entire folder) in Totem playlist, files which are not playable are also taken, As a result, Totem pops up an error message An error occured, the playback of this movie requires a decoder plugin which is not installed. Files which are obviously not media (pdf, txt, bz2, deb, jpg, etc.) should be ignored and not added to the playlist when they are dropped to the playlist. Or to make it more flexible, there should be a checkbox drag drop only playable files ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- drag drop files, folder on playlist: must ignore unplayable files https://bugs.launchpad.net/bugs/407723 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 373534] Re: Rhythmbox 0.12.0 time unknown, seekbar disabled
From my perspective, this bug is no longer relevant. After several system updates, I was hoping that there will be a fix. But the issue still remained. I have re-installed Ubuntu 9.04 x64 and this issue is gone and ... replaced by a graphic issues. Lets see how it goes I may file another bug. -- Rhythmbox 0.12.0 time unknown, seekbar disabled https://bugs.launchpad.net/bugs/373534 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 373534] Re: Rhythmbox 0.12.0 time unknown, seekbar disabled
Cross fading was on. When disabled, Rhythmbox now can play the MP3. Thanks But the seekbar still cannot move. Same behaviour when playing the same MP3 with Totem Movie Player 2.26.1. Can play song, the cursor on the seekbar can be moved (but the song still continues to play normally instead to jumping to the position indicated by the cursor). As soon as the mouse is released the cursor goes back to position 0. So practically this means the Totem's seekbar doesn't work either. I have tried to read the rhythmbox --debug output on the screen, there is no obvious error. When the song doesn't play (crossfading enabled) there is a long series of this kind of output: (00:28:32) [0x166a500] [tick_cb] rb-shell-player.c:3615: tick: [file:///home/crazyusername/Music/DemoSong.mp3, 0:0(0)] -- Rhythmbox 0.12.0 time unknown, seekbar disabled https://bugs.launchpad.net/bugs/373534 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 373534] Re: Rhythmbox 0.12.0 time unknown, seekbar disabled
That's incredible, gst-launch could play the song that Rhythmbox is unable to play. gst-launch -v playbin uri=file:///home/crazyusername/Music/Demo Song.mp3 /GstPlayBin:playbin0/GstDecodeBin:decodebin0/GstTypeFindElement:typefind.GstPad:src: caps = application/x-id3 /GstPlayBin:playbin0/GstDecodeBin:decodebin0/GstID3Demux:id3demux0.GstPad:sink: caps = application/x-id3 /GstPlayBin:playbin0/GstDecodeBin:decodebin0/GstApeDemux:apedemux0.GstPad:sink: caps = application/x-apetag /GstPlayBin:playbin0/GstStreamSelector:selector_audio_src0: active-pad = NULL /GstPlayBin:playbin0/GstDecodeBin:decodebin0/ffdec_mp3:ffdec_mp30.GstPad:sink: caps = audio/mpeg, mpegversion=(int)1, layer=(int)3 /GstPlayBin:playbin0/GstDecodeBin:decodebin0.GstGhostPad:src0: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16 /GstPlayBin:playbin0/GstDecodeBin:decodebin0/ffdec_mp3:ffdec_mp30.GstPad:src: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16 /GstPlayBin:playbin0/GstStreamSelector:selector_audio_src0.GstSelectorPad:sink0: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16 /GstPlayBin:playbin0/GstDecodeBin:decodebin0.GstGhostPad:src0: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16 /GstPlayBin:playbin0/GstDecodeBin:decodebin0.GstGhostPad:src0.GstProxyPad:proxypad1: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16 /GstPlayBin:playbin0/GstStreamSelector:selector_audio_src0.GstPad:src: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16 /GstPlayBin:playbin0/GstQueue:preroll_audio_src0.GstPad:sink: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16 /GstPlayBin:playbin0/GstQueue:preroll_audio_src0.GstPad:src: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16 /GstPlayBin:playbin0/GstBin:abin/GstAudioConvert:aconv.GstPad:src: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16 /GstPlayBin:playbin0/GstBin:abin/GstAudioConvert:aconv.GstPad:sink: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16 /GstPlayBin:playbin0/GstBin:abin.GstGhostPad:sink: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16 /GstPlayBin:playbin0/GstBin:abin.GstGhostPad:sink: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16 /GstPlayBin:playbin0/GstBin:abin.GstGhostPad:sink.GstProxyPad:proxypad3: caps = audio/x-raw-int, rate=(int)44100, channels=(int)2, channel-positions=(GstAudioChannelPosition) GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT, GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT , signed=(boolean)true, endianness=(int)1234, width=(int)16, depth=(int)16
[Bug 373534] Re: Rhythmbox 0.12.0 time unknown, seekbar disabled
Sorry for late answer. Same behaviour on Guest Session (MP3 plays but seekbar remains disabled and Time is always unknown for ALL MP3, Ogg play OK). Also on my regular user account, since I have played some Ogg, I can no longer play MP3. Each time I click an MP3, Rhythmbox hangs, must Force Quit. No pb with the MP3 file, VLC plays it OK. -- Rhythmbox 0.12.0 time unknown, seekbar disabled https://bugs.launchpad.net/bugs/373534 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 373534] Re: Rhythmbox 0.12.0 time unknown, seekbar disabled
All files are local. Just installed Ubuntu 9.04 x32 on another computer. The same MP3 files I have trouble in the upgraded Ubuntu 9.04 x64 are played OK. So it seems like it's not a rhythmbox issue. Some new info on the troubled Ubuntu 9.04 x64 machine: - Ogg files play OK (seekbar move OK and song duration is displayed in the Time column) - As soon as I clicked on an MP3 file, either VRB or fixed byte encoded, Rhythmbox hangs and becomes unresponsive. On that same machine, the same MP3 that Rhythmbox cannot play is played perfectly OK using VLC 0.99a. I guess it's a bad installation or something went wrong after the upgrade 8.10 - 9.04. May be you can just help me by showing me how to do a reinstall of Rhythmbox and the codecs? Thanks in advance. -- Rhythmbox 0.12.0 time unknown, seekbar disabled https://bugs.launchpad.net/bugs/373534 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 373534] Re: Rhythmbox 0.12.0 time unknown, seekbar disabled
dpkg -l | grep gstreamer ii bluez-gstreamer4.32-0ubuntu4.1 Bluetooth gstreamer support ii gstreamer0.10-alsa 0.10.22-5 GStreamer plugin for ALSA ii gstreamer0.10-ffmpeg 0.10.6.2-1ubuntu2 FFmpeg plugin for GStreamer ii gstreamer0.10-gnomevfs 0.10.22-5 GStreamer plugin for GnomeVFS ii gstreamer0.10-plugins-base 0.10.22-5 GStreamer plugins from the base set ii gstreamer0.10-plugins-base-apps0.10.22-5 GStreamer helper programs from the base se ii gstreamer0.10-plugins-good 0.10.14-1 GStreamer plugins from the good set ii gstreamer0.10-pulseaudio 0.10.14-1 GStreamer plugin for PulseAudio ii gstreamer0.10-schroedinger 1.0.5-1 GStreamer plugin for encoding/decoding of Di ii gstreamer0.10-tools0.10.22-1 Tools for use with GStreamer ii gstreamer0.10-x0.10.22-5 GStreamer plugins for X11 and Pango ii libgstreamer-plugins-base0.10-00.10.22-5 GStreamer libraries from the base set ii libgstreamer0.10-0 0.10.22-1 Core GStreamer libraries and elements ii totem-gstreamer2.26.1-0ubuntu5 A simple media player for the GNOME desktop -- Rhythmbox 0.12.0 time unknown, seekbar disabled https://bugs.launchpad.net/bugs/373534 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 373534] [NEW] Rhythmbox 0.12.0 time unknown, seekbar disabled
Public bug reported: Binary package hint: rhythmbox Using Ubuntu 9.04 x64, system up to date as of 2009-05-07, Rhythmbox version 0.12.0 After upgrade from 8.10 to 9.04, Rhythmbox no longer displays the duration of the song. The time column is always Unknown and remains so even after the song has been played completely. More serious yet, the seek bar is disabled. Seek bar: the cursor which shows the relative position of the playing song in the total time. The cursor always remains at position 0, it doesn't move when the song is playing and, of course, it is not possible to move it with the mouse. The only thing I can do is to listen to the song from start to end. This issue didn't exist with v8.10. On this same machine, VLC can play the same song and it is possible to move VLC's seekbar. Thanks in advance for taking care. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- Rhythmbox 0.12.0 time unknown, seekbar disabled https://bugs.launchpad.net/bugs/373534 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
