[Bug 1738133] Re: gnatstub fails to generate any Ada code
For the record, I downloaded the tar.gz version from adacore website (http://mirrors.cdn.adacore.com/art/591c6d80c7a447af2deed1d7) and I don not experiment this problem with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738133 Title: gnatstub fails to generate any Ada code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asis/+bug/1738133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738133] Re: gnatstub fails to generate any Ada code
when I contacted Adacore abot this issue, I got the following answer: The way you are using gnatstub is correct, and I can confirm that it works for AdaCore products. But we cannot say anything for the GNAT versions built and distributed outside AdaCore. Somehow the issue seems specific to the binary distributed in the ubuntu package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738133 Title: gnatstub fails to generate any Ada code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asis/+bug/1738133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738133] [NEW] gnatstub fails to generate any Ada code
Public bug reported: I am trying to use gnatstub on my ubuntu 17.10 system. I have installed the asys-programs 2017-2 through the package manager. I am trying to generate the stub function (adb file) from the following file (tiny.ads). package tiny is procedure simple_procedure; function simple_function return boolean; end tiny; When I run gnatstub, I get the following output. $ gnatstub tiny.ads +===ASIS BUG DETECTED==+ | ASIS 2.0.R for GNAT 7.2.0 CONSTRAINT_ERROR a4g-gnat_int.adb:247 range check failed| | when processing A4G.Contt.SD.Read_and_Check_New (tree file /home/jcd/Projects/hypervisor/moth/tiny.adt)| | Please submit a bug report; see http://gcc.gnu.org/bugs.html.| | Use a subject line meaningful to you and us to track the bug.| | Include the entire contents of this bug box and the ASIS debug info | | in the report. | | Include the exact list of the parameters of the ASIS queries | | Asis.Implementation.Initialize and Asis.Ada_Environments.Associate | | from the ASIS application for which the bug is detected | | Also include sources listed below in gnatchop format | | (concatenated together with no headers between files). | | NOTE: ASIS bugs may be submitted to rep...@adacore.com | +==+ Please include these source files with error report Note that list may not be accurate in some cases, so please double check that the problem can still be reproduced with the set of files listed. $ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: asis-programs 2017-2 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 14 06:45:58 2017 InstallationDate: Installed on 2016-04-23 (599 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: asis UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: asis (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738133 Title: gnatstub fails to generate any Ada code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asis/+bug/1738133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385749] Re: package syslinux-themes-debian (not installed) failed to install/upgrade: le paquet syslinux-themes-debian n'est pas prêt pour la configuration configuration impossible (état actuel
forcing the installation of syslinux-themes-debian with apt-get solves the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385749 Title: package syslinux-themes-debian (not installed) failed to install/upgrade: le paquet syslinux-themes-debian n'est pas prêt pour la configuration configuration impossible (état actuel « half- installed ») To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslinux-themes-debian/+bug/1385749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385749] [NEW] package syslinux-themes-debian (not installed) failed to install/upgrade: le paquet syslinux-themes-debian n'est pas prêt pour la configuration configuration impossible (état actu
Public bug reported: first reboot after upgrading from 14.04 (to 14.10) ProblemType: Package DistroRelease: Ubuntu 14.10 Package: syslinux-themes-debian (not installed) ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 AptOrdering: syslinux-themes-debian-wheezy: Install syslinux-themes-debian-wheezy: Configure syslinux-themes-debian: Configure Architecture: amd64 Date: Sat Oct 25 22:50:04 2014 DuplicateSignature: package:syslinux-themes-debian:(not installed):le paquet syslinux-themes-debian n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») ErrorMessage: le paquet syslinux-themes-debian n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») InstallationDate: Installed on 2012-07-06 (840 days ago) InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release amd64 (20120423) SourcePackage: syslinux-themes-debian Title: package syslinux-themes-debian (not installed) failed to install/upgrade: le paquet syslinux-themes-debian n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») UpgradeStatus: Upgraded to utopic on 2014-10-25 (0 days ago) ** Affects: syslinux-themes-debian (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385749 Title: package syslinux-themes-debian (not installed) failed to install/upgrade: le paquet syslinux-themes-debian n'est pas prêt pour la configuration configuration impossible (état actuel « half- installed ») To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslinux-themes-debian/+bug/1385749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 668202] Re: akregator crash after update
Same thing here. After a package upgrade, Kontact stopped working because akregator was crashing. removing the ~/.kde/share/apps/akregator did allow the application to start without crashing. Akregator back trace is as follow (This is akregator 1.6.5 with KDE 4.5.1 on Ubuntu 10.10 running on amd64 platform). This is reported to KDE here (https://bugs.kde.org/show_bug.cgi?id=256621): Application: Akregator (akregator), signal: Segmentation fault [KCrash Handler] #6 memcpy () at ../sysdeps/x86_64/memcpy.S:359 #7 0x7f1138239004 in c4_String::Init (this=0x7fff98bbc810, p=value optimized out, n=160914512) at //usr/include/bits/string3.h:52 #8 0x7f11382307e2 in c4_String (this=0xda3de0, ptr_=0x7fff98bbc8c0, selfDesc_=value optimized out) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4str.inl:209 #9 c4_HandlerSeq::Prepare (this=0xda3de0, ptr_=0x7fff98bbc8c0, selfDesc_=value optimized out) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:305 #10 0x7f1138234000 in c4_Persist::LoadAll (this=0xda3850) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:1026 #11 0x7f1138243375 in Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl (this=0xa781b0, url=value optimized out, main=value optimized out) at ../../../../akregator/plugins/mk4storage/feedstoragemk4impl.cpp:152 #12 0x7f1138245fca in Akregator::Backend::StorageMK4Impl::StorageMK4ImplPrivate::createFeedStorage (this=0x8cba30, url=...) at ../../../../akregator/plugins/mk4storage/storagemk4impl.cpp:77 #13 0x7f113a00735c in Akregator::Feed::loadArticles (this=0xda2790) at ../../../akregator/src/feed.cpp:234 #14 0x7f113a00ac74 in Akregator::Feed::fromOPML (e=value optimized out, storage=value optimized out) at ../../../akregator/src/feed.cpp:174 #15 0x7f113a016cf5 in Akregator::FeedList::parseChildNodes (this=0xbd4a00, node=value optimized out, parent=0xd8db10) at ../../../akregator/src/feedlist.cpp:237 #16 0x7f113a016f46 in Akregator::FeedList::parseChildNodes (this=0xbd4a00, node=value optimized out, parent=0x776db0) at ../../../akregator/src/feedlist.cpp:255 #17 0x7f113a017786 in Akregator::FeedList::readFromOpml (this=0xbd4a00, doc=value optimized out) at ../../../akregator/src/feedlist.cpp:295 #18 0x7f113a053f7b in Akregator::LoadFeedListCommand::Private::handleDocument (this=0xbd91f0, doc=...) at ../../../akregator/src/loadfeedlistcommand.cpp:68 #19 0x7f113a054a03 in Akregator::LoadFeedListCommand::Private::doLoad (this=0xbd91f0) at ../../../akregator/src/loadfeedlistcommand.cpp:173 #20 0x7f113a054dd2 in Akregator::LoadFeedListCommand::qt_metacall (this=0xbd8f60, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff98bbdca0) at ./loadfeedlistcommand.moc:78 #21 0x7f1150d15b27 in QMetaObject::activate (sender=0xbd6960, m=value optimized out, local_signal_index=value optimized out, argv=0xd3e) at kernel/qobject.cpp:3280 #22 0x7f1150d1acff in QSingleShotTimer::timerEvent (this=0xbd6960) at kernel/qtimer.cpp:308 #23 0x7f1150d0f8f9 in QObject::event (this=0xbd6960, e=0xdb6ff8) at kernel/qobject.cpp:1183 #24 0x7f11516b3fdc in QApplicationPrivate::notify_helper (this=0x675e30, receiver=0xbd6960, e=0x7fff98bbe400) at kernel/qapplication.cpp:4396 #25 0x7f11516b9aed in QApplication::notify (this=0x7fff98bbe700, receiver=0xbd6960, e=0x7fff98bbe400) at kernel/qapplication.cpp:4277 #26 0x7f1152406156 in KApplication::notify (this=0x7fff98bbe700, receiver=0xbd6960, event=0x7fff98bbe400) at ../../kdeui/kernel/kapplication.cpp:310 #27 0x7f1150cfdcdc in QCoreApplication::notifyInternal (this=0x7fff98bbe700, receiver=0xbd6960, event=0x7fff98bbe400) at kernel/qcoreapplication.cpp:732 #28 0x7f1150d2d6f2 in sendEvent (this=0x673750) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #29 QTimerInfoList::activateTimers (this=0x673750) at kernel/qeventdispatcher_unix.cpp:602 #30 0x7f1150d2a4a4 in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:184 #31 0x7f1149efe342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #32 0x7f1149f022a8 in ?? () from /lib/libglib-2.0.so.0 #33 0x7f1149f0245c in g_main_context_iteration () from /lib/libglib-2.0.so.0 #34 0x7f1150d2a193 in QEventDispatcherGlib::processEvents (this=0x646e90, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:415 #35 0x7f1151766a4e in QGuiEventDispatcherGlib::processEvents (this=0x7f112cac3054, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #36 0x7f1150cfca02 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #37 0x7f1150cfcdec in QEventLoop::exec (this=0x7fff98bbe6a0, flags=) at kernel/qeventloop.cpp:201 #38 0x7f1150d00ebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #39 0x00408e9d in main (argc=value optimized out,
[Bug 486700] Re: kdeinit4 crashed with SIGSEGV in QFont()
For now I would say no. At least, I haven't found a way yet to reproduce it. -- kdeinit4 crashed with SIGSEGV in QFont() https://bugs.launchpad.net/bugs/486700 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 486700] Re: kdeinit4 crashed with SIGSEGV in QFont()
** Visibility changed to: Public -- kdeinit4 crashed with SIGSEGV in QFont() https://bugs.launchpad.net/bugs/486700 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde4libs in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 188987] Re: *** glibc detected *** pls: double free or corruption (fasttop): 0x0805a2c8 ***
With 8.10 the problem is not there anymore but it is a bit of a pity that it took 2 full releases to fix when the fix was already available at the time the bug was reported (as I pointed out at the time). -- *** glibc detected *** pls: double free or corruption (fasttop): 0x0805a2c8 *** https://bugs.launchpad.net/bugs/188987 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 77702] Re: Memory leak in xfce4-menu-plugin
This is still not fixed. I am running xubuntu 8.10 at the moment and may xfce4-menu-plug is using 232 MB as I write this message. PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 27023 jcd 20 0 428m 232m 8924 S 0.0 24.5 318:48.74 xfce4-menu-plug -- Memory leak in xfce4-menu-plugin https://bugs.launchpad.net/bugs/77702 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 282532] Re: Firefox's buttons don't work (previous/next/refresh/..)
I am also getting this behavior on Ubuntu 8.10. Wiping out the .mozilla directory in my home dir doesn't solve the issue. here is the list of error reported by the error console: Erreur : [Exception... Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService] nsresult: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) location: JS frame :: file:///usr/lib/firefox-3.0.3/components/nsBrowserGlue.js :: bg__initPlaces :: line 465 data: no] Fichier Source : file:///usr/lib/firefox-3.0.3/components/nsBrowserGlue.js Ligne : 465 Erreur : uncaught exception: [Exception... Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService] nsresult: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) location: JS frame :: chrome://browser/content/search/search.xml :: get_searchService :: line 145 data: no] Erreur : uncaught exception: [Exception... Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService] nsresult: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) location: JS frame :: chrome://browser/content/search/search.xml :: initialize :: line 527 data: no] Erreur : uncaught exception: [Exception... Component returned failure code: 0x8007000e (NS_ERROR_OUT_OF_MEMORY) [nsIDocShellHistory.useGlobalHistory] nsresult: 0x8007000e (NS_ERROR_OUT_OF_MEMORY) location: JS frame :: chrome://browser/content/browser.js :: prepareForStartup :: line 763 data: no] I am not sure the out of memory error makes a lot of sense on my system as there seems to be plenty of memory left to allocate. -- Firefox's buttons don't work (previous/next/refresh/..) https://bugs.launchpad.net/bugs/282532 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 297871] [NEW] Kubuntu intrepid live CD behave badly on K7S41 motherboard
Public bug reported: My motherboard (a K7S41) used to run kubuntu hardy without trouble. But when I boot the Kubuntu intrepid live CD on this motherboard the video (based on the build in SIS graphic chip) is not behaving correctly. In particular, the screeen will go black any time I type on the keyboard, I click on the mouse or the mouse focus change. This black screen will last 1 to 3 seconds and then the screen get back to normal. Note that there is no visible crash, no deconnection, no CPU overload ... the system continues to work normaly but any time I try to interact with it it, the screen i getting black for a few secs and then resume to normal until I type to type again. Therefore the system is quite unusable in its actual state. Is there some know compatibility problems between KDE4 and relatively low end graphic cards without 3D support? ** Affects: ubuntu Importance: Undecided Status: New -- Kubuntu intrepid live CD behave badly on K7S41 motherboard https://bugs.launchpad.net/bugs/297871 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 297871] Re: Kubuntu intrepid live CD behave badly on K7S41 motherboard
The KDE4 behavior is the same once it is installed on the disk. On the other hand if I switch to XFCE desktop (still using kwin I guess) then I don't get the black screen behavior anymore and I can even run KDE4 application from there ... ** Description changed: My motherboard (a K7S41) used to run kubuntu hardy without trouble. But when I boot the Kubuntu intrepid live CD on this motherboard the video (based on the build in SIS graphic chip) is not behaving correctly. In particular, the screeen will go black any time I type on the keyboard, I click on the mouse or the mouse focus change. This black screen will last 1 to 3 seconds and then the screen get back to normal. Note that there is no visible crash, no deconnection, no CPU overload ... the system continues to work normaly but any time I try to - interact with it it, the screen i getting black for a few secs and - then resume to normal until I type to type again. + interact with it it, the screen is getting black for a few secs and then + resume to normal until I try to type again. Therefore the system is quite unusable in its actual state. Is there some know compatibility problems between KDE4 and relatively low end graphic cards without 3D support? -- Kubuntu intrepid live CD behave badly on K7S41 motherboard https://bugs.launchpad.net/bugs/297871 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 192411] Re: RNDIS over USB doesn't work because of driver Bug
Well flying_rhino this fix is only one piece of the equation. Now assuming the rest of the user space/daemon is up to date on hardy, your mobile should sync. -- RNDIS over USB doesn't work because of driver Bug https://bugs.launchpad.net/bugs/192411 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 192411] Re: RNDIS over USB doesn't work because of driver Bug
The patch has officialy been merged into Linus 2.6 tree. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=10d0f27c1baa4a094b4965708a15f2b0c4d65f5e Time to backport? JC -- RNDIS over USB doesn't work because of driver Bug https://bugs.launchpad.net/bugs/192411 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 192411] Re: RNDIS over USB doesn't work because of driver Bug
The patch has now been submitted to the netdev mailing list for upstream inclusion (hopefully). http://www.spinics.net/lists/netdev/msg56069.html -- RNDIS over USB doesn't work because of driver Bug https://bugs.launchpad.net/bugs/192411 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 192411] Re: RNDIS over USB doesn't work because of driver Bug
Laurent, Thanks for your comment. I have not tried the rndis-lite driver myself so I can't really comment on it. Now I believe the current RNDIS kernel driver will work for WM5/6 if my patch is applied. The point is that the Ubuntu policy does not seem to be very found of drivers that are not integrated upstream. So far I don't think the rndis-lite driver is candidate for such thing, so it seems easier to fix the current driver to get it accepted/backported to Gusty/Hardy. If you can try your WM6 device with the proposed patch that would be great. -- RNDIS over USB doesn't work because of driver Bug https://bugs.launchpad.net/bugs/192411 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 192411] Re: RNDIS over USB doensn't work because of driver Bug
** Summary changed: - RNDIS over USB doensn't work bacause of driver Bug + RNDIS over USB doensn't work because of driver Bug -- RNDIS over USB doensn't work because of driver Bug https://bugs.launchpad.net/bugs/192411 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192411] Re: RNDIS over USB doesn't work because of driver Bug
** Summary changed: - RNDIS over USB doensn't work because of driver Bug + RNDIS over USB doesn't work because of driver Bug -- RNDIS over USB doesn't work because of driver Bug https://bugs.launchpad.net/bugs/192411 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138583] Re: [Gutsy] Kernel Oops after calling synce-serial-start
So Leann, I guess this report should be split in 2 independent bugs (as I should have done from the beginning). One (the original) with the kernel OOPS problem should be nominated for Gusty release following the SRU policy by applying http://bugzilla.kernel.org/attachment.cgi?id=12918action=view to the 2.6.22 kernel And I will create another bug for the RNDIS problem that will be nominated for both Gusty and Hardy release once the patch http://www .mail-archive.com/linux-usb%40vger.kernel.org/msg01608.html is accepted in the Linux kernel tree. Does it sound right? -- [Gutsy] Kernel Oops after calling synce-serial-start https://bugs.launchpad.net/bugs/138583 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192411] [NEW] RNDIS over USB doensn't work bacause of driver Bug
Public bug reported: This bug was first reported as part of bug 138583 and now is moved into its own bug. Basically, when a WM5 smartphone was plugged into its USB cradle, the establishment of the RNDIS session to communicate with the phone would fail because of a driver bug negotiating an improper frame size with the device. the dccm daemon would therefore not detect the phone and no dialog (pls or other) was possible. The synce project proposed a patch that would make things work (http://synce.svn.sourceforge.net/svnroot/synce/trunk/patches/linux-2.6.22 -rndis_host-wm5.patch) but it was considered inadequate by the linux people. As this patch is unofficial and not part of any distribution, it would therefore require the user to recompile its kernel which is not really friendly for the average desktop user. I submitted a first proposal to fix the problem in a more appropriate way (http://bugzilla.kernel.org/show_bug.cgi?id=8094#c37) but it was considered too much intrusive. I then submitted a second proposal (http://www.mail-archive.com/linux- usb%40vger.kernel.org/msg01608.html) that should be integrated in the Linux kernel tree very soon (I hope). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- RNDIS over USB doensn't work bacause of driver Bug https://bugs.launchpad.net/bugs/192411 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138583] Re: [Gutsy] Kernel Oops after calling synce-serial-start
I created bug 192411 for the RNDIS part. I will therefore nominate this bug for release with the appropriate required information. 1) A statement explaining the impact: with the Gusty 2.6.22 kernel 2 ttyUSB serial lines are created when you plug in the smartphone into the USB. Unfortunately the first of these 2 lines (ttyUSB0) is inadequate to be used with some programs like synce-serial-config/synce-serial-start. If it was used anyway, it would trigger the OOPS reported above. OOPS are never good and should be fixed if possible. 2) An explanation of how the bug has been addressed: This bug has been fixed in the current kernel tree by applying the following patch (http://bugzilla.kernel.org/attachment.cgi?id=12918action=view). this patch is not applied to kernel 2.6.22 (and therefore to Gusty). Basically this patch is making sure that any ttyUSB line has a buk in and a buk out endpoint. As a result the interrupt in interface doesn't qualify anymore and there is only one ttyUSB created when the martphone is connected. 3) A patch applicable to the stable version of the package: the patch referenced above (http://bugzilla.kernel.org/attachment.cgi?id=12918action=view) should apply cleanly. 4) Detailed instructions how to reproduce the bug: # synce-serial-config ttyUSB0 # synce-serial-start Then: # dmesg -- [Gutsy] Kernel Oops after calling synce-serial-start https://bugs.launchpad.net/bugs/138583 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
