[00:17] <jnadeau> hello
[00:20] <knome> hullo
[00:20] <jnadeau> i have a question
[00:20] <knome> go ahead
[00:20] <jnadeau> i'm a blind user and I'm running xubuntu with orca
[00:21] <jnadeau> i've managed to get xfce to be accessible with orca but have one problem
[00:21] <jnadeau> firefox and thunderbird are very accessible under gnome and I can't get them accessible under xfce any ideas
[00:23] <knome> i have followed the discussion on the mailing list, and unfortunately i don't have any ideas
[00:23] <jnadeau> Yeah I can't figure it out and its driving me crazy
[00:23] <knome> have you tried asking #ubuntu-accessibility?
[00:24] <knome> i know that's not explicitly xubuntu, but they might have some ideas
[00:24] <jnadeau> i'm running xubuntu right now but if I log out and into gnome firefox and thunderbird are accessible but if I log back into xfce they become unaccessible again
[00:24] <knome> yes, i'm aware of that
[00:25] <jnadeau> Yeah I will try ubuntu accessibility thanks for your time and help.
[00:25] <jnadeau> Also xubuntu is looking really great
[00:25] <jnadeau> i'm running 12.10 right now
[00:26] <knome> hmm, no offense meant, but if you are bling, how can you see? :)
[00:26] <knome> heh, blind, not bling...
[00:26] <jnadeau> I don't understand what you are asking i'm sorry
[00:27] <knome> jnadeau, i link "looking great" with seeing
[00:27] <jnadeau> well I mean looking great from my point of view
[00:27] <knome> jnadeau, heh, yeah. thanks for the feedback :)
[00:27] <jnadeau> like the way it runs and its performance
[00:28] <knome> it's actually good to know we have users with accessibility issues too
[00:28] <knome> and that we can actually deliver a usable experience
[00:28] <jnadeau> Yeah it's great outside of the whole firefox and thunderbird thing
[00:29] <knome> do you have any browser and/or mail app that you can use meanwhile?
[00:29] <jnadeau> not really thats why it is such a big problem
[00:29] <jnadeau> no other browsers are accessible
[00:30] <jnadeau> and evolution is full of accessibility bugs
[00:32] <micahg> hrm, we should have the accessibility stuff installed
[00:32] <knome> jnadeau, do you have the package 'at-spi' installed?
[00:32] <jnadeau> yes I do
[00:33] <jnadeau> I also checked the accessibility box  in the xfce menu
[00:33] <jnadeau> and checked the box to start the extra gnome things to see if that would help but still nothing
[00:34] <knome> jnadeau, can you try this:
[00:34] <jnadeau> sure
[00:34] <knome> jnadeau, create .gtkrc-2.0 file in your home dir, and add the following line:
[00:34] <knome> jnadeau, gtk-modules="gail:atk-bridge"
[00:35] <jnadeau> I did add this but I put it in my .bashrc file
[00:35] <jnadeau> so i should create this folder instead and put it there
[00:35] <knome> file, and yes, you could try if it works
[00:36] <jnadeau> I also put this in my .profile to see if that would help and it didn't work either
[00:37] <jnadeau> where should I create that folder
[00:37] <knome> if you add that to .profile or .bashrc, i think the line should be "export GTK_MODULES=gail:atk-bridge"
[00:37] <knome> create the *file* .gtkrc-2.0 in your home folder
[00:37] <jnadeau> yes that is how I put it in
[00:37] <knome> okay
[00:37] <knome> then i doubt this other fix will help, but you can always try
[00:38] <jnadeau> I will try anything
[00:38] <jnadeau> hang on and I'll create that folder
[00:44] <jnadeau> okay I created the file
[00:44] <jnadeau> do I have to log out
[00:44] <knome> at least it won't hurt if you do
[00:45] <jnadeau> just to make sure I did the right thing I opened leafpad and created the file .gtkrc-2.0 and put in that command
[00:45] <knome> yes
[00:45] <jnadeau> okay i'll be back thanks for all your help
[00:45] <knome> np
[00:52] <jnadeau> no it didn't work
[00:52] <jnadeau> but I think I might have found the problem possibly
[00:53] <jnadeau> so thanks again for all your time and help.
[05:06] <pleia2> knome: first draft of doc post for xubuntu.org is up
[11:06] <knome> we fit on CD's :)
[11:08] <SkippersBoss> CONGRATS
[11:08] <SkippersBoss> so the 450k has been found
[11:09] <elfy> :)
[11:10] <knome> no... we lost it
[11:10] <knome> that's why we fit ;)
[11:11] <SkippersBoss> lol
[11:11] <SkippersBoss> Now you guys get some sleep
[11:11] <SkippersBoss> well deserved
[11:11]  * knome is afraid it'll find our new address though
[11:11]  * knome hides
[11:11] <knome> hah, i just woke up ;)
[11:11] <SkippersBoss> some1 is in a happy mood today
[11:11] <knome> well, a few hours ago...
[11:11] <knome> i'm just pretending
[11:12] <SkippersBoss> I know the feeling
[11:12] <knome> no reason to be grumpy and bath in the depression either so...
[11:13] <SkippersBoss> till the next deadline lol
[11:13] <knome> not too much to do for Q an more
[11:18] <elfy> as far as I can see from here - the only things not working in quantal are the indicators - but from what I can see that's a way off and the double partitions thing - no idea what's going on with that
[11:18] <elfy> I for one applaud those who've done what they have
[11:25] <olbi> I saw yesterday on LiveCD that sound icon appear in indicator :D
[11:25] <olbi> and works good
[11:39] <elfy> working here too olbi - had to re-add the indicator thing
[11:45] <olbi> :)
[15:59] <SkippersBoss> excuse my ignorance but what is Yelp ?
[16:01] <pleia2> help browser (rather than using firefox)
[16:03] <SkippersBoss> Ah your ladyship... : Hmm Yes we want to (in my opinion)
[16:04] <SkippersBoss> Help files/documentation needs to be accessable with a minimum of fuz in my opnion.
[16:05] <pleia2> well, you'd still launch it in the same way, just by going to "Help" in the menu :)
[16:05] <SkippersBoss> ff has too many distracting bells nd whistles
[16:05] <pleia2> not sure if it's an lighter application
[16:05] <pleia2> yeah
[16:06] <SkippersBoss> Most people got FF loaded up with at least Adblock and maybe autopager
[16:07] <SkippersBoss> SO my personal preferance would be a simple browser
[16:07] <micahg> the problem is w/out yelp/gnome-user-docs, some of the applications won't have help
[16:08] <pleia2> so it probably makes sense for our stuff to use yelp, if we need it anyway
[16:08] <SkippersBoss> that's solves that issue then
[21:45] <micahg> \o/ looks like xfce 4.12 will have some gtk3 support
[21:45] <micahg> which is good as we'll probably have that + some pieces of 4.14 for 14.04
[21:46] <pleia2> :D
[22:17] <knome> micahg, yeah, i read the same; hoorahh!


[01:48] <cr3> how can I recover an old file which has been bzr removed from the repository at some point?
[02:00] <cr3> nevermind, found it with diff -r
[03:18] <lnxtech> Has anyone gotten bzr-gtk to run on OS X Leopard?  I'm trying with both the built in python and also from macports but I haven't gotten it to work yet
[03:36] <sabdfl> lifeless: hi
[04:48] <lifeless> sabdfl: hola
[05:42] <sabdfl> hey lifeless
[05:42] <sabdfl> thanks for the answers
[18:22] <lifeless> morning y'akk
[18:43] <abentley> jelmer: ping
[18:47] <juh> Hi, I cannot push anything to the repos on my server
[18:47] <juh> using bzr locally works
[18:48] <juh> is there a tutorial who to set up bzr on a server?
[18:49] <lifeless> http://doc.bazaar-vcs.org/latest/en/user-guide/index.html
[18:53] <lifeless> you don't need bzr on the server if you are using sftp or ftp
[18:54] <lifeless> if you are using bzr:// e.g. bzr+ssh:// then you need a bzr on the server, we try to be network compatible release to release.
[18:55] <juh> lifeless: thanks I think that it works now somehow
[20:07] <woei> I'm having some problems with the bzr-gtk (0.92.1) on a netbsd-4 (python2.4) machine. Python dumps core because it gets sent SIGSEGV: http://pastebin.com/d48960808
[20:08] <woei> base bzr runs flawlessly however
[20:23] <lifeless> woei: interesting; I would guess its a python-gtk bug
[20:32] <woei> lifeless: ok, I'll try updating pygtk to 2.12 (it's at 2.10.6 now)
[22:42] <pattern> i'm about to write a little script to get version information from bazaar in the form that perl modules expect (ie. versions of the form "X.Y.Z", where "X", "Y", and "Z" are all integers), and would like some input from anyone with more experience with bazaar on whether i'm going about this the right way...
[22:44] <pattern> bazaar seems to number its revisions with a single number... which is fine... my idea is to just tag a revision i'm about to release with something like "myproject-X.Y.Z"
[22:44] <pattern> unfortunately "bzr version-info" does not specify which tag a version has
[22:45] <pattern> so i'm thinking of grabbing "revno" from "bzr version-info" and then searching for it in the output of "bzr log"
[22:46] <pattern> if it finds a tag matching the regex: "\w-\d\.\d\.\d" (ie. "word-digit.digit.digit") it'll use the "digit.digit.digit" part for the version number
[22:47] <pattern> otherwise it'll keep looking down the list of revisions until it finds such a tag and use that
[22:47] <pattern> i know this is kind of ugly and hackish, but i don't know what else to do
[22:52] <lifeless> bzr revision-info will give you the unique revision id of your tree
[22:52] <pattern> isn't that the same as the "revno:" line in "bzr version-info" ?
[22:53] <lifeless> no, its a guid
[22:53] <lifeless> 'bzr tags' will list the tags you have
[22:53] <pattern> yes, but that doesn't tell me which tag the currently checked out working tree has
[22:54] <pattern> i suppose i could just use the top-listed tag
[22:54] <pattern> and assume i'm working with the newest revision
[22:54] <pattern> but that might not always be the case
[22:56] <lifeless> uhm
[22:56] <igc> morning
[22:56] <lifeless> I thought tags listed the tag
[22:56] <lifeless> revno/revisionid
[22:57] <lifeless> hi igc
[22:57] <igc> hi lifeless
[22:58] <pattern> as i understand it, "bzr tags" lists all the tags for the branch
[22:58] <pattern> but i'm interested in just the tag for the revision of the branch that i have checked out
[22:59] <pattern> so i think i'm going to have to search through the output of "bzr log" for that
[22:59] <lifeless> pattern: there may be no such tag
[22:59] <pattern> yes
[22:59] <pattern> in which case i guess i'll have to use the newest tag for any older revision
[23:00] <pattern> as i need to set my $VERSION to something
[23:00] <lifeless> and I'm saying that looking for bzr revision-info in the output of bzr tags is the fast way to do that if you don't want to use python
[23:00] <lifeless> pattern: but if you just want to specify 'the current tree', the guid from bzr revision-info is all you need
[23:00] <lifeless> perhaps I'm not understanding what you are trying to do
[23:01] <pattern> well, "bzr revision-info" just gives me a single digit... i need to get a version in the form of "X.Y.Z" (where each of "X", "Y", and "Z" are digits)
[23:01] <lifeless> pattern: I don't know why you need that, and revision-info doesn't give a digit, it gives a revno and revid; the revid is the unique part
[23:02] <lifeless> e.g.
[23:02] <lifeless> bzr revision-info
[23:02] <pattern> so i think the way to get that is to manually set a tag for the version i want (ie. "myproject-1.0.2")
[23:02] <lifeless> 2939<EMAIL_ADDRESS>[23:02] <pattern> the reason i need that is because perl modules are usually numbered in that way
[23:02] <lifeless> the<EMAIL_ADDRESS>is the right thing to use to refer to this commit in a guaranteed manner
[23:03] <lifeless> pattern: perhaps if you start from the top; I'm really confused
[23:03] <pattern> ok...
[23:03] <pattern> i'm writing a perl module... perl modules usually have a $VERSION (version string)
[23:03] <pattern> $VERSION is used internally by the standard makefiles that compile and package up the module, and for module naming
[23:04] <pattern> and they're usually in the form "X.Y.Z" (where each of "X", "Y", and "Z" are digits)
[23:04] <pattern> usually that $VERSION lives in the code itself
[23:05] <lifeless> ok
[23:05] <pattern> but i don't want to mess with the code manually.. because i might make a mistake and get $VERSION out of sync with the actual revision in bazaar
[23:05] <lifeless> so why not just append .0.0 to what bzr supplies ?
[23:06] <pattern> well, releasing new major numbers (the first digit) is usually frowned upon unless you've made massive changes (ie. that require a reconfig, and/or API/format-changes, etc)
[23:06] <lifeless> or do
[23:07] <lifeless> 0.bzrrevno.0 ?
[23:07] <lifeless> or 1.0.bzrrevno ?
[23:07] <pattern> and then how do i increment the first and last digits?
[23:07] <pattern> or whatever digits bzrrevno doesn't account for?
[23:07] <pattern> it just makes much more sense to tag the release manually
[23:07] <lifeless> well, increment them whenever you want to
[23:07] <pattern> but have it in sync with the revision in bazaar
[23:08] <pattern> so i can check out the branch based on that tag
[23:08] <lifeless> but if you do want to use bzr tags, sure, using log and looking back for a tag will work, though you will get the same VERSION for different commits until you tag a new version
[23:08] <pattern> yeah, that is a problem
[23:09] <pattern> i'm going to have to give it more thought
[23:10] <pattern> or maybe i could just tag every revision
[23:10] <pattern> as X.Y.bzrrevno
[23:11] <pattern> and when i do releases just use X.Y.0
[23:11] <lifeless> which is the same as not tagging
[23:12] <lifeless> and using x.y.bzrrevno all the time except for releases
[23:13] <pattern> well, then if there's no tag on a version i'd need to search through earlier log entries for tags to know what X.Y is
[23:13] <lifeless> ssure
[23:13] <pattern> why not just tag every revision?
[23:13] <pattern> i could probably write a script to do it, using the previous value of X.Y, and allowing an override
[23:13] <lifeless> seems redundant and needs more work
[23:13] <lifeless> I'd just tag once, and look that up
[23:14] <pattern> it's too bad "bzr version-info" doesn't tell me the tag of the current revision
[23:14] <pattern> then i wouldn't need to search "bzr log" for it
[23:15] <lifeless> but as discussed there may be no tag
[23:15] <lifeless> unless you've tagged every time
[23:15] <pattern> right
[23:15] <pattern> which is what i think i'm going to do
[23:15] <lifeless> certainly, please do file a bug about it not providing the tag
[23:16] <pattern> well, then maybe there should be a "bzr tag-info" :)
[23:16] <i386> lifeless: http://confluence.ts.wikimedia.org/display/main/Home
[23:16] <pattern> though, i think that while "bzr version-info" is providing all sorts of other info on that revision (such as the date and branch), it might as well provide the tag as well
[23:17] <lifeless> pattern: sure; file a bug :)
[23:17] <pattern> will do :)
[23:20] <lifeless> i386: :)
[23:20] <i386> lifeless: :)
[23:25] <pattern> actually, "bzr log -r `bzr revno`" will accomplish pretty much the same as what having "bzr version-info" report the tag would do
[23:26] <pattern> and "bzr log -r `bzr revno` | grep tag" to get the tag itself
[23:27] <pattern> it's still a bit hackish... but seems to work
[23:28] <lifeless> you can use 'bzr log -r -1'
[23:29] <pattern> ah
[23:29] <pattern> nice :)
[23:29] <pattern> "bzr log -r -1 | grep tags | sed 's/^tags: //'"
[23:33] <pattern> now to write a little script that does that before running a commit, and then automatically tagging the newly committed revision with X.Y.revno (where X.Y comes from the previous tag, and revno is the current revision)
[23:33] <pattern> and when i want to increment X.Y i'd do so manually instead of running that script
[23:34] <pattern> or maybe give the script an override option
[23:34] <lifeless> its this complexity I don't like about tagging every commit
[23:34] <lifeless> you wouldn't have to wrap commit if you only tagged releases
[23:35] <pattern> well, it's either that or having to search through multiple log entries for the last tagged revision before the revision i'm working on now
[23:36] <pattern> both ways entail additional complexity
[23:36] <pattern> at least if i tag every revision, then i'd instantly know the X.Y version number of every revision by simply looking at the log for that revision
[23:38] <lifeless> so one is prone to failing if you forget to use your wrapper
[23:38] <lifeless> the other isn't prone to failing at all
[23:38] <lifeless> shrug, its up to you :)
[23:39] <pattern> there's no "bzr alias", eh?  :)
[23:39] <lifeless> you can alias commit to give you options and so on, but not to run a shell script - your shell's alias can do that
[23:40] <pattern> but shell aliases only alias the first word on the command line
[23:40] <lifeless> a precommit hook could do what you need too, though noone has actually wired up the glue for precommit hooks just yet - we've been waiting for a use ase
[23:40] <pattern> so i'd need to create a "bzrcommit" alias
[23:40] <pattern> which, as you point out, i might forget to type
[23:42] <pattern> but, if i do forget to type "bzrcommit" and type "bzr commit" instead, the next time i type "bzrcommit" or the next time i run make my "bzrcommit" script or the scripts in the makefile could warn me about not seeing a tag for the current revision
[23:42] <pattern> and i could also have a script that goes back and adds any missing tags
[23:42] <pattern> that would be trivial
[23:43] <pattern> of course, doing that would involve searching through the output of "bzr log"
[23:43] <pattern> so maybe instead of creating a wrapper for "bzr commit" i should create a wrapper for "bzr log" instead
[23:46] <pattern> well, one other advantage of tagging every revision is that i could always check out a given revision via its tag, which would include the X.Y version number... and that would make more sense than just using the revno alone
[23:49] <lifeless> I worry that you will run into scaling problems with tags
[23:50] <lifeless> they're not geared for thousands of them
[23:50] <pattern> hmm
[23:50] <lifeless> and you're really just duplicating our existing infrastructure
[23:50] <lifeless> which is why x.y.REVNO is IMO superior, for non-releases
[23:50] <lifeless> you can 'bzr branch -r REVNO' as well
[23:51] <pattern> or "bzr branch -r tag:X.Y.REVNO", right?  :)
[23:51] <lifeless> yes, but thats redundant
[23:51] <lifeless> so there is no gain; thats my point
[23:52] <pattern> the gain is in a more intuitive user experience when looking for a given X.Y.REVNO version
[23:52] <lifeless> still; if you feel you need to, it will work, it will just incrementally slow down your push/pull operations
[23:53] <lifeless> couldn't you just add a VERSION_ID to the perl script
[23:53] <lifeless> which is the GUID ?
[23:53] <pattern> well, it needs to be in the X.Y.Z format, which is the standard
[23:53] <lifeless> thats even easier in terms of getting the code for that version, and more robust against things like uncommit
[23:53] <lifeless> no, you miss my poin
[23:53] <lifeless> use VERSION for the build stuff
[23:53] <lifeless> use VERSION_ID for the bzr GUID, as ancilliary data
[23:54] <pattern> i don't understand
[23:54] <lifeless> you seem to have several use cases
[23:54] <pattern> could you explain what VERSION_ID and GUID are?
[23:54] <lifeless> case 1) provide a machine generated version number for each build; which will be semi-human-readable
[23:54] <lifeless> case 2) provide a way for users to obtain the source code
[23:55] <lifeless> VERSION_ID would just be a perl variable
[23:55] <pattern> and that would be different from VERSION ?
[23:55] <lifeless> the GUID is what is returned by 'bzr revision-info', e.g<EMAIL_ADDRESS>[23:56] <pattern> how is using GUID better than the output of "bzr revno" ?
[23:56] <lifeless> it does the correct thing when people uncommit
[23:56] <pattern> and, more importantly, how do i get a proper X.Y.Z formatted version number for the perl VERSION variable?
[23:56] <lifeless> it works in any branch of the project regardless of merge history
[23:56] <pattern> ah
[23:57] <lifeless> the guid is the underlying database id
[23:57] <pattern> well, that makes things more complicated
[23:57] <lifeless> for the Z component, I'd use the bzr revno, as you don't plan on uncommitting in your mainline, or even just lookup your last actual build you released, or use a timestamp (e.g. Z is seconds-since-epoch)
[23:58] <pattern> maybe i could just append an md5sum of GUID :)
[23:58] <lifeless> md5's have a-f in them
[23:58] <pattern> yeah, i was joking
[23:58] <lifeless> if thats permitted, just using the guid directly :).
[23:59] <pattern> i think perl users would flip if they saw a 30 digit number in their version string
[23:59] <pattern> and it's not permitted
[23:59] <pattern> i don't think


[07:29] <Blessed> Hi can i upgrade Lubuntu to 14.04 from 12.04 without updating kernel?
[07:43] <ianorlin> Blessed: if you really want to but I am not sure why you would want to do that
[07:43] <ianorlin> Lubuntu 12.04 was not an LTS release
[07:44] <Blessed> i have Lubuntu LTS
[07:44] <Blessed> 12
[07:55] <Blessed> hwo ccan i do it?
[11:00] <Cheaterman> hello buddies i hope you're doing good
[11:00] <Cheaterman> i'm on a lubuntu livecd to recover my gentoo and i have some questions
[11:00] <Cheaterman> it seems that lubuntu is very different from ubuntu? from what I see, i don't have pulseaudio?
[11:00] <Cheaterman> ● pulseaudio.service Loaded: not-found (Reason: No such file or directory)
[11:01] <Cheaterman> as i said i'm booted on the installation media if it makes any difference
[11:02] <Cheaterman> i'm asking that because lxde seems to have some software volume control nonetheless
[11:03] <Cheaterman> much like if there was PA
[11:03] <Cheaterman> and it's not linked to any channel in alsamixer
[11:04] <Cheaterman> once again, much like if there was PA
[11:04] <Cheaterman> other than that, it seems to be the best Ubuntu derivative around, so gratz to everyone and keep up the good work
[11:05] <Cheaterman> (the fact that I use lxde tools in my own setup might make me biaised, my desktop is basically lxpanel + openbox + pcmanfm for desktop icons)
[18:52] <Vlado2> hi, is it normal that Booting Lubuntu 15.10 from DVD takes about 2 hours on Pentium M?
[19:06] <Vlado2> is anyone here?
[19:28] <Vlado2> hi
[21:08] <Vlado2> hi, is anybody here?
[21:12] <bioterror> !ask | Vlado2
[21:15] <Vlado2> i'm trying to install lubuntu 15.10 on my Pentium M laptop, i selected "try live lubuntu" or something like that but, laptop is stuck at loading screen with lubuntu logo and five dots for several hours, any idea what should i do? i tried also lubuntu 14.04.3 LTS but that one didn't detect my wifi card
[21:18] <Vlado2> but 14.04 did boot to desktop at least...
[21:43] <ianorlin> Vlado2: Do you know what kind of wifi card?
[21:44] <ianorlin> also how much ram?
[21:44] <Vlado2> Intel PRO/Wireless 2200BG, 2GB ram
[21:44] <ianorlin> hmm that should work and should be enough to not have to use alternate
[21:45] <ianorlin> Vlado2: have you checked the md5sum of 15.10 and the install media for 15.10 is good?
[21:45] <Vlado2> yes, i did, both
[21:46] <Vlado2> do you want complete HW spec?
[21:46] <ianorlin> do you have acess to ethernet at least for the install ?
[21:46] <ianorlin> would be helpful
[21:47] <ianorlin> are you on another os on that pentium m right now?
[21:48] <ianorlin> I would probably try 14.04.3 then try to get wifi card working
[21:49] <Vlado2> HP nw8240, Pentium M Dothan 1.73GHz (SSE2, PAE, NX bit), 2GB ram, ATI mobility FireGL V5000, Intel PRO/Wireless 2200BG, broadcom bcm5751MKFB ETH NIC, some BT adapter, Matsushita DVD writer (PATA connected), 250GB PATA HDD
[21:50] <Vlado2> i'm writing from my desktop (win)
[21:50] <Vlado2> and... Trusted Platform Module
[21:51] <ianorlin> on the laptop?
[21:51] <Vlado2> yep
[21:51] <ianorlin> oh I have not dealt with those but heard they can make installing other things tricky
[21:52] <Vlado2> so i should try to remove it for installation?
[21:52] <ianorlin> I am not if it is soldered on
[21:53] <ianorlin> although I don't know about ATI mobility FIREGL might have a graphics issue with 15.10
[21:53] <Vlado2> the TPM can be removed, but... o
[21:53] <Vlado2> o
[21:53] <ianorlin> !nomodeset
[21:57] <Vlado2> well, graphics was working correctly on lubuntu 14.04.3 LTS, but as i already mentioned, wifi was not workin, WiFi LED on laptop was blinking, as if it was trying to turn it on and off and on again...
[22:02] <Vlado2> whoa, after several hours the lubuntu booted and is now prompting for login, i switched to F7 and there are several failures
[22:05] <Vlado2> failed to start load kernel modules, see systemctl status systemd-module-load.service for details
[22:06] <Vlado2> failed to start apply kernel variables
[22:06] <Vlado2> failed to start journal service
[22:08] <Vlado2> on the end is: [***  ] (2 of 4) a start job is running for light display manager (1min 45s/3min) [4834.504773] blk_update_request: I/O error, dev sr0, sector 258968
[22:08] <Vlado2> and several more I/O errors are appearing
[22:13] <bioterror> your cd/dvd drive might be taking the last breaths or the disc itself
[22:13] <bioterror> try USB
[22:15] <Vlado2> well, just couple hours ago i tried on that same drive and using the same DVD-RW booting Lubuntu 14.04 and it worked, so i doubt that there is any HW problem or problem with DVD-RW disc
[22:15] <Geogts> i've been using qbittorrent for a while with no problems at all.  today i did sudo apt-get upgrade qbittorrent and now it makes no connections.  when i uninstalled it and reinstalled it, it still had all the same exact settings and it was still not working.  how can i completely remove the program and reinstall it without having any settings or files left behind?
[22:24] <Geogts1> anyone?
[22:27] <bioterror> Geogts1, are you behind a NAT? if so, then forward that port
[22:27] <Geogts1> checked port forwarding.  port is fine on canyouseeme.org