Re: [Bug 1570502] Re: Menu not getting shown for gnome-terminal alone

[Balaji G]

The bug has been resolved. I deleted the ~/.config/.unity folder and now
the problem does not occur again.


On Thu, Apr 14, 2016 at 11:53 PM, Egmont Koblinger 
wrote:

> Any chance you're facing bug 1532226?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1570502
>
> Title:
>   Menu not getting shown for gnome-terminal alone
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1570502/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1570502

Title:
  Menu not getting shown for gnome-terminal alone

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1570502/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1570502] [NEW] Menu not getting shown for gnome-terminal alone

[Balaji G]

Public bug reported:

Menu is not being shown for gnome-terminal alone. I tried both options
(in the window title bar/global menu bar) and both of them seem to have
no effect and its just blank.  Looks like this got broken recently as it
was working couple of days back.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-terminal 3.18.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu Apr 14 22:51:56 2016
InstallationDate: Installed on 2016-04-10 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1570502

Title:
  Menu not getting shown for gnome-terminal alone

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1570502/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1568451] Re: Current Tab in Gnome-terminal does not get highlighted

[Balaji G]

Oh ok thanks for the information. I hope it gets fixed as its becoming
difficult to find out the current tab


On Mon, Apr 11, 2016 at 2:20 PM, Egmont Koblinger 
wrote:

> This is an issue with the default Gtk+ theme, not with gnome-terminal.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1568451
>
> Title:
>   Current Tab in Gnome-terminal does not get highlighted
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1568451/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1568451

Title:
  Current Tab in Gnome-terminal does not get highlighted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1568451/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1568451] [NEW] Current Tab in Gnome-terminal does not get highlighted

[Balaji G]

Public bug reported:

Hi

When multiple tabs are open in gnome-terminal, its difficult to find out
the current tab as the tab does not get highlighted properly. Tab
switching works fine but its very hard to find out the current one.
Ubuntu Gnome 16.04 does not have this problem as a blue underline is
displayed for the current tab and the tab also the current gets
highlighted better.

This problem is seen in Ubuntu 16.04 beta-2 with all updates installed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-terminal 3.18.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Sun Apr 10 10:35:55 2016
InstallationDate: Installed on 2016-04-10 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug xenial

** Attachment added: "gnome-terminal with multiple tabs and the current one 
does not get highlighted"
   
https://bugs.launchpad.net/bugs/1568451/+attachment/4631031/+files/Screenshot%20from%202016-04-10%2010-48-32.png

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1568451

Title:
  Current Tab in Gnome-terminal does not get highlighted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1568451/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1016854] Re: Desktop appearance changes after locking desktop for few minutes

[Balaji G]

** Changed in: unity
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1016854

Title:
  Desktop appearance changes after locking desktop for few minutes

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1016854/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 932177] Re: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11

[Balaji G]

I get this problem still. I am running XFCE 4.10 and i see the error
when i do git clone or git pull. Following is the error

git pull
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-ySN77r/pkcs11: No 
such file or directory
Already up-to-date.


-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177

Title:
  XFCE (and other non-GNOME) desktops do not initialise gnome-keyring
  correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/932177/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1016854] Re: Desktop appearance changes after locking desktop for few minutes

[Balaji G]

Have created a new bug and that has all the required information. The
bug ID is #1030963

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1016854

Title:
  Desktop appearance changes after locking desktop for few minutes

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1016854/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 998056] Re: Maximize window freezes computer for about 10 seconds

[Balaji G]

.

** Changed in: xchat-gnome (Ubuntu)
   Status: New = Confirmed

** Changed in: xchat-gnome (Ubuntu)
   Status: Confirmed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/998056

Title:
  Maximize window freezes computer for about 10 seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/998056/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 706931] Re: repeated asking to verify a certificate. enough already, I already approved it!!

[Balaji]

thanks. the solutions here were helpful.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/706931

Title:
  repeated asking to verify a certificate. enough already, I already
  approved it!!

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 629258] Re: Battery life estimation never comes around

[Balaji]

I have an HP DV6298US laptop. The laptop battery life estimation is
completely broken. It say it has only 18% life and dies down in less
than 20 minutes. Under Windows the same works for more than 1 and a half
hour. Battery charging, discharging, current every single statistic is
plain WRONG! It is impossible that charge remains at 100% for 10 minutes
even when I pull out the power chord! In the new kernel 2.6.35-22 this
is even more broken. The moment I plug out the charger, the charge level
drops to 58%. Until then it is at 100%.

Ask me for ANY settings you want. I think developing Ubuntu to work with
laptops has always been a challenge for developers. I have had issues
with it since the days of Feisty Fawn. It will be ages before this is
fixed.

The first thing is that on Ubuntu's website itself we cannot afford to
have versions of Ubuntu only for Desktops, Servers and Netbooks alone.
We need separate focus on Notebooks/Laptops. The Desktop features DO NOT
work on Laptops. It is high time the Ubuntu team realizes that Laptops
have special needs.

** Changed in: ubuntu-release-notes
   Status: Fix Released = Confirmed

** Changed in: null
   Status: Invalid = Confirmed

-- 
Battery life estimation never comes around
https://bugs.launchpad.net/bugs/629258
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 640096] Re: cpufreq using grey almost invisible font

[Balaji]

This is quite irritating. Please. Someone for Ubuntu's sake fix it. It
is ridiculous that we can't fix a simple font color issue in WEEKS!!!
Don't tell me you need a new kernel for it to work fine! It is the same
story with Ubuntu. Every new release you have 1000 new bugs and the old
ones are still not resolved! I wonder why we even take Ubuntu seriously!
Frankly, there is NO point in making alpha and beta releases of a new OS
if it does not work later on. Fix all these little issues at the very
least!

-- 
cpufreq using grey almost invisible font
https://bugs.launchpad.net/bugs/640096
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 629235] Re: cpu frequency scaling applet doesn't retain settings

[Balaji]

** Changed in: gnome-applets (Ubuntu)
   Status: New = Confirmed

-- 
cpu frequency scaling applet doesn't retain settings
https://bugs.launchpad.net/bugs/629235
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 622555] Re: gnome-applets CPU Frequency Scaling Monitor Display quirk

[Balaji]

*** This bug is a duplicate of bug 640096 ***
https://bugs.launchpad.net/bugs/640096

I thought the display has gone bad until I saw this bug. When I go close
and look, I find the text. I mean, what a shame. Just because Ubuntu
tried the Radiance theme for 10.10, you changed the default font color
for an applet?!

-- 
gnome-applets CPU Frequency Scaling Monitor Display quirk
https://bugs.launchpad.net/bugs/622555
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 633242] [NEW] vertical Mouse scroll does not cause a scroll update in the vertical scroll bar

[Balaji]

Public bug reported:

Binary package hint: evince

The following is the output of apt-cache policy evince
--

Installed: 2.30.3-0ubuntu1.1
  Candidate: 2.30.3-0ubuntu1.1
  Version table:
 *** 2.30.3-0ubuntu1.1 0
500 http://in.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
100 /var/lib/dpkg/status
 2.30.0-0ubuntu1 0
500 http://in.archive.ubuntu.com/ubuntu/ lucid/main Packages

The following is the output of lsb_release -rd

Description:Ubuntu 10.04.1 LTS
Release:10.04

Expected
-
1. A scroll using the mouse must update the scroll status in the scroll bar

Actual
-
1. The scroll bar's state does not change

Actions leading upto the observed problem
--
1. Typed the page number

2. Scrolled using the mouse

** Affects: evince (Ubuntu)
 Importance: Undecided
 Status: New

-- 
vertical Mouse scroll does not cause a scroll update in the vertical scroll bar
https://bugs.launchpad.net/bugs/633242
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 633242] Re: vertical Mouse scroll does not cause a scroll update in the vertical scroll bar

[Balaji]

Only in certain runs, this bug occurs

** Changed in: evince (Ubuntu)
   Status: New = Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/evince/+question/124629

-- 
vertical Mouse scroll does not cause a scroll update in the vertical scroll bar
https://bugs.launchpad.net/bugs/633242
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 209532] Re: Accessibility keyboard settings get lost

[Balaji G]

Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!

Thanks,
Cheers,
Balaji

** Changed in: gnome-applets (Ubuntu)
   Status: New = Confirmed

-- 
Accessibility keyboard settings get lost
https://bugs.launchpad.net/bugs/209532
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 290506] Re: cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards)

[Balaji]

There is still one problem with cheese.

1. If you take a photo using cheese, it flashes the screen and makes it all
white and after that never returns back to normal display. I have to press
Alt+Ctrl+F1 and kill cheese manually. This is annoying. The video is
recording is fine, but the photo has regressed. This happens when you use no
effects. I did not have this problem when I used some other effects I cannot
say if all the effects fix this problem, but that is very queer. Taking
photos has become a pain now.

Balaji


On Sat, Feb 21, 2009 at 5:06 PM, Fabian A. Scherschel fa...@lamerk.orgwrote:

 Seems to me, this is fixed, no? Was there a regression again? Is anyone
 experiencing problems? Both my uvcvideo and gspca webcams work fine with
 cheese right now.

 --
 cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2
 video output and disables output on gstreamer-based apps ran afterwards)
 https://bugs.launchpad.net/bugs/290506
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video 
output and disables output on gstreamer-based apps ran afterwards)
https://bugs.launchpad.net/bugs/290506
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 290506] Re: cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards)

[Balaji]

Yes, indeed there is something that needs a fix. You cannot take photos now
suddenly for some reason the flashed screen now remains white and does not
return to normal display. Please change the status back to new.

Balaji


On Sat, Feb 21, 2009 at 6:41 PM, Connor Imes rocket2...@gmail.com wrote:

 I'll close this task against Ubuntu release notes.  If there is indeed
 something that needs to be fixed here, please re-open it by changing its
 status back to new, and leave an explanation.  Thank you!

 ** Changed in: ubuntu-release-notes
Status: Incomplete = Invalid

 --
 cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2
 video output and disables output on gstreamer-based apps ran afterwards)
 https://bugs.launchpad.net/bugs/290506
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video 
output and disables output on gstreamer-based apps ran afterwards)
https://bugs.launchpad.net/bugs/290506
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 290506] Re: cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards)

[Balaji]

I just got an update of the 2.6.27-11-generic kernel and my webcam is no
longer working. I don't think it can even detect the webcam anymore. Cheese
fails to load and skype cannot see my webcam now. This has happened only
recently when the update for version 11 of the kernel came up.

The initial version 2.6.27-9 kernel was not able to use the webcam on
cheese, but I could use skype. I was watching this thread that the fix has
come up in the new kernel. But then the new kernel is a big disappointment -
I'm sorry to say. It can't even recognize my webcam now.

Mine is a HP integrated webcam that comes in an HP laptop. It was working
perfectly when I used the Stefan Bader kernel patch in November 2008. After
that in a few weeks someone smart guy came up with a broken kernel 2.6.27-9
and after that this new kernel! It deserves a Nobel prize indeed!

Please help me. This kernel is not able to detect my webcam. What should I
do?

Balaji


On Wed, Jan 28, 2009 at 7:04 PM, Kees Cook k...@ubuntu.com wrote:

 ** CVE removed: http://www.cve.mitre.org/cgi-
 bin/cvename.cgi?name=2008-5079

 ** CVE removed: http://www.cve.mitre.org/cgi-
 bin/cvename.cgi?name=2008-5300

 --
 cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2
 video output and disables output on gstreamer-based apps ran afterwards)
 https://bugs.launchpad.net/bugs/290506
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video 
output and disables output on gstreamer-based apps ran afterwards)
https://bugs.launchpad.net/bugs/290506
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 290506] Re: cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards)

[Balaji]

Sorry,

My bad. I figured the problem. I had disabled the AT SPI Registry at startup
in order to reduce startup time. But I think that was not allowing access to
the webcam. I'm sorry. This kernel is working perfectly for me.

I am using 2.6.27-11-generic kernel and both cheese and skype are working
perfectly. This is exactly how an OS should be - friendly! :) You know what,
if your hardware works, the OS is friendly, if it does not work, I don't
care what you say, the OS is not friendly if my hardware does not work. That
is how a layman will think.

If you want to put the burden of being compatible on the manufacturer, then
start issuing Ubuntu compatible logo stickers to those companies whose
products will work with Ubuntu.

I'm sorry for my last post, this kernel is a blessing indeed!

Thanks a lot,
Balaji


On Sun, Feb 1, 2009 at 1:03 AM, Balaji balaji.ramasubraman...@gmail.comwrote:

 I just got an update of the 2.6.27-11-generic kernel and my webcam is no
 longer working. I don't think it can even detect the webcam anymore. Cheese
 fails to load and skype cannot see my webcam now. This has happened only
 recently when the update for version 11 of the kernel came up.

 The initial version 2.6.27-9 kernel was not able to use the webcam on
 cheese, but I could use skype. I was watching this thread that the fix has
 come up in the new kernel. But then the new kernel is a big disappointment -
 I'm sorry to say. It can't even recognize my webcam now.

 Mine is a HP integrated webcam that comes in an HP laptop. It was working
 perfectly when I used the Stefan Bader kernel patch in November 2008. After
 that in a few weeks someone smart guy came up with a broken kernel 2.6.27-9
 and after that this new kernel! It deserves a Nobel prize indeed!

 Please help me. This kernel is not able to detect my webcam. What should I
 do?

 Balaji



 On Wed, Jan 28, 2009 at 7:04 PM, Kees Cook k...@ubuntu.com wrote:

 ** CVE removed: http://www.cve.mitre.org/cgi-
 bin/cvename.cgi?name=2008-5079

 ** CVE removed: http://www.cve.mitre.org/cgi-
 bin/cvename.cgi?name=2008-5300

 --
 cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2
 video output and disables output on gstreamer-based apps ran afterwards)
 https://bugs.launchpad.net/bugs/290506
 You received this bug notification because you are a direct subscriber
 of the bug.




-- 
cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video 
output and disables output on gstreamer-based apps ran afterwards)
https://bugs.launchpad.net/bugs/290506
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 290506] Re: cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards)

[Balaji]

Hi All,

Everything was working fine when I was using Stefan's PPA kernel patch
2.6.27-8.17 smb2. Now I have a new kernel update and the kernel I am using
is
$ uname -r
2.6.27-9-generic

At this point, my webcam has stopped working correctly. Here is an output of
cheese -v.

$ cheese -v 
[1] 16782
blackmas...@blackmaster-laptop:~/ece190$
(cheese:16782): GStreamer-WARNING **: pad source:src returned caps which are
not a real subset of its template caps

(cheese:16782): GStreamer-WARNING **: pad source:src returned caps which are
not a real subset of its template caps

(cheese:16782): GStreamer-WARNING **: pad video_source:src returned caps
which are not a real subset of its template caps
libv4l2: error converting / decoding frame data: v4l-convert: error
destination buffer too small

Thanks,
Balaji


On Tue, Dec 9, 2008 at 8:28 PM, linux23d linux...@adam.com.au wrote:

 I've removed out of date code from this thread.
 http://ubuntuforums.org/showthread.php?t=966398

 Anyone who wants a working webcam, should come here and help test all
 fixes.

 --
 cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2
 video output and disables output on gstreamer-based apps ran afterwards)
 https://bugs.launchpad.net/bugs/290506
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video 
output and disables output on gstreamer-based apps ran afterwards)
https://bugs.launchpad.net/bugs/290506
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 290506] Re: cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards)

[Balaji]

Stefan,

I had a similar problem with cheese and I was unable to record video
although my webcam takes photos and also works with Skype flawlessly. So
when I wrote to Filippo and Daniel Seigel (Cheese developers) they
directed me to this bug report.

I installed the following packages: linux-image-2.6.27-8, kernel-image-2.6.27-8
and kernel-image-2.6.27-8-generic. When I boot up with the new kernel, I
immediately have a kernel panic. If you can tell me how I can save the output
on the screen anywhere I'll do that, but from what I see, the CAPS lock simply
blinks repeatedly and nothing works. Not even Ctrl-Alt-Del. I am forced to only
power off the system. It says something like couldn't mount the file system. 
So I tried to install fs-core-modules-2.6.27-8-generic. This does not install 
complaining that it cannot overwrite the kernel object file and hence crashes. 
If I try to report the crash, crash reporter says that It is not a genuine 
Ubuntu version!!??

So the solution (kernel) proposed is not helping me. I guess this kernel 
package should not go into the
next version of the kernel - unless I made some mistake and I have to install 
some other packages.

What next? How do we fix the problem with cheese not recording properly?

I can attach, lspci -vvn, and any other log files you ask for. Please
refer http://bugzilla.gnome.org/show_bug.cgi?id=560983 to see the bug
report of the problem with Cheese for further input on what is happening
with gstreamer.

** Attachment added: Output of lspci -vvn
   http://launchpadlibrarian.net/19747936/lspci-vvn.log

-- 
cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video 
output and disables output on gstreamer-based apps ran afterwards)
https://bugs.launchpad.net/bugs/290506
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 290506] Re: cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards)

[Balaji]

Sorry, This is working perfectly fine. I cleaned everything and
installed only the linux-image-2.6.27-8 and Cheese works like a dream.
Thanks a lot Stefan. This must go into the next version for at least
fixing the problems with Cheese.

However, I am still worried. There is a kernel panic that occured on the
last kernel after about 20-25 minutes of start up. Something was broken.
This was for laptops using the Intel 3294 wireless card. I had to
install some specific package from the backports (linux-backports-
modules-intrepid) . I forgot the bug number, but it is on Launchpad for
sure. If this kernel also shows some wierd stuff I will report here. If
not, I wish it is released soon.

Thanks,
Balaji

-- 
cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video 
output and disables output on gstreamer-based apps ran afterwards)
https://bugs.launchpad.net/bugs/290506
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 282316] Re: erratic elapsed time count in sound recorder

[Balaji]

Guys, my initial complaints taken back.

Sound is working perfectly. It even works across virtual machines
seamlessly. It took me a while to configure them and tweak the settings, but
they are fine now. The recording was having a lot of ambient noise, but I
figured that it was the laptop's internal mic that had a very high
resistance.

The one thing I think Linux still needs to work on, is that upon first
installation, things don't work perfectly. Further, upon an upgrade
apparently some problems persist. These should ideally be fixed early on.

-Balaji

On Sat, Nov 8, 2008 at 5:36 AM, Hew McLachlan
[EMAIL PROTECTED]wrote:

 I'm not running Jaunty, but the description says alsa-plugins 1.0.18
 contains the fix, which means Jaunty should be fine.

 --
 erratic elapsed time count in sound recorder
 https://bugs.launchpad.net/bugs/282316
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
Balaji

-- 
erratic elapsed time count in sound recorder 
https://bugs.launchpad.net/bugs/282316
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-media in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 282316] Re: erratic elapsed time count in sound recorder

[Balaji]

Selecting PulseAudio does not solve the problem for me at all.

I seem to be struggling with PulseAudio. I had to uninstall Pulseaudio and
all its components completely to be able to record anything. So in between
for a short period recording began to work. Then again, all of a sudden,
sound completely stopped. I can no longer hear sound now. Each time the the
System beep occurs the speakers start a loud static noise that sounds more
like an old radio searching for a station.

I don't care and know what driver and which particular module is not
working. SOUND IS NOT WORKING. That's the summary. The SOUND SUPPORT SUCKS.

I  have been trying my best with searching all bug reports on this.

Here are some details:

My sound card is Intel HDA. I do see that there are some specific issues
with this - I don't know and understand them - they are greek to me.

$ uname -r
2.6.27-7-generic

$ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 03)

Here is a link I found for this family of HD Audio controller
http://www.thinkwiki.org/wiki/Intel_82801H_HDA

Please help. I just don't even know where to begin. This is very
frustrating. Sound works on my other laptop which has nVIDIA HDA and in this
one with Intel HDA, it fails miserably.

-Balaji

On Sun, Nov 2, 2008 at 10:01 AM, bugmenot [EMAIL PROTECTED]
wrote:

 Confirmed on fresh install of Ubuntu Intrepid.

 Using gnome-volume-control, the sound for capture must be put close to
 max to hear the sound properly.

 Also, like another said Selecting Pulse Audio Server solves the problem.

 --
 erratic elapsed time count in sound recorder
 https://bugs.launchpad.net/bugs/282316
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
Balaji

-- 
erratic elapsed time count in sound recorder 
https://bugs.launchpad.net/bugs/282316
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 282316] Re: erratic elapsed time count in sound recorder

[Balaji]

Ok, it started working now.

I completely removed PulseAudio and alsa-base. I further reinstalled other
alsa-until packages etc. And rebooted the machine. Things are much better
now. I heard a very load static in the beginning, but I could reduce/correct
that by fixing the volume level. In the process of removing PulseAudio
Ubuntu-desktop gets removed - I did not bother and still removed it. But
somehow things are working. I don't exactly know what I did for this to
start working - but I feel as if I am almost having a very partially working
system.

I'll test Flash, mpg and all other things and see if every sound module
interfaces fine.

Also, one more thing to be noted: I chose Autodetect in Sound Playback, HDA
Intel in Music/Movies and  Audio conferencing. But I had to choose Open
Sound Server in capture. No other combination works. This is really
frustrating. Sound should not have so much tweaking to be done. It should
work out of the box. What Ubuntu does is expecting too much from the general
user. Please fix this. PulseAudio simply does NOT work with Intel devices.
Why do we have it if it does not work. The whole project is a waste and
completely USELESS if it does not work.

Please fix all sound issues before the next release. This is shameful.

-Balaji

On Sun, Nov 2, 2008 at 1:23 PM, Balaji
[EMAIL PROTECTED]wrote:

 Selecting PulseAudio does not solve the problem for me at all.

 I seem to be struggling with PulseAudio. I had to uninstall Pulseaudio and
 all its components completely to be able to record anything. So in between
 for a short period recording began to work. Then again, all of a sudden,
 sound completely stopped. I can no longer hear sound now. Each time the the
 System beep occurs the speakers start a loud static noise that sounds more
 like an old radio searching for a station.

 I don't care and know what driver and which particular module is not
 working. SOUND IS NOT WORKING. That's the summary. The SOUND SUPPORT SUCKS.

 I  have been trying my best with searching all bug reports on this.

 Here are some details:

 My sound card is Intel HDA. I do see that there are some specific issues
 with this - I don't know and understand them - they are greek to me.

 $ uname -r
 2.6.27-7-generic

 $ lspci | grep Audio
 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
 Controller (rev 03)

 Here is a link I found for this family of HD Audio controller
 http://www.thinkwiki.org/wiki/Intel_82801H_HDA

 Please help. I just don't even know where to begin. This is very
 frustrating. Sound works on my other laptop which has nVIDIA HDA and in this
 one with Intel HDA, it fails miserably.

 -Balaji


 On Sun, Nov 2, 2008 at 10:01 AM, bugmenot [EMAIL PROTECTED] wrote:

 Confirmed on fresh install of Ubuntu Intrepid.

 Using gnome-volume-control, the sound for capture must be put close to
 max to hear the sound properly.

 Also, like another said Selecting Pulse Audio Server solves the problem.

 --
 erratic elapsed time count in sound recorder
 https://bugs.launchpad.net/bugs/282316
 You received this bug notification because you are a direct subscriber
 of the bug.




 --
 Balaji



-- 
Balaji

-- 
erratic elapsed time count in sound recorder 
https://bugs.launchpad.net/bugs/282316
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 282316] Re: erratic elapsed time count in sound recorder

[Balaji]

Thanks a lot David et al,

Daniel thanks a great deal for your inputs. Here are some of my
observations.

PulseAudio for sure does not work at all on Intel HDA. My other laptop which
has nVIDIA HDA uses PulseAudio and I wouldn't say that sound worked out of
the box in that either. In general, after Ubuntu 6.10 (Edgy Eft), the ALSA
driver had become quite stable. In 6.06 we still had problems and I could
not get the driver to recognize the headphone being plugged in. But this
retrogression in sound performance at the stage where Ubuntu is today is
simply unacceptable. We CANNOT have a poorly working sound system for a
machine that can perform composite management, virtualization and other
extreme technologies that were not standard just two years back. At this
stage of maturity, Ubuntu's choice of PulseAudio is frustrating and is also
a very very bad choice.

I don't even understand why PulseAudio needs to replicate the functionality
of ALSA. The whole advantage of open source is that you use the work someone
else has done and build upon it. PulseAudio should provide a sound server,
but should not interfere with ALSA. It should use ALSA or OpenSoundSystem
which are lower level modules. That is if at all it should exist. I don't
even see why that project is needed.

Finally, I'll try to check for all the configurations and compile a
resolution to the problem that I found. I could finally get all sound
functionality working fine on this laptop. But I need to think carefully as
to what all I actually did. For sure, I completely removed PulseAudio. But
in addition I also removed alsa-base, though not the complete alsa system.

Meanwhile, let me report one more observation:
A sound static sort of noise is heard often at bootup. This is the point
where libsound2 is being loaded. But the static noise is irritating. I found
that the noise is due to a couple of volume settings that are very high. I
fixed them and rebooted and it works without the noise. Sound recording is a
little noisy - but there could be ample ambient noise in my apartment too.

Thanks,
Balaji

On Mon, Nov 3, 2008 at 12:18 AM, David Henningsson 
[EMAIL PROTECTED] wrote:

 Balaji, I share your frustration over the sound system in Ubuntu. There
 are so many components; we have OSS, ALSA, PulseAudio, Gstreamer, Jack
 etc, and it is difficult to know where to start looking when things go
 wrong. Personally I share your view about PulseAudio - that it does not
 seem stable enough and that Ubuntu probably would be better off without
 it at the moment. Hopefully that will change in the near future.

 But also know that almost all of us are volonteers and luckily one of
 them (Daniel) has time to work with this issue. The best you can do at
 the moment is to have patience and continue to help the Ubuntu project
 in the ways that fit both you and the project (see
 http://www.ubuntu.com/community).

 --
 erratic elapsed time count in sound recorder
 https://bugs.launchpad.net/bugs/282316
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
Balaji

-- 
erratic elapsed time count in sound recorder 
https://bugs.launchpad.net/bugs/282316
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-media in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 282316] Re: erratic elapsed time count in sound recorder

[Balaji]

This is for a system that uses Intel HDA

$ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 03)

I got this audio system to work by the doing the following:
Remove all components of pulseaudio.
Remove alsa-base, but reinstall alsa-oss and alsa-utils, libclalsadrv1,
Further, reinstall, libsound2 and libsound2-plugins, libesdalsa0

I have not yet removed Bluetooth components - I don't have bluetooth. But
after this, I changed the sound settings a little. I changed the Capture to
OpenSoundSystem and the sound outputs to Intel HDA 268 (ALSA)

Finally, I changed adjusted the volume levels and sound works now
perfectly.

The only complaint is with Virtualization. If a virtual machine is using my
sound system, I cannot use it on the host simultaneously. This is upon using
VirtualBox. But that is not a show-stopper. I rarely use Windows on Ubuntu -
only if I ever need to use Office 2007 or if I need to use googletalk to
call someone.

Thanks,
Balaji

On Mon, Nov 3, 2008 at 1:02 AM, Balaji
[EMAIL PROTECTED]wrote:

 Thanks a lot David et al,

 Daniel thanks a great deal for your inputs. Here are some of my
 observations.

 PulseAudio for sure does not work at all on Intel HDA. My other laptop
 which has nVIDIA HDA uses PulseAudio and I wouldn't say that sound worked
 out of the box in that either. In general, after Ubuntu 6.10 (Edgy Eft), the
 ALSA driver had become quite stable. In 6.06 we still had problems and I
 could not get the driver to recognize the headphone being plugged in. But
 this retrogression in sound performance at the stage where Ubuntu is today
 is simply unacceptable. We CANNOT have a poorly working sound system for a
 machine that can perform composite management, virtualization and other
 extreme technologies that were not standard just two years back. At this
 stage of maturity, Ubuntu's choice of PulseAudio is frustrating and is also
 a very very bad choice.

 I don't even understand why PulseAudio needs to replicate the functionality
 of ALSA. The whole advantage of open source is that you use the work someone
 else has done and build upon it. PulseAudio should provide a sound server,
 but should not interfere with ALSA. It should use ALSA or OpenSoundSystem
 which are lower level modules. That is if at all it should exist. I don't
 even see why that project is needed.

 Finally, I'll try to check for all the configurations and compile a
 resolution to the problem that I found. I could finally get all sound
 functionality working fine on this laptop. But I need to think carefully as
 to what all I actually did. For sure, I completely removed PulseAudio. But
 in addition I also removed alsa-base, though not the complete alsa system.

 Meanwhile, let me report one more observation:
 A sound static sort of noise is heard often at bootup. This is the point
 where libsound2 is being loaded. But the static noise is irritating. I found
 that the noise is due to a couple of volume settings that are very high. I
 fixed them and rebooted and it works without the noise. Sound recording is a
 little noisy - but there could be ample ambient noise in my apartment too.

 Thanks,
 Balaji


 On Mon, Nov 3, 2008 at 12:18 AM, David Henningsson 
 [EMAIL PROTECTED] wrote:

 Balaji, I share your frustration over the sound system in Ubuntu. There
 are so many components; we have OSS, ALSA, PulseAudio, Gstreamer, Jack
 etc, and it is difficult to know where to start looking when things go
 wrong. Personally I share your view about PulseAudio - that it does not
 seem stable enough and that Ubuntu probably would be better off without
 it at the moment. Hopefully that will change in the near future.

 But also know that almost all of us are volonteers and luckily one of
 them (Daniel) has time to work with this issue. The best you can do at
 the moment is to have patience and continue to help the Ubuntu project
 in the ways that fit both you and the project (see
 http://www.ubuntu.com/community).

 --
 erratic elapsed time count in sound recorder
 https://bugs.launchpad.net/bugs/282316
 You received this bug notification because you are a direct subscriber
 of the bug.




 --
 Balaji



-- 
Balaji

-- 
erratic elapsed time count in sound recorder 
https://bugs.launchpad.net/bugs/282316
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-media in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 276035] Re: Intrepid: Error microphone: gconfaudiosrc ! audioconvert ! audioresample ! gconfaudiosink profile=chat: Could not get/set settings from/on resource.

[Balaji]

I confirm that.

If the one reading this does not believe that this bug is very much a reality, 
then see the following:
http://ubuntuforums.org/showthread.php?t=956565
http://ubuntu-virginia.ubuntuforums.org/showthread.php?t=908951

Bug# 232173

The number of people facing this bug is overwhelming. This is a shame on
the community. Exactly what causes a perfectly working system to break
in the next release? How do we fix sound recording in Intrepid Beta now.
The developers of PulseAudio and the packagers of Ubuntu are responsible
and answerable to this.

-- 
Intrepid: Error microphone: gconfaudiosrc ! audioconvert ! audioresample ! 
gconfaudiosink profile=chat: Could not get/set settings from/on resource.
https://bugs.launchpad.net/bugs/276035
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 276035] Re: Intrepid: Error microphone: gconfaudiosrc ! audioconvert ! audioresample ! gconfaudiosink profile=chat: Could not get/set settings from/on resource.

[Balaji]

I tried recompiling the alsa drivers and they didn't work either. I
don't even know how to start in order to fix the code. Can anyone please
Please PLEASE look into this bug. It is a serious problem. You cannot
afford to have an operating system that CANNOT record sound. The
microphone simply does not work.

-- 
Intrepid: Error microphone: gconfaudiosrc ! audioconvert ! audioresample ! 
gconfaudiosink profile=chat: Could not get/set settings from/on resource.
https://bugs.launchpad.net/bugs/276035
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 276035] Re: Intrepid: Error microphone: gconfaudiosrc ! audioconvert ! audioresample ! gconfaudiosink profile=chat: Could not get/set settings from/on resource.

[Balaji]

Attaching some information about the ALSA versions being used

** Attachment added: alsa-source.buildlog.2.6.27-7-generic.1225599315
   
http://launchpadlibrarian.net/19213694/alsa-source.buildlog.2.6.27-7-generic.1225599315

-- 
Intrepid: Error microphone: gconfaudiosrc ! audioconvert ! audioresample ! 
gconfaudiosink profile=chat: Could not get/set settings from/on resource.
https://bugs.launchpad.net/bugs/276035
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 276035] Re: Intrepid: Error microphone: gconfaudiosrc ! audioconvert ! audioresample ! gconfaudiosink profile=chat: Could not get/set settings from/on resource.

[Balaji]

Sorry that was the build log the ALSA version being used.

-- 
Intrepid: Error microphone: gconfaudiosrc ! audioconvert ! audioresample ! 
gconfaudiosink profile=chat: Could not get/set settings from/on resource.
https://bugs.launchpad.net/bugs/276035
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 286428] Re: cannot open a pdf file

[Balaji]

Hi

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it without more information. I
am not able to reproduce this bug in 8.04 unfortunately. Can you provide
us more information/inputs on this.

Cheers,
Balaji

-- 
cannot open a pdf file
https://bugs.launchpad.net/bugs/286428
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 286261] Re: deskbar-applet crashed with SIGSEGV in dbus_timeout_handle()

[Balaji]

Hi

Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!

Cheers,
Balaji

-- 
deskbar-applet crashed with SIGSEGV in dbus_timeout_handle()
https://bugs.launchpad.net/bugs/286261
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to deskbar-applet in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 286197] Re: evolution crashed in startup -- offline mode

[Balaji]

Hi

Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!

Cheers,
Balaji

-- 
evolution crashed in startup -- offline mode
https://bugs.launchpad.net/bugs/286197
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 151544] Re: [Gutsy] GNOME takes too much time to load during system boot

[Balaji]

*** This bug is a duplicate of bug 128803 ***
https://bugs.launchpad.net/bugs/128803

What do you use in place of network-manager-gnome? How can one connect to
the internet automatically without it, configure IP addresses etc? I may be
dumb. But this has worked so far in Ubuntu. Having to remove it to make
Ubuntu work is a clear indication of a problem with Ubuntu and not
network-manager-gnome. When will people own up the problem with Gutsy Ubuntu
and correct it? Don't shift the blame to network-manager-gnome.

-Balaji

On Dec 8, 2007 6:32 PM, AntoninoSabetta [EMAIL PROTECTED]
wrote:

 *** This bug is a duplicate of bug 128803 ***
https://bugs.launchpad.net/bugs/128803

 Removing network-manager and network-manager-gnome seems to have solved
 the issue for me.

 --
 [Gutsy] GNOME takes too much time to load during system boot
 https://bugs.launchpad.net/bugs/151544
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
Balaji

-- 
[Gutsy] GNOME takes too much time to load during system boot
https://bugs.launchpad.net/bugs/151544
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for meta-gnome2 in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 151544] Re: [Gutsy] GNOME takes too much time to load during system boot

[Balaji]

That is not true. This is not a problem with nvidia.

I think let us stop beating around the bush and concentrate on the problem.
It was never a problem in Feisty. What has changed since October end is
Ubuntu. I have had the same laptop since October 2006 and have been running
Dapper, Edgy and Feisty with no issues whatsoever. It is only Gutsy that is
the problem.

So for goddamned sure. IT IS A PROBLEM WITH ONLY AND ONLY UBUNTU AND NO
OTHER DEVICE OR OBJECT AROUND. It is really disappointing to see two
phenomena here:

1. Ubuntu support is not taking enough action on this bug. This should be a
priority. It is a shame to the Ubuntu makers that they can't give an
important bug its rightful place.
2. They are simply beating around the bush to try to transfer the blame to
someone else. It is the kernel that is the culprit. The 386 kernel is very
very slow and I find that the generic kernel is not very much improved
either. The older kernel 2.6.17 or 2.6.20 were way better. Even now, if you
try using those kernels, GNOME loads fast.

Clearly it is a problem with the kernel. It is the haughtiness of the kernel
writers that they fail to recognized the problem and fix it. When Ubuntu has
almost no market share as against Microsoft, these guys act so pricey and
all as if they know everything about the problem and keep throwing the blame
from one to another. I have no doubt that they can NEVER EVER stand
Microsoft's competition, if things go down the path of ruin in this manner.

There is NOTHING (I wish I could write in bigger letters to make it clear)
significantly useful added in Gutsy at all. Why did they make this release?
Most people have gone back to Feisty. I don't want Compiz or any other
BULLSHIT - what I want is a fast useful machine.

Balaji

On Nov 29, 2007 12:29 AM, Ricardo Pérez López [EMAIL PROTECTED]
wrote:

 My Gutsy desktop takes ~34 secs to fully load GNOME. The Feisty machines
 in my classroom (I'm a computer science teacher) takes ~12 secs to fully
 load GNOME, and these machines are significantly slower than my home
 desktop computer. Other Gutsy machines in the High School takes 25-30
 secs.

 IMHO, this is a very annoying bug, and, after a brief investigation, I
 think the problem only appears in machines with NVIDIA graphics cards.

 Maybe a compiz - nvidia interaction?

 --
 [Gutsy] GNOME takes too much time to load during system boot
 https://bugs.launchpad.net/bugs/151544
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
Balaji

-- 
[Gutsy] GNOME takes too much time to load during system boot
https://bugs.launchpad.net/bugs/151544
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for meta-gnome2 in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 151544] Re: [Gutsy] GNOME takes too much time to load during system boot

[Balaji]

Andrew
To think that the desktop should look
significantly different between releases is a side effect of having used
Windows too long!  Linux is a progressive development and many of the
tools I use have fixed issues I had in previous releases or added new
functions that I now use.

Balaji
I'm not expecting a significant change in the desktop. In fact between
Feisty and Gutsy there IS a change in the desktop - Compiz. But I don't care
about it. What I'm looking for is:
1. Better driver support for different printer, scanner models etc.
2. Better support of Wireless. My wireless connection setup is still a very
complex procedure.
3. Bettter VPN support
4. POWER MANAGEMENT - This was promised to have improved in Gutsy. I see NO
improvement at all.
5. Better Bluetooth support - I still can't send stuff to my laptop from my
mobile. I don't know when I will send SMSes from my laptop.

I know each one of them have a different software now, like vpnc or
kbluetoothd etc. The thing is I want to use the GNOME version of these and
reduce the disk space involved in installing multiple software. GNOME
promised better work on this.

Power management is a matter of the kernel. In the Gutsy release notes they
said that the use of the new kernel improves power management. BULLSHIT.

Driver support is dependent on their relationship with the community of
programmers writing drivers like SANE or ALSA etc. I don't think they have
good contacts anymore. Almost everything is broken once you migrate from
Feisty. In migrating from one version of OS to the next, I don't want to
keep redoing all the setup activities to work on every software and driver.

Even restricted drivers was a problem. They don't have a generic kernel
based driver from my laptop modem, but a 386 kernel based driver for the
same modem is there! This is bad support indeed.

There is no significant work for which UBUNTU charges for the services. I'm
sure their services suck as much as Gutsy. Till Feisty I was a string
supported of Ubuntu and loved it better than ANY OS. Gutsy is a gross
disappointment indeed. They'll lose patrons at the rate they are rushing to
ruin Linux.

-Balaji


On Nov 29, 2007 2:48 AM, anibal [EMAIL PROTECTED] wrote:

 I do agree in one thing, is an anoying bug. It even feels like wndows
 loading with a mcfee antivirus ;-)

 I do not agree is an envidia problem. I use an internal onboard video
 card no nvidia things.
 For one moment i was thinking it was a network problem, but my network
 is working correctly hosts files is correct network files also. Others X
 env are working properly.. im even thinking to switch to kbuntu but kde
 can be also really buggy.. so i will wait..



 Ricardo Pérez López wrote:
  My Gutsy desktop takes ~34 secs to fully load GNOME. The Feisty machines
  in my classroom (I'm a computer science teacher) takes ~12 secs to fully
  load GNOME, and these machines are significantly slower than my home
  desktop computer. Other Gutsy machines in the High School takes 25-30
  secs.
 
  IMHO, this is a very annoying bug, and, after a brief investigation, I
  think the problem only appears in machines with NVIDIA graphics cards.
 
  Maybe a compiz - nvidia interaction?
 
 

 --
 [Gutsy] GNOME takes too much time to load during system boot
 https://bugs.launchpad.net/bugs/151544
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
Balaji

-- 
[Gutsy] GNOME takes too much time to load during system boot
https://bugs.launchpad.net/bugs/151544
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for meta-gnome2 in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 151544] Re: [Gutsy] GNOME takes too much time to load during system boot

[Balaji]

I confirm this too.

In my case, restarting after one successful boot will surely hang. The
gnome-panel does not come up, some services take too long and it is simply
unknown as to how we can debug this problem at all since even after
Ctrl+Alt+F1 I only get a blank screen and no login prompt or shell at all.

This problem is very critical and the severity level of this problem needs
to be raised to Very high immediately. I have been using Ubuntu since the
Dapper days. I don't have Windows on my machine at all. With this bug in, I
want to go back to using Microsoft Windows and pay for the licenses. I don't
want unreliability. An upgrade should make things better, not worse.

-Balaji

On Nov 12, 2007 2:27 PM, Andrew Henry [EMAIL PROTECTED] wrote:

 A me too comment.

 Acer Aspire 5021WLMi, was running Ubuntu Fiesty and upgraded to Gutsy.
 Since upgrade gdm login takes a long time.

 I also have another issue, that I do not know if others have.  Logging
 into GDM works once.  It takes quite a while.  If I log out and try to
 login a second time, the panels and applets never appear.  Login hangs
 and I need to reboot.   Restarting gdm from a tty does not help.

 --
 [Gutsy] GNOME takes too much time to load during system boot
 https://bugs.launchpad.net/bugs/151544
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
Balaji

-- 
[Gutsy] GNOME takes too much time to load during system boot
https://bugs.launchpad.net/bugs/151544
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for meta-gnome2 in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 147265] Re: gnome-panel crashed with SIGSEGV in g_slist_remove_all()

[Balaji]

** Changed in: gnome-panel (Ubuntu)
   Status: Incomplete = Confirmed

-- 
gnome-panel crashed with SIGSEGV in g_slist_remove_all()
https://bugs.launchpad.net/bugs/147265
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 151544] Re: [Gutsy] GNOME takes too much time to load during system boot

[Balaji]

I also face the same problem. As of now, I have found no stable
solution.

The boot from grub menu to the login screen is fast. But GDM takes too
long to load.

I notice the following:

1. GDM loads only nautilus of late. It used to load several other components as 
well. Is something broken? How do I know and what file do I attach as a report 
for this?
2. gnome-panel does not start at all. It is frustrating that it does not start 
at all. I wonder if you people face this or not. Let me explain. I am currently 
using Compiz-Fusion and full effect. But that does not seem to matter at all. 
This problem has been there ever since.
3. I had run into another problem prior to this: device-mapper: table: 254:1: 
linear: dm-linear: Device lookup failed which keeps getting spammed on my tty 
screen and prevents gnome from loading properly. I noticed this by pressing 
Ctrl+Alt+F1. So I uninstalled evms as has been suggested in other bugs: eg: 
Bug# 115616 in linux-source-2.6.22 However, this problem does not seem to have 
gone at all.
4. I have tried this several times now and am actually scared to shut down my 
laptop since I am completely uncertain if it will reload. In fact, Pidgin loads 
automatically since I have it on the session start-up programs list. This time 
around I was saved because for some reason Gutsy was kind enough to give me a 
terminal at start-up by default. I loaded Firefox through that. I am a normal 
user and so don't know the command name to start the gnome panel. I searched on 
the net and found that it is 'gnome-panel'. Note that I am also a contributor 
to the CPAN pages and also contribute some software to the community. I still 
don't know all Linux commands. I completely disagree that a hacker must be 
knowing everything about this and this problem is simply bugging. I as even a 
hacker (I hacked several problems for my mom and dad at home on Dapper) think 
that sometimes the hacker community acts way too arrogantly in dealing with 
problems. Instead of helping people by using their expertise they expect people 
to do some debugging, but how will they do it if they don't know where to look 
for error messages at all!!? In this particular case for example, NO ERROR 
MESSAGE IS FLAGGED BY ANY PROGRAM except security modules. I ONLY FIND SOME 
ERRORS IN THE .xsession-errors BUT THAT IS A KNOWN BUG IN GTK+ and some 
messages in dmesg. There is nothing apparent at all that I can figure that is 
directly liked with GNOME-panel, but for some reason gnome is broken. This is 
an emergency problem and not something that needs 1000 confirmations before 
some hacker begins solving it. That way we will never have a solution.
5. I have not installed anything new. If Ubuntu installed something in the 
process of having installed Gutsy Gibbon I am not responsible and that is the 
sole responsibility of the developers. I myself am a developer of some 
Electrical Engineering CAD tools, but NEVER EVER release a new version without 
having had complete confidence on it. This is totally irresponsible of 
Canonical to have released a version of Ubuntu without any proper solution to 
these problems with GNOME. 
6. I recreated the initramfs linux image for my platform. The output of my 
'uname -r' : 2.6.22-14-386. This problem has not gone still.

Summary:
HP: V6102AU
Everything on this works so far, except GNOME which breaks very often.
VERY HIGHLY CRITICAL

Inform me of the report files you need.
dmesg output:
[0.00] Linux version 2.6.22-14-386 ([EMAIL PROTECTED]) (gcc version 
4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 Sun Oct 14 22:36:54 
GMT 2007 (Ubuntu 2.6.22-14.46-386)
[0.00] BIOS-provided physical RAM map:
[0.00]  BIOS-e820:  - 0009dc00 (usable)
[0.00]  BIOS-e820: 0009dc00 - 000a (reserved)
[0.00]  BIOS-e820: 000d2000 - 0010 (reserved)
[0.00]  BIOS-e820: 0010 - 3df0 (usable)
[0.00]  BIOS-e820: 3df0 - 3df17000 (ACPI data)
[0.00]  BIOS-e820: 3df17000 - 3df8 (ACPI NVS)
[0.00]  BIOS-e820: 3df8 - 4000 (reserved)
[0.00]  BIOS-e820: e000 - f000 (reserved)
[0.00]  BIOS-e820: fec0 - fec1 (reserved)
[0.00]  BIOS-e820: fee0 - fee01000 (reserved)
[0.00]  BIOS-e820: fff8 - 0001 (reserved)
[0.00] 95MB HIGHMEM available.
[0.00] 896MB LOWMEM available.
[0.00] found SMP MP-table at 000f89d0
[0.00] Entering add_active_range(0, 0, 253696) 0 entries of 256 used
[0.00] Zone PFN ranges:
[0.00]   DMA 0 - 4096
[0.00]   Normal   4096 -   229376
[0.00]   HighMem229376 -   253696
[0.00] early_node_map[1] active PFN ranges
[0.00] 0:0 -   253696
[

[Bug 127375] Re: Ubuntu desktop does not gain focus when all windows close

[Balaji]

This bug is not reproducible under Feisty Fawn 7.04 . The following test
cases were executed

1. I opened up couple of applications and tried closing all of them
using the keyboard first time (Alt + F4) and then pressed Alt + F1 and
the gnome menu got invoked

2. opened couple of applications and tried closing all of them using the
mouse and then pressed Alt  + F1, gnome menu got invoked

In the above cases, after closing all the applications i tried
traversing through the icons on the desktop by using the keyboard arrow
keys and i was able to select a particular icon and open it by pressing
enter key.

Regards
Balaji

-- 
Ubuntu desktop does not gain focus when all windows close
https://bugs.launchpad.net/bugs/127375
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 92879] Re: gnome-sound-recorder unable to playback

[Balaji]

Thanks Boris,

So you mean this is fine on Feisty.

About the interasting behavior, I would expect it to behave that way for
one reason at least - if I were recording and saved a sample, I should not
overwrite that file, till I explicitly save it back on that file. It would
be nice, if the application could automatically call 'Save As' for all
future saves. But I know that it can get quite annoying when not intended.
Perhaps we could have an option to fix that?

I don't know, but looks like the problem I was having with saving this audio
file is now solved.

Hoping that this patch will be uploaded and backported to Feisty.

Thanking Sebastian a lot for his efforts,
Balaji

On 7/30/07, Boris Dušek [EMAIL PROTECTED] wrote:

 @Sebastian: thanks, I will now know for the future

 @jhasse: :-) I guess I will have to visit my eye doctor ;-)

 I tested the patched version on Feisty with the deb provided at comment
 #28 (https://bugs.launchpad.net/ubuntu/+source/gnome-
 media/+bug/92879/comments/28). The new regression that is in SVN is not
 present, so I recommend it the new package for inclusion in feisty-
 backports (maybe in feisty updates after some more testing?).

 On another note, this application still has interesting behavior, like
 when you save the file, and then record again without saving, and play
 back, then not the new recording, but the old saved version is played
 back. But this is there no matter whether the patch in question is
 applied or not, the reason is simply that this application is not being
 developed.

 --
 gnome-sound-recorder unable to playback
 https://bugs.launchpad.net/bugs/92879
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
Balaji

-- 
gnome-sound-recorder unable to playback
https://bugs.launchpad.net/bugs/92879
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 92879] Re: gnome-sound-recorder unable to playback

[Balaji]

When are you likely to recieve this feedback? I am not running Gutsy here.
So I don't know who will give you this feedback.

I am excited about the fix and hope that this really works. Waiting for the
backport to Feisty.

Thanks a lot. A big pain has been solved.

Balaji

On 7/26/07, Sebastien Bacher [EMAIL PROTECTED] wrote:

 It has been fixed in gutsy today. If we get positive feedback on the
 gusty version we will consider a backport to feisty then

 --
 gnome-sound-recorder unable to playback
 https://bugs.launchpad.net/bugs/92879
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
Balaji

-- 
gnome-sound-recorder unable to playback
https://bugs.launchpad.net/bugs/92879
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 92879] Re: gnome-sound-recorder unable to playback

[Balaji]

Hi Sebastian,
Will this be available as an update for feisty and fixed in gutsy?

On 7/26/07, Sebastien Bacher [EMAIL PROTECTED] wrote:
 Thank you for your work on the bug, I'll upload a patched package after
 testing

 --
 gnome-sound-recorder unable to playback
 https://bugs.launchpad.net/bugs/92879
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
Balaji

-- 
gnome-sound-recorder unable to playback
https://bugs.launchpad.net/bugs/92879
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 92879] Re: gnome-sound-recorder unable to playback

[Balaji]

Thanks... :)

Balaji

On 7/26/07, Sebastien Bacher [EMAIL PROTECTED] wrote:

 Usually some users run the unstable version and report new bugs if there
 is a regression and can confirm that the bug is fixed, that's going to
 take a few days though

 --
 gnome-sound-recorder unable to playback
 https://bugs.launchpad.net/bugs/92879
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
Balaji

-- 
gnome-sound-recorder unable to playback
https://bugs.launchpad.net/bugs/92879
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 92879] Re: gnome-sound-recorder unable to playback

[Balaji]

I too have the same problem.

System type: Ubuntu Feisty
Architecture: 2.6.20-16-386
Processor: AMD Turion(tm) 64 X2 Mobile Technology TL-50

I tried running to program from the shell to be able to see the logs.
Upon clicking Play, no message is generated. However upon clicking
Save the following is generated:

(gnome-sound-recorder:29771): libgnomevfs-CRITICAL **:
gnome_vfs_get_file_info_uri_cancellable: assertion `uri != NULL' failed

(gnome-sound-recorder:29771): libgnomevfs-CRITICAL **:
gnome_vfs_uri_unref: assertion `uri != NULL' failed

One might want to check the libgnomevfs modules for errors.

Additionally, 'dmesg | tail' gives the following output. Don't know if
everyone is getting the same, but I'm trying to provide as much info as
possible:

[616631.98] hda: cdrom_pc_intr: The drive appears confused (ireason
= 0x01). Trying to recover by ending request.

No recording is being done on the CD.

Incidentally, recording works fine. Upon quitting, the sound-recording
prompts to save the file. Upon saving the playback works fine.
Additionally, the 'Save As' option also works fine. I think the playback
doesn't work because of bad codec integration with the gnome-sound-
recorder. Please check and fix this bug ASAP.

-- 
gnome-sound-recorder unable to playback
https://bugs.launchpad.net/bugs/92879
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs