[Bug 959151]
This bug is never going to be fixed because it is more or less just stating an obvious fact. It seems that there somehow no real easy way to avoid this message, other than going in and redirecting all your kde apps that use QCoreApplication to 2>/dev/null. I've experienced this message from ~4.8 to present (for me, 5.9.0 now in kf). While looking at all the other bugs out there, it seems futile to even ask at this point. Unless you can get about 10,000 people to post about it (different people with different IPs!! are the only counted!) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/959151 Title: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/959151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790043] Re: Bash-completion slows up the start of bash
It's worth noting that the bash completion scripts are being started twice when logging in either via a tty or bash's (-l) option. The fault with that is that most systems are checking the shell in /etc/profile.d/bash_completion.sh to see if its bash and then proceeding to call the bash_completion itself, neglecting the fact that bash calls /etc/bash.bashrc anyway which will do the same thing. Lucky for me i rarely log in via tty, im usually in xterm and dont use the (-l) option, but even with one go, those scripts that are being executed are installed into /etc/bash_completion.d/ by the various packages that feature specialized completion. Though we can't blame them because this is exactly what was intended in the first place. The tag is passed back to bash to address startup script execution times in order to speed up this it is going to have to consider the existing scripts out there already. For now maybe there is some way to cache this in a way that would be efficient for both resources and users? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790043 Title: Bash-completion slows up the start of bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/790043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183580] Re: librcc segfaults on latest saucy
(i386 [32-bit] user's instructions, amd64 [64-bit] users will have to alter the link below a bit) I was able to get mocp back up and running pretty simply, 1. sudo apt-get purge librcc0 2. then, download manually: https://launchpad.net/ubuntu/precise/i386/librcc0 3. install it (either some ui program or 'dpkg -i librcc0-0.2.9-3ubuntu1-i386.deb' (or amd64 for those 64-bit users) 4. reinstall moc and any other packages previously uninstalled when purging librcc0 thanks to comments above for giving me the idea to do this (13.10 i386, working good now so definitely something in librcc0 since I didn't have to uninstall *any* other packages :) -- hopefully this will be fixed soon, just make sure you dont accidently upgrade it before that happens or else you will be back to square one, it will probably happen with upgrades so you might want to HOLD that package until then. Hope this helps. - osirisgothra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183580 Title: librcc segfaults on latest saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librcc/+bug/1183580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839560] Re: Errors in bash man page
I've confirmed these (and some more) bugs as well, very annoying when the cornerstone of the entire OS isn't documented properly. This is still the case in 13.04 raring, and probably in 13.10 saucy as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839560 Title: Errors in bash man page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/839560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1068466] Re: none of the emulators start, even with ROMS
this problem didn't exist for me until my upgrade to 13.04 now ZSNES, VICE, and a handful of other emulators DO NOT WORK the only workaround is, run the windows versions of these emulators with wine most of them work allright in that manner but it's annoying because wine does take longer to load up even if the emulation speed is pretty much the same (ZSNES is actually faster with wine than it was native for some reason) I think SDL is to blame... any of my emulators that do not rely on SDL seem to work ok -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068466 Title: none of the emulators start, even with ROMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vice/+bug/1068466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1162846] Re: zsnes: 0xf7fdb430 in __kernel_vsyscall()
well, for the time being, i've discovered a workaround to the problem, its nothing fancy, just did NOT want to go and reinstall everything and go through and pick out all my modified scripts, customizations to the OS, custom services i've written and so fourth... so.. I tried using snes9x and of course none of their save files or states seem to be compatible "enough" for this to be a good replacement (and it seems alot slower). So on a whim I decided since i had a copy of zsnesw still lying on one of my partitions, to fire it up under wine, and i was suprised how well it worked, so for now this is my workaround, and its a whole lot better than reinstalling. I'll continue to step through the other copy and try to pinpoint the problem I am having, I've downloaded the source that was modified for debian to see if i could wade through and try to debug it, so i'll try to come back with a more detailed comment next time. But at least there IS a workaround for this, and thats all my kids cared about :) as far as they are concearned, its fixed :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1162846 Title: zsnes: 0xf7fdb430 in __kernel_vsyscall() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsnes/+bug/1162846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1162846] Re: zsnes: 0xf7fdb430 in __kernel_vsyscall()
This is the same I have to, i've been using zsnes since 12.04 (precise), i upgraded to 12.10 and had no problems, but when I upgraded to 13.04, this problem has rose, now i'm smacking myself for upgrading before the release went stable ); oh well... that same buffer overrun happens, doesnt mater if I reinstall all the dependencies, reinstalled everything even walked through the darn thing, it works fine until I go to load a game,then that error happens. Also, dont know if this is related, but in the --help items there is this. .. cut here .. 0 = None 1 = Keyboard/Gamepad -ad <> Select Audio Driver : auto = Automatically select output sdl = Simple DirectMedia Layer output [ RIGHT HERE ] -d Start with debugger enabled .cut here. notice where it says [ RIGHT HERE ] (which i added to mark that spot) ??? Well, normally there is a bit of a list of other sound interfaces to choose from, but now those two are the only ones even though i KNOW i have pulseaudio and alsa installed fully and they do work. I don't know if this is somehow related and I only noticed because I use zsnes mostly from the command line and notice small things like the options changing. Also, I've tried with various different configurations, clearing all the .zsnes\ files out completly, running as root, permissions on the filesystem, even tried running it on alternate filesystems, so i dont think that's a problem, also tried running some of the older kernels from grub, no go as well... so.. im out of gas here, hope they figure it out, looks like im gonna have to go back to 12.10 for now since my kids use this program so much it practically is the reason they have a computer these days :)... bsnes works but is too slow, snes9x has too many issues to get up and running (like that missing libpng14.so.14, which i dont feel like hunting down)... and other emulators like the pcsx seem to be ok, but not zsnes here's the complete dump below, thanks :) .cut here ZSNES v1.51, (c) 1997-2007, ZSNES Team Be sure to check http://www.zsnes.com/ for the latest version. ZSNES is written by the ZSNES Team (See AUTHORS.TXT) ZSNES comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; please read 'LICENSE.TXT' thoroughly before doing so. Use ZSNES -? for command line definitions. Starting Mouse detection. Unable to poll /dev/input/event4. Make sure you have read permissions to it. Unable to poll /dev/input/event3. Make sure you have read permissions to it. Unable to poll /dev/input/event2. Make sure you have read permissions to it. Unable to poll /dev/input/event1. Make sure you have read permissions to it. Unable to poll /dev/input/event0. Make sure you have read permissions to it. ManyMouse: 0 mice detected. Audio Opened. Driver: Simple DirectMedia Layer output Channels: 2 Rate: 44100 ZSNES could not find any joysticks. *** buffer overflow detected ***: zsnes terminated === Backtrace: = /lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x63)[0xb73c7bc3] /lib/i386-linux-gnu/libc.so.6(+0x10593a)[0xb73c693a] zsnes[0x807e5a5] zsnes[0x8103133] === Memory map: 08048000-0831c000 r-xp 08:01 165751 /usr/bin/zsnes 0831c000-0831d000 r--p 002d3000 08:01 165751 /usr/bin/zsnes 0831d000-0835c000 rw-p 002d4000 08:01 165751 /usr/bin/zsnes 0835c000-08911000 rw-p 00:00 0 09a6b000-09bd1000 rw-p 00:00 0 [heap] b00ff000-b010 ---p 00:00 0 b010-b090 rw-p 00:00 0 b090-b0921000 rw-p 00:00 0 b0921000-b0a0 ---p 00:00 0 b0a64000-b0a65000 ---p 00:00 0 b0a65000-b1265000 rw-p 00:00 0 b1265000-b5266000 rw-s 00:13 50692404 /run/shm/pulse-shm-1658252151 b5266000-b526d000 r--s 08:01 149186 /usr/lib/i386-linux-gnu/gconv/gconv-modules.cache b52de000-b53be000 rw-s 00:04 500531207 /SYSV (deleted) b53be000-b5415000 rw-p 00:00 0 b546d000-b5476000 r-xp 08:01 153205 /usr/lib/i386-linux-gnu/libXcursor.so.1.0.2 b5476000-b5477000 r--p 8000 08:01 153205 /usr/lib/i386-linux-gnu/libXcursor.so.1.0.2 b5477000-b5478000 rw-p 9000 08:01 153205 /usr/lib/i386-linux-gnu/libXcursor.so.1.0.2 b54aa000-b56aa000 r--p 08:01 132687 /usr/lib/locale/locale-archive b56aa000-b56ab000 ---p 00:00 0 b56ab000-b69da000 rw-p 00:00 0 b69da000-b69e5000 r-xp 08:01 1318150 /lib/i386-linux-gnu/libnss_files-2.17.so b69e5000-b69e6000 r--p a000 08:01 1318150 /lib/i386-linux-gnu/libnss_files-2.17.so b69e6000-b69e7000 rw-p b000 08:01 1318150 /lib/i386-linux-gnu/libnss_files-2.17.so b69e7000-b69f1000 r-xp 08:01 1318156 /lib/i386-linux-gnu/libnss_nis-2.17.so b69f1000-b69f2000 r--p 9000 08:01 1318156 /lib/i386-linux-gnu/libnss_nis
[Bug 959151] Re: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Just wanted to post that this bug seems to still exist under Ubuntu 12.04 LTS and 12.10 with KDE 9.10.0 installed and all upgrades to current backports, is this really a bug or maybe there just needs to be a way to turn off these warnings? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/959151 Title: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/959151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 959151] Re: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
-- Footnote to that, maybe place it in the kdebugdialog?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/959151 Title: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/959151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
