Public bug reported:
Hardware: Macbook 2,1
Ubuntu 14.04 (updated)
Suspend and resume works fine, but frequently after resuming from
suspend the unity lock screen is not visible.
The screen is on and the mouse cursor is visible and moves around if the
touch pad is used, but the background is
This seems like an old issue that was resolved, but is back in 14.04? I
have found similar, older bug reports, but none against 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314800
Title:
Public bug reported:
Running Ubuntu 14.04 on my old Macbook, I get the following error on
every boot. It doesn't seem to cause issues, but always happens.
[ 18.644792] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 18.644796] [drm] GPU hangs can indicate a bug anywhere in the
I know this is an old bug, but it still affects 12.04 LTS and I just ran
into it. The LIBOVERLAY_SCROLLBAR=0 workaround does work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887983
Title:
Here is a me too.
I also click the 1 resize to window button as a workaround...
ii remmina 1.0.0-1ubuntu6.1
ii remmina-common 1.0.0-1ubuntu6.1
ii remmina-plugin-rdp 1.0.0-1ubuntu6.1
ii
I would certainly be willing to do this since I would like to see it
fixed in lucid, but I don't have rights to upload a package to lucid-
proposed (I'm not a package maintainer).
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you
I would certainly be willing to do this since I would like to see it
fixed in lucid, but I don't have rights to upload a package to lucid-
proposed (I'm not a package maintainer).
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you
I suppose the chance of this fix being released for lucid is pretty low?
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to minicom in ubuntu.
--
Ubuntu-server-bugs
I suppose the chance of this fix being released for lucid is pretty low?
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I tested the latest version from mercurial (which includes the patch)
and it resolves the issue.
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to minicom in ubuntu.
--
** Changed in: minicom (Ubuntu)
Status: Confirmed = Fix Committed
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to minicom in ubuntu.
--
Ubuntu-server-bugs
OK, sorry -- I thought Fix Committed meant a fix had been committed to
the upstream source.
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to minicom in ubuntu.
--
On a related issue, I noticed the remote bug watcher for
alioth.debian.org isn't working -- it looks like it is using the wrong
URL.
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I tested the latest version from mercurial (which includes the patch)
and it resolves the issue.
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: minicom (Ubuntu)
Status: Confirmed = Fix Committed
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
OK, sorry -- I thought Fix Committed meant a fix had been committed to
the upstream source.
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
On a related issue, I noticed the remote bug watcher for
alioth.debian.org isn't working -- it looks like it is using the wrong
URL.
--
minicom scripts never exit
https://bugs.launchpad.net/bugs/585911
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch added: alioth.debian.org/ #312517
http://alioth.debian.org/support/tracker.php?aid=312517
** Also affects: minicom via
http://alioth.debian.org/support/tracker.php?aid=312517
Importance: Unknown
Status: Unknown
--
minicom scripts never exit
** Bug watch added: alioth.debian.org/ #312517
http://alioth.debian.org/support/tracker.php?aid=312517
** Also affects: minicom via
http://alioth.debian.org/support/tracker.php?aid=312517
Importance: Unknown
Status: Unknown
--
minicom scripts never exit
Public bug reported:
Binary package hint: minicom
Using Ubuntu 10.04 LTS 32-bit, minicom 2.4-1
If you run a script from within minicom while attached to a serial port,
the script doesn't exit when finished. Minicom hangs indefinitely,
until the user hits CTRL-C. Then the script exits and
I have this problem using rdesktop on Jaunty to connect to an XP
workstation. Cursor colors are inverted. The default white Windows
cursor shows up as black and if I switch the cursor scheme in Windows to
black, the cursor appears as white in rdesktop. This probably started
for me after
After getting feedback from the linux kernel bugzilla, I worked around
my timeout errors by disabling media detection polling. I'd rather have
a working drive than auto-mounting.
'hal-disable-polling --device /dev/sr0' (assuming your device is
/dev/sr0)
Thankfully, this stays in effect
** Bug watch added: Linux Kernel Bug Tracker #13492
http://bugzilla.kernel.org/show_bug.cgi?id=13492
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=13492
Importance: Unknown
Status: Unknown
--
ATAPI devices malfunctioning
I can also confirm that this still exists in the jaunty kernel with
pata_via. Using jaunty, libata doesn't throttle the bus speed down
repeatedly anymore, but still disables the device. Has anyone found any
activity in the kernel lists about this? I did some searching, but
found mostly old
Is this a duplicate of bug 231575? It looks very similar.
https://bugs.launchpad.net/bugs/231575
--
LIBATA with PATA_VIA causes ATAPI PATA devices to hang with HPET enabled
https://bugs.launchpad.net/bugs/282536
You received this bug notification because you are a member of Ubuntu
Bugs,
Has anyone tried jaunty to see if it still has this issue?
--
ATAPI devices malfunctioning
https://bugs.launchpad.net/bugs/231575
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
I finally got tired enough of this bug (since pretty much every time I
go to use my DVD drive it is useless unless you reboot) and downgraded
my kernel to 2.6.22-16 (from gutsy). I never had this issue while
running gutsy and switching back to the gutsy kernel has worked around
the problem for me
Is this the type of bug that will never get fixed in hardy even though
it's an LTS release? If so, why? Is it too complicated to pull in the
upstream change and merge it into the hardy source for evolution? I
don't really see the value of LTS releases (beyond security patches) if
known bugs
Thanks for the response.
--
Cannot add attachments from network drive
https://bugs.launchpad.net/bugs/235973
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
I upgraded my kernel to 2.6.27-2-generic and I am still seeing the same
problem.
--
ATAPI devices malfunctioning
https://bugs.launchpad.net/bugs/231575
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I am running Ubuntu 8.04 amd64 with kernel 2.6.27-2-generic and am still
seeing this issue.
Hardware: MSI K9VGM-V mainboard, AMD Athlon X2 5200+
Sep 2 18:30:03 jjg-linux kernel: [34971.601129] powernow-k8: Hardware error -
pending bit very stuck - no further pstate changes possible
Sep 2
I can also confirm this on Hardy amd64
** Changed in: jabberd2 (Ubuntu)
Status: New = Confirmed
--
jabberd2-bdb is missing the files in component.d directory on amd64
https://bugs.launchpad.net/bugs/163987
You received this bug notification because you are a member of Ubuntu
Bugs, which
Yes, it does appear to be a duplicate.
--
ATAPI devices malfunctioning
https://bugs.launchpad.net/bugs/231575
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
I can confirm this problem with my hardware.
Lite-On DVD-RW SHW-160P6S
MSI K9VGM-V mainboard
AMD Athlon X2 5200+
SATA hard drive
The dvd drive will work just fine for many hours and then stop working
for no apparent reason, even when idle. It then becomes inaccessible
until reboot. Once the
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
ATAPI devices malfunctioning
https://bugs.launchpad.net/bugs/231575
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I should add that I'm experiencing this with Hardy (8.04), kernel
2.6.24-19-generic x86_64. I don't believe I had this problem with
Gutsy.
--
ATAPI devices malfunctioning
https://bugs.launchpad.net/bugs/231575
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I tested this with hardy last week as well and I did get alarms for
exchange calendar appointments, provided evolution was running. If
evolution was not running, I only got alarms for local calendar
appointments.
--
Reminder pop-up for exchange calendar items does not work
I can confirm Stephen's comments. I tested an up-to-date hardy install
last week and was only able to see my local appointments in the calendar
applet. If evolution was not running, I only got alarms for
appointments in my local calendar and not for my exchange calendar.
I did get alarms for
Why was this bug declined for Hardy?
--
Setting static IP in Network Settings doesn't produce correct data
https://bugs.launchpad.net/bugs/185854
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can also confirm this bug in hardy beta. Unchecking and rechecking
the the box next to the network interface works around the problem (auth
eth0 shows up in /etc/network/interfaces then).
--
Setting static IP in Network Settings doesn't produce correct data
Whoops, correction: meant to write auto eth0, not auth.
--
Setting static IP in Network Settings doesn't produce correct data
https://bugs.launchpad.net/bugs/185854
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I tried out this workaround and it works for me (with Gutsy). I only
added '--sm-disable' to the Evolution Alarm Notify command under the
Startup Programs tab of the Sessions preferences. Now I get calendar
alarm notifications for both local and exchange calendar events.
--
Reminder pop-up for
I am running 7.10 and also still have this problem (had it in 7.04 too).
I have found the only reliable way to get alarms is to forcibly shutdown
the evolution components when restarting evolution. evolution --force-
shutdown; evolution. If I do this, I seem to always get alarms and my
I also have this issue with 7.10 (and with 7.04). I used the --force-
shutdown workaround and it does seem to work consistently. Every time I
restart evolution, I run 'evolution --force-shutdown' first to stop any
running evolution components. If I do this every time I restart
evolution, I get
44 matches
Mail list logo
