[Bug 1618428] Re: asp.net templates are not visible or can't be installed in monodevelop in Ubuntu 16.04
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 debugging of asp.net applications. But again, as I mentioned - the patch is probably there for a reason, and I cannot safely claim that its removal does not have any negative side effects elsewhere in the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618428 Title: asp.net templates are not visible or can't be installed in monodevelop in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/1618428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618428] Re: asp.net templates are not visible or can't be installed in monodevelop in Ubuntu 16.04
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. https://bugs.launchpad.net/bugs/1618428 Title: asp.net templates are not visible or can't be installed in monodevelop in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/1618428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618428] Re: asp.net templates are not visible or can't be installed in monodevelop in Ubuntu 16.04
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. https://bugs.launchpad.net/bugs/1618428 Title: asp.net templates are not visible or can't be installed in monodevelop in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/1618428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618428] Re: asp.net templates are not visible or can't be installed in monodevelop in Ubuntu 16.04
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 would heavily recommend that the importance of this regression be increased. I would also like to assist in its solution, but whereas I know more that a little bit about building and maintaing debian packages, the complexity of the monodevelop package is a quite daunting ... I can add that even though we only use LTS versions of Ubuntu for production we do try out the non-LTS versions - and this regression is between 15.10 Wily and 16.04 Xenial - monodevelop worked just fine with asp.net in Wily. The problem is dead simple to reproduce, just take a Trusty or Wily monodevelop, create a new Web application solution+project - the one with a single button - build and run. Works fine, then move it to a Xenial monodevelop, fails. You can get a whole load of useful information by simply googl'ing the error message string "error: The ASP.NET add-in is not installed.". Many different people, including some at Xamarin has observed the problem and commented on it. Essentially, the consensus seems to be that the Debian/Ubuntu release of monodevelop 5.10.0.871-2 are missing some elements. One widely recommended solution seems to be to download the "debianized" version of monodevelop 5.10.0.871 from http://download.mono-project.com - its version is 5.10.0.871-0xamarin2. Installing that certainly solved the immediate problem for me - but I really prefer to work with a single, supposedly consistent, distribution. Problem is that the -0xamarin2 is not that well integrated with Ubuntu Xenial - it seems more to be a kind of "generic relatively modern Debian/Ubuntu packaging". For a starter, the sources to the -0xamarin2 simply fails build on a vanilla Ubuntu Xenial. Second, there are problems with the nunit integration. I have spent some time studying the difference between the Ubuntu (-2) and the Xamarin (-0xamarian2) sources. Fortunately, both are using the same .orig.tar (which they should, of course, but it is nice to experience that packagers actually follow the conventions!). Well, the differences are pretty big - a unified diff is about 3000 lines, and that is excluding the "Only in monodevelop-this-and-that" diffs. One major difference is that the ubuntu version seems to consistently go for targetframework 4.5 in the .csproj files, whereas the xamarin version uses many different framework versions. I speculate that in pushing the Ubuntu packaging to pure 4.5, it may have been necessary to cut a few corners, and one of those be ASP.NET. Certainly one difference between the two packagings is in the file .pc/applied_patches where the Ubuntu has a new patch called "dont_bundle_aspnet_assemblies.patch" ... One of the things I intend to try out is of course to remove this patch and try a rebuild - I don't hold that much hope, however, the patch is probably there for a reason. I (and my company) really need this problem solved eventually. It is no big hurry - it is not that Ubuntu Trusty has stopped working :-) - but sooner or later, this regression will be a problem. I would like to assist, within my limited competence - certainly I will continue to report here if I figure out something of relevance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618428 Title: asp.net templates are not visible or can't be installed in monodevelop in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/1618428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364831] Re: monodevelop on trusty fails with TypeLoadException.
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 I claimed in the original posting that the systems were vanilla, this was not entirely correct - a collegue of mine had built and installed a copy of the mono system in /usr/local for some experimenting. So the system hosted two slightly different versions of the mono runtime. Removing the system from /usr/local solved the problem. Or rather, stopped it from occurring. Monodevelop is trying to be smart - it looks all over the system for dlls and loads everything. It might be a more robust architecture if monodevelop sticks to the standard mono installation per default, and then allows configuration of alternative location of the runtime system that the user might wish to use. But I realize that this is not a high-priority request - it is a pretty rare situation that a single installation holds more than one mono runtime system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364831 Title: monodevelop on trusty fails with TypeLoadException. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/1364831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364808] [NEW] monodevelop on trusty has problems with breakpoints - breaks with green arrows when calling method
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 salamander. In the earlier monodevelop, when I set a breakpoint and let monodevelop run the program, monodevelop would stop the program at the breakpoint, placing a yellow arrow in the margin and painting the relevant line yellow. In the current monodevelop, when I set a breakpoint and let monodevelop run the program, monodevelop will stop the program at the /invocation point/ of the method in which the breakpoint is set, placing a green arrow in the margin and painting the invocation line green. Multiple hits of key F5 (continue with debugging) makes the program continue, but it skips the actual breakpoint. Needless to say, this makes the monodevelop more or less useless as a development/debugging tool. Now, it is definitely possible that I have failed to read some release/update notice telling me that this is really a fine new feature that I just have to learn how to configure. But I have spent a lot of time looking for such notices with no success - all googl'ing after issues about monodevelop, breakpoints and green arrows have just given me information about different issues. ** Affects: monodevelop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364808 Title: monodevelop on trusty has problems with breakpoints - breaks with green arrows when calling method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/1364808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364831] [NEW] monodevelop on trusty fails with TypeLoadException.
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 running Kubuntu 14.04 (the KDE version of Ubuntu). On that system I do not have the problem. Unhandled Exception: System.TypeLoadException: A type load exception has occurred. at MonoDevelop.Startup.MonoDevelopMain.Main (System.String[] args) [0x0] in filename unknown:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeLoadException: A type load exception has occurred. at MonoDevelop.Startup.MonoDevelopMain.Main (System.String[] args) [0x0] in filename unknown:0 The problem is probably a trivial missing install dependency. But I cannot figure out what it it that I am missing. ** Affects: monodevelop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364831 Title: monodevelop on trusty fails with TypeLoadException. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/1364831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293481] Re: asp.net 4.0 with apache does not seem to work on trusty
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 Ubuntu distros) but as the problem belongs to a different source package (mod_mono), we should not discuss them here. I may write a report on that problem myself one day. I attach a patch - almost an overkill - but maybe that will prompt someone to verify the problem and solution and actually work the fix into the distribution. ** Attachment added: xsp_patch https://bugs.launchpad.net/ubuntu/+source/xsp/+bug/1293481/+attachment/4112221/+files/xsp_patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293481 Title: asp.net 4.0 with apache does not seem to work on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xsp/+bug/1293481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297148] [NEW] wish: Extend the start-stop-daemon program with --killpg option
Public bug reported: I have a daemon that is not able to intercept a killing signal and do the necessary clean up, by killing its own child processes. Rather than coding a pretty complicated solution to that problem, I found it much easier to modify the start-stop-daemon program with a new 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. Nørgaard The patch is made against trusty tahr beta 1 dpkg, version 1.17.5ubuntu5 ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: killpg start-stop-daemon ** Patch added: Patch to add --killpg option to start-stop-daemon program https://bugs.launchpad.net/bugs/1297148/+attachment/4042260/+files/stop-start.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297148 Title: wish: Extend the start-stop-daemon program with --killpg option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1297148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293481] Re: asp.net 4.0 with apache does not seem to work on trusty
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 System.Web.Hosting.ApplicationHost.CreateApplicationHost, to be precise, in line 150. Test output determines that the program reaches the point of this call, but the call never returns. Now, CreateApplicationHost is part of mono, not of xsp. So I went and added an exception throw to CreateApplicationHost, as the very first thing to do, compiled and installed the modified System.Web.dll and tried again. No change, the mod-mono-server4 still crashes the same way. On the other hand, if I earlier ran the application through xsp4, it has always gone fine - until I made this change - now it crashes, but with my exception. This was just to ensure that I hadn't bungled up the modification of System.Web.dll. So to my thinking the real problem is actually in calling a method in a standard Mono .NET module. Could it be related to the fact that CreateApplicationHost is compiled as UnManagedCode? or some of the security issues around CreateApplicationHost? It is hard to imagine, and even harder to imagine why it works fine in xsp4 but crashes so spectacularly in mod-mono-server4. After all, much of the code (including the calling method, VPathToHost.CreateHost) is shared between the two solutions. best regards --peder chr. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293481 Title: asp.net 4.0 with apache does not seem to work on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xsp/+bug/1293481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293481] [NEW] asp.net 4.0 with apache does not seem to work on trusty
Public bug reported: This is a sister-bug to #1292567 which reports a similar problem with asp.net 2.0. I have created two different reports, because the faults manifests themselves very differently, depending on the asp.net version. I have created an extremely small ASP.NET application (attached as a tar file). When I run that against the apache server on saucy salamander, using mono-server4, it runs just fine. When I run it against the apache server on the current beta of trusty tahr, using mono-server4, the mono-server4 dies with a SIGABRT. The client gets a 500 error and the mono process running /usr/lib/mono/4.5 /mod-mono-server4.exe disappears from the system. Luckily there is a good description in the apache error log: Stacktrace: at unknown 0x at Mono.WebServer.VPathToHost.CreateHost (Mono.WebServer.ApplicationServer,Mono.WebServer.WebSource) 0x0007b at Mono.WebServer.ApplicationServer.GetApplicationForPath (string,int,string,bool) 0x0013f at (wrapper remoting-invoke-with-check) Mono.WebServer.ApplicationServer.GetApplicationForPath (string,int,string,bool) 0x at Mono.WebServer.ModMonoWorker.InnerRun (object) 0x0024f at Mono.WebServer.ModMonoWorker.Run (object) 0x0001b at (wrapper runtime-invoke) Module.runtime_invoke_void__this___object (object,intptr,intptr,intptr) 0x Native stacktrace: /usr/bin/mono() [0x8105b4a] [0xb77bb40c] [0xb77bb424] /lib/i386-linux-gnu/libc.so.6(gsignal+0x46) [0xb75ba7e6] /lib/i386-linux-gnu/libc.so.6(abort+0x143) [0xb75bdc33] /usr/bin/mono() [0x8288b23] /usr/bin/mono() [0x8288bb3] /usr/bin/mono() [0x816b4d1] /usr/bin/mono(mono_class_get_full+0xff) [0x816bdff] /usr/bin/mono(mono_class_from_name+0x107) [0x816c237] /usr/bin/mono(mono_class_from_typeref+0x190) [0x816b9a0] /usr/bin/mono(mono_class_get_full+0x164) [0x816be64] /usr/bin/mono(mono_class_get+0x1f) [0x816bf4f] /usr/bin/mono(mono_metadata_parse_mh_full+0x45c) [0x81b29fc] /usr/bin/mono(mono_method_get_header+0xbf) [0x819130f] /usr/bin/mono() [0x807ff7c] /usr/bin/mono() [0x8066ccc] /usr/bin/mono() [0x8068de4] /usr/bin/mono() [0x8069aee] /usr/bin/mono() [0x8106d17] [0xb757903e] [0xb5816970] [0xb58167fc] [0xb5812aa8] [0xb58126c4] [0xb7466c9d] /usr/bin/mono() [0x8069bf0] Debug info from gdb: = Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. = So, as you see, the SIGABRT occurs in a basic mono runtime routine called from the mod-mono-server4.exe module. Of course, I cannot know whether the bug that causes the abortion is in xsp or in basic mono. But any search after the bug would start in mod-mono-server4, so I chose to file the bug against that package. I have the same bug on my company's larger ASP.NET application. This report is not made from the trusty installation, that one is a test installation without access to the net, so you don't get all the stuff that apport would collect to you. Honestly, you don't need it to reproduce, just grab a pristine trusty installation and try it! However, a few important package versions: libapache2-mod-mono: 2.11+git20130708.6b73e85-4ubuntu1 mono-complete: 3.2.8+dfsg-4ubuntu1 mono-apache-server2: 3.0.11-1 I am willing to offer 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. 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293481 Title: asp.net 4.0 with apache does not seem to work on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xsp/+bug/1293481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292567] Re: asp.net with apache does not seem to work on trusty
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 -- 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: https://bugs.launchpad.net/ubuntu/+source/xsp/+bug/1292567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292567] [NEW] asp.net with apache does not seem to work on trusty
Public bug reported: I have filed this bug against asp.net-examples, but I don't really think, that this specific package is in error - it is just a good example of a generic error that has stopped me cold in testing my company's ASP.NET application on the Beta 1 of trusty tahr. Of course I cannot upload our entire application in a bug report, so I was kind of relieved to observe, that the problem could be reproduced by means of asp.net-examples. When I install asp.net-examples on saucy salamander, it presents a nice, simple web page demonstrating certain ASP.NET mechanisms. When I do the same thing on a pristine installation of trusty tahr, I get this exception: System.Web.Compilation.CompilationException : Unhandled Exception: Description: Error compiling a resource required to service this request. Review your source file and modify it to fix this error. Details: : Unhandled Exception: Error origin: Compiler Error source file: Exception stack trace: at System.Web.Compilation.AssemblyBuilder.BuildAssembly (System.Web.VirtualPath virtualPath, System.CodeDom.Compiler.CompilerParameters options) [0x0] in filename unknown:0 at System.Web.Compilation.AssemblyBuilder.BuildAssembly (System.CodeDom.Compiler.CompilerParameters options) [0x0] in filename unknown:0 at System.Web.Compilation.AppCodeAssembly.Build (System.String[] binAssemblies) [0x0] in filename unknown:0 at System.Web.Compilation.AppCodeCompiler.Compile () [0x0] in filename unknown:0 at System.Web.HttpApplicationFactory.InitType (System.Web.HttpContext context) [0x0] in filename unknown:0 I have the same bug on my company's larger ASP.NET application, and I have reproduced the bug both on a server version of trusty, and a kubuntu trusty desktop - exactly the same performance. It is pretty obvious to me that the bug is not in asp.net-examples; most likely it is related to the fact that the basic mono distribution takes a great version hop between saucy and trusty - from 2.10.8.1 to 3.2.8. Some feature is simply not working! To be absolutely certain I rebuilt a fresh version of the xsp source package (source package for asp.net- examples) and installed that instead of the official trusty version - made no difference, the bug is still there. The asp.net-examples package is using mono-apache-server2, by ways of its post-installation script. I have of course also tried mono-apache- server4, but that fails in an entirely different way that will be reported in a separate launchpad bug. This report is not made from the trusty installation, that one is a test installation without access to the net, so you don't get all the stuff that apport would collect to you. Honestly, you don't need it to reproduce, just grab a pristine trusty installation and try it! However, a few important package versions: libapache2-mod-mono: 2.11+git20130708.6b73e85-4ubuntu1 mono-complete: 3.2.8+dfsg-4ubuntu1 mono-apache-server2: 3.0.11-1 I am willing to offer 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. Nørgaard ** Affects: xsp (Ubuntu) Importance: Undecided Status: New ** Tags: asp.net mono trusty -- 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: https://bugs.launchpad.net/ubuntu/+source/xsp/+bug/1292567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292567] Re: asp.net with apache does not seem to work on trusty
** 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: https://bugs.launchpad.net/ubuntu/+source/xsp/+bug/1292567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1243266] Re: okular has stopped reacting to click on hyperlinks
Sorry for the slow response. When I observed the problem, I must assume that I was in Browse mode - that is the default mode, right? But I no longer have the problem - what I observed back in October 2013 does not reproduce today - today I /can/ use the link in the PDF file. Well, 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-8230 Åbyhøj tel: +45 87 44 11 99 Denmark mob: +45 30 91 84 31 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/1243266 Title: okular has stopped reacting to click on hyperlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1243266/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1243860] [NEW] KDE battery monitor shows empty battery (wrongly) when connected to power source
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 its stuff from, but if someone will tell me, I will assist in figuring out what the problem is - whether it is a KDE problem, or a change in kernel to which KDE has not adapted. The problem is in the nuisance class, not a serious one. But it does reduce the quality of Kubuntu - visibly so. best regards ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: kde-workspace 4:4.11.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 23 20:07:12 2013 InstallationDate: Installed on 2013-05-20 (155 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: kde-workspace UpgradeStatus: Upgraded to saucy on 2013-10-18 (4 days ago) ** Affects: kde-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243860 Title: KDE battery monitor shows empty battery (wrongly) when connected to power source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1243860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243266] [NEW] okular has stopped reacting to click on hyperlinks
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, produced by lowriter, dumped as PDF and attached. If you display this document with okular 4:4.10.5-0ubuntu0.1 (the one in kubuntu 13.04) you can click on the link and see where I work. If you display this document with okular 4:4.11.2-0ubuntu1 (the one in kubuntu 13.10) you can click to your hearts content and get nothing but a sore index finger. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: okular 4:4.11.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 22 17:18:22 2013 InstallationDate: Installed on 2013-05-20 (154 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: okular UpgradeStatus: Upgraded to saucy on 2013-10-18 (3 days ago) ** Affects: okular (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: testdoc.pdf https://bugs.launchpad.net/bugs/1243266/+attachment/3887526/+files/testdoc.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243266 Title: okular has stopped reacting to click on hyperlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1243266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065096] Re: Certain keyboard shortcuts disappear between 4.9.1 and 4.9.2
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 any certainty that there are no newly introduced faults - but for daily operations we are back to the behaviour in 4.9.1 and earlier. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065096 Title: Certain keyboard shortcuts disappear between 4.9.1 and 4.9.2 To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1065096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065402] [NEW] Wish for packaging a newer version, python3 support
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 task. I do not know myself how to package python packages, but I am very willing to assist in testing, once the basic packaging is done. ** Affects: pyodbc (Ubuntu) Importance: Undecided Status: New ** Tags: python3 quantal wish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065402 Title: Wish for packaging a newer version, python3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyodbc/+bug/1065402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065096] Re: Certain keyboard shortcuts disappear between 4.9.1 and 4.9.2
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 there; evidently I don't know enough about the KDE architecture to succeed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065096 Title: Certain keyboard shortcuts disappear between 4.9.1 and 4.9.2 To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1065096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064883] [NEW] Reproducable crash in apport-bug in Quantal Beta 2+
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 OK, choose Other display-related problem, click OK, and the application crashes. (There is a peculiarity here: I choose Other problem, but this gives me the window for Display ) The KDE crash handler attempts to build a report but gives up - This crash information is not useful enough, do you want to try to improve it? You will need to install some debugging packages. It says this, even after I did install the suggested debugging packages. It finishes with a suggestion that I send the report manually - which suggestion I am following now. I have attached the partial report built by the crash handler. I notice that it does not contain any information about installed packages, so I have collected a list of what I suppose is relevant. Essentially, it is Kubuntu Quantal Beta 2 as it looks today, October 9th. apport 2.6.1-0ubuntu1 apport-symptoms 0.19 python3.2 3.2.3-6ubuntu3 python3-pyqt4 4.9.3-4 libqtcore4:amd644:4.8.3+dfsg-0ubuntu3 libkdecore5 4:4.9.2-0ubuntu3 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: beta2 quantal ** Attachment added: python3-20121009-094109.kcrash https://bugs.launchpad.net/bugs/1064883/+attachment/3391915/+files/python3-20121009-094109.kcrash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064883 Title: Reproducable crash in apport-bug in Quantal Beta 2+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1064883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065096] [NEW] Certain keyboard shortcuts disappear between 4.9.1 and 4.9.2
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 a bit of a keyboard shortcut fanatic, hating to use the mouse for standard operations). For instance, when I wish to logout, I have always been able to do it with Alt-F1, left, left, left, left, down, enter. In the 4.9.2 the last 'enter' has no effect, I have to grab the mouse and click on the Logout menu entry. Likewise, when I wish to launch a program, the name of which I know, I am used to do Alt-F1, some initial characters for the name until the program is shown in menu, one or more downs (to get to the program, enter. In 4.9.2, the initial character trick works, but I cannot use the 'down' button. Now, I am not a KDE developer, but I did run a diff between the two original sources from www.kde.org. And, true enough, there has been some changes in the source to the kickoff launcher, and those changes seem to relate to the interpretation of keyboard press events. Look in the file plasma/desktop/applets/kickoff/ui/launcher.cpp. So I think this is really an upstream problem. But if 4.9.2, as it looks now, is included in the final release of Kubuntu Quantal, it will also be a Kubuntu problem. ** Affects: kde-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: beta kde kickoff quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065096 Title: Certain keyboard shortcuts disappear between 4.9.1 and 4.9.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1065096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048430] Re: dnsmasq not available on the bus
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 server IP addresses. But now: it works. Either I did something wrong earlier, or some update (running Beta, I run dist-upgrade daily) has fixed whatever the problem were. Whatever has happened, I hereby withdraw any claim that this is really a bug in Kubuntu 12:10 Beta. (BTW, I am not allowed to set the attributes that you recommend - I get a mysterious error: lsattr: Operation not supported While reading flags on /etc/resolv.conf. Preventing modification of /etc/resolv.conf would not be the solution anyway.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048430 Title: dnsmasq not available on the bus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1048430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048430] Re: dnsmasq not available on the bus
/resolvconf Sep 21 07:57:16 pcn-Latitude-E6520 dnsmasq[1595]: setting upstream servers from DBus Sep 21 07:57:16 pcn-Latitude-E6520 dnsmasq[1595]: using nameserver 192.168.253.251#53 Sep 21 07:57:16 pcn-Latitude-E6520 dnsmasq[1595]: using nameserver 192.168.253.250#53 As you can see, it is a kind of timing issue: At a certain point in time the network-manager needs the dnsmasq on the bus but cannot find it, therefore it fails to complete the configuration; a little later (actually within the same second) it discovers that the dnsmasq pops up. And now to your questions: The dnsmasq package is not installed, but the dnsmasq-base is, version 2.63-1ubuntu1. The only dnsmasq-releated configuration file present is /etc/dnsmasq.d /network-manager, with the content # Tell any system-wide dnsmasq instance to make sure to bind to interfaces # instead of listening on 0.0.0.0 # WARNING: changes to this file will get lost if network-manager is removed. bind-interfaces The /etc/resolv.conf file is not updated at all, so the content is probably not of any relevance - it is whatever it was the last time I edited it. Right now it is: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.253.251 nameserver 192.168.253.250 search intern.it-huset.dk - the two servers mentioned are nameservers on our house internal network. In normal operation (before I upgraded to 12:10 Beta 1) it says nameserver 127.0.0.1. In /run/resolvconf/interface I find one file, 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048430 Title: dnsmasq not available on the bus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1048430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048430] Re: dnsmasq not available on the bus
This is a me too comment - I ran into exactly the same problem when I upgraded my Kubuntu 12:04 system to 12:10 Beta 1 last on Monday Sept 17th. And the problem is still there, today on Sept 20th - I mention this because the Beta 1 system is a fast-moving target, many new updates every day. There is a simple work-around for the problem, pull the DNS server out of /var/log/syslog (grep for 'using nameserver' ), and edit it manually into /etc/resolv.conf. But then you have to do that again every time you move your computer. I tried to run an apport-collect, but obviously only the original 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 - Software that transforms the business of Energy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1048430 Title: dnsmasq not available on the bus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1048430/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1048430] Re: dnsmasq not available on the bus
This is a me too comment - I ran into exactly the same problem when I upgraded my Kubuntu 12:04 system to 12:10 Beta 1 last on Monday Sept 17th. And the problem is still there, today on Sept 20th - I mention this because the Beta 1 system is a fast-moving target, many new updates every day. There is a simple work-around for the problem, pull the DNS server out of /var/log/syslog (grep for 'using nameserver' ), and edit it manually into /etc/resolv.conf. But then you have to do that again every time you move your computer. I tried to run an apport-collect, but obviously only the original 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 - Software that transforms the business of Energy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048430 Title: dnsmasq not available on the bus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1048430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873870] [NEW] Upgrade to Kubuntu 11.10 failed, missing .debs
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 http://dk.archive.ubuntu.com/ubuntu/pool/universe/x/xserver-xorg-video-tseng/xserver-xorg-video-tseng_1.2.4-2_amd64.deb 403 Forbidden Failed to fetch http://dk.archive.ubuntu.com/ubuntu/pool/universe/x/xserver-xorg-video-s3virge/xserver-xorg-video-s3virge_1.10.4-4_amd64.deb 403 Forbidden Failed to fetch http://dk.archive.ubuntu.com/ubuntu/pool/universe/x/xserver-xorg-video-i128/xserver-xorg-video-i128_1.3.4-2_amd64.deb 403 Forbidden Failed to fetch http://dk.archive.ubuntu.com/ubuntu/pool/universe/x/xserver-xorg-video-chips/xserver-xorg-video-chips_1.2.4-1_amd64.deb 403 Forbidden Failed to fetch http://dk.archive.ubuntu.com/ubuntu/pool/universe/x/xserver-xorg-video-ark/xserver-xorg-video-ark_0.7.3-2_amd64.deb 403 Forbidden Failed to fetch http://dk.archive.ubuntu.com/ubuntu/pool/universe/x/xserver-xorg-video-apm/xserver-xorg-video-apm_1.2.3-2_amd64.deb 403 Forbidden Inspection of the site (dk.archive.ubuntu.com) indicates that the files are simply missing, it is probably not a permission problem. Inspection of another site (uk.archive.ubuntu.com) shows that the files are not missing there - so maybe it is a simple synchronization problem. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873870 Title: Upgrade to Kubuntu 11.10 failed, missing .debs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/873870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
