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.
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
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;
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
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
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
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
** 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
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 ***
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
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)
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
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
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
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
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
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
** 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,
** 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,
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
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
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
22 matches
Mail list logo
