Public bug reported:
I am starting a bash shell using
$ bash --noprofile --bashrc my-custom-bash-rc-file
Due to the --rcflag, the newly started bash should *not* execute
commands from /etc/bash.bashrc. That is at least how I interpret `man
bash`:
--rcfile file
Execute
$ lsb_release --all
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.10
Release:12.10
Codename: quantal
$ bash --version
GNU bash, version 4.2.37(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL
Public bug reported:
I was invoking bash as follows:
$ env -i bash
This caused this message to be printed:
$ env -i bash
To run a command as administrator (user root), use sudo command.
See man sudo_root for details.
While I think I understand the rationale for the message, I found it
more
Hmm, I'm starting to think this is not a bug but rather something that
belongs to a policy discussion (as suggested by the Ubuntu bug
reporting tutorial)?
Anyway, the version info:
Ubuntu 12.10
$ bash --version
GNU bash, version 4.2.37(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2011 Free
** Description changed:
I was invoking bash as follows:
$ env -i bash
This caused this message to be printed:
$ env -i bash
To run a command as administrator (user root), use sudo command.
See man sudo_root for details.
While I think I understand the rationale for the
I am pretty sure this is a compatibility problem with NX and the various
Ubuntu versions. It is not emacs that is using the rgb.txt file, it is
the nxserver I think.. And nxserver assumes that this file exists in
various hardcoded locations on the system..? See
*** This bug is a duplicate of bug 300935 ***
https://bugs.launchpad.net/bugs/300935
I finally got a workaround working. See the links mentioned in my
previous comment for background. Note that this is NoMachine NX, not
FreeNX. The solution for me was to just add /etc/X11/rgb.txt and restart
*** This bug is a duplicate of bug 300935 ***
https://bugs.launchpad.net/bugs/300935
I finally got a workaround working. See the links mentioned in my
previous comment for background. Note that this is NoMachine NX, not
FreeNX. The solution for me was to just add /etc/X11/rgb.txt and restart
Bug #358678 , which IMHO is a duplicate of this one, has some more
information related to problems invoking emacs (and other applications,
see above) under NX from NoMachine (nxserver) and FreeNX.
--
missing /etc/X11/rgb.txt file and broken link to it
https://bugs.launchpad.net/bugs/300935
You
*** This bug is a duplicate of bug 346061 ***
https://bugs.launchpad.net/bugs/346061
** This bug has been marked a duplicate of bug 346061
Message Filters... DIES
--
Tools → Message Filters generates XML parsing error
https://bugs.launchpad.net/bugs/302423
You received this bug
Workaround:
For me, the problem disappeared after having restarted all XUL-based
application (Thunderbird, Firefox...).
(At restart, I noticed that both those applications had Add-ons that
wanted to update. Perhaps is that related to the problem.)
--
Message Filters... DIES
Thanks for triaging.
It is unfortunately not possible for me to check whether this is still
an issue. (I can't enable the Composite Extension, I get a pop-up that
says it is not available.) (So, I am not in a position to complain if
you close this bug.)
I guess one should probably try with a
Ok, thanks for taking the time. That wiki page is very informative.
--
displayconfig-gtk: Test fails (scrambled screen) even with default settings
https://bugs.launchpad.net/bugs/134706
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: ubuntu-desktop
Shift-F10 keyboard shortcut should, IMHO, emulate mouse right click
(which usually brings up a context menu in whatever application that has
focus).
But when compiz-fusion is enabled, compiz-fusion *overrides* Shift-F10
to mean Slow
Ians instructions in comment #12 works for me.
(Sometimes you gotta love people.. Thanks for quick fix, and support
from other posters here :-) )
- Hugo Heden
--
Apt segfaults on gutsy
https://bugs.launchpad.net/bugs/140739
You received this bug notification because you are a member of Ubuntu
Yes, probably a network-admin bug.. or a bug concerning some conflict
between NetworkManager and network-admin?
I had actually not tried ifdown/ifup.. I'm taking the newbie-perspective
here -- it shouldn't be necessary. (Actually I *am* pretty much a semi-
newbie, so I'm really good at taking
I'm just a little concerned that I can't configure wireless using
*network-admin* (System==Administration==Network) (as opposed to
NetworkManager/nm-applet). I just don't seem to get the actual
connection (though there is no UI that tells me that).
This is how I interpret this bug --
The use-case involving open displayconfig-gtk, just hit Test and your screen
will change _may_ sound a bit contrived.. But that is pretty much what will
happen in the following scenario:
I want to add a second screen to my laptop. So I plug in the cable and
turn the second screen on. Then I
Yes.. I see the exact same effect.
I made a note about this bug here on the upstream bugtracker.
--
Error displaying connection information
https://bugs.launchpad.net/bugs/126479
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Is this a duplicate of Bug #126968? And Bug #113062?
--
[Feisty] Can't assign myself a static IP on wireless card using WPA
https://bugs.launchpad.net/bugs/123881
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Is this a duplicate of Bug #126968?
--
Atheros WPA/WPA2 not configurable from network-manager (roaming mode disabled)
https://bugs.launchpad.net/bugs/113062
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Bug reported upstream, see
http://bugzilla.gnome.org/show_bug.cgi?id=394264
If you display the Connection Information from the notification area
applet and close it by way of the window close button (the X), and not
the close button, it will fail to display again, giving this error:
Error
** Summary changed:
- displayconfig-gtk: Test fails (scramled screen) even with default settings
+ displayconfig-gtk: Test fails (scrambled screen) even with default settings
--
displayconfig-gtk: Test fails (scrambled screen) even with default settings
https://bugs.launchpad.net/bugs/134706
Vicky, *thanks* for your additions and clarifications, we are indeed
seeing the same thing.
Bryce:
1) Scrambled: At first, the screen looks like on the photographs that
Vicky has attached, *except* that the Keep this configuration pop-up
is visible, and I can press Alt-c to select Cancel.
2)
Regarding the workflow issue:
As a new confused user, it is natural to think that displayconfig-gtk
would trust the perception of the hardware that the rest of the OS has
(or had at installation time) -- namely the *current settings* -- so I
feel it would be logical for displayconfig-gtk to use
Public bug reported:
Binary package hint: displayconfig-gtk
Open displayconfig-gtk. Don't change any settings. Just press button
that says Test.
I would have expected that nothing would happen -- shouldn't the
settings chosen per default by displayconfig-gtk be the current
settings? (The
$ displayconfig-gtk --version
0.2.x (development branch)
$ cat /etc/issue
Ubuntu gutsy (development branch) \n \l
** Attachment added: lspci --vvn
http://launchpadlibrarian.net/8981727/lspci-vvn.txt
--
displayconfig-gtk: Test fails (scramled screen) even with default settings
** Attachment added: lspci --vv
http://launchpadlibrarian.net/8981730/lspci-vv.txt
--
displayconfig-gtk: Test fails (scramled screen) even with default settings
https://bugs.launchpad.net/bugs/134706
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: xorg.conf
http://launchpadlibrarian.net/8981734/xorg.conf
--
displayconfig-gtk: Test fails (scramled screen) even with default settings
https://bugs.launchpad.net/bugs/134706
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
The attached log-file is probably from my current working session (where
I haven't tried to reproduce the bug, since the system hangs). Should I
attach /var/log/Xorg.0.log.old, /var/log/Xorg.9.log or
/var/log/Xorg.9.log.old as well?
Let me know if there is anything else I should add..?
**
I've now installed restricted driver fglrx, as suggested by the
Restricted Driver Manager. When performing the same steps -- (Open
displayconfig-gtk. Don't change any settings. Just press button that
says Test) -- I get an ugly gray screen with the popup. I can press
Cancel, and everything goes
I second this. I've been wanting to configure a static IP (for better
bittorrent performance etc) using wireless with WPA, but that didn't
seem to be possible using the GUI-tools in Feisty.
(Work-around: Edit /etc/network/interfaces as described in
http://ubuntuforums.org/showthread.php?t=202834
(Bug 110187 -- Wireless won't work unless 'Roaming mode' selected --
still seems to be valid)
--
network-manager only supports WPA when roaming
https://bugs.launchpad.net/bugs/126968
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I second this bug. It seems to still be valid on Gutsy Tribe 5
$ network-admin --version
GNOME network-admin 2.19.1
A somewhat messy workaround: Edit /etc/network/interfaces as described
in http://ubuntuforums.org/showthread.php?t=202834 .
--
Wireless won't work unless 'Roaming mode' selected
34 matches
Mail list logo
