[Bug 382938] Re: ufw should be enabled by default
Sorry to bring up a 4 month old topic, but I wouldn't want to see ufw enabled by default without a proper discussion. I've previously managed servers (both real and virtual) remotely and if installing ufw meant that the firewall suddenly went up, I might lose my remote connection to the servers. For me, that would be a disaster... And, I'm not sure if separating ufw into a desktop version and a server version is worthwhile. Comment #3 from 2010 about having it enabled by default may be one OS' way of taking the marketshare. I'm not convinced it's done for the user's sake. On a Windows machine, I purchased another program to manage my firewall, but I still get reminders about not having the Microsoft firewall brought up. If it was for my protection, then the existence of a firewall by another vendor should remove the Microsoft firewall (and its reminders) completely... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/382938 Title: ufw should be enabled by default To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/382938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793045] [NEW] Missing file for ufw?
Public bug reported: I'm not sure, but I think when I install the syncthing package, the file /etc/ufw/applications.d/syncthing should be included? It is mentioned here: https://docs.syncthing.net/users/firewall.html#uncomplicated- firewall-ufw . The file itself is here: https://github.com/syncthing/syncthing/blob/master/etc/firewall- ufw/syncthing . Doing so enables the "syncthing" and "syncthing-gui" profiles. Of course, it is easy to copy the file myself, but the documentation at the first link seems to imply that it should be part of the package. Perhaps it is incorrect? $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy syncthing syncthing: Installed: 0.14.43+ds1-6 Candidate: 0.14.43+ds1-6 Version table: *** 0.14.43+ds1-6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: syncthing (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/1793045 Title: Missing file for ufw? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syncthing/+bug/1793045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792499] [NEW] Incorrect quoting of titles
Public bug reported:
I think there is a bug in how titles are quoted, but only if certain
options are selected. To reproduce, one can start kbibtex and create a
new file. Then choose "Save" and a window entitled "BibTeX File
Settings" will appear. Here, choose:
* String Delimiters: "..."
* Protect Casing?: Check "Yes" for "Protect Titles"
Then create a new element (i.e., an article) and enter something in the
title. Switch to the source tab and the quoting becomes:
@article{New1,
title = "{Test"}
}
I guess the final two characters of the "title" line should be reversed.
If I save and reopen this file, then it will be read as two entries (I
haven't tried it with this example, but it has happened with my actual
BibTeX file). The second entry starts from where the "} are inverted.
I am fairly sure now that the issue is introduced when the entry is
saved; and not when it is subsequently read in.
I haven't tried yet, but I can avoid this problem if I change the string
delimiter and/or protect casing. But I thought I should report this.
Hopefully someone else sees this bug and it isn't just me...
Details about my system are:
$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
$ apt-cache policy kbibtex
kbibtex:
Installed: 0.8~20170819git31a77b27e8e83836e-3build2
Candidate: 0.8~20170819git31a77b27e8e83836e-3build2
Version table:
*** 0.8~20170819git31a77b27e8e83836e-3build2 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
** Affects: kbibtex (Ubuntu)
Importance: Undecided
Status: New
** Tags: kbibtex
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792499
Title:
Incorrect quoting of titles
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbibtex/+bug/1792499/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
I spoke too soon! The recent 4.13.0-31 kernel appears to have fixed the problem for me, at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742302 Title: Kernel 4.13.0-25 broke nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
For what it's worth, I'm using a GeForce GT 620 and Ubuntu 17.10 and I can't see the KDE login screen. I get a black screen but when I forcefully shut the computer down, I get the KDE logo as if I'm being logged out. I upgraded to the latest NVidia driver from the NVidia web site (384.111 was the most recent one offered to me) and then booting back to 4.13.0-21 works, as others have observed. That is, I'm not using the standard NVidia driver packages. I picked this option since it's easier to boot to a slightly older kernel; going back to an older NVidia driver is a bit harder... I guess there is something between 4.13.0-21 and 4.13.0-25? I'm not doing any GPU work, so I don't know if that is fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742302 Title: Kernel 4.13.0-25 broke nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643483] [NEW] Dependency problem installing Redmine [16.10]
Public bug reported: Hi all, I'm using Ubuntu 16.10 and trying to install the Redmine package (3.2.3-2). I'm getting the following error: The following partially installed packages will be configured: redmine No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Setting up redmine (3.2.3-2) ... Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. dbconfig-common: writing config to /etc/dbconfig-common/redmine/instances/default.conf redmine/instance already exists and has privileges on redmine_default. creating database redmine_default: already exists. dbconfig-common: flushing administrative password Could not find concurrent-ruby-1.0.2 in any of the sources Run `bundle install` to install missing gems. dpkg: error processing package redmine (--configure): subprocess installed post-installation script returned error exit status 7 Errors were encountered while processing: redmine E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up redmine (3.2.3-2) ... Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. dbconfig-common: writing config to /etc/dbconfig-common/redmine/instances/default.conf redmine/instance already exists and has privileges on redmine_default. creating database redmine_default: already exists. dbconfig-common: flushing administrative password Could not find concurrent-ruby-1.0.2 in any of the sources Run `bundle install` to install missing gems. dpkg: error processing package redmine (--configure): subprocess installed post-installation script returned error exit status 7 Errors were encountered while processing: redmine I'm hesitant to use "bundle install" to proceed -- I guess that might cause headaches further down the road. On the other hand, I have the ruby-concurrent package installed (1.0.0-3). Could there be some kind of name conflict? (ruby-concurrent vs. concurrent-ruby) Actually, I had Redmine installed before upgrading to Ubuntu 16.10 from 16.04 . However, because of this error, I purged Redmine and reinstalled it, hoping that "starting from scratch" would solve my problem (my database had been backed up before). It didn't. I guess others have Redmine working with 16.10? Thank you! Ray ** Affects: redmine (Ubuntu) Importance: Undecided Status: New ** Tags: redmine yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643483 Title: Dependency problem installing Redmine [16.10] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redmine/+bug/1643483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1509813] Re: Missing package from Wily (15.10)?
Thanks, Hans! That's great news! As I did get it working before, I can live with it not being in 16.04. But given my level of expertise and the time it took me to get it working, it's good to see it in the next version of Ubuntu since I may not be as "lucky" next time. Thanks a lot for the follow-up! Ray On Sun, Jul 24, 2016 at 7:59 PM, Hans Joachim Desserud <1509...@bugs.launchpad.net> wrote: > The build failure has now been resolved in Debian. :) Based on the > commit log it now works with boost 1.60 and I believe some fixes to work > with a new version of libeigen. Therefore I requested a sync and got > cufflinks into Ubuntu Yakkety, see bug 1605251 for details. > > Since the package has been reintroduced in the current development > version, I've taken the liberty of marking this as closed. > > Unfortunately no new packages will be added to Ubuntu 16.04 after its > official release, but it should be possible to request a backport > https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport. > > ** Changed in: cufflinks (Ubuntu) >Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509813 Title: Missing package from Wily (15.10)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cufflinks/+bug/1509813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573736] Re: package redmine 3.2.1-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 7
A slight variation on what happened to me. I didn't upgrade Redmine, but installed it from scratch on a recently upgraded Ubuntu 16.04 system. I received the above error message just when I was logging in. The funny thing is, Redmine is running fine. Also, aptitude indicates that it has been successfully installed. Of course, given this error message, I'm a bit worried about whether there is a problem with the installation that I haven't noticed yet. But so far, I've encountered no problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573736 Title: package redmine 3.2.1-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redmine/+bug/1573736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1486841] Re: from click import commands: ImportError: cannot import name 'commands'
Colin, Thank you for the suggestion! I generated the strace output as you suggested [see attached file] and looked through it before attaching it. I realized it was looking in my ~/.local/ directory. So, I guessed [I only know some Python...not too knowledgeable about it] renaming ~/.local/lib/python3.4/ might help and indeed it worked and click installed successfully. Of course, I don't know if it will solve other people's problems, but it solved mine. Hopefully the attached strace output can help you come up with a better solution for others? I'm not too sure what I've broken by renaming that directory...I guess as it's local to my home directory, it should be fine. Thank you! ** Attachment added: "strace output for running click" https://bugs.launchpad.net/ubuntu/+source/click/+bug/1486841/+attachment/4524449/+files/click.trace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1486841 Title: from click import commands: ImportError: cannot import name 'commands' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1486841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1486841] Re: from click import commands: ImportError: cannot import name 'commands'
Problem also exists in click (0.4.39.1+15.10.20150702-0ubuntu2) on Ubuntu 15.10 : - $ sudo apt-get install click Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: click 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/14.1 kB of archives. After this operation, 86.0 kB of additional disk space will be used. Selecting previously unselected package click. (Reading database ... 407814 files and directories currently installed.) Preparing to unpack .../click_0.4.39.1+15.10.20150702-0ubuntu2_amd64.deb ... Unpacking click (0.4.39.1+15.10.20150702-0ubuntu2) ... Processing triggers for shared-mime-info (1.3-1) ... Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Processing triggers for man-db (2.7.4-1) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up click (0.4.39.1+15.10.20150702-0ubuntu2) ... Traceback (most recent call last): File "/usr/bin/click", line 31, in from click import commands ImportError: cannot import name 'commands' dpkg: error processing package click (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for ureadahead (0.100.0-19) ... Errors were encountered while processing: click E: Sub-process /usr/bin/dpkg returned an error code (1) $ click Traceback (most recent call last): File "/usr/bin/click", line 31, in from click import commands ImportError: cannot import name 'commands' - Tried on more than one Ubuntu 15.10 system. Works on some; doesn't work on one of them. I guess some combination of packages that I have is causing it. Already tried "apt-get install --reinstall" on python, python3, and python3-click . Even removed everything in /usr/local/lib/python* , thinking they might be conflicting somehow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1486841 Title: from click import commands: ImportError: cannot import name 'commands' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1486841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1509813] Re: Missing package from Wily (15.10)?
Hi Hans, On Mon, Oct 26, 2015 at 4:38 AM, Hans Joachim Desserud <1509...@bugs.launchpad.net> wrote: >>Sorry, but I don't know how to navigate the site very well and didn't > know about "View full publishing history". > > No problem, we've all been there. The link is a bit hidden in the > corner. :P Thanks for your understanding! That page is a bit overwhelming... >>Very much so! I wasn't aware of Ubuntu's policy with new packages > after it's been release. > > To elaborate a bit, once the development cycle starts, packages get > automatically synced from Debian (unless there's some Ubuntu-specific > changes, in which case they need to be manually merged). Then around > halfway through, there's an import freeze and focus on > bugfixes/stabilizing. It is still possibly to request syncs, but towards > the end there's less changes happening. Then once the release is out, > development continues in the next development release, but in certain > cases updates and fixes for severe issues are applied to the packages in > the archive. These are often minimal changes in order to reduce the > potential for introducing new issues. > > For an overview (and more details for each point) you can take a look at > the release schedule for Xenial at > https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule. I see. The cycle makes sense. I guess for those of us not who don't look ahead at upcoming releases, we only find out a program is missing when we finally upgrade when it's finally released. By then, it's a bit too late, isn't it? I guess I should be looking ahead a bit...at least before I upgrade! By the way, I forgot to mention, when I typed "cufflinks", I get this message: $ cufflinks The program 'cufflinks' is currently not installed. You can install it by typing: sudo apt-get install cufflinks That also led me to believe I had somehow upgraded to 15.10 incorrectly [i.e., missing repository, etc.]. Shall I file a bug report with the command-not-found package? >>I will try building it from source myself with Boost 1.59, then. > > Cool. It would be really nice if you could post a comment on how it > goes. Presumably, Ubuntu/Debian will want to package a newer version of > boost at some point and it would be nice to know whether this package > starts working again or whether additional fixes will be required. I was successful. (I couldn't wait -- I do need to use this program.) The upstream instructions (https://github.com/cole-trapnell-lab/cufflinks) are interesting. Under step #1 of "Installing Boost", it clearly says that only 1.55 or lower is supported. Support is suppose to start from 1.59. I guess someone has complained upstream already to have such a message explicitly stated... Also, * I cloned from Git rather than used the tarball, which was from May 2014. There are two dependencies: eigen and samtools. a) I couldn't get it to work with the libeigen3-dev package. So, I downloaded the eigen source and compiled it according to its instructions. b) samtools made a jump [http://sourceforge.net/projects/samtools/files/samtools/] from 0.1.20 to 1.0 last year. I had to go back to the old version in order to ./configure properly. If the new series is backward compatible source-wise, it might just be a problem with the configure script's parsing of version numbers. Unfortunately, I'm not very good at looking at Autoconf scripts to fix it... So, it works and the instructions upstream may be a year old, but seems still relevant. There is some eigen and samtools redundancy with an Ubuntu system. Maybe someone can figure out what to do with the cufflinks source code... Anyway, I guess someone looking for cufflinks might come across this thread. Maybe the above will be of some help! Thanks Hans for all your help! Ray PS: Now to find out if there are any runtime errors... :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509813 Title: Missing package from Wily (15.10)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cufflinks/+bug/1509813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1509813] Re: Missing package from Wily (15.10)?
Dear Hans, Thanks a lot for the follow-up! On Sun, Oct 25, 2015 at 11:05 PM, Hans Joachim Desserud <1509...@bugs.launchpad.net> wrote: > Thanks for reporting this issue. > >>Is there any reason why it was removed for Ubuntu 15.10? > > See "View full publishing history" on the Overview-page, where it states > it was removed from 15.10 because it failed to build from source and > with a reference to https://bugs.debian.org/cgi- > bin/bugreport.cgi?bug=797280. Looks like this package requires boost > 1.55 or 1.59, so I guess it failed to build when they upgraded to boost > 1.58 or one would run into similar issues like you saw when attempting > to use the 15.04 package. Sorry, but I don't know how to navigate the site very well and didn't know about "View full publishing history". I also didn't know what "ftbfs" means until I Googled for the term... :-) Now I know about both -- thanks! >>seems to exist in Xenial > Sort of. If you expand the version number information, it looks like the > package still fails to build. > >>Are there any plans of putting it back in? > > I don't know enough about this package to answer specifically, but in > general new packages are seldom added once an Ubuntu version is > released. It will possibly be in Xenial, assuming someone figures out > how to make it build successfully (or possibly once boost is upgraded to > 1.59). > > I hope this clears some of the confusion. :) Very much so! I wasn't aware of Ubuntu's policy with new packages after it's been release. I will try building it from source myself with Boost 1.59, then. I'm not as smart as others who have tried, but at least I'm not constrained by the Boost version and can have a local copy of Boost 1.59 in a separate directory from the system's 1.58. Thank you for taking the time to explain things to me! Ray -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509813 Title: Missing package from Wily (15.10)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cufflinks/+bug/1509813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509813] [NEW] Missing package from Wily (15.10)?
Public bug reported: Dear all, Looking at: https://launchpad.net/ubuntu/+source/cufflinks I'm somewhat confused. It seems the package "cufflinks" is missing from Wily, but it existed before in Vivid (I was using it) and seems to exist in Xenial. Is there any reason why it was removed for Ubuntu 15.10? Is this a bug/accident? Are there any plans of putting it back in? I tried to install the same package manually from Ubuntu 15.04, but it requires an older version of the Boost libraries... I fear I will break many things if I continue down this path... Thank you! Ray ** Affects: cufflinks (Ubuntu) Importance: Undecided Status: New ** Tags: cufflinks missing package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509813 Title: Missing package from Wily (15.10)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cufflinks/+bug/1509813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1408327] Re: "Could not calculate the upgrade" during "do-release-upgrade -d"
Dear Brian, I don't remember if that is what I did but it does sound like something I would do. So, you are probably right. Thank you for the follow-up and the explanation! Ray On Thursday, January 15, 2015 01:16 AM, Brian Murray wrote: > Its probably because you had multiple desktop meta packages installed, > ubuntu-desktop and ubuntu-gnome-desktop, which the upgrader does not > handle well. > > ** Changed in: ubuntu-release-upgrader (Ubuntu) > Status: New => Invalid > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1408327 Title: "Could not calculate the upgrade" during "do-release-upgrade -d" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1408327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1408327] Re: "Could not calculate the upgrade" during "do-release-upgrade -d"
Hi again, Sorry for the trouble, but I found out the cause of the error message. I didn't realize there were log files to check. Inside /var/log/dist- upgrade/main.log, there is this message: 2015-01-07 23:21:28,887 ERROR Dist-upgrade failed: 'The package 'ubuntu- gnome-desktop' is marked for removal but it is in the removal blacklist.' I uninstalled this package and the upgrade appears to be fine. So, there might be a conflict in terms of the ubuntu-gnome-desktop package? Thank you! Ray -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1408327 Title: "Could not calculate the upgrade" during "do-release-upgrade -d" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1408327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1408327] [NEW] "Could not calculate the upgrade" during "do-release-upgrade -d"
Public bug reported: Hi, I'm trying to upgrade from 14.04.1 LTS to 14.10 and I'm getting this error message: - Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This can be caused by: * Upgrading to a pre-release version of Ubuntu * Running the current pre-release version of Ubuntu * Unofficial software packages not provided by Ubuntu If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. - As there are no further messages, I am unsure what I can do next. I presume there is something special about my installation that differs from everyone else? Thank you! Ray ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.6 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CrashDB: ubuntu Date: Wed Jan 7 22:47:55 2015 InstallationDate: Installed on 2012-10-27 (801 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2015-01-07 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1408327 Title: "Could not calculate the upgrade" during "do-release-upgrade -d" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1408327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172593] Re: [Dual monitor] One monitor very dim after 13.04 upgrade
Dear Christopher, Thank you for the reminder! Unfortunately, I am unable to replicate the test anymore because recently, I've made physical hardware changes to the system. I also went ahead and upgraded to Ubuntu 13.10 soon after it was released. I'm afraid you will need to close this bug unless someone else also experiences this problem. Thank you for bringing it up! Ray -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172593 Title: [Dual monitor] One monitor very dim after 13.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1172593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172593] Re: [Dual monitor] One monitor very dim after 13.04 upgrade
Selected xorg as the relevant package since the dimming of the screen occurs just before the login screen. ** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172593 Title: [Dual monitor] One monitor very dim after 13.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1172593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172593] [NEW] [Dual monitor] One monitor very dim after 13.04 upgrade
Public bug reported: Hi all, After upgrading from 12.10 to 13.04 on a system with two monitors, the second one became very dim. In fact, it's so dim that I thought it was blank. Both monitors are fine when booting up and they both show the "Ubuntu" name with 5 circles underneath...but somewhere during this point, the second screen blanks. By the time the login screen is shown, the second monitor is already very dim. Thinking that this might be caused by incompatible configuration files, I created a new account and logged in with that -- no difference. Thinking that maybe it's a hardware problem with the monitor, I swapped the DVI cables and the same monitor remained dim. I then plugged the monitor into another system and the monitor's fine. The second screen is fine sometimes (i.e., not always) right after the screen saver activates. I enter my password to unlock the screen saver and things are ok for a few seconds and then the second monitor suddenly dims. This is the output from lspci: $ lspci -v | grep -i vga 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Cedar [Radeon HD 5000/6000/7350 Series] (prog-if 00 [VGA controller]) I'm not sure what steps are required to reproduce this bug since it always happens to me... I'd be happy to provide more information if I have an idea what information might be relevant. Ray ** Affects: 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/1172593 Title: [Dual monitor] One monitor very dim after 13.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1172593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980472] [NEW] "Inappropriate ioctl for device" when ejecting USB flash drive
Public bug reported: On Ubuntu 12.04 beta 2 (eject version 2.1.5+deb1+cvs20081104-9), when I eject a flash drive using "sudo eject", I get this error message: not an sg device, or old sg driver eject: unable to eject, last error: Inappropriate ioctl for device Previously, I had no problems ejecting using the same version of eject. The problem came up when I formatted the flash drive so that it would be encrypted. Also, I change the file system from the default (FAT32, I think) to NTFS. On another drive which I formatted to ext4, the same problem occurs -- again, it is now an encrypted file system. The drive is successfully unmounted, though, since it no longer appears under "df". However, it is still "on" since the light is still on. "sudo umount" gives no problems. ** Affects: eject (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/980472 Title: "Inappropriate ioctl for device" when ejecting USB flash drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/980472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
