I have the same exact problem.
Feeling really bad about it, since I cannot essentially use my computer!
I need to have the screen locked for security reasons!
Any workarounds?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/694774
Title:
ConsoleKit uses too much memory, too many threads
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
Public bug reported:
Binary package hint: consolekit
I run a desktop box that runs quite a few cron jobs.
It started having memory issues, so I investigated. Looks like
ConsoleKit uses 847 megs of memory and spawned dozens of threads.
I wonder why a simple helper program needs to use so much me
I still am affected by this bug and it is November 2010!
::~==>ps auxw | head -1; ps auxw | grep indicator-applet
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
wife 2281 0.0 1.4 359040 118180 ? Sl Oct21 9:10
/usr/lib/indicator-applet/indicator-applet-sess
Forgot to say, my desktop is updated daily.
--
indicator-applet uses extremely large amounts of memory
https://bugs.launchpad.net/bugs/575335
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.
I have the same bug! It is November 2010.
I still am affected by this bug and it is November 2010!
::~==>ps auxw | head -1; ps auxw | grep indicator-applet
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
wife 2281 0.0 1.4 359040 118180 ? Sl Oct21 9:10
/usr/lib/indicator-applet/indicator-a
I used to brag about Linux and X11 that I could log on to another
machine remotely, that we can use dumb terminals, etc. Sad to say, but
this is no longer true, now all I can do is log on to my own machine.
--
No option to log in remotely via XDMCP
https://bugs.launchpad.net/bugs/408417
You recei
Daniel, I did that, rebooted, and re-logged on. It did not help at all
and made matters worse.
The bug is not going away at all. I have to switch sound hardware every
time I start any player (mplayer, vlc etc). It gets a little bit
ridiculous.
--
Switching user stops sound, can be restored by So
Daniel, sorry for wrong name. :)
I did remove all users from group audio and rebooted. Unfortunately, it
made things even worse.
Now, every time I start mplayer, it starts muted. I have to change the
"output configuration" to un-mute it. Again, this happens every tmie I
start mplayer, not just wh
On Wed, May 19, 2010 at 03:08:59AM -, Daniel T Chen wrote:
> Are both users A and B in the audio group? If so, they should *not* be.
>
Steve, they may be both in the audio group, yes.
Could you clarify:
1) Can a user who is NOT in audio group, listen to audio?
2) Can I have one use only in
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/48692686/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/48692687/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/48692688/BootDmesg.txt
** Att
re Devices
card 0: NVidia [HDA NVidia], device 0: VT1708S Analog [VT1708S Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ichudov 29981 F pulseaudio
/dev/snd/pcmC0D0p: ichudov 2
Here's the first bazillion lines from /var/log/messages.
** Attachment added: "/var/log/messages extract"
http://launchpadlibrarian.net/48688095/q
--
NFS bug renders machine nearly unusable due to oom-killer
https://bugs.launchpad.net/bugs/582596
You received this bug notification because you
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/48664010/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/48664011/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/48664012/ArecordDevices.t
: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ichudov5278 F pulseaudio
/dev/snd/controlC0: ichudov5278 F pulseaudio
/dev/snd/pcmC0D0p: ichudov5278 F...m
I hope that the victims of this bug will find this useful...
I installed an alternative login manager called "LXDM".
$ sudo aptitude install lxdm
make sure right then to select lxdm as the default login manager.
After installing this fine login manager, I can actually log on the
machine. Everyt
For me, this is not merely a cosmetic issue. X crashes on one laptop
when I see this message and the laptop is unusable.
--
could not write byte broken pipe
https://bugs.launchpad.net/bugs/521298
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
Binary package hint: xorg
Hopefully copying apport files from my laptop succeeded and you have all
the data about that system.
Anyway, on this laptop, X crashes as soon as I select a user from the
GDM logon screen.
The laptop is unusable. The bug is easy to reproduce and I
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/44306096/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/44306098/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/44306100/Dependencies.txt
** A
One more thing. This specific laptop on which it is happening, I do not
really need for much. I can log in to terminal via Ctrl-Alt-F1 and run
scripts, or otherwise do anything.
I am not in the least stressed out by what is happening, and would love
to help tracking down this bug.
i
--
gdm/x fa
I have the same problem on an old laptop. The system is now nearly
completely bricked. I can only use text logon from Ctrl-Alt-F1. (and
that's how I ran the below commands)
I am attaching lspci, dmidecode, lspci -vvnn, free, cpuinfo.
i
** Attachment added: "lspci, cpuinfo, free, lspci -vvnn, dmi
I have the same problem, which ruins my battery life. While this is
being worked on, how can I disable this gwibber-service?
thanks
--
accessing keyring from python threads sometimes causes 100% CPU utilization
https://bugs.launchpad.net/bugs/554005
You received this bug notification because you
Daniel, I upgraded one laptop to Lucid. Started Firefox and played a
Youtube video. I paused the video and left the laptop alone for 1.5
days. I returned to it and resumed playing, and sound continued to work
just fine.
--
All sounds stop working after long inactivity, firefox restart cures it
ht
Daniel, this bug manifests itself in all browsers, for example in
Firefox and Google Chrome. It shows on very many computers also.
I would personally disagree with marking it as incomplete, just because
a subsequent release might fix it.
The bug exists and is real and affects many people.
Lucid
Attaching info from /var/log/messages that could help.
** Attachment added: "oops.txt"
http://launchpadlibrarian.net/38536822/oops.txt
--
Suspend started failing on Karmic
https://bugs.launchpad.net/bugs/514475
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/38536791/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/38536792/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/38536793/BootDmesg.txt
** Att
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ichudov 25697 F
Here's one more weird thing.
I just had this situation again. No sound at all.
I clicked on SWITCH USER in the Gnome menu.
After having been presented with the choice of users, I chose myself,
logged back in into my continuing session.
That cured the problem!
--
All sounds stop working after
Here goes...
bling::~==>sudo fuser -v /dev/dsp* /dev/snd/* /dev/seq*
[sudo] password for ichudov:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rchudov1913 F pulseaudio
ichudov 29548 F pulseaudio
/dev/snd/controlC1: rchudov1
Daniel, how can I found out for sure why is sound not working.
Ergo, can I make some query and find out if an application is indeed
grabbing the "Alsa virtual device".
I will then be able to definitely produce a good answer.
The way I see it, it is a timeout issue or an issue of "idle".
Igor
-
When this happens, all sound sources stop to work. Thus, this is not
exactly a Firefox problem.
I will try to reproduce this with chromium-unstable.
--
All sounds stop working after long inactivity, firefox restart cures it
https://bugs.launchpad.net/bugs/491460
You received this bug notificatio
Both machines are currently on Karmic.
--
All sounds stop working after long inactivity, firefox restart cures it
https://bugs.launchpad.net/bugs/491460
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
** Attachment added: "lspci --vvnn"
http://launchpadlibrarian.net/36338708/lspci-output.txt
--
All sounds stop working after long inactivity, firefox restart cures it
https://bugs.launchpad.net/bugs/491460
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Public bug reported:
Binary package hint: pulseaudio
I have an issue on two machines. Both are upgrades from Jaunty. Ons is a
laptop (sometimes suspended) and one is a desktop (never suspended or
rebooted unless there is some sort of an issue).
The problem is that sound sporadically stops workin
On Fri, Oct 09, 2009 at 01:43:32PM -, tristan_lefebure wrote:
> I do experience the same symptoms on Jaunty, i.e. 20s break in
> "Entering interactive session." while loging through ssh. Any idea if
> this is the same bug?
>
Do "top" on your server and see if consolekit something occupies 10
I have the exact same problem, on Ubuntu Jaunty 32 bit patched to the
latest.
--
hal-acl-tool --reconfigure bother hdd -> work impossible
https://bugs.launchpad.net/bugs/421051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Public bug reported:
Binary package hint: gnome-power-manager
The symptom of this is that when I click on the menu with my name on it,
and select "suspend", the laptop does nothing whatsoever.
The cause of that is gnome-power-manager that is stuck and that does not
do anything.
The "fix" that w
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/31491155/Dependencies.txt
--
gnome-power-manager hangs waiting on futex
https://bugs.launchpad.net/bugs/426268
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
On Fri, Jun 26, 2009 at 04:11:59AM -, Bryce Harrington wrote:
> Would you mind testing Karmic Alpha-2 and seeing if it is still a
> problem? CD ISO images are available here:
I cannot test Karmic, this is my parents PC and I cannot afford to
mess it up with an alpha release. They need it to u
On Thu, Jun 25, 2009 at 01:58:44PM -, stevux wrote:
> Saw the same thing, but i _do_ think this is a pidgin issue, as I see
> the process in status 'TASK_UNINTERRUPTABLE' causing kill not to have
> (the desired) effect.
This means that it is stuck in a kernel call, thus it is a kernel bug.
i
Public bug reported:
My desktop locked up today when I tried to play a YouTube movie (could
be unrelated).
Attempts to ssh to my desktop also failed, which makes me believe that
the computer fully crashed, as opposed to X server being in trouble.
After a reboot, I looked in kernel.log and found:
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/28007898/BootDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/28007899/Dependencies.txt
** Attachment added: "HalComputerInfo.txt"
http://launchpadlibrarian.net/28007900/HalComputerInfo.txt
On Mon, Jun 15, 2009 at 11:24:27PM -, Leann Ogasawara wrote:
> Reassigning to pidgin.
>
> ** Package changed: linux (Ubuntu) => pidgin (Ubuntu)
>
If it cannot be killed with kill -9, it is NOT a pidgin bug, it is a
kernel bug.
--
HARDY -- Pidgin uses 100% CPU, cannot be killed with kill -9
Xorg.conf is unchanged.
I do not have Xorg.0.log from that moment, but I will attach it when the
problem recurs.
I do not believe that this Xorg.0.log is crucial, btw. But I will
provide it at the first opportunity.
--
Closing and opening lid sometimes leads to screen ENDLESSLY BLINKING
https:/
lspci.txt
** Attachment added: "lspci -vvnn"
http://launchpadlibrarian.net/27765319/lspci.txt
--
Closing and opening lid sometimes leads to screen ENDLESSLY BLINKING
https://bugs.launchpad.net/bugs/368946
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I think that I have a complete understanding of this bug. Yes, it was
about not detecting the NEC MultiSync 1500M monitor.
The following xorg.conf is a workaround (but is NOT a bug fix):
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debi
It looks like X cannot properly detect this monitor. If you look at
Xorg.0.log you will see nothing pertaining to detected modelines, etc.
Whereas on my home desktop PC, it works great and shows all the
modelines.
ddcprobe reports resolutions, however per Xorg.0.log X uses a
nonexistent 1152x864 r
I compared my parents (bad) Xorg.0.log with Xorg.0.log on my own
desktop.
And I think that the issue is that the video card does not detect the monitor!
On my (good) desktop, I see many lines that show that the display was
recognized with good modelines and all:
(II) NV(0): I2C device "DDC:ddc2
Public bug reported:
Binary package hint: xserver-xorg-video-intel
This is my parents computer that they have 2000 miles away from me. THey
were on Hardy and everything worked. I upgraded them to Intrepid and
rebooted, then upgraded to Jaunty. After that, they report that their
screen is full of
lspci -vvnn attachment
** Attachment added: "lspci"
http://launchpadlibrarian.net/27727608/lspci.txt
--
Jaunty -- Intel 82945G/GZ -- Screen full of vertical lines, cannot logon
https://bugs.launchpad.net/bugs/385551
You received this bug notification because you are a member of Ubuntu
Bugs, w
Xorg log:
** Attachment added: "Xorg log"
http://launchpadlibrarian.net/27727588/Xorg.0.log
--
Jaunty -- Intel 82945G/GZ -- Screen full of vertical lines, cannot logon
https://bugs.launchpad.net/bugs/385551
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
On Tue, Jun 09, 2009 at 08:44:09PM -, Scott Howard wrote:
> Thanks for the response and the requested information. Which video
> driver are you using?
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (rev 03)
I am using i915 driver, it wou
Yes, fixed in Jaunty.
i
On Sat, Jun 06, 2009 at 12:11:58AM -, Jeff Enns wrote:
> I'm just checking to see if this issue has been resolved. The bug this
> was related to was fixed in a later release. Let me know this is or is
> not the case. Thank you!
>
> ** Changed in: consolekit
>
On Thu, Jun 04, 2009 at 06:00:37PM -, Vincenzo Ciancia wrote:
> Il giorno gio, 04/06/2009 alle 13.17 +0000, ichudov ha scritto:
> > When people say "Linux is not ready for desktop", this is what they
> > mean.
> >
>
> As a 12-years old (as a linux user
When people say "Linux is not ready for desktop", this is what they
mean.
--
[i965] X freezes starting on April 3rd
https://bugs.launchpad.net/bugs/359392
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
It happened again yesterday. Some interesting things were happening in
auth.log, with the same frequency as screen blinking. It is attached,
with some cut and paste right here.
Jun 3 18:54:22 potato su[20984]: pam_unix(su:session): session closed for user
ichudov
Jun 3 18:54:22 potato su
Public bug reported:
This is a Ubuntu Hardy machine. Pidgin, after running for a while, goes
in an infinite loop and uses 100% CPU. While in this state, it cannot be
killed with kill -9 and cannot be straced (strace attaches, but reports
nothing).
~# cat /proc/version
Linux version 2.6.24-23-ser
Public bug reported:
This is a Ubuntu Hardy machine. Pidgin, after running for a while, goes
in an infinite loop and uses 100% CPU. While in this state, it cannot be
killed with kill -9 and cannot be straced (strace attaches, but reports
nothing).
~# cat /proc/version
Linux version 2.6.24-23-ser
Alexander, I tried the changed file
http://launchpadlibrarian.net/26395942/NetworkManager.conf
This file did not help.
Here's grep -i ppp /var/log/auth.log:
May 6 13:58:07 potato dbus-daemon: Rejected send message, 1 matched rules;
type="method_call", sender=":1.124" (uid=1000 pid=11447
comm=
Alexander, When I look at your attachment, all I see is a number "512"?
It is not really a conf file?
--
MASTER PPP connect fails if root is @console with pppd_timed_out() -
(NetworkManager does not connect to Mobile Broadband anymore in Jaunty (Sierra
AC880))
https://bugs.launchpad.net/bugs/3
Thanks for a workaround, it works great. Thanks to Alexander and the
rest for helping me to at least partially restore sanity.
But let's get real guys, this is not really a fix for the problem. It is
kind of funny actually.
What is with this consolekit, it is so full of problems, and no one
fixes
I am seeing the same bug. The terror message seems to be very unhelpful.
Apr 30 06:53:48 potato dbus-daemon: Rejected send message, 3 matched rules;
type="error", sender=":1.9" (uid=0 pid=9746 comm="/usr/sbin/NetworkManager
--pid-file /var/run/Netwo") interface="(unset)" member="(unset)" error
n
potato:root:/var/log ###hal-find-by-capability --capability "battery"
/org/freedesktop/Hal/devices/computer_power_supply_battery_CMB1
potato:root:/var/log ###hal-find-by-capability --capability "battery" | xargs
-n 1 hal-device
udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_CMB
There was nothing useful in /var/log/{messages,syslog}. Xorg.log had
endlessly repeating lines shown in my first message that started this
bug. They repeated exactly when screen was blinking.
--
Closing and opening lid sometimes leads to screen ENDLESSLY BLINKING
https://bugs.launchpad.net/bugs/3
Attaching gnome-power-bugreport output.
** Attachment added: "gnome-power-bugreport output."
http://launchpadlibrarian.net/26138433/gpm.log
--
Closing and opening lid sometimes leads to screen ENDLESSLY BLINKING
https://bugs.launchpad.net/bugs/368946
You received this bug notification because
Is there some other bug report for it? Any fix coming up? Any more
details will be appreciated.
I experienced two regressions about 1 week ago or so:
1) This screen blinking problem described herein
2) I can no longer run a compositing window manager.
--
Closing and opening lid sometimes leads
I have the same problem.
This is because the window manager really is NOT composited.
Go to your System/Preferences/Appearance/Desktop Effects and check. They
are set to NONE if you have the same problem as me.
The real problem is that they can no longer be changed to something
else, something l
Public bug reported:
Binary package hint: gnome-power-manager
Sometimes, on my laptop running latest Jaunty, there is strange
behavior. If I close and then open lid, the screen starts blinking
endlessly, redrawing window decorations. It is highly annoying and makes
laptop unusable.
Doing ctrl-al
I do not believe that I modified /etc/ppp/options. I am attaching it.
** Attachment added: "/etc/ppp/options file from my laptop."
http://launchpadlibrarian.net/25797973/options
--
NM Cannot connect "wireless broadband": pppd_timed_out(): Looks like pppd
didn't initialize our dbus module
h
Here's my /etc/dbus-1/system.d/NetworkManager.conf
http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";>
Sorry, I pasted it twice. Here's one copy of it to avoid confusion:
http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";>
> please include the network-manager and network-manager-applet package
version and the ubuntu version you are running in your bug description
potato:root:~ ###apt-cache policy network-manager network-manager-gnome
network-manager:
Installed: 0.7.1~rc4.1.cf199a964-0ubuntu1
Candidate: 0.7.1~rc4
> What is in /etc/dbus-1/system.d/nm-dhcp-client.conf ?
http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";>
> Did you install NM 0.7 from some PPA at some point?
I do not think so, though I cannot
Public bug reported:
Binary package hint: network-manager
This does not always happen, but it happens MOST of the time, and when
it starts happening it never stops happening:
If I use NM to connect to my wireless broadband, it starts pppd and pppd
actually connects and gets IP.
However, I see t
Public bug reported:
I have a wireless broadband card by Sierra wireless, model 887A.
This card always worked great from command line (pppd) as well as from
Network Manager.
However, lately, when activated from Network Manager applet, the applet
starts the connection, and according to my /var/lo
Seems to be good now, I am switching users like crazy, from my good
personality user to my bad personality user. Just kidding. Thanks to
all. I hope that it does not reoccur. Let's update the freedesktop bug
now.
--
Switching to another user and then to anything else causes freeze in
drm_intel_b
I am doing aptitude upgrade and will report results soon
--
Switching to another user and then to anything else causes freeze in
drm_intel_bo_unreference ()
https://bugs.launchpad.net/bugs/348428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I am thinking, the second session did not need to allocate a shared
resource, and so it did not allocate, but it tries to free it. This is
my hypothesis.
--
Switching to another user and then to anything else causes freeze in
drm_intel_bo_unreference ()
https://bugs.launchpad.net/bugs/348428
You
I subscribed to the bug at freedesktop and volunteered to be a guinea
pig.
Thanks.
--
Swithing to another user and then to anything else, freezes laptop. Jaunty
https://bugs.launchpad.net/bugs/348428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I could not build it due to lint warnings.
Anyway, has this bug been forwarded to upstream?
Let us know.
Thanks a lot.
--
Swithing to another user and then to anything else, freezes laptop. Jaunty
https://bugs.launchpad.net/bugs/348428
You received this bug notification because you are a membe
Tormod, when I try to do build after apt-get source ..., by going to
that directory and typing the above command, I get:
dpkg-checkbuilddeps: Unmet build dependencies: quilt xserver-xorg-dev (>=
2:1.5.99.901) x11proto-gl-dev x11proto-video-dev libgl1-mesa-dev | libgl-dev
libxvmc-dev (>= 1:1.0.1)
Tormod, thanks for understanding.
I will do what I can to help improve fast user switching.
I am downloading source of xserver-xorg-video-intel and will poke around the
code a little bit. I will try to set watchpoints.
I am a C++ programmer, but I rarely use debuggers, that's just the way I am.
I just wanted to add that at home, counting laptops, I have six Ubuntu
machines. Laptops, desktops, etc. Dells, nonames, Fujitsu and so on. A
heterogeneous environment in terms of hardware. Most run Intrepid.
And, I am sad to add, fast user switching works very poorly on all of
them. It is always
This is a response to Tormod's message
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/348428/comments/30.
I have reupdated everything, installed libdrm-dbg, rebooted and
reproduced the bug again.
Attached is the gdb-Xorg.txt file.
** Attachment added: "Xorg gdb log with
I have installed xserver-xorg-core-dbg libdrm2-dbg and rebooted.
Started a second session.
>From SSH, I attached to the second session and pressed Ctrl-Alt-F1.
While the same result occurred, I captured output of GDB, attached here.
Looks like there is a lot more information.
Let me know, guys,
On Fri, Mar 27, 2009 at 06:45:28PM -, Tormod Volden wrote:
> Yes, render_state = 0xc definitely looks wrong. Can you please install
> xserver-xorg-core-dbg and libdrm2-dbg and get a new full backtrace?
>
Hi, I am doing a an aptitude update now and do not see them
coming. Could you tell me whi
I did run the X server that crashes (the guest one) under GDB, as
outlined on https://wiki.ubuntu.com/X/Backtracing
I save output to file (attached) and did say backtrace full. So here it
is.
Looks like it occurs in drm_intel_bo_unreference, which, sadly, likely
suggests a memory corruption elsew
On Thu, Mar 26, 2009 at 09:12:10PM -, Tormod Volden wrote:
> ichudov, I asked some questions specifically to you, and the other
> requests I had it would be nice if you can answer as well, since you are
> the original submitter and also are familiar with ssh.
OK, I will do it t
So, guys, do you want me (the original submitter) to do anything
further? I am a little lost in the conversation and who wants whom to
try what.
Thanks
Igor
--
Swithing to another user and then to anything else, freezes laptop. Jaunty
https://bugs.launchpad.net/bugs/348428
You received this bug
Actually this time it is weird. Instead of Ctrl-Alt-F1 locking the
screen, after 2 seconds of blinking I return to the logon prompt of my
main user. (instead of going to virtual terminal 1).
--
Swithing to another user and then to anything else, freezes laptop. Jaunty
https://bugs.launchpad.net/b
Ok, OK, here's the Xorg.0.log from another try (just now).
I reproduced it once more, to the same detrimental result. Logged on as
self, switched to Guest, pressed Ctrl-Alt-F1.
** Attachment added: "Xorg.0.log from another try"
http://launchpadlibrarian.net/24339936/Xorg.0.log
--
Swithing to
Xorg.0.log is attached in message
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/348428/comments/4
--
Swithing to another user and then to anything else, freezes laptop. Jaunty
https://bugs.launchpad.net/bugs/348428
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: "GDM log from first session"
http://launchpadlibrarian.net/24330415/%3A0.log.2
--
Swithing to another user and then to anything else, freezes laptop. Jaunty
https://bugs.launchpad.net/bugs/348428
You received this bug notification because you are a member of Ubuntu
Bugs,
Sorry for two copies of :20.log.
--
Swithing to another user and then to anything else, freezes laptop. Jaunty
https://bugs.launchpad.net/bugs/348428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
** Attachment added: "GDM Log from second session"
http://launchpadlibrarian.net/24330364/%3A20.log
--
Swithing to another user and then to anything else, freezes laptop. Jaunty
https://bugs.launchpad.net/bugs/348428
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: ":20.log"
http://launchpadlibrarian.net/24330363/%3A20.log
--
Swithing to another user and then to anything else, freezes laptop. Jaunty
https://bugs.launchpad.net/bugs/348428
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: gdm
I am using Jaunty Jackalope.
If I log on, then "switch user" to another user, and do anything to get
out of that second session, laptop freezes up. It does not respond to
any keyboard or mouse movement.
Steps to reproduce:
1) Log on as myself
2) Op
Same behavior (screen locked for good, I can still SSH into the box). I
have to reboot as the laptop becomes unusable due to this. A very
obnoxious bug that, in all fairness, should be actually looked at.
--
bonobo-activation-server : could not associate with desktop session
https://bugs.launchp
I also cannot believe that this bug has not even been patched in the
repos. Patch has been posted and verified weeks ago. What is going on?
--
console-kit-daemon using a lot of cpu
https://bugs.launchpad.net/bugs/284229
You received this bug notification because you are a member of Ubuntu
Bugs, w
James, thanks a lot, this was the most obnoxious Intrepid issue for me,
I am glad that we are moving with it.
--
console-kit-daemon using a lot of cpu
https://bugs.launchpad.net/bugs/284229
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 126 matches
Mail list logo