Re: [Bug 432814] Re: Touchpad: Action for middle and right click is reversed since jaunty

[mcDavid]

Oleksandr Shybystyi, that doesn't work for gnome3? That's a shame. I think
I'm just going to give OpenSuse a try, I've had it with all those terribly
easy to solve bugs in Ubuntu that are open for more than a year.



On Wed, May 4, 2011 at 8:02 AM, Oleksandr Shybystyi <
oleksandr.shybys...@gmail.com> wrote:

> Those using natty with Unity(gnome 2), could join my PPA
> https://launchpad.net/~o.shybystyi/+archive/gnome-settings-daemon-natty
> .
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (646207).
> https://bugs.launchpad.net/bugs/432814
>
> Title:
>  Touchpad: Action for middle and right click is reversed since jaunty
>
> Status in Gnome Settings Daemon:
>  Invalid
> Status in NULL Project:
>  Invalid
> Status in “gnome-settings-daemon” package in Ubuntu:
>  Fix Released
> Status in “xserver-xorg-input-synaptics” package in Ubuntu:
>  Invalid
> Status in “gnome-settings-daemon” source package in Lucid:
>  New
> Status in “xserver-xorg-input-synaptics” source package in Lucid:
>  Invalid
>
> Bug description:
>  Binary package hint: xserver-xorg-input-synaptics
>
>  LSB version = karmic
>  Package version = 1.1.2-1ubuntu5
>
>  Expected behaviour:
>  Tap the touchpad with 2 fingers simultaneously to generate middle-click
> event. Tap with 3 fingers for right-click event.
>
>  Observed behaviour:
>  A 2-finger tap generates a right-click event and a 3-finger tap generates
> a middle-click event.
>
>
>  Looking at the changelog for 1.1.2-1ubuntu1 I see this:
>  "105_correct_multifinger_click.patch: Swap the right/middle clicks
> generated by multi-finger tapping."
>  This patch is then reverted in 1.1.2-1ubuntu2:
>  "105_correct_multifinger_click.patch: Drop patch as it breaks the expected
> behavior for multitouch clicking (LP: #320585)."
>
>  However, I still experience the behaviour introduced in -1ubuntu1.
>  Hopefully I can help get the expected behaviour back in time for
>  karmic's release.
>
>  ProblemType: Bug
>  Architecture: i386
>  CheckboxSubmission: d90fdc639d79341a7dfe13ba74210bc8
>  CheckboxSystem: 018dd987ae1f42580fa9d31146e40261
>  Date: Sat Sep 19 00:29:42 2009
>  DistroRelease: Ubuntu 9.10
>  MachineType: Packard Bell BV EasyNote MB85
>  NonfreeKernelModules: nvidia
>  Package: xserver-xorg-input-synaptics 1.1.2-1ubuntu5
>  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic
> root=UUID=25b243bb-087e-436e-81ca-bee20d03157b ro quiet splash
>  ProcEnviron:
>   LANG=en_GB.UTF-8
>   SHELL=/bin/bash
>  ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
>  RelatedPackageVersions:
>   xserver-xorg 1:7.4+3ubuntu5
>   libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu5
>   libdrm2 2.4.13-1ubuntu1
>   xserver-xorg-video-intel 2:2.8.1-1ubuntu1
>   xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu1
>  SourcePackage: xserver-xorg-input-synaptics
>  Uname: Linux 2.6.31-10-generic i686
>  dmi.bios.date: 04/07/2008
>  dmi.bios.vendor: Phoenix Technologies LTD
>  dmi.bios.version: PB2A4A04
>  dmi.board.name: PB2A
>  dmi.board.vendor: Packard Bell BV
>  dmi.board.version: Not Applicable
>  dmi.chassis.asset.tag: No Asset Tag
>  dmi.chassis.type: 1
>  dmi.chassis.vendor: Packard Bell BV
>  dmi.chassis.version: N/A
>  dmi.modalias:
> dmi:bvnPhoenixTechnologiesLTD:bvrPB2A4A04:bd04/07/2008:svnPackardBellBV:pnEasyNoteMB85:pvrPC03Q00101:rvnPackardBellBV:rnPB2A:rvrNotApplicable:cvnPackardBellBV:ct1:cvrN/A:
>  dmi.product.name: EasyNote MB85
>  dmi.product.version: PC03Q00101
>  dmi.sys.vendor: Packard Bell BV
>  fglrx: Not loaded
>  system:
>   distro: Ubuntu
>   architecture:   i686kernel: 2.6.31-10-generic
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/gnome-settings-daemon/+bug/432814/+subscribe
>

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

Title:
  Touchpad: Action for middle and right click is reversed since jaunty

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

[Bug 711202] Re: username field doesn't give warning on use of capitals

[mcDavid]

** Attachment added: "screenshot of someone who was very frustrated about not 
being able to complete the installation because nobody told him the username 
field is supposed to be lower-case only"
   
https://bugs.launchpad.net/bugs/711202/+attachment/1821686/+files/IMG_20110201_112631.jpg

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

Title:
  username field doesn't give warning on use of capitals

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

[Bug 711202] [NEW] username field doesn't give warning on use of capitals

[mcDavid]

Public bug reported:

Binary package hint: base-installer

(i hope i've got the package right)
Found in: Ubuntu 10.10 Maverick

When installing ubuntu, the last step is choosing a computername, username, 
password etc.
The username cannot contain capitals, but the input field does accept capitals 
and does not give a clear warning. The only hint is that the field doesn't have 
a green 'v' behind it. This is very confusing for users who have never used the 
old installer so don't know this field cannot contain capitals. I've had to 
help several users on dutch bulletin boards who couldn't finish the installer 
because they had a capital in their username.

If someone uses capitals in this field, it should give a clear warning (red 
cross instead of green 'v'?) with an explanation that says capitals are not 
allowed.
Or, it should be made in a way that capitals are automatically inserted as 
lower case, so it's impossible to use capitals in the first place.

** Affects: base-installer (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  username field doesn't give warning on use of capitals

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

[Bug 697006] [NEW] gwibber-service uses 100% CPU if not connected to internet

[mcDavid]

Public bug reported:

Binary package hint: gwibber

Gwibber-service is constantly using 100% CPU if I have no internet
connection.

It always uses way too much CPU-power for such a simple application (on
startup or refresh), but if I have no internet connection (for example
when I wake my laptop in the train) it just hangs at 100% use, so I have
to kill the process.

Using: 
Ubuntu 10.10 AMD64 (also had the problem with 32-bit build)
kernel 2.6.35-24-generic
Gwibber-service 2.32.2-0ubuntu2

laptop:
Asus K50IN-SX149C
CPU: C2D 2,2GHz
full specs: 
http://tweakers.net/pricewatch/246185/asus-k50in-sx149c.html#tab:info

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

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

Title:
  gwibber-service uses 100% CPU if not connected to internet

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

Re: [Bug 646207] Re: two finger tap produces right-click, three-fingers produces middle-click

[mcDavid]

Is there any status update on this bug? I've made a button now to reset the
tapbuttons to their correct value, but it's still really annoiing that i
have to click that first before it's working right...

Groeten, David


On Tue, Nov 30, 2010 at 6:04 PM, Bartosz Wucke  wrote:

> I suggest Ubuntu exchanges Enter and Esc keys function. This will make
> it even more original.
>
> --
> two finger tap produces right-click, three-fingers produces middle-click
> https://bugs.launchpad.net/bugs/646207
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “xserver-xorg-input-synaptics” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: xserver-xorg-input-synaptics
>
> I'm using: Ubuntu 10.10 beta, xserver-xorg-input-synaptics 1.2.2-2ubuntu5
> Hardware Asus K50IN laptop, with multitouch-touchpad
>
> What I expected to happen:
> I expected two-finger tap to produce a middleclick event, and three-finger
> tap to produce a rightclick event
>
> What happened instead:
> two-finger tap produces a rightclick event, three finger tap produces a
> middleclick event. Two-finger scrolling however, still works perfectly fine
> with two fingers.
>
> It's almost impossible to do a three-finger tap on a small touchpad, and as
> most laptops don't have a "hardware" button for middleclick, this makes it
> very hard to make a middleclick (my second-most used mousebutton) with the
> touchpad.
>
> What I tried to fix it myself:
> I tried to change the mousebutton mapping from 123 etc. to 132 etc. This
> works for the touchpad, but it also changes the "hardware" buttons under the
> touchpad and every other mouse. This is no option.
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/646207/+subscribe
>

-- 
two finger tap produces right-click, three-fingers produces middle-click
https://bugs.launchpad.net/bugs/646207
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 646207] Re: two finger tap produces right-click, three-fingers produces middle-click

[mcDavid]

attached: sysclient.log.

TapButton2  = 3
TapButton3  = 2

Is it just me, or doesn't that make sense at all?

** Attachment added: "sysclient log"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/646207/+attachment/1724460/+files/synclient.log

-- 
two finger tap produces right-click, three-fingers produces middle-click
https://bugs.launchpad.net/bugs/646207
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 646207] Re: two finger tap produces right-click, three-fingers produces middle-click

[mcDavid]

I found the solution for this bug here:

http://ubuntuforums.org/showthread.php?t=1460790

I don't know why but it seems like somehow someone decided it would be a
good idea just to map the tap-actions in the wrong order... I'm just
glad I can fix this problem, I hope it will be reversed for other people
with the same touchpad.

-- 
two finger tap produces right-click, three-fingers produces middle-click
https://bugs.launchpad.net/bugs/646207
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 646207] Re: two finger tap produces right-click, three-fingers produces middle-click

[mcDavid]

I forgot to mention: I've got this problem since upgrading to Maverick
Alpha. On Lucid, the mapping was perfectly fine.

-- 
two finger tap produces right-click, three-fingers produces middle-click
https://bugs.launchpad.net/bugs/646207
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 646207] [NEW] two finger tap produces right-click, three-fingers produces middle-click

[mcDavid]

Public bug reported:

Binary package hint: xserver-xorg-input-synaptics

I'm using: Ubuntu 10.10 beta, xserver-xorg-input-synaptics 1.2.2-2ubuntu5
Hardware Asus K50IN laptop, with multitouch-touchpad

What I expected to happen:
I expected two-finger tap to produce a middleclick event, and three-finger tap 
to produce a rightclick event

What happened instead:
two-finger tap produces a rightclick event, three finger tap produces a 
middleclick event. Two-finger scrolling however, still works perfectly fine 
with two fingers.

It's almost impossible to do a three-finger tap on a small touchpad, and
as most laptops don't have a "hardware" button for middleclick, this
makes it very hard to make a middleclick (my second-most used
mousebutton) with the touchpad.

What I tried to fix it myself:
I tried to change the mousebutton mapping from 123 etc. to 132 etc. This works 
for the touchpad, but it also changes the "hardware" buttons under the touchpad 
and every other mouse. This is no option.

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New

-- 
two finger tap produces right-click, three-fingers produces middle-click
https://bugs.launchpad.net/bugs/646207
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 605128] Re: gnome-language-selector crashed with OSError in find_string_and_replace()

[mcDavid]

> FYI, this may be related to the fact that / is a btrfs filesystem.

I'm experiencing this bug with EXT4

-- 
gnome-language-selector crashed with OSError in find_string_and_replace()
https://bugs.launchpad.net/bugs/605128
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 573987] [NEW] No error on wrong password

[mcDavid]

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

Public bug reported:

Binary package hint: gdebi

Ubuntu 10.04 LTS

Gdebi 0.6.0ubuntu1
1) Open a random .deb file
2) click install
3) enter a wrong password
4) gdebi quits without a warning. Of course you would expect an error like 
"wrong password" or so, and the posibility to try again.

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

-- 
No error on wrong password
https://bugs.launchpad.net/bugs/573987
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 519099] [NEW] ftp doesn't reconnect when trying to save an open file

[mcDavid]

Public bug reported:

Binary package hint: nautilus

1) Open a text-file on an FTP location with Gedit
2) Wait till the connection is closed
3) Try to save the text-file

This won't work, you'll have to go to nautilus, refresh a folder on the
FTP-location, and then save the file again.

Connection should be automatically re-established when some program
tries to save to the FTP-location.

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

-- 
ftp doesn't reconnect when trying to save an open file
https://bugs.launchpad.net/bugs/519099
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Re: [Bug 438536] Re: Notifications should show up closer to top right

[mcDavid]

>What happens when the regular part of your interface that you are trying to
>interact with is located below the close button?

You could either locate the close-button somewhere else (like on the gnome
panel just above) or dismiss all queing notifications when a close-button is
clicked.

I also think the notifications are not faded enough right now. It's still
quite hard to see what you're clicking on through the notification bubble.

Groeten, David


2009/11/19 Scott Armitage 

> >
> > Actually I kinda like the fact that the notification is just a
> notification
> > and you can click trough it.
> > Maybe a close button could be a good idea though.
> >
>
> What happens when the regular part of your interface that you are trying to
> interact with is located below the close button? You would be forced to
> then
> close the notification prior to being able to interact with your interface.
> What's worse, is what if there are several notifications in the queue? Each
> time you close one, the next one pops up -- you are prevented from
> interacting with your desktop until the notification queue has been
> depleted.
>
> --
> Scott Armitage, B.A.Sc., M.A.Sc. candidate
> Space Flight Laboratory
> University of Toronto Institute for Aerospace Studies
> 4925 Dufferin Street, Toronto, Ontario, Canada, M3H 5T6
>
> --
> Notifications should show up closer to top right
> https://bugs.launchpad.net/bugs/438536
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in One Hundred Paper Cuts: Invalid
> Status in Notify OSD: Triaged
> Status in “notify-osd” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: notify-osd
>
> Currently the notify-osd notifications allot space for the volume
> control/brightness semi-notifications; this is rather jarring when the
> volume/brightness isn't being adjusted, unlike in Jaunty where application
> notifications default to above the volume/brightness.
>
> -
> This is a design decision , any comments relating to the position can be
> discussed  in the ayatana Mailing list or you can follow the discussion >
> http://www.mail-archive.com/ayat...@lists.launchpad.net/msg00741.html
>
> Any discussion regarding the position need to be discussed in the mailing
> list.
> --
>
> Mark Shuttleworth's comments from the mailing list:
>
> "The position is final for 9.10 but can certainly be reconsidered for
> Lucid.
>
> The factors that need to be considered are:
>
>  * fitting things into the corner is most aesthetically pleasing
>
>  * the "synchronous" notifications (like brightness and volume) are fixed
> in size
>
>  * the async notifications (IM's etc, things that happen elsewhere, not in
> response to a keypress) are variable sized and can grow vertically
>
>  * sliding things around when something else grows is really bad, it is
> unpredictable and frustrating for a user trying to look at the thing
> that suddenly moves, so:
> - synchronous should not be below async (so that it does not have to
> slide down)
> - the bottom right corner doesn't work (because then async has to grow
> "upwards")
>
>  * the top right corner has a lot of stuff there - window decorations,
> tabs, tab controls (new tab, close tab etc) and in many apps, a search
> input. So even though the look-through and click-through is *cool*, it's
> still better not to put async right into the top right corner
>
> For 9.10, two positions were considered and tried:
>
> In both cases, we put sync above and async below, to avoid sliding
> problems. We put them on the right hand side of the screen, as that's a
> less-used area.
>
> In the first case, we used the midpoint of the right side of the screen and
> placed the notifications there, with sync above and async below. It seems
> slightly odd to have them "hanging in space", but they conflict
> with far less content there. This was the plan for 9.10. However, when it
> landed, there were a lot of complaints saying that folks didn't like it "out
> of a corner".
>
> As a compromise, we moved to plan b, which was to put them in the top
> right, with sync above. That means that the common case, with async
> notifications, appears to leave a "gap". But it also avoids the worst
> overlaps with things like window and tab controls, and usually also the
> search bar.
>
> That's where we settled for 9.10. For 10.04 I would like to revisit the
> midpoint of the right hand side. I would not want to rehash old territory,
> so please factor in the above in proposing new ideas. I'm of
> the view that this decision involves at least one ugly compromise no matter
> which way it goes, and am happy to make the call so far (i.e. happy to be
> the one with the thick skin).
>
> If there is an implementation which avoids the issues and is sane, I'd love
> to include it.
>
> Mark"
>
>

-- 
Notifications should show up closer to top right
https://bugs.launchpad.net/bugs/438536
You received this bug n

[Bug 475815] Re: firefox about-window too small (dutch language-pack)

[mcDavid]

** Attachment added: "Schermafdruk.png"
   http://launchpadlibrarian.net/35191314/Schermafdruk.png

** Also affects: firefox
   Importance: Undecided
   Status: New

-- 
firefox about-window too small (dutch language-pack)
https://bugs.launchpad.net/bugs/475815
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 475815] [NEW] firefox about-window too small (dutch language-pack)

[mcDavid]

Public bug reported:

Binary package hint: firefox-3.5

The "about mozilla firefox" (or in dutch: "over mozilla firefox") window
is just a bit too small to contain all the text in it.

One can make the window bigger, but I think this is an unnecessary
little glitch.

see attached screenshot.

** Affects: firefox
 Importance: Undecided
 Status: New

** Affects: firefox-3.5 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
firefox about-window too small (dutch language-pack)
https://bugs.launchpad.net/bugs/475815
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Re: [Bug 438536] Re: Notifications should show up closer to top right

[mcDavid]

*#5. The developers says that it's more important that notify-os makes sense
to new users, rather than allowing old users to customize the desktop.
*
The first reaction of a college-mate of me (who has always runned KDE) when
I showed him the "new ubuntu" was "*Hey, the notifications are misplaced, is
that a bug in the beta-release?"*. And to be honest, that was my first
reaction too. I only learned there is a difference between "synchronous" and
"asynchronous" notifications when I read about it while trying to file a bug
report about it.

I think we have to look at the notifications in an other way to solve this
issue. We can go in two directions:

#1: No difference is being made between "asynchronous" and "synchronous"
notifications, and they are handled exactly the same way. If the system does
make a difference, it will only be confusing to users.

#2: If we dó make a difference, this difference should immediately be clear
to users. For example by giving them a different layout and/or a compeltely
different location (as some users suggested, put the synchronous ones in the
middle of the screen).

Groeten, David


2009/11/2 cristian.vrabie 

> Having read this head to tail I see that the discussion is becoming
> repetitive and not bringing nothing new, I think we should push it into
> a more constructive direction. I will summarize the most important
> points that have been said and add my 2 cents.
>
> #1. The "old" notify-osd version had no clear rules. It displayed the
> messages as they come.
> #2. Some people complained that it's obstructing some important components
> like the minimize/close buttons and Firefox search bar.
> #3. The "new" version choses to have predictable positions for the
> synchronous/asynchronous messages so that the synchronous messages now do
> not obstruct the above mentioned components.positions
> #4. The "new" version looks bad to some/many (old) users.
> #5. The developers says that it's more important that notify-os makes sense
> to new users, rather than allowing old users to customize the desktop.
> #6. Users reply that a mature os should do both (make sense to new users
> and be pleasing to old users).
> #7. Users ask for at least a way to customize the behavior back to the
> original behavior.
> #8. The developers say that adding more customization is bad.
>
> Ok. My point of view:
> #A. I understand the need for #3 and #5 but I don't think that the current
> solution is the best solution for #4 and #6. However i cannot say that I
> have a better, new one.
> #B. I would add that we must understand that the majority of new users are
> not all new, but probably had some contact with another OS. In neither OS
> that I know a similar solution is used so it probably isn't that good for
> them either. At least the old version looked like the usual Windows
> notification but in reverse (coming down instead of going up).  This
> combined with #4 makes the old version better than the current one.
> #C. If indeed the Gnome3 approach is the one presented above, we should
> also consider that the transition to that is smooth, not a complete
> redefinition.
> #D.  We need to take into account scalability. The new design makes some
> assumptions that are not all in all correct, like: "all sync messages have a
> fixed size". Will this solution still fit as new notifications are added or
> the granularity of the current one will be increased. We don't know on what
> devices will Ubuntu run next and what messages/notifications will those
> offer.
> #E. We (the users) need to understand that what the developers main purpose
> is that "Ubuntu succeeds". Windows and Mac OS have proved that less
> configurability works, when many distributions that were driven by the
> community have failed. It is in my opinion a good decision to keep
> configurability low. However #5 is a very good point. This is open source.
> Why add reasons for a fork. Plus, where to place the notifications is not a
> life changing decision. My solutions would be:
>  - #E.1. Allow configurabilly from a configuration file. The new users
> wouldn't be confused by many options and the old/advanced users would still
> have the option to configure it to their pleasing.
>  - #E.2. Do a vote or better, a research with both old and new users.
>
> Hope this helps bringing the community and the developers to a consent.
>
> --
> Notifications should show up closer to top right
> https://bugs.launchpad.net/bugs/438536
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in One Hundred Paper Cuts: Invalid
> Status in Notify OSD: Triaged
> Status in “notify-osd” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: notify-osd
>
> Currently the notify-osd notifications allot space for the volume
> control/brightness semi-notifications; this is rather jarring when the
> volume/brightness isn't being adjusted, unlike in Jaunty where application
> notifications def

Re: [Bug 438536] Re: Notifications should show up closer to top right

[mcDavid]

Everybody keeps saying that sliding notifications is wrong, but looking at
the sample somebody else posted:
http://www.markshuttleworth.com/archives/253
I don't think its annoying or anything at all. I think it looks very nice. I
think this would be the best way to solve this problem.

Groeten, David


2009/10/31 quatsch3000 

> I would like to make a suggestion and consider the points that were
> addressed by Marc. Main point for me is that notifications should appear
> in a corner. And imo the notifications look quite misplaced currently.
> Also I would rather not be able to see the window decoration for a
> second than the window's content. For these two reasons I would prefer
> another solution to the synch/asynch-problem. The differentiation into
> sync and async notifies itself is not as bad as I thought in the
> beginning, but still, placing the notifications so low as a consequence
> just seems plain wrong.
>
> So my suggestion is (similar to Greg Nicholson's and others) to keep the
> differentiation but place the synchronous notifications somewhere else
> (e.g. centred on the screen, maybe even for a little shortened period)
> while keeping the asynchronous notifications in the corner. (Yes, I
> know, that might seem MAC-like to some but just because someone already
> thought of it, does not automatically mean it's wrong.) Or, to get back
> to the points, Marc made:
>
> "The factors that need to be considered are:
>  * fitting things into the corner is most aesthetically pleasing"
> true. +1
>
> " * the "synchronous" notifications [...] are fixed in size"
> Okilidokili, they can appear centred and fade out after a second or so.
>
> " * the async notifications [...] are variable sized and can grow
> vertically"
> Shouldn't be a problem any more because the synchronous notifications are
> out of the way
>
> " * sliding things around when something else grows is really bad, it is
> unpredictable and frustrating for a user trying to look at the thing
> that suddenly moves, so:
> - synchronous should not be below async (so that it does not have to
> slide down)
> - the bottom right corner doesn't work (because then async has to grow
> "upwards")"
> Ok, so no movement of the notifications. Let's stick with the sequential
> appear-disappear solution. Also as I said above: "Shouldn't be a problem any
> more because the synchronous notifications are out of the way."
>
> " * the top right corner has a lot of stuff there - window decorations,
> tabs, tab controls (new tab, close tab etc) and in many apps, a search
> input. So even though the look-through and click-through is *cool*, it's
> still better not to put async right into the top right corner"
> That's where I disagree for three reasons: 1.) "fitting things into the
> corner is most aesthetically pleasing", 2.) If I had to decide between
> seeing the decoration and the window's content, I would always go for the
> window's content. And 3.) If I really had to press a button (new tab or so)
> in that exact second, I would have to move my cursor there anyway, thus
> making the notification transparent.
>
> --
> Notifications should show up closer to top right
> https://bugs.launchpad.net/bugs/438536
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in One Hundred Paper Cuts: Invalid
> Status in Notify OSD: Triaged
> Status in “notify-osd” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: notify-osd
>
> Currently the notify-osd notifications allot space for the volume
> control/brightness semi-notifications; this is rather jarring when the
> volume/brightness isn't being adjusted, unlike in Jaunty where application
> notifications default to above the volume/brightness.
>
> -
> This is a design decision , any comments relating to the position can be
> discussed  in the ayatana Mailing list or you can follow the discussion >
> http://www.mail-archive.com/ayat...@lists.launchpad.net/msg00741.html
>
> Any discussion regarding the position need to be discussed in the mailing
> list.
> --
>
> Mark Shuttleworth's comments from the mailing list:
>
> "The position is final for 9.10 but can certainly be reconsidered for
> Lucid.
>
> The factors that need to be considered are:
>
>  * fitting things into the corner is most aesthetically pleasing
>
>  * the "synchronous" notifications (like brightness and volume) are fixed
> in size
>
>  * the async notifications (IM's etc, things that happen elsewhere, not in
> response to a keypress) are variable sized and can grow vertically
>
>  * sliding things around when something else grows is really bad, it is
> unpredictable and frustrating for a user trying to look at the thing
> that suddenly moves, so:
> - synchronous should not be below async (so that it does not have to
> slide down)
> - the bottom right corner doesn't work (because then async has to grow
> "upwards")
>
>  * the top right corner has a

Re: [Bug 438536] Re: Notifications should show up closer to top right

[mcDavid]

I think the best solution would be to put the notification in the highest
free position, so that if there are more notifications at the same time,
they show up underneath each other.

I think it would also be nice to have them slide up if a higher notification
disappears.

The best option by far would be to have a config tab in the
appearance-window, so everybody can choose his/her own favorite behavior.


2009/10/20 Francisco Diéguez 

> And why not differenciate notification events with colors or icons?
>
> I think that with icons it will be more graphical and with a simple view
> of the notification you can "know" what  is about.
>
> --
> Notifications should show up closer to top right
> https://bugs.launchpad.net/bugs/438536
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in One Hundred Paper Cuts: Invalid
> Status in Notify OSD: Triaged
> Status in “notify-osd” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: notify-osd
>
> Currently the notify-osd notifications allot space for the volume
> control/brightness semi-notifications; this is rather jarring when the
> volume/brightness isn't being adjusted, unlike in Jaunty where application
> notifications default to above the volume/brightness.
>
> ProblemType: Bug
> Architecture: i386
> Date: Tue Sep 29 01:15:29 2009
> DistroRelease: Ubuntu 9.10
> GtkTheme: DarkRoom
> IconTheme: Humanity
> MachineType: ASUSTeK Computer INC. 1005HA
> Package: notify-osd 0.9.22-0ubuntu1
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic
> root=UUID=76c53fb3-d079-4002-a434-4fb674c9613e ro quiet splash
> ProcEnviron:
>  LANG=en_US.UTF-8
>  SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
> RelatedPackageVersions:
>  xserver-xorg 1:7.4+3ubuntu5
>  libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu6
>  libdrm2 2.4.13-1ubuntu1
>  xserver-xorg-video-intel 2:2.8.1-1ubuntu2
>  xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu2
> SourcePackage: notify-osd
> Tags:  ubuntu-unr
> Uname: Linux 2.6.31-11-generic i686
> WindowManager: gnome-wm
> dmi.bios.date: 09/23/2009
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 0905
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: 1005HA
> dmi.board.vendor: ASUSTeK Computer INC.
> dmi.board.version: x.xx
> dmi.chassis.asset.tag: 0x
> dmi.chassis.type: 10
> dmi.chassis.vendor: ASUSTeK Computer INC.
> dmi.chassis.version: x.x
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr0905:bd09/23/2009:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
> dmi.product.name: 1005HA
> dmi.product.version: x.x
> dmi.sys.vendor: ASUSTeK Computer INC.
>

-- 
Notifications should show up closer to top right
https://bugs.launchpad.net/bugs/438536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 452473] Re: notification position is too low

[mcDavid]

Correction: not *all* notifications are too low, volume, brightness,
etc. notifications show up in the right position. Other notifications
show up right underneath it, which is quite nice but only if there
indeed ís another notification above it...

Again, screenshot attached..

** Attachment added: "Schermafdruk-3.png"
   http://launchpadlibrarian.net/33755316/Schermafdruk-3.png

-- 
notification position is too low
https://bugs.launchpad.net/bugs/452473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 452473] Re: notification position is too low

[mcDavid]

another screenshot...

** Attachment added: "Schermafdruk-1.png"
   http://launchpadlibrarian.net/33752384/Schermafdruk-1.png

-- 
notification position is too low
https://bugs.launchpad.net/bugs/452473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 452473] Re: notification position is too low

[mcDavid]

** Attachment added: "Schermafdruk.png"
   http://launchpadlibrarian.net/33751945/Schermafdruk.png

-- 
notification position is too low
https://bugs.launchpad.net/bugs/452473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 452473] [NEW] notification position is too low

[mcDavid]

Public bug reported:

Notifications show up too low. This applies to all notifications, they
all show up at the same position, but it's quite a bit lower than you
would expect.

See attached screenshot.

Unbuntu version: Ubuntu Karmic 9.10Beta

libnotify1:
  Geïnstalleerd: 0.4.5-1ubuntu1
  Kandidaat: 0.4.5-1ubuntu1
  Versietabel:
 *** 0.4.5-1ubuntu1 0
500 http://nl.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status

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

-- 
notification position is too low
https://bugs.launchpad.net/bugs/452473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 152187] Re: Serial Wacom tablet fails to return from ACPI suspend to RAM

[mcDavid]

I've got exactly the same problem, running Ubuntu 9.04B, kernel
2.6.28-11, using a Bamboo fun medium tablet.

-- 
Serial Wacom tablet fails to return from ACPI suspend to RAM
https://bugs.launchpad.net/bugs/152187
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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