** Bug watch added: freedesktop.org Bugzilla #18889
https://bugs.freedesktop.org/show_bug.cgi?id=18889
** Also affects: xserver-xorg-video-intel via
https://bugs.freedesktop.org/show_bug.cgi?id=18889
Importance: Unknown
Status: Unknown
--
asus eeetop backlight needs kernel suppor
Here's a Xorg log file with ModeDebug on, if it's of any use
** Attachment added: "Xorg log, intel driver, ModeDebug on"
http://launchpadlibrarian.net/20204258/Xorg.0.log
--
asus eeetop backlight needs kernel support
https://bugs.launchpad.net/bugs/304558
You received this bug notification be
Public bug reported:
(verbatim copy from this forum post:
http://ubuntuforums.org/showthread.php?t=992882)
I have two new shiny Asus Eee Top ET1602 systems. I tried running Ubuntu
7.10 and 8.10 on them. In the console, and while showing the splash, the
screen works fine. When X starts with the in
The motherboard mentioned above is an Asus P5E-V HDMI.
The lspci -vvnn output for the video card is this:
00:02.1 Display controller [0380]: Intel Corporation 82G35 Express Integrated
Graphics Controller [8086:2983] (rev 03)
Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
Con
The ioctl loop happened to me as well over the weekend. I booted a
Ubuntu 8.10 live CD on a machine this Friday, started a screensaver
(Stonerview) and left it running over the weekend. It worked fine the
entire Friday, but when I came back on Monday, X was using 100% of the
CPU and strace showed i
Hmm... looks like the message trail for this bug entry treats two bugs:
- one about glipper having trouble reading stuff from a .glipper directory
after upgrading (which has nothing to do with gnome panel, as you have to
delete the .glipper directory for things to work out) -- looks like what is
Oh yeah, can bugs really be renamed? Or do I have to open a new bug and
reference this thread?
--
[Hardy] Glipper dies when desktop starting
https://bugs.launchpad.net/bugs/213494
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Andrew, it actually sounds like the same issue, generalized.
The way I see it, the issue goes like this:
Gnome panel starts the applets too early. Glipper is "lucky" enough to
start faster than the rest of the applets, so it fails to start almost
every first login after powering on the system. If
Hi all,
Guess what happened to me today: other applets wanted to be deleted.
Most of the applets in my bar. And that's after I removed glipper from
there.
This makes me think that this is not a bug in glipper, but rather a
condition in the gnome panel that spawns the applets before it is ready
to
That sleep worked for me for a while too. Then I have no idea what I
did, but at login, my drive is getting hammered, enough to make that
sleep useless. I happen to be seeing trackerd using a lot of CPU at
login, so I wonder if that has anything to do with the delay.
Is there a way to start the ap
Just an update. Bug #205507 explained my condition. Deleting the old
.glipper directory solved my problem.
--
[Hardy] Glipper dies when desktop starting
https://bugs.launchpad.net/bugs/213494
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I'm running a 64bit installation of 8.04 and glipper doesn't crash. It
doesn't start either. I have to kill it myself, otherwise it freezes
gnome-panel.
--
[Hardy] Glipper dies when desktop starting
https://bugs.launchpad.net/bugs/213494
You received this bug notification because you are a member
Public bug reported:
There seems to be a bug in ide-scsi when querying a cd drive's tray
status: it always reports that the tray is open, even though it's
closed.
A very simple C program that tests the tray status looks like this:
#include
#include
#include
#include
#include
int main()
{
Public bug reported:
Binary package hint: libopenh323-dev
Here's a piece of code:
test.cpp:
-- CUT --
#include "ptlib.h"
#include "h323.h"
#include "h323ep.h"
int
main ()
{
H323EndPoint ep = H323EndPoint();
;
return 0;
}
--
Public bug reported:
Binary package hint: asterisk
In 7.10, the asterisk package is version 1.4.10~dfsg-1, but the source
package is version 1.4.11~dfsg. As I found out the hard way, and as a
poster to bug 139732(asterisk 1.4.11~dfsg-1 segfaults on
startup) clearly states, 1.4.11 does not
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/8777073/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/8777074/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/8777075/ProcStatus.txt
** Attachment
Public bug reported:
Binary package hint: kde-guidance
Message appeared on KDE startup.
ProblemType: Crash
Architecture: i386
Date: Sat Aug 11 06:03:05 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/share/python-support/kde-guidance/guidance-power-manager.py
InterpreterPath: /usr/bin/pytho
Public bug reported:
Binary package hint: dash
dash breaks scripts that are executed via the "system(3)" call.
I'll start with the details, then explain what they mean.
* From the manpage (man 3 system):
system() executes a command specified in command by calling /bin/sh
-c command, and re
18 matches
Mail list logo
