I am happy to see that the importance of this bug has been upgraded.
I have tested what I wrote about earlier - the removal of the patch
.pc/applied_patches/dont_bundle_aspnet_assemblies.patch. It seems
to solve the problem - the monodevelop .deb I built from the modified
source actually allows
Oh, by the way, the bug seems to be a duplicate of two other bugs,
1563090 and 1573918. All counted together, it does affect a
considerable number of persons.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oh, by the way, the bug seems to be a duplicate of two other bugs,
1563090 and 1573918. All counted together, it does affect a
considerable number of persons.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is a "me, too" comment. With a few more pointers and opinions.
The problem is a not-so-minor regression for the Ubuntu Xenial
distribution - it is very close to be a showstopper for my company for
upgrading from Trusty to Xenial. Monodevelop simply doesn't work with
asp.net in Xenial. I
I figured out the reason that monodevelop failed to start on two of our
trusty systems.
What I did was to start monodevelop under strace, trying to figure out
what kind of load caused the exeception. Instead I found that
monodevelop picked up dlls that I did not know was on the system.
So when
Public bug reported:
I am using Kubuntu 14.04 trusty tahr.
The monodevelop version is the current 14.04 one, 4.0.12+dfsg-2. I use
monodevelop for
development/debugging of C# programs using the mono packages.
The problem I describe here started when I upgraded from Kubuntu 13.10
saucy
Public bug reported:
This is a vanilla Ubuntu 14.04 trusty tahr.
monodevelop is the current 14.04 one, 4.0.12+dfsg-2.
I have observed the problem on both a server and a Unity desktop, both
vanilla installations.
What makes the problem really peculiar is that I have a third system, a desktop
Zachary, shahid, thanks for your help.
The bug is truly easy to fix in the distribution: Just change line 83
in the source file debian/mono-server4-update to use 4.5 instead of 4.0.
So now
Zachary, the problem you mention with the module installs - I have had
them, too (and also in ealier
option, --killpg. I attach the patch, it is tested and in operation now
and works just fine. I hope that you will consider making this a part
of future releases; it is a small change that does a really useful
thing; I thought that other people than myself could profit from it.
best regards
Peder Chr
I have some additional information on this bug - not anything like a
solution, but an idea about the direction in which to search.
As was clear from the original posting, the crash occurs in
Mono.WebServer.VPathToHost.CreateHost. I have now narrowed it down to
the call of
.
best regards
Peder Chr. Nørgaard
** Affects: xsp (Ubuntu)
Importance: Undecided
Status: New
** Tags: asp.net mono trusty xsp
** Attachment added: tar file with a very small ASP.NET application
https://bugs.launchpad.net/bugs/1293481/+attachment/4028108/+files/sample.tar
I have now added a bug on how there is a just as critical bug when one
is using ASP.NET 4.0. I have reported two bugs because the behaviour of
the two bugs is quite different. The other bug is here:
https://bugs.launchpad.net/ubuntu/+source/xsp/+bug/1293481
best regards
Peder Chr. Nørgaard
any possible kind of assistance in fixing this
problem - my company had looked forward to upgrade to trusty. But,
to be honest, I don't think you really need my help - the problem is so
trivial to reproduce, it ought to be pretty trivial to fix if you know
the ropes.
best regards
Peder Chr
** Tags added: xsp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292567
Title:
asp.net with apache does not seem to work on trusty
To manage notifications about this bug go to:
, it is not the same okular version, either - it has moved from
4.11.2 to 4.11.3. So I guess we've better close the bug.
On Tuesday, January 07, 2014 20:56:42 you wrote:
Are you in Browse mode (as opposed to Zoom or Selection)?
best regards
--
Peder Chr. Nørgaard e-mail: p...@pogt.dk
Gefionsvej 19
DK
Public bug reported:
Upgrading my kubuntu from 13.04 to 13.10, I noticed that my battery
monitor told me, that the battery is empty. It isn't - when I
disconnected the power source, it told me something like 98 % - well,
now it is 91 %.
Regrettably, I don't know where the battery monitor get
Public bug reported:
When I upgrade from kubuntu 13.04 (completely up-to-date) to kubuntu
13.10, first thing I notice is that okular is no longer reacting to
clicks on hyperlinks. I discovered the problem on a confidential
document, but I have reproduced it on a very small test document,
I can confirm, that the patch mentioned in #33 can be applied directly
to the source for kde-workspace in Kubuntu (4:4.9.2-0ubuntu2), the
packages can be compiled and installed, and in the resulting system this
regression seem to be gone.
This is just a user-level observation - I cannot say with
Public bug reported:
The Technical Overview for Quantal claims a desire to switch to pure
Python 3. For this I would need the pyodbc package to be supported
under Python 3. The original package has versions that claims Python 3
support, so I would assume that this is a rather simple packaging
Yes, that is exactly this bug. Nice to see that someone are working on
the problem. If we are lucky, they may have some code out that can go
in the final Quantal release.
Actually, I did search bugs.kde.org before posting this report to
launchpad, and tried to find something about the problem
Public bug reported:
I try to run apport-bug on Kubuntu Quantal Beta 2 Plus; I call it
Plus because it is fully apt-get dist-upgraded, and that includes
update of both the entire KDE suite and python.
The apport-bug program crashes consistently. It opens a window, I
choose Other problem, click
Public bug reported:
I am running Quantal Beta 2 with full apt-get dist-upgrade. Doing that
I noticed a change in KDE behaviour between the original Beta 2 release
(4:4.9.1-0ubuntu1) and the current version (4:4.9.2-0ubuntu2).
The change is related to mouse-less use of the kickoff launcher (I am
Thank you for your response.
Fortunately (or regrettably, depending on your point of view), the bug
has disappeared on me. Earlier, when I restored the link from
/etc/resolv.conf to /run/resolvconf/resolv.conf, no DNS worked, even
though the syslog file showed that dnsmasq had received correct
, NetworkManager with the
content
domain intern.it-huset.dk
search intern.it-huset.dk
nameserver 127.0.1.1
And finally, no, no other nameserver installed, specifically not bind.
Best regards
Peder Chr. Nørgaard, M.Sc.
Senior SW Developer
www.actua.dk - Software that transforms the business of Energy
submitter of the report is allowed to do that.
I think the problem may be the one that is discussed on the network-
manager mailing list - see https://mail.gnome.org/archives
/networkmanager-list/2012-August/msg00094.html
Best regards
Peder Chr. Nørgaard, M.Sc.
Senior SW Developer
www.actua.dk
submitter of the report is allowed to do that.
I think the problem may be the one that is discussed on the network-
manager mailing list - see https://mail.gnome.org/archives
/networkmanager-list/2012-August/msg00094.html
Best regards
Peder Chr. Nørgaard, M.Sc.
Senior SW Developer
www.actua.dk
Public bug reported:
Attempting to upgrade my Kubuntu from 11.04 to 11.10 stopped with the
following message:
Failed to fetch
http://dk.archive.ubuntu.com/ubuntu/pool/universe/x/xserver-xorg-video-voodoo/xserver-xorg-video-voodoo_1.2.4-2_amd64.deb
403 Forbidden
Failed to fetch
27 matches
Mail list logo
