[Bug 270719] [NEW] 'old' bssid's causing problems wireless?
Public bug reported: Binary package hint: network-manager Ubuntu Hardy. on macbook connecting to wireless network (802.1X ) using the following options TTLS Dynamic WEP PAP username passwd There are 5 bssids for the different accesss points. It seems that as I accumulate access points, I can't get back on the network. In this particular instance doing iwlist ath0 ap shows that I see two acess points (00:12:...) in the screen shot and that I have four bssids stored in my profile. It seems that I cannot reconnect until I remove the 'old' bssid's from the profile. It seems like the wireless software is not making it through the list of bssids or something. I have done this a number of times but I don't really know enough about how this stuff works to rule out coincidence ... i.e. maybe I just fiddle with stuff until the wireless is back on and I think I fixed it by my fiddling. Any advice on making this report more useful? I will only be on this wireless network for another week or so. screenshots of the bssid editor and iwcofig ath0 ap output follow. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 'old' bssid's causing problems wireless? https://bugs.launchpad.net/bugs/270719 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270719] Re: 'old' bssid's causing problems wireless?
** Attachment added: "screenshots.tarzip" http://launchpadlibrarian.net/17632853/screenshots.tarzip -- 'old' bssid's causing problems wireless? https://bugs.launchpad.net/bugs/270719 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270018] [NEW] command-line option --zoom=ZOOMFACTOR fails when called with multiple tabs
Public bug reported: Binary package hint: gnome-terminal GNOME gnome-terminal 2.22.1 on Hardy. The following command open two tabs in a new terminal window but seems to ignore the zoom factors gnome-terminal --tab --zoom=3 --tab --zoom=3 gnome-terminal --tab --zoom=3 --tab also produces two tabs with no zoom. However, the command gnome-terminal --tab --zoom=3 works ... producing one tab with the proper zoom factor. Importance: If zoom doesn't work then the whole command line aspect of gnome-terminal is not very useful since opening several tabs with a script only to have to manually fix the size is a real pain. The zoom factor is properly inherited from manually opened (ctrl-shift-t) tabs. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- command-line option --zoom=ZOOMFACTOR fails when called with multiple tabs https://bugs.launchpad.net/bugs/270018 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 270719] Re: 'old' bssid's causing problems wireless?
I'm not around the same wireless network so I haven't noticed the problem occuring ... I am still having disconnects but I'll have to look into it to see if the symptoms look to be similar. On Thu, Jan 15, 2009 at 8:21 AM, Pedro Villavicencio wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. You reported this bug a while ago and there hasn't been > any activity in it recently. We were wondering is this still an issue > for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? > Thanks in advance. > > ** Changed in: network-manager (Ubuntu) > Status: New => Incomplete > > -- > 'old' bssid's causing problems wireless? > https://bugs.launchpad.net/bugs/270719 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in "network-manager" source package in Ubuntu: Incomplete > > Bug description: > Binary package hint: network-manager > > Ubuntu Hardy. on macbook > > connecting to wireless network (802.1X ) using the following options > > TTLS > Dynamic WEP > PAP > username > passwd > > There are 5 bssids for the different accesss points. It seems that as I > accumulate access points, I can't get back on the network. > > In this particular instance > doing iwlist ath0 ap > shows that I see two acess points (00:12:...) in the screen shot and that I > have four bssids stored in my profile. > > It seems that I cannot reconnect until I remove the 'old' bssid's from the > profile. It seems like the wireless software is not making it through the > list of bssids or something. > > I have done this a number of times but I don't really know enough about how > this stuff works to rule out coincidence ... i.e. maybe I just fiddle with > stuff until the wireless is back on and I think I fixed it by my fiddling. > > Any advice on making this report more useful? I will only be on this > wireless network for another week or so. > > screenshots of the bssid editor and iwcofig ath0 ap output follow. > -- 'old' bssid's causing problems wireless? https://bugs.launchpad.net/bugs/270719 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184996] Re: Annotation tools are broken in hardy
I am using 0.4.2.1-0.1ubuntu1 on intrepid. I think I have the same error. The annotation tools do not seem to work, furthermore using them (i.e. drawing something) causes xournal to use up lots of processor. Launching xournal from the command line, the only output I get is $ xournal (xournal:7000): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (xournal:7000): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated I dont think this output is relevant to the bug but I don't really know. I would really like to get xournal working on my home machine (intrepid + macbook) ... I have started to use it regularly at work when reading articles. I haven't yet tried the above listed patches which seem to be for hardy but will report back if I get anywhere. -- Annotation tools are broken in hardy https://bugs.launchpad.net/bugs/184996 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 306400] Re: compiz stopped working
I am having similar problems on an msiwind with compiz returning same complaints up to Software rasterizer detected, abortingaborting and using fallback: /usr/bin/metacity I used an extra monitor yesterday and everything was working fine so it is not a graphics card issue. Any ideas? I think there was only one update since yesterday and I didn't think it was anything important. -- compiz stopped working https://bugs.launchpad.net/bugs/306400 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 306400] Re: compiz stopped working
Attached is an archive of the three files: ** Attachment added: "files.tar.gz" http://launchpadlibrarian.net/24972783/files.tar.gz -- compiz stopped working https://bugs.launchpad.net/bugs/306400 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 306400] Re: compiz stopped working
It seems that things are working after today's updates (which I just ran). So apparently running "compiz --replace" or "compiz" in the terminal is not same as enabling desktop effects in the gui? Some of my settings were lost (I had to reenable various options) but it looks like it's working. oh, well. I guess I should learn to wait at least a day before hitting launchpad when compiz breaks :). -- compiz stopped working https://bugs.launchpad.net/bugs/306400 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650961] Re: ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106
Same, was ok. now problems. On 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650961 Title: ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1650961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955155] [NEW] Ubuntu shuts down now from locked screen after some amount of time despite all automatic shutdown disabled
Public bug reported: I have no idea when this started, but my Desktop goes offline (shuts down) when left in the lock screen or when left on the log in screen with no activity. I used to have things set up to auto-reboot on power failure and no shut down occurred. This was working as of last year roughly and I do not have any event to associate the change in behaviour other than all the updates that happened over that time. On 20.04. This is a pretty disastrous bug as you can imagine as a) nobody has any information on this, looking at logs (last -x) I saw no shutdown commands issued. b) configs are a mess documentation wise with words like "sleep", "suspend" thrown around and nobody really knows what they mean. Asking about "sleep" gets a lots of responses about "why are you asking about /bin/sleep". It is a kind of state where you end up in an asylum because nobody wants to debug this, it's probably a config change done by some update, and it's not very interesting in terms of problems to solve. Except it is absolutely disastrous since now my machine is offline and I am away (I tried N rounds of debugging and testing before I left) but was *unable* to block automatic shutdown AND not leave the computer logged in and totally vulnerable. Probably what should happen is that instead of some massive and fruitless debugging project, a feature should be enabled that is a "block ALL automatic shutdowns no matter what reason never ever allow anything to shut me down that isn't a human typing at a keyboard. Reboots are fine." You might call this server mode. I have seen people saying to simply set /bin/shutdown to unexecutable ... I might try that when back but it sounds like it might have potentially bad side effects. ** 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/1955155 Title: Ubuntu shuts down now from locked screen after some amount of time despite all automatic shutdown disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1955155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
