Public bug reported:
When using dialog python package to present a yesno dialog, it silently
fails if the user has a locally installed terminfo and the terminfo is
unavailable (for example because the dialog is presented from a script
launch via sudo).
To reproduce, you'll need those two files:
Public bug reported:
When using the Ambiance theme and using the keyboard key to change the
volume, the volume is displayed in OSD along an icon. This icon appears
to be a low resolution icon scaled up, and is really ugly.
If I switch to another theme like Adwaita, the icon used is an icon at
@Kychot
Yes, I know that the criteria used to enable the workaround in gnome-
power-manager probably does detect every variation of the MSI Wind U100.
It use the same criteria as the patch to hal-info proposed in comment
#95.
As I said, a correct correction would be to move the dection in
@Fruchtpfote
My patch is for gnome-power-manager, the Gnome Desktop power management
daemon. KDE is using another daemon (as is XFCE), thus my patch won't
work for KDE or XFCE users. It can probably be adapted, but as I'm not
using those desktop environment, I could not test it.
So sorry, it is
Here is another version of the patch that use the same regular
expression as the HAL hack to detect if the computer is a MSI Wind
(check that board name contains either U-100 or U100).
** Attachment added: Updated patch
@Alexander Skiba
Probably, it depends on the content of the
/sys/devices/virtual/dmi/id/board_vendor and
/sys/devices/virtual/dmi/id/board_name files.
--
brightness is broken on MSI WIND U100
https://bugs.launchpad.net/bugs/415023
You received this bug notification because you are a member of
@jbob
My second patch should work on your MSI Wind. if you want to try a binay
package, you can get my second version here :
http://kamisama.free.fr/transfert/gnome-power-
manager_2.28.1-0ubuntu1local2_i386.deb
--
brightness is broken on MSI WIND U100
https://bugs.launchpad.net/bugs/415023
You
Patches updated to use quilt, and uploaded to my ppa ...
https://launchpad.net/~sdefresne/+archive/ppa
--
brightness is broken on MSI WIND U100
https://bugs.launchpad.net/bugs/415023
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
@Demosthenes
No, the brightness key will still work with this patch. And you get back
the eight brightness level. The main problem is that the implementation
is really ugly. More work will be required before it can be intergrated
upstream I think (detection of broken BIOS must be moved into
I've done an ugly patch against gnome-power-manager that check via sysfs
if the system is an MSI Wind U100 (check that
/sys/devices/virtual/dmi/id/board_vendor starts by MICRO-STAR
INTERNATIONAL CO., LTD and that /sys/devices/virtual/dmi/id/board_name
starts by U-100) and then ignore brightness
For testing pupose, you can find a compiled binary package here :
http://kamisama.free.fr/transfert/gnome-power-
manager_2.28.1-0ubuntu1local1_i386.deb
--
brightness is broken on MSI WIND U100
https://bugs.launchpad.net/bugs/415023
You received this bug notification because you are a member of
To build a new version of gnome-patch-manager using the patch, you can follow
the following steps in a terminal (do not type the $, it is to symbolise the
shell prompt) :
$ apt-get source gnome-power-manager
$ sudo apt-get build-dep gnome-power-manager
$ cd gnome-power-manager-2.28.1/
$ patch
I tested the btdownloadcurses from the bittorrent package from Ubuntu
8.04, and it still does exhibit this bug. But is really outdated:
version available in Ubuntu is 3.4.2-11ubuntu5, when upstream version is
5.0.
Moreover, the default bittorrent client in Ubuntu 8.04 is Transmission,
and it
I tried the Hardy LiveCD and the sound was working without modification,
so I guess the bug was corrected. Thank you,
--
Alsa module need model=uniwill-m31 to work on my laptop
https://bugs.launchpad.net/bugs/107577
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm using Hardy.
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION=Ubuntu hardy (development branch)
$ apt-cache policy vim
vim:
Installé : (aucun)
Candidat : 1:7.1-138+1ubuntu3
Table de version :
1:7.1-138+1ubuntu3 0
500
Public bug reported:
Launching vim in a terminal (I don't have .vimrc file), and typing :e
~sTab (where Tab is the tabulation key) crash vim in free.
Stacktrace :
(gdb) bt
#0 0x7fef38fcc095 in raise () from /lib/libc.so.6
#1 0x7fef38fcdaf0 in abort () from /lib/libc.so.6
#2
I just installed the Beta of Ubuntu 7.10 today, and I still had to
manually add the following line to /etc/modprobe.d to get sound :
options snd-hda-intel model=uniwill-m31
So either, those patch have not been integrated in the kernel used by
Ubuntu 7.10, or they are not working.
--
Alsa
Public bug reported:
I just bought a laptop, and had some trouble making sound work. After
some reading on the forum and experimentation, I managed to make it
work, by passing the model=uniwill-m31 to the snd-hda-intel module. So,
maybe the alsa developer may be interested in adding this model to
Public bug reported:
Binary package hint: gaim
I tried to invite someone to a conversation, and gaim crashed when she
joined it.
** Affects: gaim (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Crash after inviting someone to a conversation
https://launchpad.net/bugs/93068
Additional information from apport (?)
** Attachment added: Additional information from apport (?)
http://librarian.launchpad.net/6847229/_usr_bin_gaim.1000.crash
--
Crash after inviting someone to a conversation
https://launchpad.net/bugs/93068
--
ubuntu-bugs mailing list
It does happen with an other user. I created a new user for the test,
and the menu of the compose window present the same strange behaviour.
The only plugin I think I'm using is the plugin to use bogofilter as
spam filter instead of spamassassin, but I had not activated for my test
with a new user
Well I'm also using Ubuntu Edgy with fr_FR.UTF-8 locale. Specific
version of language-pack-gnome-fr-base is 1:6.10+20061019, and for
evolution it is 2.8.1-0ubuntu4.
--
Menu item change from Édition to Éditer depending on focus
https://launchpad.net/bugs/67134
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: evolution
The second menu item (Edit in the english locale) of the mail compose
windows alternate between Édition and Éditer depending on the focus.
If the focus is on the Subject: widget, it reads Édition, otherwise
it reads Éditer.
I think this is a
This little screen cast (thanks to byzanz) should make simpler to
understand the problem. See how the second menu item change when focus
change.
** Attachment added: Bug in the french localisation of evolution.
http://librarian.launchpad.net/4899928/evolution-bug.gif
--
Menu item change from
** Attachment added: /var/log/Xorg.0.log
http://librarian.launchpad.net/4796398/Xorg.0.log
--
glxinfo crash X
https://launchpad.net/bugs/62180
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: /etc/X11/xorg.conf
http://librarian.launchpad.net/4796400/xorg.conf
--
glxinfo crash X
https://launchpad.net/bugs/62180
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
No problem, I'll install debug symbols for ubuntulooks and libcairo next
time it happens. Concerning thread apply all bt, this is not really
necessary as gnome-panel only use a single thread (info threads show
only one thread).
--
gnome-panel dead-locked after apt-get upgrade
*** This bug is a duplicate of bug 60621 ***
Changing to 1024x768 does not work for me. I still get a black screen
with a OSD message from the monitor indicating that the frequency is out
of range.
--
usplash use incorrect frequency
https://launchpad.net/bugs/63156
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: gnome-panel
After my last apt-get upgrade (and the two previous), gnome-panel dead-
locked during the process. Trying to trace it, it appears to be blobked
trying to acquire a mutex that it already holds.
$ ps x|grep gnome-panel
4330 ?Ss
** Attachment added: Backtrace of gnome-panel
http://librarian.launchpad.net/4667535/gnome-panel.backtrace
--
gnome-panel dead-locked after apt-get upgrade
https://launchpad.net/bugs/64120
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: Log of dpkg corresponding to the last apt-get upgrade
http://librarian.launchpad.net/4667536/gnome-panel.upgrade
--
gnome-panel dead-locked after apt-get upgrade
https://launchpad.net/bugs/64120
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 60621 ***
After reading bug #60621, I don't know if this bug is really a duplicate
of it. On my machine, usplash is working correctly, it is just using a
mode 1280x1024 @80Hz, which is not supported by my screen (it only
support 1280x1024 @60Hz).
--
usplash
Public bug reported:
After the last upgrade, usplash (version 0.4-30) uses frequency not
supported by my monitor (LCD 17, it display a black screen with a
message stating the frequency is out of range), even though the
resolution listed in /etc/usplash.conf (1280x1024) is supported by it
(I'm
Public bug reported:
Binary package hint: apt
There is no information about the 'autoremove' command, either in the
manpage or when invoking apt-get with the --help option.
$ man apt|grep autoremove
$ man apt-get|grep autoremove
$ apt-get --help|grep autoremove
** Affects: apt (Ubuntu)
Public bug reported:
Every time I use glxinfo, X crash and I'm back at gdm login prompt.
However, running opengl applications does not crash the X server (opengl
screensavers works flawlessly, even tough they are not accelerated,
AFAIK).
Some version informations :
$ dpkg --status mesa-utils
35 matches
Mail list logo
