I would like to say I have been battling with this issue for a little
over a year, when I first started with ralink wireless drivers.
The above post is correct, when scanning for new networks, the network
speeds drop out. Wagner Volanin had a PPA which disabled this in
network-manager, but the abo
hi how are you ?
i just ordered an iphone4 from this company
:
best price and fast ship / i like it very much
take a look , sure you will like it
thousands of products .
save more than 30%!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the
I have just opened a bug report in gnome since this still persists in
9.10 and seems to be vino specific.
(https://bugzilla.gnome.org/show_bug.cgi?id=595949)
A gconf option (/desktop/gnome/remote_session/disable_xdamage) has been
added to disable the xdamage extension which is a temporary workarou
If the ~/.vnc/passwd file is missing completely setup fails also.
--
Mythbuntu control center VNC setup freezes if & in password
https://bugs.launchpad.net/bugs/241402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
I think it happened on other packages as well. I'll check when I'm home
tonight.
It's difficult to debug because it crashes in the chroot and I don't know
where the logs are (help here).
Also, hangs is a better word than crashes since it just sits there without
doing anything.
-a
--
cannot inst
Mario,
I think this might be back open for Jaunty.
The install hangs when going to configure packages (like when you enable
automatic login) in the diskless chroot.
Let me know if you need anything to help debug / reproduce.
-andy
--
cannot install packages using MCC in diskless chroot
https:
** Changed in: xorg-server
Importance: Undecided => Unknown
Bugwatch: None => freedesktop.org Bugzilla #12255
Status: New => Unknown
--
Compiz / vnc screen refresh with nvidia-restricted driver
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you ar
** Also affects: xorg-server
Importance: Undecided
Status: New
--
Compiz / vnc screen refresh with nvidia-restricted driver
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Description changed:
Binary package hint: compiz
When using the nvidia-restricted driver and compiz desktop effects the
vnc server will not refresh the screen. This is being caused by the
xserver not getting "damaged" by the nvidia-restricted drivers. Linked
bugs confirm this is no
*** This bug is a duplicate of bug 353126 ***
https://bugs.launchpad.net/bugs/353126
** This bug is no longer a duplicate of bug 77442
compiz / vnc screen updates with nVidia restricted
** This bug has been marked a duplicate of bug 353126
Compiz / vnc screen refresh with nvidia-restric
*** This bug is a duplicate of bug 353126 ***
https://bugs.launchpad.net/bugs/353126
** This bug has been marked a duplicate of bug 353126
Compiz / vnc screen refresh with nvidia-restricted driver
--
compiz / vnc screen updates with nVidia restricted
https://bugs.launchpad.net/bugs/77442
*** This bug is a duplicate of bug 353126 ***
https://bugs.launchpad.net/bugs/353126
** This bug is no longer a duplicate of bug 77442
compiz / vnc screen updates with nVidia restricted
** This bug has been marked a duplicate of bug 353126
Compiz / vnc screen refresh with nvidia-restric
*** This bug is a duplicate of bug 353126 ***
https://bugs.launchpad.net/bugs/353126
** This bug is no longer a duplicate of bug 77442
compiz / vnc screen updates with nVidia restricted
** This bug has been marked a duplicate of bug 353126
Compiz / vnc screen refresh with nvidia-restric
*** This bug is a duplicate of bug 353126 ***
https://bugs.launchpad.net/bugs/353126
** This bug is no longer a duplicate of bug 77442
compiz / vnc screen updates with nVidia restricted
** This bug has been marked a duplicate of bug 353126
Compiz / vnc screen refresh with nvidia-restric
*** This bug is a duplicate of bug 353126 ***
https://bugs.launchpad.net/bugs/353126
** This bug is no longer a duplicate of bug 77442
compiz / vnc screen updates with nVidia restricted
** This bug has been marked a duplicate of bug 353126
Compiz / vnc screen refresh with nvidia-restric
*** This bug is a duplicate of bug 353126 ***
https://bugs.launchpad.net/bugs/353126
** This bug is no longer a duplicate of bug 77442
compiz / vnc screen updates with nVidia restricted
** This bug has been marked a duplicate of bug 353126
Compiz / vnc screen refresh with nvidia-restric
Public bug reported:
Binary package hint: compiz
When using the nvidia-restricted driver and compiz desktop effects the
vnc server will not refresh the screen. This is being caused by the
xserver not getting "damaged" by the nvidia-restricted drivers. Linked
bugs confirm this is not an issue on i
** Summary changed:
- No screen updates when using desktop-effects with vnc
+ compiz / vnc screen updates with nVidia restricted
--
compiz / vnc screen updates with nVidia restricted
https://bugs.launchpad.net/bugs/77442
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 77442 ***
https://bugs.launchpad.net/bugs/77442
** This bug has been marked a duplicate of bug 77442
No screen updates when using desktop-effects with vnc
--
vino server does not refresh from remote location
https://bugs.launchpad.net/bugs/328559
You rec
Tried to report via apport but lost the attachments somehow..
Still valid for Jaunty. Should we open an additional bug since this
report has been closed by
http://bugzilla.gnome.org/show_bug.cgi?id=383147
** Changed in: vnc (Ubuntu)
Status: Fix Released => Incomplete
** Changed in: compiz
I have a recent Jaunty alpha and am experiencing something similar. The
main (only) user on my system is no longer part of groups required for
normal desktop operation (audio, fuse, video, etc).
Because of this I was experiencing many errors / warnings like this:
andrew-desktop pulseaudio[9291]:
I can also confirm that this exists and still remains an issue.
--
No screen updates when using desktop-effects with vnc
https://bugs.launchpad.net/bugs/333564
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This has been verified on my own machine as well.
--
vino server does not refresh from remote location
https://bugs.launchpad.net/bugs/328559
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.
Public bug reported:
Binary package hint: xorg-driver-fglrx
Xorg does not seem to keep the screen resolution you set within the
Catalyst Control Center after a reboot.
Hardcoding the resolution into the xorg.conf file will work, but this is
not the intended functionality.
** Affects: linux-rest
This dialog still appears in Hardy and still does not work correctly.
** Changed in: gnome-volume-manager (Ubuntu)
Status: Invalid => Confirmed
--
'Always perform this action': Ignore for photo card option doesn't work.
https://bugs.launchpad.net/bugs/102495
You received this bug notific
Public bug reported:
Creating the problem:
PVR-150 Retail
Hauppauge remote specified.
Run irw
No response to key presses.
Run mode2
Output. Verified that chipset is working.
Lircd is currently:
lircd --device=/dev/lirc0
When changing arguments to:
lircd --device=/dev/lirc0 /usr/share/lirc/remot
Public bug reported:
/var/www/mythweb/data/video and /var/www/mythweb/data/video_covers are
incorrectly linked.
They should be /var/lib/mythtv/videos and ~/.mythtv/MythVideo
NOTE:
I'm proposing that the default storage directory for video_covers is changed to
/var/lib/mythtv/video_covers in th
Sorry, the above is not too clear.
The lirc0 node that is created represents both the hauppauge remote and
the hauppauge blaster.
--
MythBuntu control center lirc logic not working
https://bugs.launchpad.net/bugs/50
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
When you select the "pvr150" transmitter, the lirc_pvr150 module is
loaded.
The lirc_pvr150 module creates a node (/dev/lirc0 for example) which is
both a transmitter and a receiver.
If a hauppauge remote is selected, a lircd instance should just be
created (and do not load
** Attachment added: "interfaces"
http://launchpadlibrarian.net/13034740/interfaces
--
Wireless connections not established until after login
https://bugs.launchpad.net/bugs/210531
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
wireless network connections are not established until the first user
logs in.
This causes problems when you reboot the machine from over the network
and the connection is never re-established.
Wireless connection has no security enabled.
** Affects: network-manager (Ubuntu
The problem is not with lirc but with the ubuntu package configuration.
debian/modules-source/lirc-modules-source.conf needs the following
adjustments:
add -DLIRC_SERIAL_SOFTCARRIER
fix LIRC_SERIAL_PORT and LIRC_SERIAL_IRQ to use ttyS0
diff is attached.
Thanks mario and laga for the help in fix
ches that came after 0.8.3~pre1.
>
> Maybe the better idea is to apt-get source lirc, and then dpatch
> apply-all.
> Run the standard build process (configure/make not debuild) to make sure
> nothing in the build system that we have on top is breaking it.
>
> On Tue, Mar 25,
s not work (Gutsy 7.10 + Hardy 8.04)
> https://bugs.launchpad.net/bugs/182530
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Andrew Barbaccia
MonolithMC Sales & Support
(631) 865 - 1025
--
lirc_serial loads but does not work (Gutsy 7
PM, Andrew Barbaccia <[EMAIL PROTECTED]>
wrote:
> I'm starting to think this is more of a configuration problem with the
> package than it is with the actual software code itself.
>
> I cannot test the response of my cable box because I am not home (and was
> way to la
pulse 128
space 896
pulse 128
space 3200
pulse 128
space 3200
pulse 128
space 4992
pulse 128
space 13440
pulse 128
space 6528
pulse 128
On Sun, Mar 23, 2008 at 2:07 PM, Andrew Barbaccia <[EMAIL PROTECTED]>
wrote:
> Pete,
>
> Again, I think this is something to do with y
VICE to be set in hardware.conf
> https://bugs.launchpad.net/bugs/204769
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Andrew Barbaccia
MonolithMC Sales & Support
(631) 865 - 1025
--
/etc/init.d/lirc requires TRANSMITTER_DEVICE
Pete,
Again, I think this is something to do with your configuration settings
rather than the lirc package itself.
This bug is trying to address the lack of transmission support in the
current lirc package.
On Sun, Mar 23, 2008 at 12:32 PM, Andrew Barbaccia <[EMAIL PROTECTED]>
; /etc/init.d/lirc requires TRANSMITTER_DEVICE to be set in hardware.conf
> https://bugs.launchpad.net/bugs/204769
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Andrew Barbaccia
MonolithMC Sales & Support
(631) 865 - 1025
--
/etc/init.d/li
Another note:
If TRANSMITTER_DEVICE is set, REMOTE_DEVICE also needs to be set since
the init script will not attempt to guess REMOTE_DEVICE if more than one
device is being loaded.
--
/etc/init.d/lirc requires TRANSMITTER_DEVICE to be set in hardware.conf
https://bugs.launchpad.net/bugs/204769
Public bug reported:
Currently /etc/init.d/lirc requires TRANSMITTER_DEVICE to be set by hand
(or during debconf) to load the transmitter's daemon. Additionally, if a
remote is being used in conjunction with a transmitter, REMOTE_DEVICE
needs to be set as well to have both daemons load properly.
Public bug reported:
When using a remote and a transmitter on the same box, udev will cause
some (ugly) race conditions that result in very long boot times and
occasionally will bring down the system. The udev script also notes some
flaws when trying to handle two lirc instances.
Since the module
** Attachment added: "Patch for /etc/init.d/lirc"
http://launchpadlibrarian.net/12789062/lirc.patch
--
Typo in lirc init script prevents loading two instances
https://bugs.launchpad.net/bugs/204664
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
/etc/init.d/lirc has a typo which uses the remote's options when loading
the transmitter's daemon.
See attached for simple change.
** Affects: lirc (Ubuntu)
Importance: Undecided
Status: New
--
Typo in lirc init script prevents loading two instances
https://b
> https://bugs.launchpad.net/bugs/182530
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Andrew Barbaccia
MonolithMC Sales & Support
(631) 865 - 1025
--
lirc_serial loads but does not work (Gutsy 7.10 + Hardy 8.04)
https://bugs.launchpad
** Attachment added: "transmitter.hwdb patch"
http://launchpadlibrarian.net/12763178/204342.patch
** Summary changed:
- Scientific Atlanta generic file not correctly named - Use alternate file
+ Scientific Atlanta lircd general.conf - bad naming convention - use alternate
file
--
Scientifi
** Attachment added: "Better lirc config file"
http://launchpadlibrarian.net/12763176/AT8400
--
Scientific Atlanta lircd general.conf - bad naming convention - use alternate
file
https://bugs.launchpad.net/bugs/204342
You received this bug notification because you are a member of Ubuntu
Bugs
Public bug reported:
The lirc package currently supplies generic lircd.conf files for popular
remote and set top boxes. An update to one of these files is necessary:
When selecting "Serial Port (UART) : Scientific Atlanta Cable box" the
file /usr/share/lirc/transmitters/scientificatlanta/general.
lo
> [EMAIL PROTECTED]
> Sent from my iPod Touch
>
>
> On Mar 20, 2008, at 8:22, Andrew Barbaccia <[EMAIL PROTECTED]>
> wrote:
>
>
> > Okay, good. Because I was starting to get worried here...
> >
> > Sending signals with lirc 0.8.3pre1 seems to be brok
in!! -> Refresh does not work. Ctl+F5 does
not work. Do not log in. Access denied.
sudo /etc/init.d/apache2 restart
Access Site -> Not prompted to log in
Can you produce the same?
On 3/20/08, laga <[EMAIL PROTECTED]> wrote:
>
> Andrew Barbaccia schrieb:
>
> > Public bug
Public bug reported:
When you click enable or disable "Set password for MythWeb", the
configuration process correctly adjusts the mythweb.conf files in
apache2. These settings will not take effect until after the web server
has been restarted, which currently does not seem to be the case.
** Affe
gt; https://bugs.launchpad.net/bugs/182530
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Andrew Barbaccia
MonolithMC Sales & Support
(631) 865 - 1025
--
lirc_serial loads but does not work (Gutsy 7.10 + Hardy 8.04)
https://bugs.launchpad
>
> > Mario Limonciello
> > [EMAIL PROTECTED]
> > Sent from my iPod Touch
> >
> > On Mar 19, 2008, at 22:02, Andrew Barbaccia <[EMAIL PROTECTED]>
> > wrote:
> >
> >
> >> Mario,
> >>
> >> I don't know where t
ings.
>
>
> --
> lirc_serial loads but does not work (Gutsy 7.10 + Hardy 8.04)
> https://bugs.launchpad.net/bugs/182530
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Andrew Barbaccia
MonolithMC Sales & Support
(631) 865 -
I've had the same problem.
Very repeatable: Install packages for lirc on fresh install of gutsy,
create config files, no output. Remove packages, download SVN, compile,
reuse same config files (and same kernel, etc) and success.
It seems a bug was introduced into 0.8.2 and continues to exist in
0
Public bug reported:
Tmp directory is not automatically populated or created in mytharchive
package.
Should probably be /var/lib/mythtv/tmp or something of the like.
** Affects: mythbuntu
Importance: Undecided
Status: New
** Affects: mythvideo (Ubuntu)
Importance: Undecided
** Also affects: mythbuntu-trunk
Importance: Undecided
Status: New
--
Can't set up mythweb auth in control centre
https://bugs.launchpad.net/bugs/139983
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Currently mcc updates /etc/mythtv/mythweb-digest with the correct user
and password digest provided by the user. This file is not yet
implemented though.
Needed:
* update the /mythweb.conf.apache file to use mythweb-digest
authentication
-- uncomment auth lines given as example
-- update AuthUs
*** This bug is a duplicate of bug 200515 ***
https://bugs.launchpad.net/bugs/200515
Public bug reported:
Binary package hint: mythbuntu-control-centre
Just opening after installing ubuntu-desktop causes a crash on each
reload.
ProblemType: Crash
Architecture: i386
Date: Wed Mar 19 09:55:15
*** This bug is a duplicate of bug 200515 ***
https://bugs.launchpad.net/bugs/200515
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/12738284/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/12738285/ProcMaps.txt
** Attachment ad
As a temporary workaround as the problem is fixed upstream, generic
kernels could be compiled with 64G ram support.
** Bug watch added: Linux Kernel Bug Tracker #9893
http://bugzilla.kernel.org/show_bug.cgi?id=9893
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=9893
Public bug reported:
This problem occurs in all gutsy -generic kernels and feisty -generic
kernels.
I have a system with 4GB ram installed. The BIOS correctly identifies
all 4GB.
When booting into the -generic kernel only 2GB shows up in
/proc/meminfo. Looking at the kernel configuration CONFIG_
Public bug reported:
Binary package hint: ubuntu-desktop
Default install of Hardy Alpha 3.
Does not install restricted-manager by default. Is not included as a
dependency of ubuntu-desktop.
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
Restricted Manager
uced.
>
>
> Regards,
>
> Michael
>
> --
> bug in lirc 0.8.2 breaks transmitters - need 0.8.3pre1 packages
> https://bugs.launchpad.net/bugs/179121
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Andrew Barbaccia
Mo
*** This bug is a duplicate of bug 179121 ***
https://bugs.launchpad.net/bugs/179121
** This bug has been marked a duplicate of bug 179121
bug in lirc 0.8.2 breaks transmitters - need 0.8.3pre1 packages
--
lircd in 6.10 is working with serial rc but doesn't work anymore in 7.10
https://bu
Public bug reported:
Binary package hint: lirc
Upgrading to Gutsy breaks lirc transmitters (IR Blasters) for many
users. Both serial and pvr150 along with others. After much testing, it
was found as a known bug in the 0.8.2 source of lirc. By remove the
lirc-modules package, and compiling 0.8.3pr
66 matches
Mail list logo
