Done, see: https://bugzilla.gnome.org/show_bug.cgi?id=613214
** Bug watch added: GNOME Bug Tracker #613214
https://bugzilla.gnome.org/show_bug.cgi?id=613214
--
totem subtitle plugin cannot contact opensubtitles.org
https://bugs.launchpad.net/bugs/540533
You received this bug notification
Public bug reported:
Binary package hint: totem
The subtitle plugin in Totem cannot contact the opensubtitles.org's
database anymore, since the URL 'www.opensubtitles.org' isn't valid
anymore for API calls. It apparently has changed to
http://api.opensubtitles.org. The URL of the server for API
** Patch added: opensubtitles.py.patch
http://launchpadlibrarian.net/41168012/opensubtitles.py.patch
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41166345/Dependencies.txt
** Attachment added: GstreamerVersions.txt
Hey,
Indeed it's still an issue on the specific machine I used to report this
issue. It's still running jaunty as it's a perfectly stable system
otherwise. Nevertheless, I will test for this issue with the most recent
10.4 alpha version and report on the results.
Thanks!
--
audio skips,
just for the sake of completeness: also kernel 2.6.32-16-generic shows
the same symptoms, as originally described, on my machine
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of
And I unfortunately also cannot use lucid with kernel 2.6.32-15-generic.
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Update: situation is unchanged after an update to kernel
2.6.32-14-generic.
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Confirming, indeed the main page now show characters in a different
language. To me it seems to be Thai.
** Attachment added: thai.png
http://launchpadlibrarian.net/39927267/thai.png
--
Software Center shows categories in another language
https://bugs.launchpad.net/bugs/519441
You received
Confirming, after an upgrade of rsyslogd from 4.2.0-2ubuntu5.1 to
4.2.0-2ubuntu7, rsyslog is consuming a lot of CPU cycles on my machine.
See also the attached image of htop running. CPU use is more than 80%.
** Attachment added: Image of output of HTOP showing rsyslogd using 80% of
CPU
BTW, I'm running a 2.6.31-14 kernel, which is supposedly supported. Will
downgrade for the moment though.
--
rsyslogd gives 100%CPU
https://bugs.launchpad.net/bugs/523468
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: thunar
After opening Thunar, I can click once on a folder, it opens, but then
Thunar's file panel does not respond to left clicks anymore. For
example, I cannot open a file by double-clicking it, or open a subfolder
by double-clicking. Right clicks are
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39107056/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/39107057/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/39107058/ProcStatus.txt
** Attachment
*** This bug is a duplicate of bug 520118 ***
https://bugs.launchpad.net/bugs/520118
OK, first attempt at creating a backtrace, hope this is what's needed.
** Attachment added: backtrace-thunar.txt
http://launchpadlibrarian.net/39126179/backtrace-thunar.txt
--
Thunar's file panel does
You're welcome, glad to be of help :)
--
time-admin crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/520136
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
Update: situation is unchanged after an update to kernel
2.6.32-13-generic.
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Yes, karmic kernel 2.6.31-14-generic works just fine.
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/39031980/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39031981/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/39031982/Disassembly.txt
** Attachment
After some research on launchpad, it seems more likely to be a bug in
Plymouth than in xserver-xorg-video-openchrome. Moreover, I've
completely removed Xorg and I still can't log in on a TTY
** Package changed: xserver-xorg-video-openchrome (Ubuntu) = plymouth
(Ubuntu)
** Description changed:
Public bug reported:
Binary package hint: xserver-xorg-video-openchrome
I have upgraded my Xubuntu karmic installation to lucid to test the
alpha release of lucid. After the upgrade, which went smoothly, I
rebooted the machine. I expected to see the GDM login screen eventually,
but all I got was
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/38872373/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/38872374/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38872375/Dependencies.txt
**
Unfortunately, the issue still exists with with a kernel updated to
2.6.31-19.
--
After resume, wireless connection is not restored with kernel 2.6.31-17-generic
https://bugs.launchpad.net/bugs/514675
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: linux-image-2.6.31-17-generic
After the update of (X)ubuntu karmic to kernel 2.6.31-17-generic, my
wireless connection is not restored anymore after a suspend/resume
cycle. My wireless card is of the PCMCIA type, and when I pop it out and
push it back
Blech, apport-collect crashes. Anyway, here's the output of lspci -vv
** Attachment added: lspci.txt
http://launchpadlibrarian.net/38552904/lspci.txt
--
After resume, wireless connection is not restored with kernel 2.6.31-17-generic
https://bugs.launchpad.net/bugs/514675
You received this
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/38552906/dmesg.txt
--
After resume, wireless connection is not restored with kernel 2.6.31-17-generic
https://bugs.launchpad.net/bugs/514675
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This copy of syslog contains all the information of a (re)boot, suspend,
resume, wireless card ejection (becaus of no connection) and reinsertion
(connection is reestablished).
** Attachment added: syslog.txt
http://launchpadlibrarian.net/38552924/syslog.txt
--
After resume, wireless
I have the same problem with ubuntu 9.10, running kernel 2.6.31-17. In
my case, the wireless adapter is a PCMCIA card, and if I pop it out and
push it back into its slot, the network connection is re-established.
If I use kernel 2.6.31-16, everything's fine and network connection is
automatically
@MicRos, mistseeker: please note that this bug is about the VESA driver
failing with a KM400 chipset, not the openchrome driver. The openchrome
driver, whatever issues it might have, works allright on my machine as
well. The VESA driver fails miserably.
Cheers,
Robert
--
Via KM400 : no matching
Ok, short answer: yes and no.
Full story:
I've updated my copy of the openchrome source to svn revision 817. I ran
'./configure --enable-debug --prefix=/usr' and then proceeded with make.
I uninstalled the xserver-xorg-video-openchrome package and installed
the self-built openchrome driver with
** Attachment added: login screen after adding the modeswitch option and
restarting gdm
http://launchpadlibrarian.net/35874531/gdm_restart.JPG
--
[KM400]black screen after logout
https://bugs.launchpad.net/bugs/313701
You received this bug notification because you are a member of Ubuntu
** Attachment added: Xorg.0.log file after adding the Option ModeSwitch
new line
http://launchpadlibrarian.net/35874527/Xorg.0.log.after
--
[KM400]black screen after logout
https://bugs.launchpad.net/bugs/313701
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: gdm_boot.JPG
http://launchpadlibrarian.net/35874548/gdm_boot.JPG
--
[KM400]black screen after logout
https://bugs.launchpad.net/bugs/313701
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
*** This bug is a duplicate of bug 355843 ***
https://bugs.launchpad.net/bugs/355843
I've noticed that this bug report is marked as a duplicate, and I'm by
no means an expert on the subject, but still I'd like to mention that I
did not have this problem with 9.04, what the 'original' bug
Here's a status update on this issue with karmic koala: in the
meanwhile, I've upgraded the machine to karmic alpha 6 + latest updates,
and I've installed a self-built openchrome driver. The driver's version
is 0.2.903+svn798. The issue still arises in karmic in combination with
this revision of
This bug has been reported as well at bugs.freedesktop.org:
https://bugs.freedesktop.org/show_bug.cgi?id=24348
** Bug watch added: freedesktop.org Bugzilla #24348
https://bugs.freedesktop.org/show_bug.cgi?id=24348
--
Via KM400 : no matching mode for vesa
I have upgraded my jaunty machine to karmic alpha 6 + latest updates,
and I still can't get any graphics on screen with the vesa driver.
Version of the installed xserver-xorg-video-vesa package is 1:2.2.1-1,
failure reason still is (according to X server) 'no matching modes'.
What else do you need
I've checked the BIOS of the machine I'm experiencing difficulties with,
it has an option for 'Display', which I can set to 'auto' or 'both'. I
*think* this has to do with the possible external display. However, no
external display is connected.
--
[KM400]black screen after logout
I don't dare to reopen the bug report, but I have experienced the same
issue. I installed kde-core on Xubuntu Jaunty + kdm. After a reboot,
right-clicking any icon except the trash can crashed the plasma
workspace. Also installing kdebase removed the issue.
--
Plasma Workspace right clicking on
Well, the chipset is in my laptop and connected to the built-in LCD. No
external screens are attached. Should I try the above anyway?
--
[KM400]black screen after logout
https://bugs.launchpad.net/bugs/313701
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Dear people, I'd love to continue to help, but to do that I need an
answer on my question above
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/313701/comments/13)
Thanks,
Robert
--
[KM400]black screen after logout
https://bugs.launchpad.net/bugs/313701
You received this bug notification
Er, do I need to update the patch first before I can try and disable the
TV output? Or is there an option I can put in the xorg.conf file to do
this? I found the ActiveDevice option, but it seems to be used only
for enabling certain hardware. Any help on this is appreciated.
--
[KM400]black
Here you go :)
** Attachment added: xorg.conf
http://launchpadlibrarian.net/30427870/xorg.conf
--
[KM400]black screen after logout
https://bugs.launchpad.net/bugs/313701
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
*** This bug is a duplicate of bug 293326 ***
https://bugs.launchpad.net/bugs/293326
I'm posting a comment here, because I want to confirm that I also cannot
get any working modes with the VESA driver on a VIA KM400, Ubuntu
Jaunty. In my opinion, this bug report is not a duplicate of bug
I've tried getting the VESA driver to work with my laptop, but I only
get an error message from X stating: Screen(s) found, but none have a
usable configuration. The symptoms are the same as those reported in
bug #258764. I did not find a workaround.
Then, I downloaded svn version 774 of the
Hi,
At the moment I'd say that the first symptom (no gdm login screen after
logout) seems to have been solved, but I only recently upgraded to
jaunty. I still do have the issue of a dead machine with a black screen
every now and then, but I'm currently less convinced that it's the same
bug.
Well, I unfortunately spoke too soon. After writing the previous
comment, I thought: 'Let's try one more time.' I logged of from my
desktop session and got just a black screen again. Machine was still
running, as TTY were available, but I had to reboot to get a gdm login
screen.
So, yes, this
Public bug reported:
Binary package hint: pulseaudio
During playback of audio, I frequently (3-4 times a night) encounter the
problem that during playback audio suddenly is skipped. It then sounds
like when you fast-forward a CD in a CD player - a small fragment of
audio is played correctly,
** Attachment added: lsmod output
http://launchpadlibrarian.net/28000954/lsmod.out
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/28000955/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/28000956/AplayDevices.txt
** Attachment
BTW, I have two audio devices, one on-board (AC97) that I do not use,
and a SoundBlaster PCI 128 (Ensoniq 5880B) with which the above
described behavior occurs. I have attached the output of lspci for
details.
** Attachment added: lspci output
http://launchpadlibrarian.net/28001019/lspci.out
Here's a log file of th eoutput of pulseaudio when started with -vvv as
command line option. During the playback, the above described behavior
happens twice. The first time I also could resolve the issue by pausing
the audio and wait a couple of seconds. On resuming playback, the audio
was normal
Confirming that the 738 releases fixes the 'No valid modes found' error
for me.
I had exactly the same problem, I was dropped to a text-only login
screen after a successful boot. I have followed the guide at
https://help.ubuntu.com/community/OpenChrome to build and install the
738 release.
I can confirm this for a fully updated (24 jan. 2009) intrepid, synaptic
0.62.1ubuntu10
--
[intrepid] problem with quick search
https://bugs.launchpad.net/bugs/247496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: syslog
http://launchpadlibrarian.net/20896670/syslog
--
black screen after logout
https://bugs.launchpad.net/bugs/313701
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Some additional log files right after getting the black screen
** Attachment added: kern.log
http://launchpadlibrarian.net/20896648/kern.log
--
black screen after logout
https://bugs.launchpad.net/bugs/313701
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/20896672/Xorg.0.log
--
black screen after logout
https://bugs.launchpad.net/bugs/313701
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Distributor ID: Ubuntu
Description:Ubuntu 8.10
Release:8.10
Codename: intrepid
Linux wuppie 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux
I've experienced a couple of times that after I've logged out of a
graphical session and am
** Attachment added: lspci_vvnn.log
http://launchpadlibrarian.net/20896632/lspci_vvnn.log
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/20896634/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/20896635/CurrentDmesg.txt
** Attachment
I came across this topic in the fedora forum:
http://forums.fedoraforum.org/showthread.php?t=209533
It discussed loss of sound and auto-mounting of hard disks, cd-roms etc. What
triggered me was that apparently this person's gnome session wasn't properly
started as he/she chose another login
Public bug reported:
Binary package hint: virtualbox-ose-guest-utils
I've seen bug report #262990 where on intrepid, virtualbox-ose-guest-
utils conflicts with xserver-xorg-core and cannot be installed without
uninstalling xserver-xorg. I have the same problem with (X)ubuntu jaunty
(fully
Update: I also cannot use the unlock button on a Ubuntu server 8.04.1
install that runs under VirtualBox, with the XFCE desktop and gnome-
system-tools installed.
--
'Unlock' button is grayed out in system tools
https://bugs.launchpad.net/bugs/287932
You received this bug notification because
Chris, thank you for your comment. I read through some other threads and
understood that this was indeed correct behavior for remote sessions.
However, I was at the specific server's console at the beginning of the
week and I still couldn't unlock the applications. I have the same
behavior on a
I've only come across this report just now, so I hope it's not too late
to add some input. Here's the output on my terminal:
x...@yyy:~$ users-admin
** (users-admin:6502): CRITICAL **: Unable to find session for cookie
--
'Unlock' button is grayed out in system tools
I should add that this is via a ssh and VNC session
--
'Unlock' button is grayed out in system tools
https://bugs.launchpad.net/bugs/287932
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On a fresh install of Xubuntu 8.10, VLC's video output (DVD, avi)
freezes as well, while the audio continues uninterrupted. Sometimes it
catches on again (instantly), but usually there's no recovery but to
restart VLC. I am not using Compiz, and have the free nVidia drivers
installed. Other
Replacing libsmbclient (as desribed in
https://bugs.launchpad.net/ubuntu/+source/fusesmb/+bug/198351) with the
version available from http://packages.ubuntu.com/hardy-
updates/libsmbclient solved the problem for me. Running Xubuntu 8.10.
--
fusesmb mount disappears - libsmbclient segfaults
Replacing libsmbclient (as desribed in
https://bugs.launchpad.net/ubuntu/+source/fusesmb/+bug/198351) with the
version available from http://packages.ubuntu.com/hardy-
updates/libsmbclient solved the problem for me. Running Xubuntu 8.10.
--
fusesmb mount disappears - libsmbclient segfaults
I can confirm that on Xubuntu 8.10, the workaround posted by Dmik works
for me. The SMB connection is stable while browsing the network with
Thunar.
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
I am using an Acer Aspire 1352XC with kernel 2.6.27-7-generic, ubuntu
8.10. I too experience that sometimes (say 1 out of 5 times) the
keyboard is dead after a resume from suspend. The touchpad is working
properly though. I never experienced this with gutsy, kernel
2.6.22-15-generic. Additional
I tried the keytouch package (2.3.2-2.1ubuntu1 and a self-built 2.4.1)
on Xubuntu 8.10, kernel 2.6.27-7-generic without luck. Hardware is an
Acer Aspire 1352XC. It worked properly on gutsy with kernel
2.6.22-15-generic. I checked with xev and there are keycodes (if you
call them that) generated
I have upgraded Xubuntu from 7.10 to 8.04, and I occasionally have the
same problem. I need to killall gdm to shut down the X server from a
normal terminal (CTRL+ALT 1), or simply do a sudo reboot. As it doesn't
happen 100% of the time, I suspect that the suspend mode has something
to do with it.
I can consistently reproduce a black screen after putting my laptop in
suspend mode. After resuming from suspend mode, log out closes all
applications, I briefly see the terminal screen showing some stuff from
booting, and then the screen goes black, presumably when the graphical
login screen
I'm running Xubuntu 8.04 here, and I have the same problem. When
keytouch is functioning, I cannot log out. When I remove keytouch, I can
log out. I'm not running seahorse.
--
[hardy] keytouch blocks logout
https://bugs.launchpad.net/bugs/186713
You received this bug notification because you are
I upgraded Xubuntu 7.10 to 8.04. I did install and remove keytouch a
couple of times, but at least that did not help.
--
[hardy] keytouch blocks logout
https://bugs.launchpad.net/bugs/186713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Probably related to bregol's experience: when I removed keytouch and
rebooted, I could log out. Then I installed keytouch again, and I could
logout once, just the session I reinstalled keytouch in. After a reboot,
I could not log out anymore.
--
[hardy] keytouch blocks logout
In addition to my previous post, I also noted that more than one
instance of keytouch was running, more like 3. I assumed it was normal
however.
--
[hardy] keytouch blocks logout
https://bugs.launchpad.net/bugs/186713
You received this bug notification because you are a member of Ubuntu
Bugs,
74 matches
Mail list logo
