You guys control this and can do what you think is best, but the reason
I noted this as a 'bug' way back in 2016 is because I had a HD failure
and only was made aware of it when i ran smartmontools from cli. I would
think that an average user would install this package (smart-notifier)
and expect
Still an issue with 18.04. FWIW, it is included in the Arch version of
Gnome and gvfs-nfs works in Arch. Both in Nautilus and in DejaDup. NFS
should also be a possible means of a backup with deja-dup, but because
this module is not included in gvfs, it does not work. Waiting for this
regression to
Postponing this for 18.10 would be a problem, IMO. Please include it in
18.04.x (LTS). This missing package not only does not allow a Nautilus
browse, it also breaks deja dup nfs functionality as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
gvfs will not allow an NFS mount.
In nautilus, one cannot mount an NFS mount using 'other locations'. If a
valid url is typed, (nfs://IP _ADDRESS/MOUNT_POINT one can never select
'connect' as it is always greyed out.
Fully up to date ubuntu 18.04. Duplicates same behavior
Please, can't we just remove this STA driver from Ubuntu. IMO, it is not
worth the effort and it is pulling resources from other issues/bugs that
can actually be fixed. This STA driver has been a problem because
Broadcom does not want to work with open source. The resolution of
incompatibilities
My experience with this driver or any broadcom wl or wl/bt card is that
it is too much trouble to deal with. I pulled both of them I had and
replaced them with Intel cards which have great support and 'just work'.
Amazon or newegg or wherever has great intel cards that work for about
$25.00. It
Fix released! Awesome. Is there a link to anything that will allow me to
verify that it is fixed? Is it in the current 16.04 kernel? 16.10?
17.04? Upstream?
Thanks.
Keith
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Running 4.4.0-64 in 16.04. This is definitely a flaky wireless driver.
If I turn it off, and back on I cannot browse any ssids. If I suspend
and resume, I cannot browse any ssids. I have recently added the options
to the /etc/modprobe.d/rtl8821ae.conf file "options rtl8821ae ips=0
fwlps=0" It is
Same deal in 16.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598896
Title:
Warning from smart-notifier
To manage notifications about this bug go to:
Also does not work in 16.10. Same error:
$ smart-notifier
/usr/share/smart-notifier/smart_notifier/gui.py:23: PyGIWarning: Gtk was
imported without specifying a version first. Use gi.require_version('Gtk',
'3.0') before import to ensure that the right version gets loaded.
from gi.repository
Same here. Adding the line to /etc/hosts with the .local works. The printers
are automatically detected (as expected) and auto populate the printers. I did
not have to go to the cups web interface to add them. Without the .local, it
does not work.
Has worked with every release since 11.04. This
This package no longer works with the current smartmontools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598896
Title:
Warning from smart-notifier
To manage notifications about this bug go to:
I get loginloop where it is trying to set the video mode but just
resets. I cannot even login to a terminal as it constantly wipes it out
and sends me to tty7. My card is:
*-display
description: VGA compatible controller
product: G71GL [Quadro FX 3500] [10DE:29D]
It is also a regression, isn't it? It appears that mail is set up, but
it is mailed to root and it is uncommon for a user to log in as root...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646886
Public bug reported:
This package is broken. The smartmon tools use commands which are no
longer in 16.04.
Example:
/etc/smartmontools/run.d/10powersave-notify
#! /bin/sh
# Send message if /usr/lib/powersave/powersave-notify exists or exit silently
[ -x /usr/lib/powersave/powersave-notify ]
Public bug reported:
Previously (12.04 - 15.04), if I edited the /etc/systemd/logind.conf
file to auto suspend the GDM login screen it worked. Now, if I edit the
2 lines to cause a suspend if the login screen (GDM) is up and no one
logs in for 15 minutes, I get unintended random suspend from an
Well, It does not work for me.
I went to the archives. I grabbed the 6.30.223.141-1 archive. Unpacked it. Put
the edited files from the patch above in the amd64 directory and built the
module. To get it to build, I had to edit the MAKEFILE to add this EXTRA_CFLAGS
"-Wno-error=date-time" as it
Just spent some time trying to do this. Can you please give more
'recipe' type instructions. If I install the driver, I get the fully
compiled driver. If I install the source, it also compiles and installs
the 'wl' driver.
Also, the current version of 16.04 no longer has that older STA package.
I'm interested in this. If you go to Broadcom, though, there is a later version
of the driver.
http://www.broadcom.com/docs/linux_sta/hybrid-v35-nodebug-pcoem-6_30_223_271.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
May be due to edit of /etc/systemd/login.conf edited to suspend computer
if login screen is up. uncommented:
#IdleAction=suspend
#IdleActionSec=15min
and saw the behavior.
re-commented and have not seen the behavior. This edit has worked to suspend
the gdm login screen since 12.04 to 15.04.
I have some older hardware (Core 2 Duo 1.5) and unless I disable
tracker, the computer is unusable. CPU 100%, CPU temps up to 85C. With
it disabled, CPU idles at 47 and the old laptop is, at least, useful for
light browsing, email, etc. Using Gnome shell. I have no clue what it
is doing, but it
I installed 16.04 on 3 machines. One gigabyte AMD/nvidia 361.42, One
Dell Core 2 Duo/Nvidia 304.131 and one Dell Inspiron Laptop i915 with
default video driver. All 3 do this randomly. I am working along typing,
mousing, reading, etc and the computer suspends. It always resumes
correctly. I need
how about 16.04? It does not hang any more, but the message is still
repeated many times in the dmesg log:
[1.940071] [ cut here ]
[1.940109] WARNING: CPU: 1 PID: 6 at
/build/linux-Ay7j_C/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326
drm_wait_one_vblank+0x1b5/0x1c0
Public bug reported:
I have seen this with 15.10 and now with 16.04. Am running a fresh/clean
install 16.04LTS (not upgraded) with Nvidia driver (361.42). I have a
firefox browser open and when browsing, it will just suspend randomly. I
am typing or mous-ing and it suspends. I do have the UI set
I do not know why this is associated with nvidia-graphis-drivers-304 as
I am running 361.42
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574127
Title:
Random suspend when working
To manage
running 15.04 with the nvidia 304.131(proprietary, tested) and get a
similar result:
Inconsistency detected by ld.so: dl-version.c: 224:
_dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
The binutils installed is 2.25-5ubuntu7
I get this on another machine with the nvidia
ethany,
I do not really remember. Try 13.04 (and 12.04 if it is still in 13.04).
It was one of those, IIRC, that did not have it. Problem is that so much
has changed in the kernel since then. I went through a huge kernel
bisect project to then be told to report it to the kernel i915 group and
got
I still get this:
[1.968043] [ cut here ]
[1.968074] WARNING: CPU: 0 PID: 85 at
/home/kernel/COD/linux/drivers/gpu/drm/drm_irq.c:1216
drm_wait_one_vblank+0x1b5/0x1c0 [drm]()
And it is way laggy. 15.10 is unusable for me with any of these kernels
(stock, latest,
Christopher,
I grabbed kernel 4.4.0-040400rc3-generic as it shows as the latest. I
installed it and get the same messages in the dmesg log. I do note that
the fans are not running so fast. I have been having problems where it
will overheat and shut down. Never had that problem with 15.04 or
Just loaded ubuntu 15.10 (kernel 4.2.0-18-generic) and it is still
there.
Interestingly, I have this as well:
CPU: 1 PID: 1276 Comm: Xorg Tainted: GW 4.2.0-18-generic
#22-Ubuntu.
I do not know why it is tainted as I did not install any private
modules. on the 'Software & Updates"
It failed to build for me as well. Ib jumped through lots of googling
and found a couple patches which show it to build, but it never worked
fur me. I can see ssids, but never connect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Grabbed all the patches from the 4 corners of the internet to have it
compile on 3.19. Compiles, Installs, shows a list of only the 2.5Ghz
ssids, but will not connect to them. I have never been able to get this
laptop to connect using the STA driver. This behavior is the same as
when I install
Just upgraded to 15.04. I still get the error and sometimes it will not
shut down and takes a long time to reboot.
Is this just that the i915 driver is not very good or that my hardware
is not well supported?
# lspci
...
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
I have an Inspiron 1525 and among its many problems is low volume. Max volume
feels like half volume at best. Running 14.04 with recent kernel:
3.13.0-40-generic
$ cat /proc/asound/card0/codec* | grep Codec
Codec: Conexant ID 2c06
Codec: Silicon Image SiI1392 HDMI
Codec: SigmaTel STAC9228
$
? I do not fully understand your request. As you said, this was a
failure to resume bug. That bug has been resolved. I am currently
running the current kernel with ubuntu 14.04 and allowing it to update
as time progresses. (apt-get dist-upgrade)
I still have tons of errors in my dmesg. I have
I guess I don't fully get your response. This has been noted as a bug
since saucy and has never had a patch or workaround associated with it
(other than using bluman instead of gnome-bluetooth). Is there a better
bug list for gnome specific problems than here?
--
You received this bug
Still a problem in 14.04LTS. Had to revert to using bluetooth manager,
again. Works every time with bluetooth manager.
Why has this not been addressed?!?!?!?!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sounds like a rewrite is in order. Blueman always works for me. Gnome
Bluetooth is pretty well broken, IMO.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/551950
Title:
gnome-bluetooth cannot use
this is a CD/DVD drive problem and I believe it has been fixed upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/892768
Title:
Slow boot with ata4.00: failed command: IDENTIFY PACKET DEVICE
Still broken in 13.10. You can select special pin, but not continue to
pair it. It is a shame this has been broken for so long and such a
simple repair. My work around is to use bluetooth manager instead of
gnome bluetooth.
--
You received this bug notification because you are a member of Ubuntu
3.16.0 - still messages in the log, but it will now suspend and resume
with ubuntu GNOME 14.04 and the 3.16.0 kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324935
Title:
[Dell Inspiron
I don't think it is 'fixed' as I still get my log filled with the error
message, but I can use hardware acceleration and it will suspend and
resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I finished the bisect. I am running xubuntu 14.04. I pulled mainline
kernels v3.6 which worked without error and v3.7 which exhibited the
error. I then bisected between the 2. It took 14 steps and concluded
with this which makes more sense:
24929352481f085c5f85d4d4cbc919ddf106d381 is the first
The dmesg from this version of the kernel (different line number in the
*.c file) is attached.
Keith
** Attachment added: dmesg output from the failed commit
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/+attachment/4163777/+files/249293_dmesg.txt
--
You received this bug
yes, it is still present. dmesg attached.
** Attachment added: dmesg with 3,16-rc6
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/+attachment/4163968/+files/dmesg-3.16_rc6.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Can you explain something to me. Does v3.6.0-rc7 come before v3.6.0? I
thought that release candidates preceeded the release. I am running yet
another bisect, this time good is v3.6 and bad is v3.7. I cannot tell
where bisect is in the tree while it is running, it just reports UUIDs
as it runs,
Now I am at step 8 and the kernel is linux-image-3.5.0-rc4. What am I
doing wrong? I would guess that the first bisect would be 3.6.x
(somewhere between v3.6.0 and v3.7.0).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since I was unable to successfully use git bisect, I decided to take
another tack. I am running 14.04 no mods or edits, just a simple unstall
of Xubuntu. I installed the b43 driver so the wifi works. If I try to
install and 'install updates', the install crashes. I installed then did
an 'apt-get
fwiw, I grabbed the latest kernel and the bug is still there. I built
v3.16.0-rc5 and still get this filling the log:
l WARNING: CPU: 1 PID: 1143 at drivers/gpu/drm/i915/intel_display.c:10101
intel_modeset_check_state+0x5f3/0x7a0 [i915]()
[ 115.283641] encoder's hw state doesn't match sw
This is too far out of my league. I need more guidance. This bug appears
to be imtermittent. I have certain kernels which have never exhibited
this error in the dmesg. I have others which sometimes show it. I have
built well over 30 kernels on this laptop and it is like trying to find
a needle in
I kept seeing it and eventually built v3.8.0 and it 'appeared' to not
show the error. I thought I had found it and started another bisect
between the commits for v3.8.0 and v3.8.1, but when I tried to boot back
to v3.8.0, the error in the log showed up. It was not there previously.
Now if I reboot
I have no clue what is going on. I have started building kernels from
v3.8.13 and back. So far all fail. I am at v3.8.7 and still have the
dmesg error. It is not clear from the ubuntu kernel to mainline map as
to which is/should be the version that I have on there which works
without error. The
I rebooted to 14.04 again and built the kernel from that commit,
installed and rebooted 14.04 and the error still shows in the log.
Previously, I was using 13.04 as the base. I guess I will continue to
buils kernels backwards from here until it goes away. Any other
suggestions? I wonder if this is
So far I have tested 5 back and still have the error. Isn't this what git
bisect is supposed to do? At this rate I'll be compiling for a week, one at
a time.
On Jun 28, 2014 2:55 PM, KeithG 1324...@bugs.launchpad.net wrote:
it turned up bad. I am going one back from
I started with commit c40e36... and worked back according to the git
log. The last 'good' build was fb72a0... The next commit breaks it.
c40e3641670eb6ebfdb71d4b0c775416ef95f4f0 bad
e651eab0af88aa7a281fe9e8c36c0846552aa7fc bad
7fb476c231bbc551ede5b4afb189d9ca5ab7406d bad
Yes. Bisecting between commits actually did that for me. My 8th pass
used commit c40e3641670eb6ebfdb71d4b0c775416ef95f4f0 which was 'good'
and was the next older commit. The next newer commit was the 9th pass
which used commit 8164f7af88d9ad3a757bd14f634b23997ee77f6b which was
'bad'. Should I
It seems odd as the diff shows only changes to the arm branch of the
code. the result of the lshw command are attached.
** Attachment added: lshw
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/+attachment/4141378/+files/lshw.txt
--
You received this bug notification because
Christoper, I am not sure. My second git bisect was done using commits
as the end points and not versions. I tracked the commit numbers as
bisect did its work and it appeared that the 8th run actually built to
that commit. I have done a git pull to the commit right before this
it turned up bad. I am going one back from that.
e651eab0af88aa7a281fe9e8c36c0846552aa7fc. and will test that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324935
Title:
[Dell Inspiron 1525]
Christopher.
I used the commit numbers and did the bisect again. Now it points to one
commit which causes the error:
8164f7af88d9ad3a757bd14f634b23997ee77f6b is the first bad commit
commit 8164f7af88d9ad3a757bd14f634b23997ee77f6b
Author: Stephen Boyd sb...@codeaurora.org
Date: Mon Mar 18
Christopher.
I think know how to do those steps. Is it important that I git clone
again? Should my repository be linux-stable? Mine is currently ~/linux
I was able to build commit ed34add734e33afa33e7bf5ee5826650efdc0fe8 and
that works.
I am confused as to how to go about selecting which
. Penalver
christopher.m.penal...@gmail.com wrote:
KeithG, you would just build your kernel up to a commit in the middle
and see where you stand specifically.
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1324935
Title
I guess the bisect has run to its completion. 10 trials between v3.9 and
v3.10. The output of my last 'git bisect bad' is this:
The merge base c1be5a5b1b355d40e6cf79cc979eb66dafa24ad1 is bad.
This means the bug has been fixed between
c1be5a5b1b355d40e6cf79cc979eb66dafa24ad1 and
do not remember
which kernel version was the last 'good' one.
Keith
On Tue, Jun 17, 2014 at 6:00 PM, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
KeithG, you would actually have to test the fix commit itself in order
to verify these findings.
--
You received this bug
Am now getting full builds with modules. Still no 4th decimal. There is
some disconnect, though, between the Ubuntu Kernels and the Mainline
kernels. All V3.8.x kernels build and do not exhibit the error. The V3.9
Kernel does not exhibit the error. The v3.8.15 does, though. I am
building the v3.10
Poked around some more and was able to get other versions in my copy of
the mainline kernel.
this command got me some more kernel versions:
git remote set-url origin
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
now, when I 'tab' to see what is there, I get:
$ git
Ok, Something is going wrong. It stalled at 3.8.0-26.38. It is 'good',
but when I go and do 'git bisect good', it does some stuff and returns
and appears to have a new version to build. WHen I build it, it is the
same version 3.8.0-26.38.
--
You received this bug notification because you are a
Please help! I am trying to follow the instructions to find this bug and am a
bit lost. I have determined that this bug is between 3.8.0-26.38 and
3.8.0-28.42. These do not 'map' to the Mainline kernel map, directly. so I am
guessing near these 2 end points. Following the Mainline instructions,
Christopher,
I Appreciate the help and apologize for being so dense. I think I get it, but
am still a bit lost with the mainline kernel. From the kernel mapping, I see
the 2 kernel versions you are referring to. I have git cloned the kernel. When
I try to tell it that I want 3.8.13.2, though,
I figured it out. I was able to start over. The key is to not edit any
of the files as it bisects. The revision numbers are good enough for me
to keep track of where I am. As it is, I have done 4 or 5 bisects and am
narrowing it down.
--
You received this bug notification because you are a
This is extremely confusing. 1) The kernels I am using do not appear in
that mainline map (version numbers are just not there) 2) I'd rather
just keep going with my first attempt. 3) the example on the
https://wiki.ubuntu.com/Kernel/KernelBisection apparently uses a older
version of git than in
I tried 12.10 and 13.04. 12.10 appears to work. Initial install of 13.04
appears to work. When I dist-upgraded 13.04 after I installed it, I got
the warning in the log. I think I have narrowed it down to this release.
I was going to respond with the kernel versions at beginning and end of
13.04,
Ok, I did my first bisect with 3.8.0-28.42 and it came up bad. Now I am
here:
$ git bisect bad
Bisecting: 388 revisions left to test after this (roughly 9 steps)
error: Your local changes to the following files would be overwritten by
checkout:
debian.master/changelog
Please, commit your
know now? If so, I need a bit more help to
do it.
KeithG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324935
Title:
[Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at
/build/buildd/linux-3.13.0
I loaded 12.04 amd64 on it this morning. This appears to work correctly.
I can suspend and resume with no issues. There is no warning in the log
other than the 'duplicate interface' which does not seem to affect
anything. I have not upgraded anything, just installed xubuntu 12.04
then installed
I have started the process. Strange that this bug has crept in and no
one has noticed. It is pretty limiting, actually.
KeithG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324935
Title:
[Dell
Just installed it and checked dmesg and this warning was there. I
recently got this computer and have only tried 13.10 and 14.04. THis si
after a cold boot. If I try to suspend, it appears to suspend correctly.
When I resume, it has black screen. I have done a ton of updates, so I
need to try
call
modeset=0 video.allow_duplicates=1
I no longer get the message in the log. The video does not appear to be
as crisp somehow, but I can suspend and wake from the command line (tty
or terminal) I get a black screen on resume when I allow the UI to
timeout and suspend.
KeithG
--
You received
If I set modeset=1 or -1, I get the crash on resume. Black screen on all
ttys and no reconnect to network (I cannot ssh back in).
modeset = 0 will allow normal function, but no KMS.
KeithG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Dmesg is filled with this:
[32582.450283] [ cut here ]
[32582.450302] WARNING: CPU: 1 PID: 1154 at
/build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226
intel_modeset_check_state+0x62d/0x780 [i915]()
[32582.450304] encoder's hw state
Tried latest mainline intel kernel I could find (3.15.0-994-generic) and
same issue. This appears to be from, at least, 13.10 to current kernel.
I got this latest kernel here: http://kernel.ubuntu.com/~kernel-
ppa/mainline/ and selected this one: drm-intel-nightly from 5/30/14
I see that the bot
3.15.0-031500rc7-generic kernel has it as well.
** Tags added: bug exists upstream
** Tags removed: bug exists upstream
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In 12.04, it is still an issue. I run 13.10 at home and it appears
fixed, there, but not in 12.04.
Using Wine/Excel 2007. Cannot open a file from the server share (windows
domain), but need to use nautilus to get it local edit then put it back
on server via nautilus.
Like I said, I think this is
persists in 13.10 saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/892768
Title:
Slow boot with ata4.00: failed command: IDENTIFY PACKET DEVICE in log.
To manage notifications about this bug go
not fixed. Still present. I can select any time I want in the 'turn
screen off' dialog box, it saves it, but the screen never turns off.
This is with the Nvidia driver and Gnome 3 window manager, do not know
of that is pertinent or not. I confirm it on 2 installs where 13.10 is
upgraded from
well, this is really fixed as I cannot turn off the screen at this time!
ALl I want is to set DPMS to turn the screen off after 5 minutes with
the login screen and with a user... Nothing tough, but there is not a
setting for this in the new, minimal gnome settings...
--
You received this bug
Tried this tonight with 13.04. Installed the DEB and all seems to be
fine so far. I was getting kernel panic and freeze during periods of
high wifi usage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed it by grabbing the latest GIT of the driver then patching with this:
https://bugs.freedesktop.org/show_bug.cgi?id=57023
The patched version on the git removes a reference to xaa. It loads but
gives a black screen.
This is one patch (required) has already been added to the git repository
Public bug reported:
Install cloudprint. The printer is added to google and shows up in the
google control page. I can send files to it, but none print and the
command line reports an error. When I install it as per the google
documents on this page, it works fine.
For what it is worth, this same dongle hangs a windows 7 machine as well
as a Mac.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930848
Title:
USB BT dongle freezes machine
To manage notifications
Public bug reported:
new BT dongle is very flaky. If it will pair, whenever it is used to
send any data, it freezes the machine (flashing caps lock and num lock
leds). The only way to get it back is to press and hold the power
button. I have 2 other dongles which work fine. It announces itself as
The chip in the adapter is marked OVC3620. Do not know if this is
helpful or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930848
Title:
USB BT dongle freezes machine
To manage notifications
*** This bug is a duplicate of bug 873058 ***
https://bugs.launchpad.net/bugs/873058
It appears that the nvidia issues are fixed (confirmed on my laptop).
The ATI problem appears to still be with us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: samba
Automatic bug announcement.
Trying to mount smb shares on local domain and cannot do so over VPN.
Worked in 9.04, 9.10, 10.04, 10.10. Able to mount them when connected
directly, just not over VPN (PPTP).
ProblemType: Package
DistroRelease: Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/790967
Title:
package samba 2:3.5.8~dfsg-1ubuntu2.2 failed to install/upgrade:
subprocess installed post-installation script returned
Public bug reported:
Binary package hint: samba
Automatic bug announcement.
Trying to mount smb shares on local domain and cannot do so over VPN.
Worked in 9.04, 9.10, 10.04, 10.10. Able to mount them when connected
directly, just not over VPN (PPTP).
ProblemType: Package
DistroRelease: Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790967
Title:
package samba 2:3.5.8~dfsg-1ubuntu2.2 failed to install/upgrade:
subprocess installed post-installation script returned error exit
On my problem, it is the BIOS. I am running an X2 AMD chip and was
running a BIOS that allowed me to unlock the 2 extra cores on the die.
With this BIOS, it will not wake up from an S3 suspend. With the normal
BIOS, it works as expected. Suspends and resumes with no issues. I have
contacted
From a clean install of 64 bit Natty, it works as expected. I set the
gconf settings so that it does not lock the screen. To make thsi really
work, I had to set the gconfedit setting Desktop - Gnome - Lockdown
disable_lock_screen and now it will not ask for a password if I suspend
it from that
Sounds like same problem with 11.04 Natty running 2.6.38-8-generic on
AMD. This is on a Gigabyte MB running latest BIOS.
pm_suspend log appears to be fine. power on, fans come on, but no boot.
Keith
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1 - 100 of 148 matches
Mail list logo
