*** This bug is a duplicate of bug 439448 ***
https://bugs.launchpad.net/bugs/439448
** This bug has been marked a duplicate of bug 439448
Visual corruption affecting several panel applets
* You can subscribe to bug 439448 by following this link:
I don't agree with the justification but the upstream linux kernel bug
(#15313) has been closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/518818
Title:
ath9k driver not working properly with
I have previously downloaded (starting at comment #52) compat-
wireless-2010-09-12 from http://www.orbit-lab.org/kernel/compat-
wireless-2.6/ and reported success with my ath9k NIC and several others
have done also with the same result.
What I have noticed since is that while this is working
Well nearing 24hours later and 'compat-wireless-2010-09-12' has
certainly fixed my wifi dropouts. I agree with Franck, Is there a chance
that linux-backports-modules-wireless-maverick-generic shipping with
Ubuntu 10.10 final gets updated to this version ?
--
ath9k driver not working properly
I've just downloaded and installed the ath9k module from 'compat-
wireless-2010-09-12' and it seems after 30min of testing that my problem
may be resolved. I will report back after more testing.
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received
Also affected by this bug. uploading apport info now
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER
apport information
** Attachment added: AcpiTables.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567626/+files/AcpiTables.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a member of
apport information
** Attachment added: AlsaDevices.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567627/+files/AlsaDevices.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a member
apport information
** Attachment added: AplayDevices.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567628/+files/AplayDevices.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567633/+files/BootDmesg.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a member of
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567642/+files/Card0.Amixer.values.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567652/+files/Card0.Codecs.codec.0.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because
apport information
** Attachment added: Card1.Amixer.values.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567654/+files/Card1.Amixer.values.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because
apport information
** Attachment added: Card1.Codecs.codec.0.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567655/+files/Card1.Codecs.codec.0.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because
apport information
** Attachment added: Card1.Codecs.codec.1.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567656/+files/Card1.Codecs.codec.1.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because
apport information
** Attachment added: Card1.Codecs.codec.2.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567657/+files/Card1.Codecs.codec.2.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because
apport information
** Attachment added: Card1.Codecs.codec.3.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567658/+files/Card1.Codecs.codec.3.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567659/+files/CurrentDmesg.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a
apport information
** Attachment added: Dependencies.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567660/+files/Dependencies.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a
apport information
** Attachment added: IwConfig.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567661/+files/IwConfig.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a member of
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567662/+files/Lspci.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567663/+files/Lsusb.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: PciMultimedia.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567664/+files/PciMultimedia.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567665/+files/ProcCpuinfo.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a member
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567667/+files/ProcModules.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a member
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567666/+files/ProcInterrupts.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a
apport information
** Attachment added: RfKill.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567668/+files/RfKill.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567669/+files/UdevDb.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/518818/+attachment/1567670/+files/UdevLog.txt
--
ath9k driver not working properly with AR9285
https://bugs.launchpad.net/bugs/518818
You received this bug notification because you are a member of
I am feeling the affect of this too. Sometimes its works well but usually its
so slow it's unusable. This is on my wireless connection and I am unable to
test (due to my particular setup) the wired connection.
From lspci:
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan]
Can you please let us know what the fix was?
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
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
Ok,
I've found a fix that works for me. I was find that if I didn't shut down my
computer gracefully (and there letting /etc/init.d/alsa-utils run it's stop
procedure) that the sound levels would be set and un-muted on next boot.
Therefore, I commented out line 372 in /etc/init.d/alsa-utils:
#
Hi PTN,
Yeah my bad. Upon further investigation, my suggestion wasn't working as
I thought it was
Keep looking
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
For me, manually running /etc/init.d/alsa-utils restart will unmute the
sound.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have been running Ibex since it was released even with everything up-
to-date, I am experiencing this. I too can confirm that disabling the
plain text plugin fixes the error.
--
evolution does not recognize a meeting
https://bugs.launchpad.net/bugs/231091
You received this bug notification
Updated to NM 0.7~~svn20080928t225540+eni0-0ubuntu2 and rebooted. Upon login it
asked for my WEP key again so I entered it. :(
Then I rebooted again and logged back in and hey presto! I was connected
without having to re-enter my WEP key. It seems that entering the key one more
time after
Where do you D/L 0.7~~svn20080928t225540+eni0-0ubuntu2~nm3~hardy1 ?
--
Network Manager does not remember WEP/WPA key
https://bugs.launchpad.net/bugs/36651
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I get the following messages (and plenty of them) when I run EVO from a
shell:
(evolution:14569): calendar-gui-CRITICAL **: e_day_view_add_event:
assertion `end add_event_data-day_view-lower' failed
(evolution:14569): calendar-gui-CRITICAL **: e_week_view_add_event:
assertion `end
I personally wouldn't want a bookmark for a one-time open of a remote location.
I know that bookmarking is what we have to do as the momentary fix but we need
this fixed upstream. If you look at the upstream activity
(http://bugzilla.gnome.org/show_bug.cgi?id=520390), there has been some
Last set of updates has fixed the issue for me. I am using the nVidia
new drivers. Thankyou!
Packages installed:
ii compiz 1:0.6.0+git20071008-0ubuntu1
OpenGL window and compositing manager
ii compiz-core
Have also now test on two other PC's (one with proprietry nVidia and the
other with Intel 945 graphics) and both are working.
--
[MASTER] broken initial stacking (was: compiz hides quick loading windows at
login)
https://bugs.launchpad.net/bugs/147943
You received this bug notification because
Unjustified status change. This problem is not fixed.
--
[MASTER] broken initial stacking (was: compiz hides quick loading windows at
login)
https://bugs.launchpad.net/bugs/147943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I too can confirm that the latest update to 1:0.6.0+git20071006-0ubuntu2
has not had any affect towards resolving this issue.
--
[MASTER] broken initial stacking (was: compiz hides quick loading windows at
login)
https://bugs.launchpad.net/bugs/147943
You received this bug notification because
I have three PCs, two desktop with nVidia cards and one laptop with
Intel 945 and the last Compiz fixes have not helped. I noticed that in
todays updates that there is new gnome-panel patches and I was hopeful
that it may have helped the situation. But alas, the problem still
persists on all three
Problem still persists with todays update:
ii compiz 1:0.6.0+git20071004-0ubuntu2
OpenGL window and compositing manager
ii compiz-core1:0.6.0+git20071004-0ubuntu2
OpenGL window and compositing manager
ii
I have applied todays updates (of which compiz
(1:0.6.0+git20071004-0ubuntu1) gutsy was included) and the problem still
persists.
--
[MASTER] broken initial stacking (was: compiz hides quick loading windows at
login)
https://bugs.launchpad.net/bugs/147943
You received this bug notification
As of the last compiz updates (0.6.0.x), this problem is still
occurring.
Packages installed:
[EMAIL PROTECTED]:~# dpkg -l | grep compiz
ii compiz 1:0.6.0+git20071002-0ubuntu1
OpenGL window and compositing manager
ii compiz-core
This is happening to me too but it is only the bottom panel that does
not show. I can also make it show by clicking on where the panel should
be. When I maximise a window, they have the correct geometry, so it
knows the panel is there, but it takes a click to make it display.
--
panels are
This is happening for me on a Dell desktop with a nVidia GPU and also a
HP Pavilion Laptop with Intel graphics. I would suggest to not use the
work-around in the compiz settings as then you will have be mindfull
that this has been done when testing fixes. Either restart the panel or
click on it
Withdrawing my previous comment as it is a better fit for Bug# 147070
than here.
--
panels are invisible when Compiz Fusion run
https://bugs.launchpad.net/bugs/139749
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I have added an additional comment to the upstream bug you make
reference to.
--
Rythmbox should scan for new music on start by default
https://bugs.launchpad.net/bugs/144334
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Just an update. I have not had this issues with this for about a week
now. Sorry for my tardiness in updating this bug.
--
Can't have two slashes error while loading configuration
https://bugs.launchpad.net/bugs/41803
You received this bug notification because you are a member of Ubuntu
Bugs,
I can confirm that it is happening for me on two Dell PC's with Gusty
Tribe-5 + current updates. I too can confirm that it seems to be only
happening on desktop machines. For example, I can run 'setkeycodes e000
12' successfully on my laptop but the same command fails on my desktop
no matter what
Public bug reported:
For the sake of usability, Rhythmbox should have the preference option
of Watch my library for new files enabled by default so people do not
have to remember to re-import their collection.
** Affects: ubuntu
Importance: Undecided
Status: New
--
Rythmbox
Here's my logic, tell me if it's wrong:
People don't submit bug reports when things are working and when this was
working (before the last updates) for the nVidia users, it seems that there
were also no complaints from the ATI users. The wrapper may need to be patched
and if it breaks for ATI
Public bug reported:
Binary package hint: compiz
Currently running Gutsy Tribe-5 + updates on a Dell PC and Desktop Effects were
working. Since applying updates today, desktop effects no longer work.
The following output is what I get when I run gnome-appearance-properties from
gnome-terminal:
** Attachment added: List of installed packages
http://launchpadlibrarian.net/9390626/PackageList.txt
--
Suddenly unable to use Desktop Effects
https://bugs.launchpad.net/bugs/141136
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
As of today, I have been hit with this bug too. Here is the output:
[EMAIL PROTECTED]:~$ gnome-appearance-properties
/bin/sh: /usr/bin/esd: not found
nvidia_new restricted driver is already enabled
Checking for Xgl: not present.
Detected PCI ID for VGA: 01:00.0 0300: 10de:014e (rev a2) (prog-if
I did search first but after submitting this bug, I then discovered that
it is a duplicate of Bug #124519. Therefore this one needs to be closed.
--
Suddenly unable to use Desktop Effects
https://bugs.launchpad.net/bugs/141136
You received this bug notification because you are a member of Ubuntu
Duplicate of Bug #124519
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
Suddenly unable to use Desktop Effects
https://bugs.launchpad.net/bugs/141136
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
May I add that my above comment is for Gutsy Tribe5 + latest updates.
--
need to add max texture size check
https://bugs.launchpad.net/bugs/124519
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
As of todays updates, I have not been able to re- create the fault and
that is without about 6 reboots now.
--
[Gutsy] NetworkManager fails at startup: waitpid () from /lib/libpthread.so.0
https://bugs.launchpad.net/bugs/139966
You received this bug notification because you are a member of
Sorry for posting again but I was also able to fix it by changing line 222 in
/usr/bin/compiz from:
TEXTURE_LIMIT=$(glxinfo -l | grep GL_MAX_3D_TEXTURE_SIZE | sed
's/.*=[^0-9]//g')
to:
TEXTURE_LIMIT=$(glxinfo -l | grep GL_MAX_TEXTURE_SIZE | sed 's/.*=[^0-9]//g')
--
need to add max texture
@unggnu - I have added my comments as suggested to the bug in
GnomeTracker and also included another copy of the daemon.log with the
portion pertaining to wpa_supplicant
** Attachment added: daemon.log output - wpa_supplicant failure
http://launchpadlibrarian.net/9366742/wpa_supplicant1.txt
I am unsure of the relevance but I had also had issues with the network manager
applet not loading. I try to restart the network service
(/etc/init.d/networking) but to no avail. The only option is to reboot the
computer. This is with the ipw3495 chipset btw.
Attached is the relevant section of
I think this is relevant here: I have also had issues with the network manager
applet not loading. I try to restart the network service
(/etc/init.d/networking) but to no avail. The only option is to reboot the
computer. This is with the ipw3495 chipset btw.
Attached is the relevant section of
Yes it is the daemon crashing and the bug you refer to has the same output in
the daemon log. Trying to start NM will only end up with another crash.
Does this bug need to be re-allocated/categorised?
Anyhow, here is my daemon.log output to show that I am having the same
symptoms.
** Attachment
Further to my last post, I am experiencing this on Gutsy Tribe5+Updates.
The applet itself seems fine, it is the daemon causing the issue.
--
nm-applet vanished from tray
https://bugs.launchpad.net/bugs/43379
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
I was meaning to try that as suggested but since then, I have applied
todays updates in order to see if Bug #140469 is still an issue and do
you think that the NM daemon wants to crash? It's behaving itself at the
moment. I'll have to wait for it to happen again I suppose.
--
nm-applet vanished
The NetworkManager daemon has died again (I had a good run of about four
reboots though!) and as suggested I killed wpa_supplicant prior to
restart NetworkManager - It worked! Looks like wpa_supplicant is the
culprit huh?
--
nm-applet vanished from tray
https://bugs.launchpad.net/bugs/43379
You
I have tested one more of the three machines affected and this one is using a
wired connection. After running all the updates and partial dist upgrade this
morning, I had to do the old disable enable networking after I rebooted.
Attached is the daemon.log.
** Attachment added:
Confirmed to be now working on one of the three machines that has been
experiencing this. Wont not be able to confirm those for a few days.
--
[Tribe5] Need to de-activated and re-activated to work right
https://bugs.launchpad.net/bugs/134267
You received this bug notification because you are a
Running Gutsy Tribe5 with the latest updates and I have had this message appear
too.
My Network-Manager is:
ii network-manager0.6.5-0ubuntu10
network management framework daemon
ii network-manager-gnome 0.6.5-0ubuntu8
Running Gutsy and just applied the most recent updates. As of today, I have
started getting '*' in the password mask too.
Version of GDM installed:
ii gdm2.19.8-0ubuntu2
GNOME Display Manager
--
gdm circles vs asterisks in password
Also confirmed. I have seen this happen on three machines now. Attached
is the daemon.log log from when it happended today.
** Attachment added: daemon.log - Wired connection fails
http://launchpadlibrarian.net/9160114/daemon.log
--
[Tribe5] Need to de-activated and re-activated to work
76 matches
Mail list logo
