Public bug reported:
Binary package hint: dia-gnome
dia-gnome: 0.95.0-4ubuntu2
The Tools menu lists hotkeys for the various tools in dia. E.g. Alt-T
for Text. Some of these don't work because the pop up the menu that is
associated with that hotkey.
Steps to reproduce:
1. Open new Dia document
Thanks. At the moment I am not able to test this because I don't have
access to that network anymore.
--
network-manager-vpnc lacks nat traversal mode option
https://bugs.launchpad.net/bugs/165237
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have a Dell Latitude D630, Intel Core 2 Duo T7300.
I still have the problem.
I used the Hardy beta LiveCD, updated pm-utils to 0.99.2-3ubuntu6 (newest
version), and then tried suspend directly from the LiveCD.
After suspend Core 1 was stuck at 2 GHz. (max), and scaling was only working on
Mario:
Also not fixed here on Daily LiveCD (2008-03-27).
--
Intel Core 2 Duo - Resume from suspend, CPU Frequency Scaling is gone on CPU1
https://bugs.launchpad.net/bugs/183033
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have Hardy 32bit, and Tilda 0.9.5pre.
The bug doesn't occur for me anymore, even with animated pulldown
disabled. I am using compiz.
--
tilda stays like a gray window
https://bugs.launchpad.net/bugs/144175
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Cannot confirm (Ubuntu 8.04, sun-java6 installed),
Are you sure that you are really using the jedit from the Ubuntu
repository?
If you downloaded and installed jedit from the jedit website, that
version requires the $JAVA_HOME environment variable to be set and
assumes the 1.6.0.03 directory if
No problem. Thanks for helping make Ubuntu better anyway.
Marking bug invalid.
** Changed in: jedit (Ubuntu)
Status: Incomplete = Invalid
--
jEdit doesn't find installed JRE
https://bugs.launchpad.net/bugs/92
You received this bug notification because you are a member of Ubuntu
Bugs,
I think I have the same problem. on the early Gutsy final versions, CPU1
got stuck on 2 GHz (full speed) most of the time after a suspend-to-ram.
But now CPU1 always gets stuck at 800 MHz (lowest speed) after a
suspend. Performance scaling with CPU0 works fine.
I have added a more detailed
Tested this with the new Hardy Alpha 5 LiveCD.
CPU1 gets stuck at 2 GHz (full speed) again now after resuming from a
suspend.
--
cpufreq scaling_grovernor only saved for CPU0 on SMP following suspend/resume.
https://bugs.launchpad.net/bugs/68191
You received this bug notification because you
Setting status back to confirmed since previous fix apparently doesn't
work as expected.
** Changed in: acpi-support (Ubuntu)
Status: Fix Released = Confirmed
--
cpufreq scaling_grovernor only saved for CPU0 on SMP following suspend/resume.
https://bugs.launchpad.net/bugs/68191
You
Same problem as in description happens to me, with the following system:
Ubuntu 7.10
Kernel: Linux moria 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686
GNU/Linux
Dell Latitude D630 Laptop
Processor: Intel Core 2 Duo T7300 (2x 2 GHz)
Before suspend, frequency scaling is working
** Attachment added: 'cpufreq-info' directly after reboot, before suspending
http://launchpadlibrarian.net/12134855/cpufreq-info-before-suspend.log
--
Intel Core 2 Duo - Resume from suspend, CPU Frequency Scaling is gone on CPU1
https://bugs.launchpad.net/bugs/183033
You received this bug
To clarify, I'm talking about Suspend-to-RAM.
** Attachment added: 'cpufreq-info' after resuming from suspend
http://launchpadlibrarian.net/12134859/cpufreq-info-after-suspend.log
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: None = linux-source-2.6.22
Status: New =
Tested with LiveCD of new Hardy Alpha 5:
CPU1 now stays at 2 GHz after resume from suspend. (Same behaviour as
with older Gutsy Kernels)
--
Intel Core 2 Duo - Resume from suspend, CPU Frequency Scaling is gone on CPU1
https://bugs.launchpad.net/bugs/183033
You received this bug notification
Public bug reported:
Some settings that I have set in xorg.conf for the synaptics driver are
not being accepted or overwritten at some point during the start of X11.
My relevant parts from xorg.conf look like this:
Section InputDevice
Identifier Synaptics Touchpad
Driver
Ubuntu 7.10 with all updates and linux-backport-modules installed.
$ uname -a
Linux moria 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
--
synaptics driver disregards some xorg.conf settings
https://bugs.launchpad.net/bugs/160624
You received this bug notification because
When setting
Option SHMConfig false
in xorg.conf, the problem goes away. But then you naturally can't use
synclient to access the touchpad settings.
--
synaptics driver disregards some xorg.conf settings
https://bugs.launchpad.net/bugs/160624
You received this bug notification because you are
OK, I found out that apparently gsynaptics is overwriting some xorg.conf
values, if installed.
After I removed gsynaptics, everything works normally now.
** Also affects: gsynaptics (Ubuntu)
Importance: Undecided
Status: New
--
synaptics driver disregards some xorg.conf settings
Public bug reported:
For some VPN networks (eg. my university cisco vpn network) you have to
set the NAT Traversal Mode to something different than standard, to be
able to use the network correctly.
In the cli vpnc, this is the --natt option. In the vpnc config file the NAT
Traversal Mode
forgot to assign to correct package
** Changed in: network-manager-vpnc (Ubuntu)
Sourcepackagename: None = network-manager-vpnc
--
network-manager-vpnc lacks nat traversal mode option
https://bugs.launchpad.net/bugs/165237
You received this bug notification because you are a member of Ubuntu
Are you sure that all possible mixers are unmuted? There are at least two
independent mixers that I know of:
1) 'alsamixer' on the command line
2) Gnome alsa mixer. Double click the speaker icon at the top right panel in
gnome. Here you can display different channels by going into the
** Tags added: vpn
--
network-manager-vpnc lacks nat traversal mode option
https://bugs.launchpad.net/bugs/165237
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
Could this have something to do with the fact that nm-vpnc lacks support
for different settings that vpnc-connect uses (eg. through a config
file)? See for example Bug #165237 for one such problem.
--
nm-vpnc and vpnc-connect produce different routing tables
Also working here on Dell Latitude D630. No ACPI errors on suspend/resume.
Thanks Dennis and Mario for the fix!
--
Intel Core 2 Duo - Resume from suspend, CPU Frequency Scaling is gone on CPU1
https://bugs.launchpad.net/bugs/183033
You received this bug notification because you are a member of
Maybe we are talking about two different things here.
* totem: does buffer correctly according to
/apps/totem/network-buffer-threshold value.
Note: /apps/totem/buffer-size has to be set at least as high as
network-buffer-treshold, otherwise it won't play, as some people have noted
above. I
Just noticed that the 'totem' source package provides the binary package
'totem-mozilla'. So ignore the last sentence of my previous comment.
--
totem isn't buffering correctly
https://bugs.launchpad.net/bugs/108623
You received this bug notification because you are a member of Ubuntu
Bugs,
Bug #144175 is also fixed by upstream version 0.9.6, which I am running now.
I have animated pulldown deactivated and do not get the gray window anymore.
--
New upstream release - tilda 0.9.6
https://bugs.launchpad.net/bugs/223723
You received this bug notification because you are a member of
Hi Andrew, thanks for the response.
While I am using Beryl, I tested this with all 3 Window Managers (Beryl,
Compiz, Metacity, switched with beryl-manager; also tested with both
Emerald and GTK Decorators), and the behaviour was exactly the same. No
speed/time difference whatsoever. Since I am
I opened another bugreport about this some time ago because I didn't
find this one first when searching. Bug #108580
I think I have an explanation there about what triggers this bug. It's
the analyser part of the main window (between playback and volume
controls at the bottom).
--
Intense
I installed kubuntu-desktop and checked it out. The problem remains the
same.
But some more testing:
I cleared my playlist (which previously had all my music files listed),
and the problem went away. Amarok starts almost instantaneously. I don't
know why I didn't try that before.
The more
Public bug reported:
I found out some inconsistent behaviour when using search-as-you-type in
nautilus file browser. I use Feisty, but the same applies to Edgy IIRC.
Steps to reproduce:
1) Go to some folder in the file browser
2) Type the first few letters of a filename (search box should pop up
Sorry, forgot to mention that.
This only happens in List mode. In Icon mode everything works normally.
--
Double-click not handled correctly after search-as-you-type in file browser
https://bugs.launchpad.net/bugs/117795
You received this bug notification because you are a member of Ubuntu
I got the media keys working on amarok also, but not exactly by the same
way.
I deleted every shortcut from kcontrol, but that didn't help. Then I
deleted every media key from Gnome Shortcuts Applet. After that the
Next and Prev keys started working, but not the Play/Pause. I then
played around
dizastix:
The problem are not the normal key combinations. We are talking about the
special multimedia keys most of the new keyboards today have, like special keys
for muting sound, setting the volume, play, stop, next and prev track etc.
The standard combinations like Win+C etc. have always
Public bug reported:
I cannot see anywhere how much space is free or used on my /
filesystem. I'm using Feisty, bug Edgy had the same problem. I do not
know exactly when it stopped showing up but it might been after upgrade
from Dapper to Edgy.
Specifically, I can check the free/used space of my
Public bug reported:
Binary package hint: gnome-system-monitor
Steps to reproduce:
1. Start Gnome System Monitor, go to File Systems tab
2. Resize any column width
3. Close System Monitor
4. Open System Monitor and go to File Systems tab
What happens:
The columns widths have been reset. This is
Public bug reported:
Binary package hint: restricted-manager
Problems that happened after upgrade from Edgy to Feisty:
I was using fglrx with Edgy (using the xorg-driver-fglrx package from
the official Ubuntu repositories). After the upgrade restricted-manager
told me that some restricted
I don't think that's a duplicate of #89583.
The sole problem in my eyes was that restricted-manager did not remove the
fglrx entry from X.org replacing it with ati.
The Xorg.log said specifically fglrx could not be loaded.
I had to do that manually (or through dpkg-reconfigure xserver-xorg).
clarification:
In the second sentence of my last comment, ...did not remove the fglrx entry
from X.org... should of course be ...entry from xorg.conf...
--
Disabling Ati drivers in restricted manager leaves broken X
https://bugs.launchpad.net/bugs/107856
You received this bug notification
Maybe related:
When compiz is active, and Fade option is deactivated in gnome-compiz-
preferences (Windows tab), clicking on System or Places menu never
brings the menu up, but the depressed effect is there. The
Applications menu works normally.
Furthermore, my deskbar applet that resides on the
In addidtion, I've noticed that after the update, when I maximize
windows. sometimes their titlebar becomes inactive (the buttons don't
work either). Attached a small screencast to show the aforementioned
bugs.
I can confirm that with Feisty final, compiz activated, Radeon 9800 Pro with
'ati'
Found out something new (still don't know if this is relevant here or if
I should open a new bug):
The menus are actually opened, but 100% transparent. If i move the mouse
down, I can click on the menu entries without seeing anything, and the
action gets carried out. Also if I move the mouse over
Public bug reported:
Binary package hint: amarok
I'm using Feisty with Gnome.
Amarok version:
Qt: 3.3.7
KDE: 3.5.6
Amarok: 1.4.5
Every time I start amarok, it uses almost 100% CPU for about a minute.
During this time amarok is not ready. Only some buttons and menus are
displayed, the main
Public bug reported:
Binary package hint: amarok
Using Feisty, with Gnome. This only happens when Beryl is active.
Amarok version:
Qt: 3.3.7
KDE: 3.5.6
Amarok: 1.4.5
When certain analysers (between playback and volume controls, at the
bottom of amarok main window) are active, CPU usage of Xorg
Public bug reported:
Binary package hint: listen
Listen does not save/remember some settings, when it is running and the
user los out of Gnome.
Steps to reproduce:
1. Start listen
2. Change some setting (ie. the volume slider position, or the size of the
playlist areas) and remember what you
Public bug reported:
Binary package hint: beryl
The Beryl Put plugin behaves slighty unexpextedly when moving
maximized windows.
Steps to reproduce:
1. Open Beryl Settings Manager
2. Go to Window Management and activate Put
3. Assign a shortcut to eg. Put on Face 2
3. Go to Desktop 1, open any
I can confirm that. Same problem with Beryl. I haven't found a way to
configure or change that yet.
--
Viewports/Cube - Windows with URGENT hints aren't shown on all Viewports' task
bars
https://bugs.launchpad.net/bugs/102741
You received this bug notification because you are a member of Ubuntu
changed package from beryl-core to beryl-plugins
** Changed in: beryl-plugins (Ubuntu)
Sourcepackagename: beryl-core = beryl-plugins
--
Beryl Put plugin problem with maximized windows
https://bugs.launchpad.net/bugs/108967
You received this bug notification because you are a member of Ubuntu
Qt: 3.3.6
KDE: 3.5.5
Amarok: 1.4.5
Problem still exists.
I found out that if I change the time forward eg. 1 minute, amarok skips
1 minute ahead in the current song. If the remaining song time is less
than 1 minute, the next song in the playlist is played.
--
amarok weird behaviour when
I thought I had the same problem. But if you wait long enough, the
program will respond again after the key generation. Apparently the
generation is taking a long time for some reason.
--
Gaim always crashes with Off-The-Record Messaging plugin
https://bugs.launchpad.net/bugs/97010
You received
This does not happen anymore with Ubuntu 7.04
$amarok --version
Qt: 3.3.7
KDE: 3.5.6
Amarok: 1.4.5
(amarok package version: 2:1.4.5-0ubuntu7)
So I think this had possibly not much to du with amarok itself but other
programs that were updated from Edgy to Feisty (ALSA, etc.?)
--
Amarok
Thanks for checking this with the devs and their bugtracker.
I will try out 1.4.6 when it's out, and report here if it's better.
But since I now know that Amarok wasn't really designed for these big
playlists, I can use the collection and the dynamic playlists more to
avoid these big playlists.
*** This bug is a duplicate of bug 69757 ***
https://bugs.launchpad.net/bugs/69757
** This bug has been marked a duplicate of bug 69757
/ not showing up in df or mount in Edgy
--
root filesystem not displayed anywhere
https://bugs.launchpad.net/bugs/107845
You received this bug
I can confirm this on Feisty.
Since I have both the symptoms described here and in #50406 I suppose it has
the same cause?
Don't know if you needed another confirmation or if this is already fixed, but
since this report is still Unconfirmed and Undecided.
Attached are maybe some relevant lines
I can confirm this.
I just found this bug report (created the duplicate Bug #107845 first).
The same happened for me probably after upgrading Dapper to Edgy, and it
persisted after upgrade to Feisty. Apparently something goes wrong on
some hardware/drive/partition setups during the upgrade from
Confirmed here for amarok.
I created a new bug in KDE bugtracker.
** Bug watch added: KDE Bug Tracking System #145239
http://bugs.kde.org/show_bug.cgi?id=145239
** Also affects: amarok (upstream) via
http://bugs.kde.org/show_bug.cgi?id=145239
Importance: Unknown
Status: Unknown
Public bug reported:
gisomount apparently does not provide .desktop files, thus missing from
the menu and from open with other application... in Nautilus after
installation.
** Affects: gisomount (Ubuntu)
Importance: Undecided
Status: New
--
gisomount: missing desktop files
Easy workaround:
Enable animated pulldown from Right or Left, set delay to 1 usec. The
result is about the same as without pulldown animation and it works
correctly.
--
tilda stays like a gray window
https://bugs.launchpad.net/bugs/144175
You received this bug notification because you are a
Yes this is still happening, exact the same behaviour with:
Ubuntu 7.04
$ uname -a
Linux gondor 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686
GNU/Linux
$ amarok --version
Qt: 3.3.7
KDE: 3.5.6
Amarok: 1.4.7
--
amarok weird behaviour when changing system time
With metacity (standard Ubuntu 7.04, not composited, with nv driver on
an GF 8800 GTS) no high CPU usage can be seen when the analysers are
turned on. The graphically more intensive ones (the last few ones when
clicking through) do cause a bit more CPU usage by the 'Xorg' process
(15% compared to
Public bug reported:
(not sure if I selected the correct package; change it if necessary)
When running Gutsy Beta LiveCD in Vmware Workstation 5.5.2 build-29772, I
cannot change the resolution from System Screen Resolution.
(Host: Ubuntu 7.04 all updates/backports applied, nv driver)
The
Same problem as Tim Hull confirmed also with VMWare Workstation 5.5.2
and Gutsy Beta 1 (Desktop-LiveCD and Installed), Feisty Host.
--
installer and livecd should detect vmware mouse device and use the right driver
https://bugs.launchpad.net/bugs/71167
You received this bug notification because
Still having the problem with newest Gutsy (all post-beta updates
included). Is the fixed version going to be in Gutsy Final? Because with
this bug Tilda is unusable.
--
tilda stays like a gray window
https://bugs.launchpad.net/bugs/144175
You received this bug notification because you are a
This problem is fixed for me in the latest Gutsy. When Failsafe X comes
up after broken mouse driver entry, pressing Continue starts failsafe
GDM correctly with working mouse.
--
failsafe x fails to recover from bad mouse driver
https://bugs.launchpad.net/bugs/151206
You received this bug
Public bug reported:
I ran into this accidentally while testing stuff. I don't know if it's
affecting anything, failsafe X seems to work normally.
I intentionally broke the mouse driver entry in xorg.conf. Failsafe X
came up and I started the failsafe GDM. Then without logging in or
chaning
Works, the error message is gone.
--
failsafeXServer: line 47: [: too many arguments
https://bugs.launchpad.net/bugs/151388
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Áron:
Can you revert then to the old (feisty) version for gutsy? Because, really
what's the point of having some software in the archive that's broken. And I
saw no big flaws or bugs in the old version anyways.
--
tilda stays like a gray window
https://bugs.launchpad.net/bugs/144175
You
OK then I would declare it as an UI bug. It should at least say that
instead of just wait a moment please.
--
Gaim always crashes with Off-The-Record Messaging plugin
https://bugs.launchpad.net/bugs/97010
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Thanks BrowneR, that script works perfectly.
Since Amarok won't fix this until 2.0, I think it would be great and
also in the spirit of Ubuntu (it just works) to include it in the deb.
--
Multimedia keys not working in Feisty (no need to confirm behavior anymore)
Ah, I'm sorry, I have since replaced my Ati card with an Nvidia one.
restrictred-manager did not install the correct driver for my Geforce
8800gts either, but that's another problem and probably already known.
So if nobody else has this problem, this bug can probably be closed
since I'm not able
Sarah, could you explain why you set this to Wontfix? Is there no
possibilty for BrowneR's script to be installed automatically only for
Amarok/Gnome users? And if not, shouldn't this remain open anyway till
2.0 is released and if it's fixed then, the bug can be closed.
--
Multimedia keys not
Public bug reported:
When installing picard from Ubuntu Feisty universe repositories,
libtunepimp5-mp3 will not get installed automatically and so picard will
have no mp3 support. Users have to go searching the internet for a
solution.
IMHO the picard package should at least recommend
*** This bug is a duplicate of bug 206583 ***
https://bugs.launchpad.net/bugs/206583
Reproduced and confirmed on up-to-date Ubuntu 8.10.
** Changed in: gnome-system-monitor (Ubuntu)
Status: Incomplete = Confirmed
** This bug has been marked a duplicate of bug 206583
System Monitor
*** This bug is a duplicate of bug 206583 ***
https://bugs.launchpad.net/bugs/206583
Actually, it only does not work when lowering nice value. When raising, it
works ok.
There is already a bug report about that, marked this as a duplicate.
--
Changing priority will not stay at new value
Public bug reported:
This is a regression. It worked in Hardy, but not in Intrepid anymore.
System:
Dell Latitude D630 Laptop
Kernel:
Linux 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux
Intrepid fully patched.
Bug description:
When pressing Fn-F3 nothing happens. On Hardy,
Loic: The problems appears to be that cairo adds a newline character
(0x0A) at the end of any binary type 1 font definition in the PDF. This
is the thing that the patch fixes, so you can check for that.
Since I'm not really familiar with the PDF file format, and the font
definitions/declarations
After a completely fresh install of Ubuntu 9.10 64bit, the problem is
gone for me.
--
Help does not work in gnome-power-preferences
https://bugs.launchpad.net/bugs/410804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Merijn, you can use the packages from
https://launchpad.net/~janne-hyotyla/+archive/jhyotyla
for the time being. The fix is integrated there.
I added this info to the bug description so that it doesn't get lost in
the comments.
** Description changed:
Binary package hint: cups
When
Confirmed as well after today's update.
--
Restart button did not restart Firefox after update
https://bugs.launchpad.net/bugs/466353
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm reopening this. Bug #429914 has this problem, the GNOME bug #595287
is not found.
** Changed in: launchpad
Status: Fix Released = Confirmed
--
Launchpad couldn't extract a status on GNOME Bug Tracker
https://bugs.launchpad.net/bugs/341176
You received this bug notification because
Problem went away after upgrade to 1.5.1~git2260a87-0ubuntu1
** Changed in: banshee (Ubuntu)
Status: Confirmed = Fix Released
--
Banshee won't start - no error messages
https://bugs.launchpad.net/bugs/411799
You received this bug notification because you are a member of Ubuntu
Bugs,
For me (Dell Latitude D630, IWL3945) kernel #lp430809v3 + DKMS v4
package works almost perfectly, but there remains a bug in the switching
logic:
Now the killswitch acts on both bluetooth and wlan although I have set in BIOS
for it to only act on bluetooth.
Apart from that BT/WLAN are now
Daniel: look at the comments in Bug #430809
For me (Dell Latitude D630, IWL3945) kernel #lp430809v3 + DKMS v4 package works
almost perfectly, but there remains a bug in the switching logic:
Now the killswitch acts on both bluetooth and wlan although I have set in BIOS
for it to only act on
Forgot to mention: BIOS setting is still BT only
dmesg output directly after turning bluetooth off via applet, having had
killswitch off (so WLAN and BT on):
[ 1108.968678] dell_rfkill_query called for radio 1.
[ 1108.969569] Query returned the following raw data:
[ 1108.969572]
Not yet working correctly with Dell Latitude D630:
Previous bugs were fixed, but a new one introduced:
Killswitch is off, I switch bluetooth off via bluetooth-applet, and now WLAN
(phy0: Wireless LAN) gets turned hard off. When I flip the killswitch on and
back off, WLAN turns on again.
Mario thanks a lot for debugging and fixing this. Everything mostly
works now, just a small nitpick remaning:
I start w/ killswitch off (0), then switch BT off by software (1), the
BT indicator LED turns off. Then I turn killswitch on (2) and off again
(3); now the BT indicator turns on again
Mario: dkms v0.4 works.
--
[Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill
switch
https://bugs.launchpad.net/bugs/430809
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I noticed just now that I also hear the bell again.
I have a Dell Latitude D630.
snd_pskp und pcspkr are blacklisted and do not appear in lsmod
(attached).
You'll notice several new reporters in the last 24h in this bug. Could
this have something to do with the kernel update to 2.6.31.14 from
Bobenceto: I have the same problem, I left it out of this report to not
confuse things further.
Alexander: Do you want to have wlan killswitch problems also in this bug
or should this go in a new one?
--
MASTER dell-bluetooth - confusing/contradictory bluetooth killswitch status /
rfkill
Ah I just saw: Bug #441161 is exactly the wifi killswitch problem you
and I experience Bobenceto. So we should move any discussion of it to
that bug and leave this for bluetooth only.
--
MASTER dell-bluetooth - confusing/contradictory bluetooth killswitch status /
rfkill behaviour - potential
Added iwl 3945ABG to subject; this problem occurs on my Dell D630
Latitude with said intel chip.
** Summary changed:
- [karmic][iwlagn][dell-wifi] MASTER wireless disabled for IWL 4965 5100 and
5300 devices if booted with killswitch/rfkill enabled
+ [karmic][iwlagn][dell-wifi] MASTER wireless
Was this supposed to be fixed already? I just got a crash apparently in
libstaticswitcher.so, see Bug #446696
--
compiz.real crashed with SIGSEGV in handleEvent()
https://bugs.launchpad.net/bugs/430518
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Could this be related to the install/upgrade path to the current karmic.
I did a fresh install between alpha 3 and 4 and have been continuously
upgrading since then.
--
Help does not work in gnome-power-preferences
https://bugs.launchpad.net/bugs/410804
You received this bug notification
I confirm that with mainline 2.6.31.3 everything works as it should here,
specifically:
If I have configured in BIOS that the killswitch only acts on bluetooth, WLAN
stays on whether the killswitch is on or off during boot.
With the current karmic kernel, I have the same behaviour as in comment
See also
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/441161/comments/26
and following comments.
With mainline kernel 2.6.31.3 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.31.3/ normal functionality
is restored.
I.e. independent on whether I boot with killswitch on or off, I
Public bug reported:
Binary package hint: evince
This was fixed for firefox (Bug #414114), but I'm using Opera as my
default browser, so I still cannot open URLs from evince.
dmesg:
[104214.627826] type=1503 audit(1256741527.803:22): operation=exec pid=21973
parent=21970
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34542659/Dependencies.txt
** Attachment added: KernLog.txt
http://launchpadlibrarian.net/34542661/KernLog.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/34542662/ProcMaps.txt
** Attachment added:
This still does not work if using another default browser (Opera in my
case) -- I opened Bug #462675
--
Apparmor profile disallows hyperlinks
https://bugs.launchpad.net/bugs/414114
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Question:
I still have firefox-3.0 installed, so apparently this forceful
upgrade did not happen yet. Is it of any help in future testing if I
leave the firefox-3.0 installed for now, or can I manually remove it
already?
--
[karmic] Firefox 3 menu entry opens Firefox 3.5
Martin:
Muting the beep control in alsamixer solved my problem.
Previously the volume of the control was set to 00 but it was not muted,
and this produced the ugly and extremely loud beeps (especially on
headphones).
I don't know whether I have ever changed that control. But I installed a
fresh
1 - 100 of 302 matches
Mail list logo
