[Desktop-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged

2015-03-10 Thread Raymond
how did you set the pin default of subwoofer ?


  Pin Default 0x90170111: [Fixed] Speaker at Int N/A
Conn = Analog, Color = Unknown
DefAssociation = 0x1, Sequence = 0x1
 Misc = NO_PRESENCE



  subwoofer may use same DAC if  there is low pass filter, 

did your hear sound from speaker  and subwoofet ?

spk_outs = 14/18/0/0 : 4/4/0/0
  spk path: depth=3 '04:0e:14'
  spk path: depth=3 '04:0e:18'

you need four channels and software low pass filter only when there is
no hardware low pass filter

multi_outs = 14/18/0/0 : 2/3/0/0 (type SP)
  out path: depth=3 '02:0c:14'
  out path: depth=3 '03:0d:18'

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1302090

Title:
  Dell Alienware 14, Speaker sound output is mono until a headphone jack
  is plugged

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Here's the required release and package information:

  Description:Ubuntu Trusty Tahr (development branch)
  Release:14.04

  Package: linux-image-extra-3.13.0-19-generic
  Version: 3.13.0-19.40

  When playing audio through speakers on my Alienware 14 2014, the sound
  output is in mono until I plug a headphone in any of the two available
  headphone jacks (obviously, the auto-mute option must be disabled).
  When I do so, the sound starts to play in stereo.

  I would love the sound output to be stereo by default and not be
  forced to plug anything to achieve that.

  Attached is the alsa-info.sh output for my machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5

2015-03-10 Thread Kal Solette
It's been over two weeks now and no sign of a fix or even a response. So
sorry, I'm going back to Windows again. Everytime I try to get away from
it and use Ubuntu I get slapped in the face with bugs and issues. Why do
I even bother?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1424491

Title:
  apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5

Status in fglrx-installer package in Ubuntu:
  Confirmed

Bug description:
  Activity:  Install fglrx AMD driver on 12.04.5 and 14.02.2

  Expected behavior:  fglrx would intall

  Observed behavior:  fglrx is not installed as follows


  Attempt to install fglrx fails as follows:

  zack3@ZACK3:~$ sudo apt-get install fglrx-updates xvba-va-driver
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   fglrx-updates : Depends: xorg-video-abi-11 but it is not installable 
or
    xorg-video-abi-12 but it is not installable 
or
    xorg-video-abi-13 but it is not installable 
or
    xorg-video-abi-14 but it is not installable 
or
    xorg-video-abi-15
  E: Unable to correct problems, you have held broken packages.


  
  Attempt to insatll xorg-video-abi-15 yields:

  zack3@ZACK3:~$ sudo apt-get install xorg-video-abi-15
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Note, selecting 'xserver-xorg-core' instead of 'xorg-video-abi-15'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it 
is not going to be installed
     Depends: libcogl15 (= 1.15.8) but it is not going 
to be installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not 
going to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is 
not going to be installed
  Depends: libcogl15 (= 1.15.8) but it is not 
going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be 
caused by held packages.


  
  Attempting to install xserver-xorg-core instead yields:

  zack3@ZACK3:~$ sudo apt-get install xserver-xorg-core
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it 
is not going to be installed
     Depends: libcogl15 (= 1.15.8) but it is not going 
to be installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not 
going to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is 
not going to be installed
  Depends: libcogl15 (= 1.15.8) but it is not 
going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be 
caused by held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1424491/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1382462] Re: 10de:0dfa Desktop/windows painted incorrectly in dual monitor configuration

2015-03-10 Thread Francisco Gouveia
After days lost with replacing NVidia drivers and manually editing
xorg.conf file, I finally found this!

Rockwalrus (rockwalrus) solution works!

On CompizConfig Settings Manager, go to General Options, then Display
Settings and do the following:

- Uncheck Deteck Outputs
- In the Outputs array, set the resolutions of each of your screens. The 
numbers after the resolution 1920x1080+0+0 are the offset. It's important to 
add this offset according to your needs. I have two full HD screens, so I added 
the following configuration:
1920x1080+0+0
1920x1080+1920+0

The second output has an offset of 1920, because it is on the right side
of the first output, which has a width of 1920.

I was hopeless already, what a relief!

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

Title:
  10de:0dfa Desktop/windows painted incorrectly in dual monitor
  configuration

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the broken one nor destroys the good one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is created whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  

[Desktop-packages] [Bug 1377872] Re: Double-buffered compositing performance is very poor (30 FPS) on intel

2015-03-10 Thread Daniel van Vugt
I wonder if calling gbm_surface_lock_front_buffer() a bit earlier would
keep the system sufficiently awake to avoid this?...

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

Title:
  Double-buffered compositing performance is very poor (30 FPS) on intel

Status in Mesa:
  Confirmed
Status in Mir:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Double-buffered compositing performance is poor.

  Fortunately we don't use double-buffering in our default compositor
  (mostly), and Ubuntu touch does not use the default compositor either.
  However, if you make the compositor double-buffered, then it quickly
  drops down to 30 FPS while not consuming any significant CPU or render
  time.

  Test case A:
  Convert your compositor to double buffering by the code change suggested in 
bug 1350725.

  Test case B (different bug?):
  Switch all clients to double-buffering using this branch:  
lp:~vanvugt/mir/double
  and then start a nested server.

  Now start a bunch of clients, and you will find they slow down to 30
  FPS after only starting a few. This does not happen with the default
  triple buffered compositor.

  I've been ignoring this issue for a little while [1] thinking I had simply 
run out of power, although suspected that can't be right as this is a powerful 
quad-core i7 and it's slowing down with only 10 clients.
  [1] https://bugs.launchpad.net/mir/+bug/1350725/comments/1

  Now today test case B has revealed (via MIR_CLIENT_PERF_REPORT) that
  the slowdown happens without using any significant render time (less
  than 2 ms) and without using any significant CPU (less than 20% of one
  out of four cores).

  So the conclusion is our default compositor is probably holding
  buffers for a little too long somewhere. Because that's the only
  sensible reason I can think of for my system to bog down to 30 FPS
  without stressing the CPU or GPU. We've got poor parallelism in our
  code somewhere. And once that's solved, we'll be able to make further
  improvements such as resolving bug 1350725.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 763148] Re: Adding/Removing an external monitor causes open windows to move to another workspace

2015-03-10 Thread Roland Bock
Yeah, this is still/again an issue in 14.04 (with Unity)

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

Title:
  Adding/Removing an external monitor causes open windows to move to
  another workspace

Status in Compiz:
  Fix Released
Status in Compiz 0.9.9 series:
  Fix Released
Status in Compiz Core:
  Fix Committed
Status in compiz package in Ubuntu:
  Fix Released
Status in compiz source package in Precise:
  Fix Released

Bug description:
  [Impact]
  Many users will put different windows in different workspaces for better work 
flow.  If a user connects and/or disconnects an external monitor or projector, 
all of these windows will be put in the first workspace.  Having to go back and 
move all of the windows back to their workspaces is very frustrating and time 
consuming.

  [Test Case]
  #. Open some applications in different workspaces.
  #. Plug in an external monitor.

  [Regression Potential]
  Very low possibility that a window still ends up in the wrong workspace.

  

  Original description:
  well, i plug in my external screen.

  expected behaviour would be, if all of my windows would stay in the
  workspaces i aligned them to, and if they'd be on the same screen i
  had them in the first place.

  unfortunatly in unity, if i plug-in (or plug-off) my external screen
  the windows are all around, but not where i'd expect them to be
  (namely in the same place they were before). so i always have to
  toggle expo-mode and re-align all of my windows.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 584632]

2015-03-10 Thread Ehsan-mozilla
(In reply to Jorg K from comment #38)
 Coming back to the suggestion from comment #25 and looking in
 nsFrame::HandlePress.
 
 I traced it down into ns[Text]Frame::GetChildFrameContainingOffset with a
 call stack of:
 
 nsFrame::GetChildFrameContainingOffset *or*
 nsTextFrame::GetChildFrameContainingOffset
 nsFrameSelection::GetFrameForNodeOffset
 nsFrameSelection::BidiLevelFromClick
 nsFrameSelection::HandleClick
 nsFrame::HandlePress
 
 It varies whether nsFrame::GetChildFrameContainingOffset or
 nsTextFrame::GetChildFrameContainingOffset is being called depending on
 whether you click on the text, but almost to the left of the text, or
 completely to the left of the text.
 
 When the nsTextFrame::GetChildFrameContainingOffsetAny version is called, it
 offset is calculated correctly and the font is right. When the
 nsFrame::GetChildFrameContainingOffset is called, the font is wrong. In the
 latter case the caret still appears behind the text.

Yes, this is what I was explaining in comment 22.  The frame on which
this function is called depends on the frame receiving the click event;
if you click on the text it's going to be a textframe, otherwise it's
going to be the parent frame (in the normal case as in the test case you
describe above) or anything else that is under the mouse cursor.

 Try it with a wide letter, like m!
 
 So in case a Frame being hit instead of a TextFrame, perhaps the program
 should look whether there is a text right before the caret once placed.

No, we shouldn't change the way that we hit-test to find out which frame
was clicked.

As I said in comment 22, we should probably look into normalizing the
selection, so that if the line ends in an inline frame containing a text
frame, we should put the selection at the end of the text frame as
opposed to at the end of the inline frame terminating the line.

But before we can do that, we need to investigate the behavior of other
engines in this situation (as in, we should see where they put the
selection.)  You need to create a test case which lets you click
somewhere and have it dump out the place of the selection (which you can
get through window.getSelection()).  The simplest way to create such a
test case is to set it up to print the selection after 10 seconds or so.
Then you should document the behavior of IE/Chrome/Opera/Safari on that
test case.  If they all agree on putting the selection where I described
above (IIRC some of the engines did that the last time I tested this
years ago) then we can look into changing our code.  Beware that it will
probably take a significant amount of work adjusting everywhere in our
code where we depend on the existing behavior, same in our existing
tests.

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

Title:
  composer changes font mid email

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: thunderbird

  As I'm typing my emails in Thunderbird, I can see what appears to be a
  font size change on screen, normally in the second line of text. The
  second line appear smaller than the first. It's barely perceptible, so
  half them time I think I am imagining it.

  Well, I've started Bccing to myself to check, and the emails I am
  receiving from myself are not only a different size, they're also a
  different font. Composer starts in some default serif, and by the
  second line is sans. I'd bee glad to email someone viz thunderbird,
  and also send along a screenshot of how it looks while I am typing.

  Thanks.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 584632]

2015-03-10 Thread Mozilla-jorgk
Created attachment 8574843
Stripped down Midas demo, also alerts on clicks and dumps out info

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

Title:
  composer changes font mid email

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: thunderbird

  As I'm typing my emails in Thunderbird, I can see what appears to be a
  font size change on screen, normally in the second line of text. The
  second line appear smaller than the first. It's barely perceptible, so
  half them time I think I am imagining it.

  Well, I've started Bccing to myself to check, and the emails I am
  receiving from myself are not only a different size, they're also a
  different font. Composer starts in some default serif, and by the
  second line is sans. I'd bee glad to email someone viz thunderbird,
  and also send along a screenshot of how it looks while I am typing.

  Thanks.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 584632]

2015-03-10 Thread Mozilla-jorgk
More results:
Safari (5.1.7, had it on some old machine): Same behaviour as Chrome.
Opera (27.0, fresh install): Same behaviour as Chrome.

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

Title:
  composer changes font mid email

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: thunderbird

  As I'm typing my emails in Thunderbird, I can see what appears to be a
  font size change on screen, normally in the second line of text. The
  second line appear smaller than the first. It's barely perceptible, so
  half them time I think I am imagining it.

  Well, I've started Bccing to myself to check, and the emails I am
  receiving from myself are not only a different size, they're also a
  different font. Composer starts in some default serif, and by the
  second line is sans. I'd bee glad to email someone viz thunderbird,
  and also send along a screenshot of how it looks while I am typing.

  Thanks.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 584632]

2015-03-10 Thread Mozilla-jorgk
Sadly I don't understand some of what you wrote. Let me see what I
understood.

You're saying you want to check how other rendering engines behave. I
ran the test from comment #37 on Chrome and IE. Both continue text entry
with the font present on the first line, so their behaviour is what I
would expect.

Next you talk about test cases where you click and dump out the
selection. In this case, we do a single click, so the selection will
have one collapsed range. I don't know which property of the Selection
or Range you want to inspect, maybe
selRange.[start|end]Container.nodeName.

I've stripped down the so-called Midas demo and added some information
about the clicking when carrying out the text case from comment #37.
Result:

FF: BODY, continues in the wrong font.
Chrome: #text, continues with the correct font.
IE: #text if you used enter between the lines, or BODY if you used 
shiftenter, continues with correct font in both cases.

Let me know what to do next. And please, clear instructions ;-)

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

Title:
  composer changes font mid email

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: thunderbird

  As I'm typing my emails in Thunderbird, I can see what appears to be a
  font size change on screen, normally in the second line of text. The
  second line appear smaller than the first. It's barely perceptible, so
  half them time I think I am imagining it.

  Well, I've started Bccing to myself to check, and the emails I am
  receiving from myself are not only a different size, they're also a
  different font. Composer starts in some default serif, and by the
  second line is sans. I'd bee glad to email someone viz thunderbird,
  and also send along a screenshot of how it looks while I am typing.

  Thanks.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 584632]

2015-03-10 Thread Mozilla-jorgk
Created attachment 8575104
Alternate test, much simpler

Here is a much simplified test alternate.htm. Results:
FF: DIV, wrong font
IE: DIV, correct font
Chrome and Opera: #text, correct font.

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

Title:
  composer changes font mid email

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: thunderbird

  As I'm typing my emails in Thunderbird, I can see what appears to be a
  font size change on screen, normally in the second line of text. The
  second line appear smaller than the first. It's barely perceptible, so
  half them time I think I am imagining it.

  Well, I've started Bccing to myself to check, and the emails I am
  receiving from myself are not only a different size, they're also a
  different font. Composer starts in some default serif, and by the
  second line is sans. I'd bee glad to email someone viz thunderbird,
  and also send along a screenshot of how it looks while I am typing.

  Thanks.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1423448] Re: package libgl1-mesa-dri 10.1.3-0ubuntu0.3 failed to install/upgrade: intentando sobreescribir el compartido `/etc/drirc', que es distinto de otras instancias del p

2015-03-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mesa (Ubuntu)
   Status: New = Confirmed

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

Title:
  package libgl1-mesa-dri 10.1.3-0ubuntu0.3 failed to install/upgrade:
  intentando sobreescribir el compartido `/etc/drirc', que es distinto
  de otras instancias del paquetes libgl1-mesa-dri:i386

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Expected. 
  After Bug #1423414 (no unity-control-center) I decided to go anyway with:

  sudo apt-get install ubuntu-desktop

  I say Yes to *-utopic removal and this bug come up.

  but now I have unity-control-center! :-)

  Next step:
  sudo apt-get install xserver-xorg-lts-utopic libgl1-mesa-glx-lts-utopic 
libegl1-mesa-drivers-lts-utopic
  Fingers crossed...

  Recap:
  After LTS Enablement Stack:
  sudo apt-get install --install-recommends linux-generic-lts-utopic 
xserver-xorg-lts-utopic libgl1-mesa-glx-lts-utopic 
libegl1-mesa-drivers-lts-utopic
  Bug #1423414: unity-control-center gets uninstalled
  So, I reinstall ubutu-desktop
  sudo apt-get install ubuntu-desktop
  This bug come up

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Feb 19 02:17:37 2015
  DistUpgraded: 2014-03-26 05:29:04,147 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.3:intentando 
sobreescribir el compartido `/etc/drirc', que es distinto de otras instancias 
del paquetes libgl1-mesa-dri:i386
  ErrorMessage: intentando sobreescribir el compartido `/etc/drirc', que es 
distinto de otras instancias del paquetes libgl1-mesa-dri:i386
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] 
[1002:9640] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84c8]
  InstallationDate: Installed on 2010-01-28 (1847 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=4bcab513-d663-472a-9d5a-6b0b7f3b75cc ro bootchart=svg 
elevator=deadline quiet splash crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
vt.handoff=7
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.3 failed to install/upgrade: 
intentando sobreescribir el compartido `/etc/drirc', que es distinto de otras 
instancias del paquetes libgl1-mesa-dri:i386
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 127: /usr/lib/nux/unity_support_test: error while 
loading shared libraries: libGL.so.1: cannot open shared object file: No such 
file or directory
  UpgradeStatus: Upgraded to trusty on 2014-03-26 (329 days ago)
  dmi.bios.date: 01/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F1A75-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd01/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A75-VPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Desktop-packages] [Bug 1422143] Re: No wifi connection after suspend with systemd

2015-03-10 Thread Fran Diéguez
Here is the log file

 - Mar 10 00:37:22, laptop lid closed
 - Mar 10 10:04:24, laptop lid opened
 - Mar 10 10:06:42, opened g-c-c and switch Wifi off and back on again

Now my wireless connection works.

** Attachment added: nm.log
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1422143/+attachment/4339752/+files/nm.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1422143

Title:
  No wifi connection after suspend with systemd

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   docker0  bridgeunavailable  /org/freedesktop/NetworkManager/Devices/3  
--   ----   
  
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--   ----   
  
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5

2015-03-10 Thread Alberto Milone
** Changed in: fglrx-installer (Ubuntu)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

** Changed in: fglrx-installer (Ubuntu)
   Importance: Undecided = High

** Changed in: fglrx-installer (Ubuntu)
   Status: Confirmed = Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1424491

Title:
  apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5

Status in fglrx-installer package in Ubuntu:
  Triaged

Bug description:
  Activity:  Install fglrx AMD driver on 12.04.5 and 14.02.2

  Expected behavior:  fglrx would intall

  Observed behavior:  fglrx is not installed as follows


  Attempt to install fglrx fails as follows:

  zack3@ZACK3:~$ sudo apt-get install fglrx-updates xvba-va-driver
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   fglrx-updates : Depends: xorg-video-abi-11 but it is not installable 
or
    xorg-video-abi-12 but it is not installable 
or
    xorg-video-abi-13 but it is not installable 
or
    xorg-video-abi-14 but it is not installable 
or
    xorg-video-abi-15
  E: Unable to correct problems, you have held broken packages.


  
  Attempt to insatll xorg-video-abi-15 yields:

  zack3@ZACK3:~$ sudo apt-get install xorg-video-abi-15
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Note, selecting 'xserver-xorg-core' instead of 'xorg-video-abi-15'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it 
is not going to be installed
     Depends: libcogl15 (= 1.15.8) but it is not going 
to be installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not 
going to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is 
not going to be installed
  Depends: libcogl15 (= 1.15.8) but it is not 
going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be 
caused by held packages.


  
  Attempting to install xserver-xorg-core instead yields:

  zack3@ZACK3:~$ sudo apt-get install xserver-xorg-core
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it 
is not going to be installed
     Depends: libcogl15 (= 1.15.8) but it is not going 
to be installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not 
going to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is 
not going to be installed
  Depends: libcogl15 (= 1.15.8) but it is not 
going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be 
caused by held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1424491/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 889889] Re: Use PNG or SVG instead of GIF

2015-03-10 Thread Fred
I believe CSS can do animations without JavaScript.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dvd+rw-tools in Ubuntu.
https://bugs.launchpad.net/bugs/889889

Title:
  Use PNG or SVG instead of GIF

Status in Ubuntu Adium Theme:
  Fix Released
Status in ace package in Ubuntu:
  New
Status in app-install-data-ubuntu package in Ubuntu:
  Confirmed
Status in blender package in Ubuntu:
  New
Status in chardet package in Ubuntu:
  New
Status in cups package in Ubuntu:
  New
Status in dvd+rw-tools package in Ubuntu:
  New
Status in foo2zjs package in Ubuntu:
  New
Status in libcgi-pm-perl package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New
Status in python3.4 package in Ubuntu:
  New
Status in software-center package in Ubuntu:
  Invalid

Bug description:
  Use modern file formats such as PNG or SVG instead of the legacy GIF
  file formats.

  $ find /usr -name *.gif

To manage notifications about this bug go to:
https://bugs.launchpad.net/adium-theme-ubuntu/+bug/889889/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1404088] Re: Adding new location to date/time picker does not consistently autocomplete

2015-03-10 Thread Alberto Salvia Novella
** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided = Low

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

** Changed in: hundredpapercuts
   Status: New = Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided = Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1404088

Title:
  Adding new location to date/time picker does not consistently
  autocomplete

Status in One Hundred Papercuts:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  When I navigate to System Settings -  Time and Date - Clock -
  Choose Locations, I'm prompted to add or remove a location from the
  current locations.  When I click the new location icon, I can enter a
  location name, however I'm only offered an autocomplete list when
  there are three letters typed.  For example, I would like to add
  Beijing to the list, but I'm only presented with an autocomplete
  list when I type Bei, and Beijing is not on that list.  Any more
  or fewer letters and the list disappears.  If I type anything besides
  Bei, I'm not presented with a list of possible options either.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity-control-center 15.04.0+15.04.20141217-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.15-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec 18 20:19:18 2014
  InstallationDate: Installed on 2014-12-11 (8 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141210)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center: deja-dup 32.0-0ubuntu1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Desktop-packages] [Bug 1401792] Re: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build

2015-03-10 Thread snurfle
Huh.  The duplicate bug (1268257) has been updated to this:

Changed in nvidia-graphics-drivers-331-updates (Ubuntu):*assignee*:Moreno
(nenoattila) → nobodyChanged in nvidia-graphics-drivers-331 (Ubuntu):
*status*:Triaged → Incomplete*status*:Incomplete → InvalidChanged in
nvidia-graphics-drivers-331-updates (Ubuntu):*status*:Triaged → Invalid

Because apparently doing this:

$ sudo dpkg-reconfigure nvidia-331
$ sudo dpkg-reconfigure nvidia-331-uvm

not only fixes the issue, but apparently makes it completely irrelevant.

If plugging in a workaround is enough, after more than a year, to make a
bug invalid, then wouldn't the same workaround make all of the duplicates
invalid as well?

Just seems like a huge waste of resources to me to ignore the solution to a
bug, and continue looking for other ways to solve a duplicate issue.

Or, perhaps none of the devs let each other know when an issue has been
fixed.


On Tue, Mar 10, 2015 at 7:47 AM, mitch07 michel.min...@wanadoo.fr
wrote:

 ** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
  Assignee: (unassigned) = mitch07 (michel-minary)

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1401792

 Title:
   nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module
   failed to build

 Status in nvidia-graphics-drivers-331 package in Ubuntu:
   Confirmed

 Bug description:
   stop during installing

   ProblemType: Package
   DistroRelease: Ubuntu 14.04
   Package: nvidia-331-uvm 331.113-0ubuntu0.0.4
   ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
   Uname: Linux 3.13.0-43-generic x86_64
   ApportVersion: 2.14.1-0ubuntu3.6
   Architecture: amd64
   DKMSKernelVersion: 3.13.0-43-generic
   Date: Fri Dec 12 12:12:09 2014
   PackageVersion: 331.113-0ubuntu0.0.4
   SourcePackage: nvidia-graphics-drivers-331
   Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module
 failed to build
   UpgradeStatus: No upgrade log present (probably fresh install)

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1401792/+subscriptions


-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
https://bugs.launchpad.net/bugs/1401792

Title:
  nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module
  failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed

Bug description:
  stop during installing

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-uvm 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-43-generic
  Date: Fri Dec 12 12:12:09 2014
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1401792/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430133] Re: can't install fglrx on 14.04.2

2015-03-10 Thread Yung Shen
*** This bug is a duplicate of bug 1424491 ***
https://bugs.launchpad.net/bugs/1424491

** This bug has been marked a duplicate of bug 1424491
   apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1430133

Title:
  can't install fglrx on 14.04.2

Status in fglrx package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Using a fresh install of 14.04.2, tried to install ATI drivers using
  the following:

   sudo apt-get install fglrx
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   fglrx : Depends: xorg-video-abi-11 but it is not installable or
xorg-video-abi-12 but it is not installable or
xorg-video-abi-13 but it is not installable or
xorg-video-abi-14 but it is not installable or
xorg-video-abi-15
  E: Unable to correct problems, you have held broken packages.

  Versions/Hardware:

  3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux
  ii  xserver-xorg-core-lts-utopic
2:1.16.0-1ubuntu1.2~trusty2amd64  Xorg X server - 
core server
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx/+bug/1430133/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1403149] Re: Unable to mount OSX Yosemite causing excessive (~25%) CPU usage and moderate desktop sluggishness

2015-03-10 Thread Christopher M. Penalver
Sebastien Bacher, I would test Trusty, but my only instance of it is
using Kubuntu (due to how Ubuntu doesn't support RDP as per LP#1251281),
and Kubuntu doesn't natively support AFP. I'm using Utopic (gnome-
session-flashback) on my main laptop, so I'll have to wait for when the
fix lands in Utopic Proposed.

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

Title:
  Unable to mount OSX Yosemite causing excessive (~25%) CPU usage and
  moderate desktop sluggishness

Status in GVFS:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Committed

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2) apt-cache policy gvfs
  gvfs:
    Installed: 1.20.1-1ubuntu1
    Candidate: 1.20.1-1ubuntu1
    Version table:
   *** 1.20.1-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one mounts a shared folder from
  OSX Yosemite, the connection is unmountable, and doesn't cause
  excessive (~25%) CPU usage.

  4) What happens instead is the mount is unmountable, and is consuming
  (~25%) CPU as per the attached screenshot. This causes moderate
  desktop sluggishness. Tried restarting OSX, no change.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.37~14.04.1-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 16 11:28:39 2014
  InstallationDate: Installed on 2014-06-21 (177 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1422143] Re: No wifi connection after suspend with systemd

2015-03-10 Thread Martin Pitt
*** This bug is a duplicate of bug 1270257 ***
https://bugs.launchpad.net/bugs/1270257

Ah, this was indeed reported before already, also under upstart.
Duplicating/untagging.

** Tags removed: systemd-boot

** This bug has been marked a duplicate of bug 1270257
   NetworkManager failed to function after suspend and resume

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1422143

Title:
  No wifi connection after suspend with systemd

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   docker0  bridgeunavailable  /org/freedesktop/NetworkManager/Devices/3  
--   ----   
  
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--   ----   
  
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1270257] Re: NetworkManager failed to function after suspend and resume

2015-03-10 Thread Martin Pitt
Adding interesting log excerpt from a duplicate bug, it's the same
symptom here:

Mar 09 23:27:59 fry NetworkManager[1000]: info (wlan0): device state change: 
secondaries - activated (reason 'none') [90 100 0]
Mar 09 23:27:59 fry NetworkManager[1000]: info NetworkManager state is now 
CONNECTED_LOCAL
Mar 09 23:27:59 fry NetworkManager[1000]: info NetworkManager state is now 
CONNECTED_GLOBAL
[...]
Mar 10 00:37:20 fry NetworkManager[1000]: info sleep requested (sleeping: no 
enabled: yes)
Mar 10 00:37:20 fry NetworkManager[1000]: info sleeping...
Mar 10 10:04:24 fry NetworkManager[1000]: info waking up...
Mar 10 10:04:24 fry NetworkManager[1000]: info (wlan0): device state change: 
activated - unmanaged (reason 'sleeping') [100 10 37]
Mar 10 10:04:24 fry NetworkManager[1000]: info (wlan0): deactivating device 
(reason 'sleeping') [37]

So it seems that the activated - unmanaged action should be done
*before* sleeping..., and then it just forgets to bring it back up
after waking up. Here it has the correct order, so that sounds like a
race condition.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1270257

Title:
  NetworkManager failed to function after suspend and resume

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager failed to function after resuming from suspend. The
  indicator applet in the Mac OS style menu bar showed the empty
  quarter-circle, and clicking Enable Networking didn't change the
  menu options or the style of the applet. Running sudo service
  network-manager restart brought back functionality.

  $ dpkg -l systemd* logind*
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==
  un  logind none(no description 
available)
  un  systemdnone(no description 
available)
  ii  systemd-services   204-0ubuntu19.1  amd64systemd runtime 
services
  ii  systemd-shim   6-0ubuntu0.13.10 amd64shim for systemd

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri Jan 17 10:08:48 2014
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-18 (456 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.14  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-11-06 (72 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-05T17:49:23
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1270257/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1270257] Re: NetworkManager failed to function after suspend and resume

2015-03-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1270257

Title:
  NetworkManager failed to function after suspend and resume

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager failed to function after resuming from suspend. The
  indicator applet in the Mac OS style menu bar showed the empty
  quarter-circle, and clicking Enable Networking didn't change the
  menu options or the style of the applet. Running sudo service
  network-manager restart brought back functionality.

  $ dpkg -l systemd* logind*
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==
  un  logind none(no description 
available)
  un  systemdnone(no description 
available)
  ii  systemd-services   204-0ubuntu19.1  amd64systemd runtime 
services
  ii  systemd-shim   6-0ubuntu0.13.10 amd64shim for systemd

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri Jan 17 10:08:48 2014
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-18 (456 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.14  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-11-06 (72 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-05T17:49:23
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1270257/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 833071] Re: gedit crashed with SIGSEGV in on_document_loaded()

2015-03-10 Thread Bug Watch Updater
** Changed in: gedit
   Status: Incomplete = Expired

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

Title:
  gedit crashed with SIGSEGV in on_document_loaded()

Status in Light-Weight Text Editor for Gnome:
  Expired
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  What I did was type in the terminal
  gedit setup.py 
  and press [ENTER]

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gedit 3.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  Architecture: i386
  Date: Wed Aug 24 17:10:18 2011
  ExecutablePath: /usr/bin/gedit
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110822)
  ProcCmdline: gedit
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x439fa84: mov0x4(%ecx),%edx
   PC (0x0439fa84) ok
   source 0x4(%ecx) (0x0004) not located in a known VMA region (needed 
readable region)!
   destination %edx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gedit
  StacktraceTop:
   ?? () from /usr/lib/gedit/plugins/libspell.so
   g_cclosure_marshal_VOID__BOXED () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gedit crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1401792] Re: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build

2015-03-10 Thread mitch07
** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
 Assignee: (unassigned) = mitch07 (michel-minary)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
https://bugs.launchpad.net/bugs/1401792

Title:
  nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module
  failed to build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed

Bug description:
  stop during installing

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-uvm 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-43-generic
  Date: Fri Dec 12 12:12:09 2014
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1401792/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430280] [NEW] NetworkManager-wait-online.service not enabled after package installation

2015-03-10 Thread Martin Pitt
Public bug reported:

After installing NetworkManager in a fresh vivid VM, NetworkManager-
wait-online.service is disabled. We should consider enabling it on
systems which don't have any static interfaces in
/etc/network/interfaces, so that units that need network-online.target
work properly.

** Affects: network-manager (Ubuntu)
 Importance: Medium
 Status: New


** Tags: systemd-boot

** Tags added: systemd-boot

** Changed in: network-manager (Ubuntu)
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1430280

Title:
  NetworkManager-wait-online.service not enabled after package
  installation

Status in network-manager package in Ubuntu:
  New

Bug description:
  After installing NetworkManager in a fresh vivid VM, NetworkManager-
  wait-online.service is disabled. We should consider enabling it on
  systems which don't have any static interfaces in
  /etc/network/interfaces, so that units that need network-online.target
  work properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1430280/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1403377] Re: The compress function works abnormal for trash, disk and so on

2015-03-10 Thread Anthony Wong
Thank you :)

** Changed in: ubuntukylin
   Status: In Progress = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1403377

Title:
  The compress function works abnormal for trash, disk and so on

Status in File Roller:
  Confirmed
Status in Ubuntu Kylin:
  Fix Released
Status in file-roller package in Ubuntu:
  Fix Released

Bug description:
  The compress function works abnormal for trash, disk and so on.

  右键点击回收站、磁盘等,选择压缩,点击确认提示压缩成功,实际上未生成压缩文件

  Steps:
  1. Login system
  2. Right click for trash or disk
  3. Chose compress
  4. Click OK button
  5. After compress successfully, check the gz file
  --Failed. There is no gz file found.

  Configuration:
  OS: Vivid x32 Daily Build 20141214

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1403377/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1422143] Re: No wifi connection after suspend with systemd

2015-03-10 Thread Fran Diéguez
*** This bug is a duplicate of bug 1270257 ***
https://bugs.launchpad.net/bugs/1270257

No, I don't get this error under upstart

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1422143

Title:
  No wifi connection after suspend with systemd

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   docker0  bridgeunavailable  /org/freedesktop/NetworkManager/Devices/3  
--   ----   
  
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--   ----   
  
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430246] [NEW] Impossible to unlock lock screen for user without password

2015-03-10 Thread Alex Ryan
Public bug reported:

One of the options in Ubuntu when creating a user is to give that user
no password. On the login screen, one simply clicks a button to log such
a user in. On the lock screen, however, one is required to enter a
password. Entering no password doesn't work, and entering a random
password doesn't work. The user without a password is stuck on the lock
screen.

I was able to reproduce this issue on Ubuntu 14.04.2 LTS. It's a fairly
serious issue since the default system behavior is to automatically lock
after a few minutes.

An emergency workaround is to click the Change User button to return to
the main login screen, and then proceed from there.

** Affects: unity-greeter (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1430246

Title:
  Impossible to unlock lock screen for user without password

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  One of the options in Ubuntu when creating a user is to give that user
  no password. On the login screen, one simply clicks a button to log
  such a user in. On the lock screen, however, one is required to enter
  a password. Entering no password doesn't work, and entering a random
  password doesn't work. The user without a password is stuck on the
  lock screen.

  I was able to reproduce this issue on Ubuntu 14.04.2 LTS. It's a
  fairly serious issue since the default system behavior is to
  automatically lock after a few minutes.

  An emergency workaround is to click the Change User button to return
  to the main login screen, and then proceed from there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1430246/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1429644] Re: [ENS1371 - Emulated Ensoniq AudioPCI inside VMware, playback] Sound is distorted

2015-03-10 Thread Raymond
https://wiki.ubuntu.com/PulseAudio/Log


you need to provide pulseaudio verbose inside vmware when the sound is distorted

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

Title:
  [ENS1371 - Emulated Ensoniq AudioPCI inside VMware, playback] Sound is
  distorted

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  sound quality poor.

  distoted sound

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaditya   15448 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar  9 01:58:35 2015
  InstallationDate: Installed on 2015-03-06 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI 
successful
  Symptom_Card: Creative Sound Blaster AudioPCI64V, AudioPCI128 - Ensoniq 
AudioPCI
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Digital clip or distortion, or overdriven sound
  Title: [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2015-03-07T12:55:40.634974

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1429644/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5

2015-03-10 Thread EdouardC
Sorry, what is the way to downgrade from 14.04.2 to 14.04 ?

Many people say: remove Hardware Enablement Stack but it is pretty obscur.
No package has this name.
I know linux and distros, since I'm working with them since 1998!

Please help. Thanks in advance.
Regards.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1424491

Title:
  apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5

Status in fglrx-installer package in Ubuntu:
  Triaged

Bug description:
  Activity:  Install fglrx AMD driver on 12.04.5 and 14.02.2

  Expected behavior:  fglrx would intall

  Observed behavior:  fglrx is not installed as follows


  Attempt to install fglrx fails as follows:

  zack3@ZACK3:~$ sudo apt-get install fglrx-updates xvba-va-driver
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   fglrx-updates : Depends: xorg-video-abi-11 but it is not installable 
or
    xorg-video-abi-12 but it is not installable 
or
    xorg-video-abi-13 but it is not installable 
or
    xorg-video-abi-14 but it is not installable 
or
    xorg-video-abi-15
  E: Unable to correct problems, you have held broken packages.


  
  Attempt to insatll xorg-video-abi-15 yields:

  zack3@ZACK3:~$ sudo apt-get install xorg-video-abi-15
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Note, selecting 'xserver-xorg-core' instead of 'xorg-video-abi-15'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it 
is not going to be installed
     Depends: libcogl15 (= 1.15.8) but it is not going 
to be installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not 
going to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is 
not going to be installed
  Depends: libcogl15 (= 1.15.8) but it is not 
going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be 
caused by held packages.


  
  Attempting to install xserver-xorg-core instead yields:

  zack3@ZACK3:~$ sudo apt-get install xserver-xorg-core
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it 
is not going to be installed
     Depends: libcogl15 (= 1.15.8) but it is not going 
to be installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not 
going to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is 
not going to be installed
  Depends: libcogl15 (= 1.15.8) but it is not 
going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be 
caused by held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1424491/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1427344] Re: cups-browsed crashed with SIGSEGV in timeout_free()

2015-03-10 Thread Cristian Aravena Romero
** Attachment added: cups-browsed.conf
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1427344/+attachment/4339788/+files/cups-browsed.conf

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1427344

Title:
  cups-browsed crashed with SIGSEGV in timeout_free()

Status in cups-filters package in Ubuntu:
  Incomplete

Bug description:
  on every boot

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-browsed 1.0.66-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Mar  2 17:27:28 2015
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2015-01-25 (35 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150125)
  Lpstat: device for HP-Photosmart-C3100-series: 
usb://HP/Photosmart%20C3100%20series?serial=MY6ABC32ND04P9interface=1
  MachineType: ASUS All Series
  Papersize: a4
  PpdFiles: HP-Photosmart-C3100-series: HP Photosmart c3100 Series, hpcups 
3.14.6
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=a1f4e400-6d47-4810-8d22-d51139013aa1 ro 
resume=UUID=c756b5d8-0950-4dd7-8532-4932aac06078 quiet splash vga=845
  SegvAnalysis:
   Segfault happened at: 0x7fdf8bc9a15a:movl   $0x1,0xa8(%rax)
   PC (0x7fdf8bc9a15a) ok
   source $0x1 ok
   destination 0xa8(%rax) (0x00a8) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1802
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1802:bd01/28/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1427344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1422143] Re: No wifi connection after suspend with systemd

2015-03-10 Thread Martin Pitt
Thanks for the log. Putting the interesting excerpt here for
convenience:

Mar 09 23:27:59 fry NetworkManager[1000]: info (wlan0): device state change: 
secondaries - activated (reason 'none') [90 100 0]
Mar 09 23:27:59 fry NetworkManager[1000]: info NetworkManager state is now 
CONNECTED_LOCAL
Mar 09 23:27:59 fry NetworkManager[1000]: info NetworkManager state is now 
CONNECTED_GLOBAL
[...]
Mar 10 00:37:20 fry NetworkManager[1000]: info sleep requested (sleeping: no  
enabled: yes)
Mar 10 00:37:20 fry NetworkManager[1000]: info sleeping...
Mar 10 10:04:24 fry NetworkManager[1000]: info waking up...
Mar 10 10:04:24 fry NetworkManager[1000]: info (wlan0): device state change: 
activated - unmanaged (reason 'sleeping') [100 10 37]
Mar 10 10:04:24 fry NetworkManager[1000]: info (wlan0): deactivating device 
(reason 'sleeping') [37]

So it seems that the activated - unmanaged action should be done
*before* sleeping..., and then it just forgets to bring it back up
after waking up. Here it has the correct order, so that sounds like a
race condition.

This part (logind interaction) hasn't actually changed in quite some
time. Out of interest, do you get this error under upstart too? This
doesn't actually sound specific to using systemd as init, but it would
be nice to confirm that. Otherwise it's another data point for debugging
this. Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1422143

Title:
  No wifi connection after suspend with systemd

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   docker0  bridgeunavailable  /org/freedesktop/NetworkManager/Devices/3  
--   ----   
  
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--   ----   
  
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430276] Re: Desktop/windows painted incorrectly in dual monitor configuration

2015-03-10 Thread Bontius
Follow up to
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1382462

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in xorg package in Ubuntu:
  New

Bug description:
  Problem 1. if miniDVI (connected to NVIDIA card) is connected upon
  boot, the desktop resolution is detected incorrectly.

  Problem 2. lightdm won't start from scratch, needs to be restarted as service 
on every boot, and then ctrl+alt+f7 has to be pressed repeatedly until the 
login window appears, and then again repeatedly, until the desktop appears 
(after which, the miniDVI can be inserted). If you skip the first repeated 
pressing, you end up with a console window saying 
/org/FreeDesktop/Accounts/User1000 has been changed. If you skip the second 
repeated pressing, you revert to login window.
  Yes, I've tried the following:
  sudo dpkg-reconfigure lightdm
  sudo chown -R username .
  sudo apt-get install --reinstall ubuntu-desktop unity unity-greeter
  including setting HEED_DEFAULT_DESKTOP_MANAGER=false in /etc/init.d/lightdm

  Problem 3. right now (as of yesterday), unity decorator and dash does
  not apper after login, and dconf reset -f /org/compiz/  setsid
  unity has to be run from lightdm, provided that you somehow manage to
  get a terminal up (ctrl+alt+T does not work, neither does Alt+f2)

  The result of this:

  sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date
  is:

  A14
  09/24/2014

  Sorry for the mess, I'd be happy to provide further information, since this 
laptop seems to be an outlier to all your fixes.
  P.S. /etc/modprobe.d is not a file still persists...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: vtsspp sep3_15 pax wl nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Mar 10 11:31:49 2015
  DistUpgraded: 2014-06-06 12:58:55,700 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05aa]
   NVIDIA Corporation GK106M [GeForce GTX 770M] [10de:11e0] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell Device [1028:05aa]
  MachineType: Alienware Alienware 17
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=40c4f155-d830-45c7-8784-98c30335b94c ro nvidia.modeset=1 nosplash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-06-06 (276 days ago)
  dmi.bios.date: 09/24/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A14
  dmi.board.name: 068R5X
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnAlienware:bvrA14:bd09/24/2014:svnAlienware:pnAlienware17:pvrA14:rvnAlienware:rn068R5X:rvrA01:cvnAlienware:ct8:cvrA14:
  dmi.product.name: Alienware 17
  dmi.product.version: A14
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59+git20150225.1f73578d-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20150204.661c8bb2-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20150204.661c8bb2-0ubuntu0ricotz~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1430276/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages

[Desktop-packages] [Bug 1430276] [NEW] Desktop/windows painted incorrectly in dual monitor configuration

2015-03-10 Thread Bontius
Public bug reported:

Problem 1. if miniDVI (connected to NVIDIA card) is connected upon boot,
the desktop resolution is detected incorrectly.

Problem 2. lightdm won't start from scratch, needs to be restarted as service 
on every boot, and then ctrl+alt+f7 has to be pressed repeatedly until the 
login window appears, and then again repeatedly, until the desktop appears 
(after which, the miniDVI can be inserted). If you skip the first repeated 
pressing, you end up with a console window saying 
/org/FreeDesktop/Accounts/User1000 has been changed. If you skip the second 
repeated pressing, you revert to login window.
Yes, I've tried the following:
sudo dpkg-reconfigure lightdm
sudo chown -R username .
sudo apt-get install --reinstall ubuntu-desktop unity unity-greeter
including setting HEED_DEFAULT_DESKTOP_MANAGER=false in /etc/init.d/lightdm

Problem 3. right now (as of yesterday), unity decorator and dash does
not apper after login, and dconf reset -f /org/compiz/  setsid unity
has to be run from lightdm, provided that you somehow manage to get a
terminal up (ctrl+alt+T does not work, neither does Alt+f2)

The result of this:

sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date
is:

A14
09/24/2014

Sorry for the mess, I'd be happy to provide further information, since this 
laptop seems to be an outlier to all your fixes.
P.S. /etc/modprobe.d is not a file still persists...

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
NonfreeKernelModules: vtsspp sep3_15 pax wl nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Mar 10 11:31:49 2015
DistUpgraded: 2014-06-06 12:58:55,700 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:05aa]
 NVIDIA Corporation GK106M [GeForce GTX 770M] [10de:11e0] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell Device [1028:05aa]
MachineType: Alienware Alienware 17
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=40c4f155-d830-45c7-8784-98c30335b94c ro nvidia.modeset=1 nosplash
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-06-06 (276 days ago)
dmi.bios.date: 09/24/2014
dmi.bios.vendor: Alienware
dmi.bios.version: A14
dmi.board.name: 068R5X
dmi.board.vendor: Alienware
dmi.board.version: A01
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A14
dmi.modalias: 
dmi:bvnAlienware:bvrA14:bd09/24/2014:svnAlienware:pnAlienware17:pvrA14:rvnAlienware:rn068R5X:rvrA01:cvnAlienware:ct8:cvrA14:
dmi.product.name: Alienware 17
dmi.product.version: A14
dmi.sys.vendor: Alienware
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.59+git20150225.1f73578d-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20150204.661c8bb2-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20150204.661c8bb2-0ubuntu0ricotz~trusty
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages trusty ubuntu

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in xorg package in Ubuntu:
  New

Bug description:
  Problem 1. if miniDVI (connected to NVIDIA card) is connected upon
  boot, the desktop resolution is detected incorrectly.

  Problem 2. lightdm won't start from scratch, needs to be restarted as service 
on every boot, and then 

[Desktop-packages] [Bug 1385292] Re: can't rename files in nautilus

2015-03-10 Thread Alberto Salvia Novella
** Changed in: ibus (Ubuntu)
   Importance: Critical = Low

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

Title:
  can't rename files in nautilus

Status in IBus:
  Unknown
Status in ibus package in Ubuntu:
  Triaged

Bug description:
  sometimes can't rename files with F2 button. It is higlight changing,
  but nothing gonna happen, it is not responding

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 24 17:48:33 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2014-10-24 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430280] Re: NetworkManager-wait-online.service not enabled after package installation

2015-03-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1430280

Title:
  NetworkManager-wait-online.service not enabled after package
  installation

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After installing NetworkManager in a fresh vivid VM, NetworkManager-
  wait-online.service is disabled. We should consider enabling it on
  systems which don't have any static interfaces in
  /etc/network/interfaces, so that units that need network-online.target
  work properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1430280/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430230] [NEW] Log flooding with warning message when using linux-lowlatency kernel

2015-03-10 Thread Franck
Public bug reported:

In Vivid, when booting with lowlatency kernel (and possibly with generic
kernel and threadirqs), Intel graphics driver will flood the logs with
warning:

Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247652] [ cut 
here ]
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247683] WARNING: CPU: 3 
PID: 659 at 
/build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:9705 
intel_check_page_flip+0xa2/0xf0 [i915]()
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247685] WARN_ON(!in_irq())
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247686] Modules linked in: 
md4 nls_utf8 cifs fscache msr acpi_call(OE) xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 bridge stp llc 
ebtable_filter ebtables pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) binfmt_misc rfcomm bnep nls_iso8859_1 hid_apple intel_rapl iosf_mbi 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel uvcvideo kvm 
videobuf2_vmalloc videobuf2_memops crct10dif_pclmul i915 videobuf2_core 
crc32_pclmul ghash_clmulni_intel v4l2_common videodev aesni_intel media 
aes_x86_64 btusb lrw gf128mul glue_helper bluetooth ablk_helper cryptd arc4 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iwldvm 
dm_multipath scsi_dh snd_hda_intel mac80211 snd_hda_controller snd_hda_codec 
joydev snd_hwdep serio_raw drm_kms_helper iwlwifi snd_pcm thinkpad_acpi 
cfg80211 snd_seq_midi snd_seq_midi_event nvram snd_rawmidi snd_seq ip6t_REJECT 
nf_reject_ipv6 snd_seq_devi
 ce nf_log_ipv6 lpc_ich snd_timer drm shpchp xt_hl snd mei_me nf_conntrack_ipv6 
mei nf_defrag_ipv6 i2c_algo_bit ip6t_rt soundcore wmi video mac_hid ipt_REJECT 
nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_addrtype xt_conntrack ip6table_filter 
ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast cuse nf_nat_ftp 
nf_nat nf_conntrack_ftp parport_pc nf_conntrack ppdev iptable_filter ip_tables 
lp x_tables parport autofs4 btrfs xor raid6_pq hid_generic usbhid hid psmouse 
ahci e1000e sdhci_pci libahci sdhci ptp pps_core
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247768] CPU: 3 PID: 659 
Comm: irq/32-i915 Tainted: GW  OE  3.19.0-7-lowlatency #7-Ubuntu
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247770] Hardware name: 
LENOVO 2353CTO/2353CTO, BIOS G7ETA0WW (2.60 ) 05/14/2014
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247781]  c0be7010 
88042a353c98 817c5402 88043e2cfd78
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247784]  88042a353ce8 
88042a353cd8 8107738a 88042a353cd8
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247786]  880428f3f000 
880428f5e800  
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247788] Call Trace:
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247795]  
[817c5402] dump_stack+0x4c/0x6e
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247805]  
[8107738a] warn_slowpath_common+0x8a/0xc0
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247814]  
[81077406] warn_slowpath_fmt+0x46/0x50
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247830]  
[c0b92482] intel_check_page_flip+0xa2/0xf0 [i915]
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247843]  
[c0b5f4d8] ironlake_irq_handler+0x428/0x1010 [i915]
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247847]  
[8109b55d] ? finish_task_switch+0x5d/0x100
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247854]  
[810cfc60] ? irq_thread_fn+0x50/0x50
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247858]  
[810cfc8d] irq_forced_thread_fn+0x2d/0x70
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247861]  
[810d01af] irq_thread+0x11f/0x150
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247865]  
[810cfd00] ? wake_threads_waitq+0x30/0x30
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247868]  
[810d0090] ? irq_thread_check_affinity+0x90/0x90
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247871]  
[81095bc9] kthread+0xc9/0xe0
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247874]  
[81095b00] ? kthread_create_on_node+0x1c0/0x1c0
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247877]  
[817cc33c] ret_from_fork+0x7c/0xb0
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247880]  
[81095b00] ? kthread_create_on_node+0x1c0/0x1c0
Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247883] ---[ end trace 
fa4376848cde145f ]---

There seems to be a bug report here
https://bugs.freedesktop.org/show_bug.cgi?id=89321

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64

[Desktop-packages] [Bug 1324113] Re: Screen goes black or flashes with Dual Monitors when certain apps are opened.

2015-03-10 Thread Pablo180
Thanks for all the help Christopher, but I think that I will just
upgrade to Vivid as soon as I can, as it is only a few weeks away, so no
backport needed and it can be closed as invalid.

Thanks again for the help.

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

Title:
  Screen goes black or flashes with Dual Monitors when certain apps are
  opened.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This has been going on for a while, but only seems to occur on dual
  monitors and when certain applications are opened. Previously the
  screen would go black and then reappear and be fine. Now the screen
  either goes black and does not come back until one of the monitors is
  removed or it flashes on and off like it is trying and re-trying to
  set the resolution but failing. This goes on until I unplug a monitor.

  Applications that cause this behaviour range from Viber Desktop to
  Wine programs through to System Settings and Totem Video Player (in
  this example in the bug) but it can be random, sometimes but not
  always do they cause this behaviour. Just to clarify, this does not
  happen with the laptop screen, only when external dual monitors are
  used.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May 28 13:42:02 2014
  DistUpgraded: 2014-04-27 17:46:29,919 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:054d]
  InstallationDate: Installed on 2013-02-07 (474 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MachineType: Dell Inc. XPS L421X
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=5ce6b55e-d260-430c-a0cf-bd634db73afa ro 
resume=UUID=e7da6c40-f59f-4118-b11a-6a8dcb87b771 quiet splash 
intel_pstate=enable vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (30 days ago)
  dmi.bios.date: 05/22/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 08HDPJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/22/2013:svnDellInc.:pnXPSL421X:pvrA14:rvnDellInc.:rn08HDPJ:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: XPS L421X
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed May 28 13:33:25 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   30324 
   vendor BNQ
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1324113/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should hit Mincho(serif) font

2015-03-10 Thread Nobuto Murata
The PDF document above is a template of tax declaration paper from
Japanese National Tax Agency. It specifies both Ryumin(serif) and
Gothic-BBB(sans-serif), but Evince uses one sans-serif font
TakaoPGothic to substitute both.

** Attachment added: GothicBBB_Ryumin.png
   
https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+attachment/4339988/+files/GothicBBB_Ryumin.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-takao in Ubuntu.
https://bugs.launchpad.net/bugs/1430339

Title:
  fc-match Ryumin should hit Mincho(serif) font

Status in fonts-takao package in Ubuntu:
  New

Bug description:
  Ryumin and Gothic-BBB are generic font names for serif/sans-serif like
  Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer
  substitute for Ryumin, however `fc-match Ryumin` does not return
  fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif)
  instead.

  Expected result:
  $ fc-match Ryumin
  fonts-japanese-mincho.ttf: TakaoPMincho Regular

  Actual result:
  $ fc-match Ryumin
  fonts-japanese-gothic.ttf: Takao Pゴシック Regular

  
  [1]
  /etc/fonts/conf.d/65-fonts-takao-mincho.conf
   21 match target=pattern
   22 test qual=any name=family
   23 stringRyumin/string
   24 /test
   25 edit name=family mode=prepend
   26 stringTakao P明朝/string
   27 /edit
   28 /match

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fonts-takao-mincho 003.02.01-9ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 22:41:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-28 (9 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228)
  PackageArchitecture: all
  SourcePackage: fonts-takao
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430339] [NEW] fc-match Ryumin should hit Mincho(serif) font

2015-03-10 Thread Nobuto Murata
Public bug reported:

Ryumin and Gothic-BBB are generic font names for serif/sans-serif like
Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer
substitute for Ryumin, however `fc-match Ryumin` does not return fonts-
takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead.

Expected result:
$ fc-match Ryumin
fonts-japanese-mincho.ttf: TakaoPMincho Regular

Actual result:
$ fc-match Ryumin
fonts-japanese-gothic.ttf: Takao Pゴシック Regular


[1]
/etc/fonts/conf.d/65-fonts-takao-mincho.conf
 21 match target=pattern
 22 test qual=any name=family
 23 stringRyumin/string
 24 /test
 25 edit name=family mode=prepend
 26 stringTakao P明朝/string
 27 /edit
 28 /match

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: fonts-takao-mincho 003.02.01-9ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 10 22:41:44 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-02-28 (9 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228)
PackageArchitecture: all
SourcePackage: fonts-takao
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: fonts-takao (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-takao in Ubuntu.
https://bugs.launchpad.net/bugs/1430339

Title:
  fc-match Ryumin should hit Mincho(serif) font

Status in fonts-takao package in Ubuntu:
  New

Bug description:
  Ryumin and Gothic-BBB are generic font names for serif/sans-serif like
  Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer
  substitute for Ryumin, however `fc-match Ryumin` does not return
  fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif)
  instead.

  Expected result:
  $ fc-match Ryumin
  fonts-japanese-mincho.ttf: TakaoPMincho Regular

  Actual result:
  $ fc-match Ryumin
  fonts-japanese-gothic.ttf: Takao Pゴシック Regular

  
  [1]
  /etc/fonts/conf.d/65-fonts-takao-mincho.conf
   21 match target=pattern
   22 test qual=any name=family
   23 stringRyumin/string
   24 /test
   25 edit name=family mode=prepend
   26 stringTakao P明朝/string
   27 /edit
   28 /match

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fonts-takao-mincho 003.02.01-9ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 22:41:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-28 (9 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228)
  PackageArchitecture: all
  SourcePackage: fonts-takao
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

2015-03-10 Thread pqwoerituytrueiwoq
I have been having this issue on my 14.04 install for a while now (probably as 
long as Mario), i have been using my rPi and a button to run a command over ssh 
to fix it 
DISPLAY=:0.0 xrandr --output HDMI-0 --auto

i upgraded me and my dad to xfce 4.12 and now he has the issue ga-a55m-ds2 
motherboard and a AMD A6-3500 APU
he is running xubuntu 14.04 w/ linux 3.16.7 w/ xfce 4.12 (open source drivers, 
NOT fglrx/catalyst)
he is using DVI on a HP 2009M monitor
this command restores the display for him
DISPLAY=:0.0 xrandr --output DVI-0 --auto
he seems to have this issue wen the power manager turns the display off and the 
monitor goes into standby

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1308105

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
  Confirmed
Status in xfce4-settings:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode NULL

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello supe...@ubuntu.com

  OUTPUT=HDMI-0
  BAD_MODE=1280x720
  GOOD_MODE=1920x1080

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 953342] Re: Add support for Qt Designer UI files

2015-03-10 Thread Rodney Dawes
This apparently needs a freeze exception to be able to get the new
version into Ubuntu which contains this. :-/

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

Title:
  [ffe] Add support for Qt Designer UI files

Status in Internationalization Tool Collection:
  Fix Released
Status in intltool package in Ubuntu:
  New

Bug description:
  Qt Designer files are XML files that describe the UI of a Qt
  application, and are the Glade .ui file equivalent in the Qt world.

  Their format definition can be found here:

  - http://qt-project.org/doc/designer-ui-file-format.html

  While many Qt projects use Qt's own i18n/l10n framework, others rely
  on gettext. Some examples are core Ubuntu applications such as the
  Ubuntu One client and Checkbox, which have started to migrate to Qt-
  based user interfaces while overriding Qt's i18n system and using
  gettext instead.

  These cases need a way to extract translatable messages from Qt's .ui
  files, merge the translations in .pot files and thus integrate with
  the gettext workflow.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 953342] Re: [ffe] Add support for Qt Designer UI files

2015-03-10 Thread Sebastien Bacher
** Summary changed:

- Add support for Qt Designer UI files
+ [ffe] Add support for Qt Designer UI files

** Changed in: intltool (Ubuntu)
   Status: Triaged = New

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

Title:
  [ffe] Add support for Qt Designer UI files

Status in Internationalization Tool Collection:
  Fix Released
Status in intltool package in Ubuntu:
  New

Bug description:
  Qt Designer files are XML files that describe the UI of a Qt
  application, and are the Glade .ui file equivalent in the Qt world.

  Their format definition can be found here:

  - http://qt-project.org/doc/designer-ui-file-format.html

  While many Qt projects use Qt's own i18n/l10n framework, others rely
  on gettext. Some examples are core Ubuntu applications such as the
  Ubuntu One client and Checkbox, which have started to migrate to Qt-
  based user interfaces while overriding Qt's i18n system and using
  gettext instead.

  These cases need a way to extract translatable messages from Qt's .ui
  files, merge the translations in .pot files and thus integrate with
  the gettext workflow.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430307] [NEW] Deprecation warning should be turned off for release

2015-03-10 Thread Marc Deslauriers
Public bug reported:

A lot of applications that are currently shipping in vivid display gtk
deprecation warnings. While this is useful to developers, it is a
nuisance for users who are powerless to fix these issues.

For certain graphical applications, printing warnings on the console
isn't much of an issue, but for others, such as gedit, it's annoying and
inelegant.

Here are a few examples:

$ ubuntu-bug sdasdasd
dpkg-query: no packages found matching sdasdasd
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

$ gedit
sys:1: Warning: The property GtkSettings:gtk-menu-images is deprecated and 
shouldn't be used anymore. It will be removed in a future version.
sys:1: Warning: The property GtkToolButton:stock-id is deprecated and shouldn't 
be used anymore. It will be removed in a future version.
sys:1: Warning: The property GtkWidget:margin-right is deprecated and shouldn't 
be used anymore. It will be removed in a future version.
sys:1: Warning: The property GtkButton:use-stock is deprecated and shouldn't be 
used anymore. It will be removed in a future version.
sys:1: Warning: The property GtkSettings:gtk-button-images is deprecated and 
shouldn't be used anymore. It will be removed in a future version.
sys:1: Warning: The property GtkButton:xalign is deprecated and shouldn't be 
used anymore. It will be removed in a future version.
sys:1: Warning: The property GtkAlignment:left-padding is deprecated and 
shouldn't be used anymore. It will be removed in a future version.
sys:1: Warning: The property GtkTreeView:rules-hint is deprecated and shouldn't 
be used anymore. It will be removed in a future version.

$ brasero

(brasero:5606): GLib-GObject-WARNING **: The property 
GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It 
will be removed in a future version.
(brasero:5606): GLib-GObject-WARNING **: The property 
GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It 
will be removed in a future version.
(brasero:5606): GLib-GObject-WARNING **: The property GtkAlignment:xalign is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.
(brasero:5606): GLib-GObject-WARNING **: The property GtkAlignment:yalign is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.
(brasero:5606): GLib-GObject-WARNING **: The property GtkButton:use-stock is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.


$ gnote

(gnote:5712): GLib-GObject-WARNING **: The property GSettings:schema is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.
(gnote:5712): GLib-GObject-WARNING **: The property GtkTextTag:foreground-gdk 
is deprecated and shouldn't be used anymore. It will be removed in a future 
version.
(gnote:5712): GLib-GObject-WARNING **: The property GtkSettings:gtk-menu-images 
is deprecated and shouldn't be used anymore. It will be removed in a future 
version.
(gnote:5712): GLib-GObject-WARNING **: The property GtkAlignment:xalign is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.
(gnote:5712): GLib-GObject-WARNING **: The property GtkAlignment:yalign is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.
(gnote:5712): GLib-GObject-WARNING **: The property GtkAlignment:xscale is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.
(gnote:5712): GLib-GObject-WARNING **: The property GtkAlignment:yscale is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.
(gnote:5712): GLib-GObject-WARNING **: The property GtkImage:stock is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.
(gnote:5712): GLib-GObject-WARNING **: The property 
GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It 
will be removed in a future version.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: libgtk-3-0 3.14.8-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 10 08:34:20 2015
InstallationDate: Installed on 2013-11-26 (468 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
SourcePackage: gtk+3.0
UpgradeStatus: Upgraded to vivid on 2015-03-07 (2 days ago)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1430307

Title:
  Deprecation warning should be turned off for release

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  A lot of applications that are currently shipping in vivid display gtk
  deprecation warnings. While this is useful to developers, it is 

[Desktop-packages] [Bug 1430280] Re: NetworkManager-wait-online.service not enabled after package installation

2015-03-10 Thread Martin Pitt
For the record, that's the command to check this:

grep -l DefaultDependencies /run/systemd/generator.late/*.service |
xargs egrep 'remote-fs|network-online'

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1430280

Title:
  NetworkManager-wait-online.service not enabled after package
  installation

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After installing NetworkManager in a fresh vivid VM, NetworkManager-
  wait-online.service is disabled. We should consider enabling it on
  systems which don't have any static interfaces in
  /etc/network/interfaces, so that units that need network-online.target
  work properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1430280/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1424864] Re: Xorg crash

2015-03-10 Thread Galen Thurber
apport-collect -p xorg 1424864
has been run and added to the bug

firefox 36.0.1 now allows -remote url to work once again, allowing
reports etc..

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Xorg crashing out  back into login manager
  and apport failed 
  This problem report is damaged and cannot be processed.

  IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpXYLMdA is
  truncated: expected core file size = 75243520, found: 6356992.',)

  
  openConnection: connect: No such file or directory
  cannot connect to brltty at :0
  xfce4-settings-helper: Another instance is already running. Leaving...

  (polkit-gnome-authentication-agent-1:9183): GLib-CRITICAL **:
  g_variant_new_string: assertion `string != NULL' failed

  (polkit-gnome-authentication-agent-1:9183): polkit-gnome-1-WARNING **:
  Failed to register client:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations

  
  (xfce4-settings-helper:9229): xfce4-settings-helper-WARNING **: Failed to get 
the _NET_NUMBER_OF_DESKTOPS property.
  ** Message: applet now removed from the notification area
  ** Message: using fallback from indicator to GtkStatusIcon
  ** Message: applet now embedded in the notification area
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No 
such file or directory

  (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32:
  assertion `G_IS_FILE_INFO (info)' failed

  (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: 
assertion `G_IS_FILE_INFO (info)' failed
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No 
such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66
  Uname: Linux 3.2.0-76-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Mon Feb 23 19:14:16 2015
  InstallationMedia: Xubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140205)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  InstallationMedia: Xubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140205)
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66
  Tags:  precise ubuntu
  Uname: Linux 3.2.0-76-generic x86_64
  UnreportableReason: Please work this issue through technical support channels 
first.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dialout dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1424864/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430280] Re: NetworkManager-wait-online.service not enabled after package installation

2015-03-10 Thread Martin Pitt
Michael points out that this is blocked on having rcS init.d scripts
which have Required/Should-Start: $network or $remote_fs, otherwise it's
too easy to get dependency cycles.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1430280

Title:
  NetworkManager-wait-online.service not enabled after package
  installation

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After installing NetworkManager in a fresh vivid VM, NetworkManager-
  wait-online.service is disabled. We should consider enabling it on
  systems which don't have any static interfaces in
  /etc/network/interfaces, so that units that need network-online.target
  work properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1430280/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1388612]

2015-03-10 Thread Mattst88
*** Bug 1 has been marked as a duplicate of this bug. ***

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

Title:
  [GM965] GPU lockup running OpenGL applications on Dell Vostro 1510

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  In Progress

Bug description:
  Hello, I'm suffering a GPU lockup problem with Ubuntu 14.10 64-bit on
  a Dell Vostro 1510 laptop with Intel graphics. The problem used to
  arise also with Ubuntu 14.04 and is always reproducible with glmark2
  on the LiveCD. Just to run the ideas benchmark of glmark2 to trigger
  the lockup in few seconds (glmark2 -b ideas). Other OpenGL
  applications also causes the lockup (e.g. FooBillard++, my self-made
  SDL applications). Memory test passed, BIOS at the latest version.
  Don't know if the following is a good point but I think that the
  problem is not caused by a failing hardware because it works fine on
  Windows. I tried with the latest Intel upstream kernel
  (http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
  next/current/) and upstream X.org (https://launchpad.net/~xorg-
  edgers/+archive/ubuntu/ppa), no change.

  [Personal Notes]
  I'm new to Ubuntu's world, I hope I've done things right, if not please tell 
me and I will resend the report or supply more information. I've created the 
bug report with ubuntu-bug xorg --save from another machine via SSH while the 
sick machine was frozen. It seemed to me more logical than using ubuntu-bug 
directly when the system is working fine. I've collected other information via 
SSH during the same lockup: dmesg, Xorg.0.log, i915_error_state. The latter was 
added as attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Nov  2 19:24:31 2014
  DistUpgraded: 2014-10-25 12:05:51,479 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.13.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.16.0-23-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.16.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0273]
 Subsystem: Dell Device [1028:0273]
  InstallationDate: Installed on 2014-10-11 (22 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Vostro1510
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=9b3612b7-c4bf-4840-885b-9fae75d6342c ro splash quiet vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (8 days ago)
  dmi.bios.date: 03/18/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0M277C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd03/18/2009:svnDellInc.:pnVostro1510:pvrNull:rvnDellInc.:rn0M277C:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro1510
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sun Nov  2 18:41:51 2014
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include /sys/class/drm/card0/error and 
the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   15873 
   vendor LPL
  xserver.version: 2:1.16.0-1ubuntu1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : 

[Desktop-packages] [Bug 1427804] Re: Mouse pointer disappears after upgrade to kernel 3.19

2015-03-10 Thread Alberto Salvia Novella
Please:
- Following https://wiki.ubuntu.com/Kernel/MainlineBuilds, test if this bug 
affects the mainline kernel built.
- Post your result here.
- Set this bug status back to confirmed.

Thank you.

** Changed in: xorg (Ubuntu)
   Importance: Undecided = Critical

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New = Confirmed

** Changed in: linux (Ubuntu)
   Importance: Undecided = Critical

** Changed in: linux (Ubuntu)
   Status: Confirmed = Incomplete

** Changed in: xorg (Ubuntu)
   Status: Confirmed = Incomplete

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

Title:
  Mouse pointer disappears after upgrade to kernel 3.19

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to kernel 3.19, the mouse pointer disappears.
  The mouse is fully functional, just cannot see its pointer, which makes it 
pretty useless...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Mar  3 19:23:30 2015
  DistUpgraded: 2014-11-04 19:50:17,092 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.16.0-31-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-031900-generic, x86_64: installed
   vboxhost, 4.3.18, 3.16.0-30-generic, x86_64: installed
   vboxhost, 4.3.18, 3.16.0-31-generic, x86_64: installed
   vboxhost, 4.3.18, 3.19.0-031900-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
  InstallationDate: Installed on 2014-10-24 (129 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-031900-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (118 days ago)
  dmi.bios.date: 09/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2012
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO(Wi-Fi ac)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2012:bd09/30/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Mar  3 19:21:19 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4121 
   vendor WAC
  xserver.version: 2:1.16.0-1ubuntu1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427804/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses

2015-03-10 Thread Björn Michaelsen
Just quickly: Of course its insane to rebuild all rdeps. However, this
is what would be the only way to fix this properly.

A. Heinlein in comment 70 only rebuild the packages between glib and
LibreOffice, which fixes the immediate problem, but might cause
unforseeable and hard to debug/triage problems with all the other
packages depending on glib that were _not_ rebuild. As such it is not
recommendable in an production environment.

So: upgrading to 14.04 still is the recommended action.

@Adam Conrad: Possibly this bug in 12.04 should have a target for 12.04
and be Wont Fix there, just to make this more explicit.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1214352

Title:
  [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in
  parentheses

Status in LibreOffice Productivity Suite:
  Fix Released
Status in The G Library - GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gvfs package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New

Bug description:
  [Impact]
   * This bug affects Glib-dependent packages, one of them is modern version of 
LibreOffice 4.x from PPA 
(https://launchpad.net/~libreoffice/+archive/ubuntu/ppa).
  * LibreOffice is very important software. Modern versions are more 
functional. Without them Ubuntu is nothing, it is a toy.

  [Test Case]
   1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server 
(Samba on GNU/Linux, or from Windows). Make this share available for read-write.
   2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait 
the share to be mounted with GVFS.
   2a.2. Double click on 'test.odt'
   2b. Launch terminal and send 'libreoffice 
smb://server_name/share_name/test.odt' command.
   3. Get error message from LibreOffice:
   The file 'test.odt' is corrupt and therefore cannot be opened.
   LibreOffice can try to repair the file.

  The corruption could be the result of document manipulation or of
   structural document damage due to data transmission.
   We recommend that you do not trust the content of the repaired document.
   Execution of macros is disabled for this document.

  Should LibreOffice repair the file?

  Yes No
   4a. If I click 'Yes', the file is opened, but the title of the document
    is Untitled 1 (repaired document), not original name.
   4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text:
    The file 'test.odt' could not be repaired and therefore cannot be 
opened.
  OK

  I click 'OK' here, the next window LibreOffice 4.4.1.2 is opened 
with text:
  General Error.
  General input/output error.

  OK

  If I click OK here - no files are opened.

  While step 3 gvfsd-smb process eats CPU then terminates with error.
  This error is caused by bug in Glib (wrong type conversion in macros).

  [Regression Potential]

   * This functionality is essential. Please fix this bug.
  I (and you) can't tell Windows users, that they should not open office files 
from network shares in GNU/Linux.

   * The patch has two lines
  
(https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4)
  and well-tested at upstream.

   * This bug may cause potential loss of data.

  [Other Info]

   * Corresponding links to LibO bugs are:
     https://bugs.freedesktop.org/show_bug.cgi?id=67527
     https://bugs.documentfoundation.org/show_bug.cgi?id=72337

  [Original description]
  On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument 
in parentheses, causing trouble down the stack in gvfs and LibreOffice (and 
possibly in lots of obscure bugs elsewhere).
  There is a patch available, but as this touches the header, it needs a full 
recompile of rdepends.
  see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html 
ff. for details

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1424864] Re: Xorg crash

2015-03-10 Thread Galen Thurber
apport information

** Tags added: apport-collected ubuntu

** Description changed:

  Xorg crashing out  back into login manager
  and apport failed 
  This problem report is damaged and cannot be processed.
  
  IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpXYLMdA is truncated:
  expected core file size = 75243520, found: 6356992.',)
  
  
  openConnection: connect: No such file or directory
  cannot connect to brltty at :0
  xfce4-settings-helper: Another instance is already running. Leaving...
  
  (polkit-gnome-authentication-agent-1:9183): GLib-CRITICAL **:
  g_variant_new_string: assertion `string != NULL' failed
  
  (polkit-gnome-authentication-agent-1:9183): polkit-gnome-1-WARNING **:
  Failed to register client:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files
  
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  
  
  (xfce4-settings-helper:9229): xfce4-settings-helper-WARNING **: Failed to get 
the _NET_NUMBER_OF_DESKTOPS property.
  ** Message: applet now removed from the notification area
  ** Message: using fallback from indicator to GtkStatusIcon
  ** Message: applet now embedded in the notification area
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No 
such file or directory
  
  (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32:
  assertion `G_IS_FILE_INFO (info)' failed
  
  (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: 
assertion `G_IS_FILE_INFO (info)' failed
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No 
such file or directory
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66
  Uname: Linux 3.2.0-76-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Mon Feb 23 19:14:16 2015
  InstallationMedia: Xubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140205)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.0.1-0ubuntu17.8
+ Architecture: amd64
+ DistroCodename: precise
+ DistroRelease: Ubuntu 12.04
+ DistroVariant: ubuntu
+ InstallationMedia: Xubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140205)
+ MarkForUpload: True
+ NonfreeKernelModules: nvidia
+ Package: xorg 1:7.6+12ubuntu2
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANGUAGE=en_CA:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_CA.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66
+ Tags:  precise ubuntu
+ Uname: Linux 3.2.0-76-generic x86_64
+ UnreportableReason: Please work this issue through technical support channels 
first.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom debian-tor dialout dip lpadmin plugdev sambashare sudo

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1424864/+attachment/4339918/+files/Dependencies.txt

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Xorg crashing out  back into login manager
  and apport failed 
  This problem report is damaged and cannot be processed.

  IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpXYLMdA is
  truncated: expected core file size = 75243520, found: 6356992.',)

  
  openConnection: connect: No such file or directory
  cannot connect to brltty at :0
  xfce4-settings-helper: Another instance is already running. Leaving...

  (polkit-gnome-authentication-agent-1:9183): GLib-CRITICAL **:
  g_variant_new_string: assertion `string != NULL' failed

  (polkit-gnome-authentication-agent-1:9183): polkit-gnome-1-WARNING **:
  Failed to register client:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations

  
  (xfce4-settings-helper:9229): xfce4-settings-helper-WARNING **: Failed to get 
the _NET_NUMBER_OF_DESKTOPS property.
  ** Message: applet now removed from the notification area
  ** Message: using fallback from indicator to GtkStatusIcon
  ** Message: applet now embedded in the notification area
  WARNING: gnome-keyring:: couldn't 

[Desktop-packages] [Bug 1418077] Re: After radio technology is changed, mobile-data takes ~5m to re-connect

2015-03-10 Thread Pat McGowan
** Changed in: network-manager (Ubuntu)
   Status: Confirmed = In Progress

** Changed in: network-manager (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = Tony Espy (awe)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1418077

Title:
  After radio technology is changed, mobile-data takes ~5m to re-connect

Status in the base for Ubuntu mobile products:
  Confirmed
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:
  1. Confirm cellular data (disable wifi)
  2. Change TechnologyPreference on online SIM
  3. Confirm no cellular data
  4. Wait ~10 minutes
  5. Confirm cellular data 

  What happens:
  Changing something on the modem causes cellular data to disappear for 10 
minutes

  What should happen:
  It should behave as before, i.e. cellular data should come back immediately

  current build number: 97
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-02 12:48:25
  version version: 97
  version ubuntu: 20150202
  version device: 20150128-5379bdb
  version custom: 20150202

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418077/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should hit Mincho(serif) font

2015-03-10 Thread Nobuto Murata
Example PDF document.

** Attachment added: h26syotoku.pdf
   
https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+attachment/4339987/+files/h26syotoku.pdf

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-takao in Ubuntu.
https://bugs.launchpad.net/bugs/1430339

Title:
  fc-match Ryumin should hit Mincho(serif) font

Status in fonts-takao package in Ubuntu:
  New

Bug description:
  Ryumin and Gothic-BBB are generic font names for serif/sans-serif like
  Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer
  substitute for Ryumin, however `fc-match Ryumin` does not return
  fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif)
  instead.

  Expected result:
  $ fc-match Ryumin
  fonts-japanese-mincho.ttf: TakaoPMincho Regular

  Actual result:
  $ fc-match Ryumin
  fonts-japanese-gothic.ttf: Takao Pゴシック Regular

  
  [1]
  /etc/fonts/conf.d/65-fonts-takao-mincho.conf
   21 match target=pattern
   22 test qual=any name=family
   23 stringRyumin/string
   24 /test
   25 edit name=family mode=prepend
   26 stringTakao P明朝/string
   27 /edit
   28 /match

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fonts-takao-mincho 003.02.01-9ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 22:41:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-28 (9 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228)
  PackageArchitecture: all
  SourcePackage: fonts-takao
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430280] Re: NetworkManager-wait-online.service not enabled after package installation

2015-03-10 Thread Martin Pitt
At the moment, a default installation has these rcS init.d scripts:

  apparmor console-setup ifupdown lvm2 lvm networking qemu-kvm qemu-
system-x86

Of those only console-setup.service has Required-Start: $remote-fs, and
none of them have $network.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1430280

Title:
  NetworkManager-wait-online.service not enabled after package
  installation

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After installing NetworkManager in a fresh vivid VM, NetworkManager-
  wait-online.service is disabled. We should consider enabling it on
  systems which don't have any static interfaces in
  /etc/network/interfaces, so that units that need network-online.target
  work properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1430280/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1428356] Re: 03f0:2b17 USB HP LaserJet 1020 printer will not print after boot

2015-03-10 Thread chris pollock
Attached is the output of all the commands in the USB printer section of
the link you sent above.  When you look at the output of 'lsusb' in the
attached you can see that the printer is not shown however nor is the
indicator lamp lit on my USB Hub (yes, I've tried connecting this
printer to each and every USB port on my system whether it's physically
on the computer itself or on the 7 Port Hub I have). Once I turn the
printer off then on again as shown below it's recognized with 'lsusb'
but still will not print.

chris@localhost:~$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 009: ID 1058:0830 Western Digital Technologies, Inc. 
Bus 001 Device 020: ID 03f0:2b17 Hewlett-Packard LaserJet 1020
Bus 001 Device 004: ID 0bc2:2120 Seagate RSS LLC 
Bus 001 Device 003: ID 050d:0237 Belkin Components F5U237 USB 2.0 7-Port Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


** Attachment added: Debugging output for USB printer problems from Ubuntu 
Wiki
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1428356/+attachment/4340676/+files/bug1428356printerts.txt

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

Title:
  03f0:2b17 USB HP LaserJet 1020 printer will not print after boot

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  After a reboot due to cups related package update my HP1020 printer is not 
initialized. This is shown in my syslog:
  Mar  4 15:32:42 localhost kernel: [  178.196280] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:32:42 localhost kernel: [  178.198667] usblp0: removed
  Mar  4 15:32:53 localhost kernel: [  189.196356] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:32:53 localhost kernel: [  189.198743] usblp0: removed
  Mar  4 15:33:04 localhost kernel: [  200.196869] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:33:04 localhost kernel: [  200.199629] usblp0: removed
  Mar  4 15:33:15 localhost kernel: [  211.200586] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17

  This just continues on for hundreds of entries until I unplug and
  replug the printer back in, and power cycle several times. It will
  then eventually print a test page via 'CUPS'.

  Some other information from my syslog:
  Mar  4 15:42:10 localhost kernel: [  746.297929] usblp: can't set desired 
altsetting 0 on interface 0
  Mar  4 15:42:10 localhost kernel: [  746.488804] usb 1-3.5: USB disconnect, 
device number 5
  Mar  4 15:42:14 localhost kernel: [  750.528166] usb 1-3.5: new high-speed 
USB device number 7 using ehci-pci
  Mar  4 15:42:16 localhost udev-configure-printer: remove 
/devices/pci:00/:00:1a.7/usb1/1-3/1-3.5
  Mar  4 15:42:16 localhost colord: device removed: 
sysfs-Hewlett-Packard-HP_LaserJet_1020
  Mar  4 15:42:23 localhost kernel: [  758.976137] usb 1-3.5: new high-speed 
USB device number 8 using ehci-pci
  Mar  4 15:42:23 localhost kernel: [  759.088384] usb 1-3.5: New USB device 
found, idVendor=03f0, idProduct=2b17
  Mar  4 15:42:23 localhost kernel: [  759.088389] usb 1-3.5: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Mar  4 15:42:23 localhost kernel: [  759.088392] usb 1-3.5: Product: HP 
LaserJet 1020
  Mar  4 15:42:23 localhost kernel: [  759.088394] usb 1-3.5: Manufacturer: 
Hewlett-Packard
  Mar  4 15:42:23 localhost kernel: [  759.088396] usb 1-3.5: SerialNumber: 
JL1F0DC
  Mar  4 15:42:23 localhost kernel: [  759.091958] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 8 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:42:23 localhost logger: loading HP Device 001 008
  Mar  4 15:42:23 localhost udev-configure-printer: add 
/devices/pci:00/:00:1a.7/usb1/1-3/1-3.5
  Mar  4 15:42:23 localhost udev-configure-printer: device devpath is 
/devices/pci:00/:00:1a.7/usb1/1-3/1-3.5
  Mar  4 15:42:23 localhost udev-configure-printer: MFG:Hewlett-Packard MDL:HP 
LaserJet 1020 SERN:- serial:JL1F0DC
  Mar  4 15:42:24 localhost kernel: [  760.148568] usblp0: removed
  Mar  4 15:42:24 localhost kernel: [  760.159830] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 8 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  

[Desktop-packages] [Bug 1308800] Re: Unity doesn't respawn all the times on crashes

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
Milestone: 7.2.4 = 7.2.5

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

Title:
  Unity doesn't respawn all the times on crashes

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in gnome-session package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Killing compiz repeatedly doesn't make unity to reload all the times.

  This is caused by the fact that due to a regression unity7 is not
  loaded anymore by upstart (but by gnome-session) and thus it seems
  that sometimes it doesn't properly gets restarted.

  This is also a security issue, because if the session was locked, and
  unity is not reloaded the session won't be locked anymore.

  [Test Case]
  From a terminal run killall -9 compiz multiple times, it should always 
reload, but it fails after a couple of times.

  [Regression Potential]
  The fix is about always making unity to be launched by upstart.
  Regression potential is low, since upstart is now used by most ubuntu desktop 
applications, and it ensures compiz will run properly anyway.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1385285] Re: Clicking in panel elements when the expo is active, performs to the maximized windows

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1385285

Title:
  Clicking in panel elements when the expo is active, performs to the
  maximized windows

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  1. Open a maximized window (it must be focused when using global menus, not 
with LIMs)
  2. Hit Super+s to enter in expo mode
  3. Click in the panel, in different areas and you'll get:
     - top-left corner buttons will work (although when not visible)
     - grab area will make possible to grab and focus (when in LIM mode) a 
window

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could potentially introduce
  new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity where it has been in the Ubuntu Vivid Vervet dev release form
  several weeks without apparent regression.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1361679] Re: Switcher Icons does not show progress emblem

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1361679

Title:
  Switcher Icons does not show progress emblem

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  - Open an application that shows progress information on its icon (i.e. 
nautilus or Hello Unity)
  - Open Alt-Tab switcher

  Expected behavior:
  - The icon should show the progress bar overlay

  Actual behavior:
  - No progress bar is shown.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any change to Switcher rendering has the potential to mess up drawing
  icons in the Switcher or crashing Unity.

  [ Other Info ]

  The Ubuntu 14.04 LTS SRU was cherry-picked from the Ubuntu 14.10
  release where it has been in production use for some time without
  apparent regression.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1350331] Re: Dash doesn't close when Drag and dropping from it to another window

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1350331

Title:
  Dash doesn't close when Drag and dropping from it to another window

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

   1. Open one nautilus window and another window, so that nautilus is not 
focused
   2. Open the dash File lens (Super+F)
   3. Start dragging a file from that to the nautilus launcher icon
   4. Wait some delay

  Expected Result:
   4. The dash is closed and nautilus window is focused

  Actual result:
   4. The nautilus window is focused, but the dash is not closed

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change in Unity has the potential to introduce crashes in
  Unity.

  This particular fix has the potential to not close the dash after a
  drag-and-drop operation, which could conceivably result in a desktop
  lock-up requiring a restart.

  [ Other Info ]

  The Ubuntu 14.04 LTS SRU fix was cherry-picked from Ubuntu 14.10 where
  it has been in production use for some time without apparent
  regression.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1384958] Re: Ubuntu Desktop title is moved right as if the window buttons were there

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1384958

Title:
  Ubuntu Desktop title is moved right as if the window buttons were
  there

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  1. Open a maximized window
  2. Hit Super+s
  3. The Ubuntu Desktop title is moved some pixels to the right, as shown in 
the attached screenshot.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell has the potential to
  introduce new crashes or lockups.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity where it has been included in the Ubuntu Vivid Vervet dev
  release for some time without apparent regression.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1361751] Re: Launcher Icon shortcut labels don't honor text scaling

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1361751

Title:
  Launcher Icon shortcut labels don't honor text scaling

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  Text scaling value is ignored by icons overlay text.

   - From u-c-c → accessibility → enable Big Text option

  Icons overlay text should honor that setting.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell has the potential to
  introduce new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for several weeks without
  apparent regression.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1373695] Re: Not resizable windows can be moved by dragging them on every edge

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1373695

Title:
  Not resizable windows can be moved by dragging them on every edge

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  1. Open a non resizable window such as Calculator or Unity Control Center
  2. Move the mouse to the edge of the window, outside the window itself
     but in the area that is close at least 10 px.
  3. Press the mouse and start to drag

  Expected behavior:
  4. nothing happens

  Actual behavior
  5. the hand cursor is shown and window can be dragged around
  As side effect, if LIMs are enabled, moving the mouse over a window edge 
makes the menus to show.

   [ Test Case ]

  See above.

  [ Regression Potential ]

  Any change to the Unity desktop shell could potentially introduce new
  crashed or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  apparent regression.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1361713] Re: Launcher icon count does not honour the text scaling

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1361713

Title:
  Launcher icon count does not honour the text scaling

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  Text scaling value is ignored by icon count (emblem).

   - From u-c-c → accessibility → enable Big Text option

  Icon count text should be bigger.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any modification to Unity desktop shell sources has the potential to
  introduce desktop shell crashes or lockups.

  [ Addition Info ]

  The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time with no apparent
  regressions.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1072206] Re: [nvidia] Window content is black or transparent

2015-03-10 Thread Tomislav
Can some1 tell me when this fix will hit ubuntu 14.04 ? thx

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

Title:
  [nvidia] Window content is black or transparent

Status in Compiz:
  In Progress
Status in Compiz 0.9.11 series:
  Triaged
Status in NVIDIA Drivers Ubuntu:
  Invalid
Status in Unity:
  Invalid
Status in compiz package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 12.10 64bit (updated from 12.04) / NVIDIA GeForce 8 proprietary
  driver.

  This bug happens to me from 12.04 from some update I think.
  It appears mostly when I open a new application and only ocassionally.
  As temporary solution creating some other event like opening Unity dash or 
opening some next window, etc. fix it. Then window content is refreshed and I 
can see all correctly.
  Same with stable and experimental nvidia drivers.

  Screenshot of this bug is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.48  Sun Sep  9 20:22:27 
PDT 2012
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Oct 27 23:00:14 2012
  DistUpgraded: 2012-10-23 19:34:29,842 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-experimental-304, 304.48, 3.5.0-17-generic, x86_64: installed
   virtualbox, 4.1.18, 3.2.0-32-generic, x86_64: installed
   virtualbox, 4.1.18, 3.5.0-17-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Giga-byte Technology Device [1458:3468]
  InstallationDate: Installed on 2012-08-29 (59 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328)
  JockeyStatus:
   kmod:nvidia_experimental_304 - nvidia_experimental_304 (Proprietary, 
Enabled, Not in use)
   kmod:nvidia_173 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_current - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_173_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and 
VDPAU library (Proprietary, Disabled, Not in use)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=3ae94b68-4a0c-4633-aec7-b4ed25a23003 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2012-10-23 (4 days ago)
  XorgConf:
   Section Device
Identifier  Default Device
Option  NoLogoTrue
   EndSection
  dmi.bios.date: 05/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0208
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0208:bd05/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLX:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.8.4-0ubuntu3
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  

[Desktop-packages] [Bug 1424664] Re: no ifupdown configuration found

2015-03-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1424664

Title:
  no ifupdown configuration found

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  booted with systemd-sysv

  found into syslog:

  NetworkManager[770]: info management mode: unmanaged
  NetworkManager[770]: info devices added (path: 
/sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, iface: eth0)
  NetworkManager[770]: info device added (path: 
/sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, iface: eth0): no 
ifupdown configuration found.
  NetworkManager[770]: info devices added (path: 
/sys/devices/pci:00/:00:1c.4/:03:00.0/net/eth1, iface: eth1)
  NetworkManager[770]: info device added (path: 
/sys/devices/pci:00/:00:1c.4/:03:00.0/net/eth1, iface: eth1): no 
ifupdown configuration found.
  NetworkManager[770]: info devices added (path: /sys/devices/virtual/net/lo, 
iface: lo)
  NetworkManager[770]: info device added (path: /sys/devices/virtual/net/lo, 
iface: lo): no ifupdown configuration found.
  NetworkManager[770]: info end _init.

  
  NetworkManager[770]: (NetworkManager:770): GLib-CRITICAL **: g_dir_read_name: 
assertion 'dir != NULL' failed

  .
  NetworkManager[770]: info (eth1): link connected
  NetworkManager[770]: info (eth1): device state change: unavailable - 
disconnected (reason 'carrier-changed') [20 30 40]
  NetworkManager[770]: info Auto-activating connection 'Wired connection 1'.
  Feb 23 15:06:39 u32 NetworkManager[770]: info Activation (eth1) starting 
connection 'Wired connection 1'
  NetworkManager[770]: info Activation (eth1) Stage 1 of 5 (Device Prepare) 
scheduled...
  NetworkManager[770]: info Activation (eth1) Stage 1 of 5 (Device Prepare) 
started...
  NetworkManager[770]: info (eth1): device state change: disconnected - 
prepare (reason 'none') [30 40 0]
  NetworkManager[770]: info NetworkManager state is now CONNECTING

  note: only eth1 is used to get stream; so it looks like a race as
  networkmanager seems working as expected; but what a confusing
  process: do really need a better design, because that one is a real
  mess.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-6.6-generic 3.19.0
  Uname: Linux 3.19.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Feb 23 15:45:26 2015
  IpRoute:
   default via 192.168.1.1 dev eth1  proto static  metric 1024
   169.254.0.0/16 dev eth1  scope link  metric 1000
   192.168.1.0/24 dev eth1  proto kernel  scope link  src 192.168.1.3
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.

   eth1  no wireless extensions.
  RfKill:

  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH
   Wired connection 1  7086b2ff-1446-45fe-b8f3-cd333cd4cee1  802-3-ethernet  
1424702496  lun. 23 févr. 2015 15:41:36 CET  yes  no
/org/freedesktop/NetworkManager/Settings/0  yes eth1activated  
/org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   eth1ethernet  connected/org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  7086b2ff-1446-45fe-b8f3-cd333cd4cee1  
/org/freedesktop/NetworkManager/ActiveConnection/0
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1424664/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430194] Re: totem can't show menu correctly while playing video in fullscreen

2015-03-10 Thread TienFu Chen
** Description changed:

  While playing video in fullscreen, right click should show the menu, but 
totem will flicker the menu instead.
- I can't reproduce this issue with VLC player.
+ I can't reproduce this issue with VLC player or chrome playing youtube video.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: totem 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 15:50:13 2015
  DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-stella-datong150206-trusty-amd64-20150214-1
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-stella-datong150206-trusty-amd64-20150214-1
  InstallationDate: Installed on 2015-02-17 (21 days ago)
  InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20150214-07:47
  LogAlsaMixer:
-  Simple mixer control 'IEC958',0
-Capabilities: pswitch pswitch-joined
-Playback channels: Mono
-Mono: Playback [on]
+  Simple mixer control 'IEC958',0
+    Capabilities: pswitch pswitch-joined
+    Playback channels: Mono
+    Mono: Playback [on]
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  totem can't show menu correctly while playing video in fullscreen

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  While playing video in fullscreen, right click should show the menu, but 
totem will flicker the menu instead.
  I can't reproduce this issue with VLC player or chrome playing youtube video.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: totem 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 15:50:13 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong150206-trusty-amd64-20150214-1
  InstallationDate: Installed on 2015-02-17 (21 days ago)
  InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20150214-07:47
  LogAlsaMixer:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1430194/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1388901] Re: nvidia-prime fails to switch profiles (alternatives related)

2015-03-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-prime (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1388901

Title:
  nvidia-prime fails to switch profiles (alternatives related)

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Hello everyone,

  nvidia-prime has more bugs with every release! On a fresh install of
  Kubuntu 14.10, I've installed nvidia-prime and nvidia-331. After the
  obligatory restart, the Nvidia chip was active. Trying to switch to
  the Intel profile looks like this:

  joern@Aspire-V3-571G:~$ sudo prime-select intel
  Info: the current alternatives in use are: ['nvidia-331', 'nvidia-331']
  Info: selecting nvidia-331-prime for the intel profile
  update-alternatives: /usr/lib/nvidia-331-prime/ld.so.conf wird verwendet, um 
/etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) im 
manueller Modus bereitzustellen
  update-alternatives: /usr/lib/nvidia-331-prime/alt_ld.so.conf wird verwendet, 
um /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) im 
manueller Modus bereitzustellen

  That is only fixable by reinstalling Mesa, everytime I want to switch.
  Really annoying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1388901/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1428972] Re: Unmet dependencies for libcheese-gtk23 and libcheese7 on 14.04.2

2015-03-10 Thread HaiyanZhou
Similar error when install qt-sdk or qtcreator on 14.04.2
zhy@zhy-ubuntu:~$ sudo apt-get install qtcreator
正在读取软件包列表... 完成
正在分析软件包的依赖关系树   
正在读取状态信息... 完成   
有一些软件包无法被安装。如果您用的是 unstable 发行版,这也许是
因为系统无法达到您要求的状态造成的。该版本中可能会有一些您需要的软件
包尚未被创建或是它们已被从新到(Incoming)目录移出。
下列信息可能会对解决问题有所帮助:

下列软件包有未满足的依赖关系:
 unity-control-center : 依赖: libcheese-gtk23 (= 3.4.0) 但是它将不会被安装
依赖: libcheese7 (= 3.0.1) 但是它将不会被安装
E: 错误,pkgProblemResolver::Resolve 发生故障,这可能是有软件包被要求保持现状的缘故。

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1428972

Title:
  Unmet dependencies for libcheese-gtk23 and libcheese7 on 14.04.2

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I bumped into this issue while trying to install canonical-
  certification-client from our PPA [1]

  ubuntu@201307-13942:~$ sudo apt-get install canonical-certification-client
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   unity-control-center : Depends: libcheese-gtk23 (= 3.4.0) but it is not 
going to be installed
  Depends: libcheese7 (= 3.0.1) but it is not going to 
be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  However, the version number for these two packages are bigger than the
  required version number:

  ubuntu@201307-13942:~$ dpkg -l | grep libcheese-gtk23
  ii  libcheese-gtk23:amd64 3.10.2-0ubuntu2 
amd64tool to take pictures and videos 
from your webcam - widgets
  ubuntu@201307-13942:~$ dpkg -l | grep libcheese7
  ii  libcheese7:amd64  3.10.2-0ubuntu2 
amd64tool to take pictures and videos 
from your webcam - base library
  ubuntu@201307-13942:~$

  I have no clue for how this happens. I thought it was a problem to our
  PPA (bug 1427524), but I think we're not alone [2]

  [1] http://ppa.launchpad.net/checkbox-dev/ppa/ubuntu/
  [2] http://askubuntu.com/questions/593369/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1428972/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1428356] Re: 03f0:2b17 USB HP LaserJet 1020 printer will not print after boot

2015-03-10 Thread Christopher M. Penalver
** Changed in: cups (Ubuntu)
   Status: Incomplete = New

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

Title:
  03f0:2b17 USB HP LaserJet 1020 printer will not print after boot

Status in cups package in Ubuntu:
  New

Bug description:
  After a reboot due to cups related package update my HP1020 printer is not 
initialized. This is shown in my syslog:
  Mar  4 15:32:42 localhost kernel: [  178.196280] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:32:42 localhost kernel: [  178.198667] usblp0: removed
  Mar  4 15:32:53 localhost kernel: [  189.196356] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:32:53 localhost kernel: [  189.198743] usblp0: removed
  Mar  4 15:33:04 localhost kernel: [  200.196869] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:33:04 localhost kernel: [  200.199629] usblp0: removed
  Mar  4 15:33:15 localhost kernel: [  211.200586] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17

  This just continues on for hundreds of entries until I unplug and
  replug the printer back in, and power cycle several times. It will
  then eventually print a test page via 'CUPS'.

  Some other information from my syslog:
  Mar  4 15:42:10 localhost kernel: [  746.297929] usblp: can't set desired 
altsetting 0 on interface 0
  Mar  4 15:42:10 localhost kernel: [  746.488804] usb 1-3.5: USB disconnect, 
device number 5
  Mar  4 15:42:14 localhost kernel: [  750.528166] usb 1-3.5: new high-speed 
USB device number 7 using ehci-pci
  Mar  4 15:42:16 localhost udev-configure-printer: remove 
/devices/pci:00/:00:1a.7/usb1/1-3/1-3.5
  Mar  4 15:42:16 localhost colord: device removed: 
sysfs-Hewlett-Packard-HP_LaserJet_1020
  Mar  4 15:42:23 localhost kernel: [  758.976137] usb 1-3.5: new high-speed 
USB device number 8 using ehci-pci
  Mar  4 15:42:23 localhost kernel: [  759.088384] usb 1-3.5: New USB device 
found, idVendor=03f0, idProduct=2b17
  Mar  4 15:42:23 localhost kernel: [  759.088389] usb 1-3.5: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Mar  4 15:42:23 localhost kernel: [  759.088392] usb 1-3.5: Product: HP 
LaserJet 1020
  Mar  4 15:42:23 localhost kernel: [  759.088394] usb 1-3.5: Manufacturer: 
Hewlett-Packard
  Mar  4 15:42:23 localhost kernel: [  759.088396] usb 1-3.5: SerialNumber: 
JL1F0DC
  Mar  4 15:42:23 localhost kernel: [  759.091958] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 8 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:42:23 localhost logger: loading HP Device 001 008
  Mar  4 15:42:23 localhost udev-configure-printer: add 
/devices/pci:00/:00:1a.7/usb1/1-3/1-3.5
  Mar  4 15:42:23 localhost udev-configure-printer: device devpath is 
/devices/pci:00/:00:1a.7/usb1/1-3/1-3.5
  Mar  4 15:42:23 localhost udev-configure-printer: MFG:Hewlett-Packard MDL:HP 
LaserJet 1020 SERN:- serial:JL1F0DC
  Mar  4 15:42:24 localhost kernel: [  760.148568] usblp0: removed
  Mar  4 15:42:24 localhost kernel: [  760.159830] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 8 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:42:24 localhost udev-configure-printer: URI contains USB serial 
number
  Mar  4 15:42:24 localhost udev-configure-printer: URI match: 
usb://HP/LaserJet%201020?serial=JL1F0DC
  Mar  4 15:42:24 localhost udev-configure-printer: SERN field matches USB 
serial number
  Mar  4 15:42:24 localhost udev-configure-printer: URI match: 
hp:/usb/HP_LaserJet_1020?serial=JL1F0DC
  Mar  4 15:42:24 localhost udev-configure-printer: URI of detected printer: 
usb://HP/LaserJet%201020?serial=JL1F0DC, normalized: laserjet 1020 serial 
jl1f0dc
  Mar  4 15:42:24 localhost udev-configure-printer: URI of print queue: 
usb://HP/LaserJet%201020?serial=JL1F0DC, normalized: laserjet 1020 serial 
jl1f0dc
  Mar  4 15:42:24 localhost udev-configure-printer: Queue 
ipp://localhost:631/printers/HP-LaserJet-1020 has matching device URI
  Mar  4 15:42:24 localhost udev-configure-printer: URI of detected printer: 
hp:/usb/HP_LaserJet_1020?serial=JL1F0DC, normalized: laserjet 1020 serial 
jl1f0dc
  Mar  4 15:42:24 localhost udev-configure-printer: Queue 
ipp://localhost:631/printers/HP-LaserJet-1020 has matching device URI
  Mar  4 15:42:26 localhost kernel: [  762.327990] usblp0: removed
  Mar  4 15:42:30 localhost colord: Device added: 
sysfs-Hewlett-Packard-HP_LaserJet_1020

  chris@localhost:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 008 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business
  Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 006 Device 

[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file

2015-03-10 Thread Daniel van Vugt
** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
   Status: Invalid = Triaged

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
   Status: Invalid = Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
https://bugs.launchpad.net/bugs/1268257

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: objdump: '... .tmp_nv.o': No such
  file

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Triaged

Bug description:
  **WARNING:** This bug has been widely reported and has *many*
  automatic subscribers. Please be considerate.

  **If you need help:** try searching and asking on
  http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a
  nearby user group (see http://loco.ubuntu.com or search for LUG in
  your area). Link back to this bug for clarity.

  ---

  This seems to fix it (at least for one version upgrade) for many
  people

  $ sudo dpkg-reconfigure nvidia-331

  after that...

  $ sudo dpkg-reconfigure nvidia-331-uvm

  (some users may be on the versions of these packages suffixed with
  -updates )

  ---

  **If you want to unsubscribe:** see
  https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
  drivers-331-updates/+bug/1268257/+subscribe. You can also change your
  settings so you don't get comments but do get notified when the bug is
  solved - see https://askubuntu.com/questions/576523 for details.

  **If you want to comment:** Please consider if you have something
  meaningful to contribute to the 2500+ people who will get an email.

  **If you are an Ubuntu developer:** thanks for looking into this! :D

  

  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1370017] Re: Unity Lockscreen shows unlocked desktop while shutting down

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1370017

Title:
  Unity Lockscreen shows unlocked desktop while shutting down

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [Impact and Test Case]

  Steps to reproduce:
  1 - Lock the screen
  2 - From the lockscreen, tell the computer to shut down / restart

  Expected behavior:
  * Session programs are closed while the screen is still locked
  * During shutdown, no user interaction is possible

  Observed behavior:
  * The lockscreen is gone immediately, with the rest of compiz (e.g. window 
decorations are not present)
  * But it's possible to interact with programs that are still running in the 
session for about 3 seconds

  Observed on an updated Trusty machine, running unity version
  7.2.2+14.04.20140714-0ubuntu1.1

  I consider this bug a security vulnerability because during those 3
  seconds it could be possible to access and interact with sensitive
  information.  Yes, it's short, but you could take a picture or even rm
  -rf / if there happened to be a root console available.

  [Regression Potential]

  An improper implementation of the fix for this issue could result in
  an indefinite hang during system shutdown, or could result in the
  problem not being completely fixed and the security vulnerability
  continuing.

  Neither appear to be the case.

  [ Other Info ]

  The Ubuntu 14.04 LTS SRU has been cherry-picked from upstream Unity
  where it has been in development-level production code in Ubuntu
  'Vivid Vervet' development release for a few months and has not
  display additional problems.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1371764] Re: Screen does not lock when an unity indicator is open

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1371764

Title:
  Screen does not lock when an unity indicator is open

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  Screen does not lock when a Unity indicator is open.

  [ Test Case ]

  1. Open an unity Indicator
  2. Close the laptop lid¹

  Expected behavior:
  3. The indicator menu should be closed and the screen is locked

  Actual behavior:
  3. The screen is not locked with the menu visible, it gets locked
  as soon as the menu is closed.

  [1] instead of this action, you can also run the script below just before 
opening an indicator:
    sleep 3  gdbus call --session --dest com.canonical.Unity \
     --object-path /com/canonical/Unity/Session \
     --method com.canonical.Unity.Session.Lock

  [ Regression Potential ]

  Worst case is the lock screen still does not come up if an indicator
  is open, which could be a potential security problem.

  [ Other Info ]

  The fix for Ubuntu 14.04 LTS is cherry-picked from Ubuntu 14.10 where
  it has been in production use for some time without apparent
  regression.

  This is a special case of bug #49579, although this applies only to
  the unity indicators.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1368427] Re: With 2 monitors, after suspending, it is possible to skip the password

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1368427

Title:
  With 2 monitors, after suspending, it is possible to skip the password

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Having a notebook with an extra monitor, after suspending the session, it is 
possible to skip the password.
  My external monitor is connected through VGA, and I am able to reproduce this 
bug around 70-80% of the time (I don't know if it happens with an HDMI cable).
  If I try to reproduce and the bug does not happen, I need to reboot the 
notebook so it can happen again.
  I tried with different resolutions and rotations for the monitor and the 
bug still happens.
  The external monitor needs to be configured to be on the left of the 
notebook, or the bug will not happen.

  It is so many steps to make it happen, that I made a short video
  explaining.

  https://www.youtube.com/watch?v=FYzz32K6q10

  ps.; The video is unlisted, so only with the link is accessible.

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 11 17:49:57 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 1800
  InstallationDate: Installed on 2014-04-12 (152 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140411)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1364225] Re: Shadow applied inconsistently to windows that use XShape

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1364225

Title:
  Shadow applied inconsistently to windows that use XShape

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  Non-standard windows of a non-rectangular shape end up with
  rectangular shadows drawn behind them by Unity.

  It is better to have no shadow at all for these windows rather than an
  incorrect rectangular shadow.

  [ Test Case ]

  C code for a test case is attached to this bug.  It needs to be
  compiled and run to demonstrate the problem and solution.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could introduce a new crash
  or hang.

  A possible regression in this particular fix is a lack of shadows when
  expected, or a non-standard non-rectangular window still having a
  shadow as before.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  regression.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1332509] Re: Lockscreen misses arrow activator.

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1332509

Title:
  Lockscreen misses arrow activator.

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Unity lock screen password entry should have an activator arrow like
  unity-greeter.

  [Test Case]

  Using the Unity desktop shell, lock the screen using Super-L (or you
  favourite method).  When the lockscreen is displayed, a little wedgie
  should be displayed at the right-hand end of the password entry field,
  and clicking on that wedgie should perform the authentication action.

  [Regression Potential]

  This is a cosmetic change to allow click-clicky mouse interaction to
  work just like hitting [Enter].  The biggest potential for regression
  is that the asset (artwork) does not get displayed or the mouse click
  does not work just like hitting Enter does.

  [Other Info]

  The Ubuntu 14.04 LTS SRU was cherry-picked from Ubuntu 14.10 whwere it
  has been in production use for some months without apparent
  regression.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1349281] Re: The exposed open windows are not displayed in the geometric order

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1349281

Title:
  The exposed open windows are not displayed in the geometric order

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  When multiple non-maximised windows of the same program are open and
  one clicks on the icon of the program in the launcher, they are all
  shown one next to each other but in an unexpected, difficult-to-
  predict order: windows that are in the top-left corner of the
  workspace can be shown in the exposé in the right bottom position or
  on the left bottom corner.

  This makes very hard to switch between similarly looking windows like
  terminals.

  [ Test Case ]

  
  * launch four or so terminal windows;
  * write something different on each of them to be able to tell them apart;
  * move each window to a different corner, possibly using the auto-resizing 
feature of Unity;
  * click on the terminal icon in the launcher;
  * many terminal windows are displayed;
  * choose the thumbnail in the right-top corner;
  * very likely a window that was in another corner has been selected;
  * try again various time and realize how confusing this all is.

  [ Potential Regressions ]

  An invalid ordering calculation might still position windows in the
  exposé in unexpected ways.  This is not a serious regression and has
  not been observed under production situations.

  [ Additional Info ]

  The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity as
  released in Ubuntu 14.10 where it demonstrated stability under daily
  use.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1329584] Re: The label in the panel menu doesn't match the /etc/os-release NAME

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1329584

Title:
  The label in the panel menu doesn't match the  /etc/os-release NAME

Status in Ubuntu Kylin:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  The label in the Unity Panel when the desktop is in the forground is
  not properly internationalizable or customizable for derivative
  distributrions.

  [ Test Case ]

  Install Ubuntu Kylin and observe the title in the Unity Panel when the
  desktop is in the foreground.

  [ Regression Potential ]

  Improperly implemented, this change could result in no label or an
  incorrect label displayed in the Unity Panel when the desktop is in
  the foreground.  This does not appear to occur during testing.

  [ Additional Info ]

  The Ubuntu 14.04 LTS SRU has been cherry-picked from upstream Unity as
  released in Ubuntu 14.10 and has proved to be stable in daily use.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1362162] Re: Dash buttons do not honour the text scaling

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1362162

Title:
  Dash buttons do not honour the text scaling

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  Text scaling value is ignored by dash buttons (filters and preview
  actions).

   - From u-c-c → accessibility → enable Big Text option

  Filters and preview action buttons should match this option.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change in the Unity desktop shell has the potential to
  introduce new crashes or lockups.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  apparent regression.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1374785] Re: Screen-saver fade-to-black does not cover entire screen on HiDPI

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1374785

Title:
  Screen-saver fade-to-black does not cover entire screen on HiDPI

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  When display scaling is set to 2x or greater the fade-to-black
  animation when the screen saver is invoked covers only a fraction of
  the screen.

  [ Test Case ]

  Requires a display with 2x UI scaling (works best with a high-DPI
  display).

  The fade-to-black which occurs prior to the screen shutting off only
  covers the top left quarter of the screen.

  When scaling is set to 1x, the entire screen fades to black.

  [ Regression Potential ]

  An invalid scaling calculation (or rounding error) could result in writing 
outside the screen buffer bounds with resulting unknown impact.  Inpspection 
and code review shows this not to be the case wit this patch.
  [ Other Info ]

  The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity where
  it has been in production use in Ubuntu 'Vivid Vervet' for some time
  and has not shown ergressions.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1197872] Re: unity crashed on session::view::Populate

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
Milestone: 7.2.4 = 7.2.5

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

Title:
  unity crashed on session::view::Populate

Status in Nux:
  Triaged
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in compiz package in Ubuntu:
  Invalid
Status in nux package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  I am not sure when this crash happened. However, when shutting down,
  the shutdown/restart dialog took ages to appear and the actual
  shutdown also took ages to start. I could not observe this behavior
  with 13.04 so I assume it is a bug and it might be the trigger for the
  crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: compiz-core 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
  Uname: Linux 3.10.0-2-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Thu Jul  4 14:10:04 2013
  DistUpgraded: 2013-06-29 10:51:30,966 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
  InstallationDate: Installed on 2013-04-18 (76 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic 
root=UUID=fa400436-f6bc-4f1e-9e78-5284a6e9f17c ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0xb7531710:or %dl,(%edi)
   PC (0xb7531710) in non-executable VMA region: 0xb7531000-0xb7532000 rw-p 
/lib/i386-linux-gnu/libc-2.17.so
   source %dl ok
   destination (%edi) (0x0960d9e8) ok
  SegvReason: executing writable VMA /lib/i386-linux-gnu/libc-2.17.so
  Signal: 11
  SourcePackage: compiz
  Stacktrace:
   #0  0xb7531710 in ?? () from /lib/i386-linux-gnu/libc.so.6
   No symbol table info available.
   #1  0x094d60c0 in ?? ()
   No symbol table info available.
   Backtrace stopped: previous frame inner to this frame (corrupt stack?)
  StacktraceTop:
   ?? () from /lib/i386-linux-gnu/libc.so.6
   ?? ()
  Title: compiz crashed with SIGSEGV
  UpgradeStatus: Upgraded to saucy on 2013-06-29 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/20/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 01GT.M026.20101220.RHU
  dmi.board.asset.tag: SAMSUNG
  dmi.board.name: N150P
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr01GT.M026.20101220.RHU:bd12/20/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: N150P
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.libdrm2: libdrm2 2.4.45-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
9.2~git20130628.g6b676e6-0ubuntu0+mir1-jenkins83saucy0
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
9.2~git20130628.g6b676e6-0ubuntu0+mir1-jenkins83saucy0
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu13
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.8-0ubuntu1
  xserver.bootTime: Thu Jul  4 17:32:07 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu13
  xserver.video_driver: intel

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1121941] Re: Spread (Super+W) causes maximised windows to resize/repaint and not just scale

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
Milestone: 7.2.4 = 7.2.5

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

Title:
  Spread (Super+W) causes maximised windows to resize/repaint and not
  just scale

Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in compiz package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Open two windows of an application on Raring
  Press Super+W to enable spread.
  Observe that the windows shrink vertically and repaint when entering spread 
and re-expand when leaving spread.
  I expect the windows should scale and not repaint or resize when entering or 
leaving spread.

  Test case.
  Start a virtualbox VM (with guest additions enabled so desktop resizing is 
automatic)
  Maximise the virtualbox window.
  Open a terminal in virtualbox and run the following command:-

  watch xrandr

  This will show the current resolution (which on my 1080p desktop is 
1855x1034) - attached max.png
  Enter spread on the host with Super+W
  Observe the guest repainting the desktop
  Wait a second or two for xrandr to display the new resolution (which on my 
machine goes to 1855x1006 - a reduction of 28px) - attached spread.png
  Exit spread and observe the screen size goes back to what it was before.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6
  Uname: Linux 3.8.0-5-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Mon Feb 11 11:05:19 2013
  DistUpgraded: 2013-01-18 10:34:11,775 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.2.4, 3.2.0-36-generic, x86_64: installed
   vboxhost, 4.2.4, 3.5.0-22-generic, x86_64: installed
   vboxhost, 4.2.4, 3.8.0-3-generic, x86_64: installed
   vboxhost, 4.2.4, 3.8.0-4-generic, x86_64: installed
   vboxhost, 4.2.4, 3.8.0-5-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2012-06-29 (226 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: LENOVO 4287CTO
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-5-generic 
root=UUID=c8438547-b9fb-46af-8012-4663c77c70e7 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: Upgraded to raring on 2013-01-18 (23 days ago)
  dmi.bios.date: 12/05/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET67WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4287CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET67WW(1.37):bd12/05/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4287CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.0-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Mon Feb 11 09:38:59 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1241972] Re: Drag and drop from Dash to Desktop doesn't work

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
Milestone: 7.2.4 = 7.2.5

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

Title:
  Drag and drop from Dash to Desktop doesn't work

Status in Chromium Browser:
  New
Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in Unity 7.1 series:
  Won't Fix
Status in Unity 7.2 series:
  Triaged
Status in nautilus package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  When you try to drag and drop an app from Dash (both from app lens and
  home lens) to Desktop, system display an error and the shortcut isn't
  created.

  The error is:
  Error while copying - There was an error getting information about /.
  More details: The specified location is not supported

  Then there are four buttons: Cancel - Skip all - Skip - Retry.

  Way to reproduce:
  - Open the dash
  - Drag an app icon and drop on desktop

  What happend:
  - An error is raised

  What expected:
  - A shortcut is created

  With file, music and photo is all ok.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1241972/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1066971] Re: Launcher count overflows when displaying 5+ digits

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1066971

Title:
  Launcher count overflows when displaying 5+ digits

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  What happens:

  1. The user (Me, in this case) installs the gmail plugin for the launcher.
  2. The user has more than  unread emails.
  3. The count becomes an unreadable mess.

  What should happen:

  1. The user (Me, in this case) installs the gmail plugin for the launcher.
  2. The user has more than  unread emails.
  3a. The count stretches, allowing for up to 8-9 digits to be displayed.
  3b. The count is truncated, still showing the most important parts of the 
number.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any software change in the Unity desktop shell has the potential to
  introduce desktop shell crashes or lockups.

  [ Other Info ]

  The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time with apparent
  regressions.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1047517] Re: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
Milestone: 7.2.4 = 7.2.5

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1047517

Title:
  compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ...
  from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()

Status in Unity:
  Confirmed
Status in Unity 7.2 series:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Unity crashed when i was trying the Preview.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity 6.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic i686
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: i386
  CrashCounter: 1
  Date: Fri Sep  7 18:49:48 2012
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb0d448c2 g_mount_spec_to_dbus_with_path+50:
mov0x4(%eax),%ebp
   PC (0xb0d448c2) ok
   source 0x4(%eax) (0x0005) not located in a known VMA region (needed 
readable region)!
   destination %ebp ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   g_mount_spec_to_dbus_with_path () from 
/usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
  Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path()
  UpgradeStatus: Upgraded to quantal on 2012-09-07 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
Milestone: 7.2.4 = 7.2.5

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Expired
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Confirmed
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Confirmed
Status in gnome-screensaver source package in Precise:
  Confirmed
Status in unity source package in Precise:
  Confirmed
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1424664] Re: no ifupdown configuration found

2015-03-10 Thread Teafx
Affects vivid touch as well (unofficial port):

Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info init!
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info 
update_system_hostname
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info   
interface-parser: parsing file /etc/network/interfaces
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: warn ignoring 
out-of-block data 'source-directory /etc/network/interfaces.d'
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info   
interface-parser: finished parsing file /etc/network/interfaces
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info management mode: 
unmanaged
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info devices added (path: 
/sys/devices/virtual/net/ifb0, iface: ifb0)
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info device added (path: 
/sys/devices/virtual/net/ifb0, iface: ifb0): no ifupdown configuration found.
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info devices added (path: 
/sys/devices/virtual/net/ifb1, iface: ifb1)
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info device added (path: 
/sys/devices/virtual/net/ifb1, iface: ifb1): no ifupdown configuration found.
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info devices added (path: 
/sys/devices/virtual/net/ip6tnl0, iface: ip6tnl0)
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info device added (path: 
/sys/devices/virtual/net/ip6tnl0, iface: ip6tnl0): no ifupdown configuration 
found.
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info devices added (path: 
/sys/devices/virtual/net/lo, iface: lo)
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info device added (path: 
/sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info devices added (path: 
/sys/devices/virtual/net/sit0, iface: sit0)
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info device added (path: 
/sys/devices/virtual/net/sit0, iface: sit0): no ifupdown configuration found.
Mar 10 22:15:57 ubuntu-phablet NetworkManager[814]: info end _init.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1424664

Title:
  no ifupdown configuration found

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  booted with systemd-sysv

  found into syslog:

  NetworkManager[770]: info management mode: unmanaged
  NetworkManager[770]: info devices added (path: 
/sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, iface: eth0)
  NetworkManager[770]: info device added (path: 
/sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, iface: eth0): no 
ifupdown configuration found.
  NetworkManager[770]: info devices added (path: 
/sys/devices/pci:00/:00:1c.4/:03:00.0/net/eth1, iface: eth1)
  NetworkManager[770]: info device added (path: 
/sys/devices/pci:00/:00:1c.4/:03:00.0/net/eth1, iface: eth1): no 
ifupdown configuration found.
  NetworkManager[770]: info devices added (path: /sys/devices/virtual/net/lo, 
iface: lo)
  NetworkManager[770]: info device added (path: /sys/devices/virtual/net/lo, 
iface: lo): no ifupdown configuration found.
  NetworkManager[770]: info end _init.

  
  NetworkManager[770]: (NetworkManager:770): GLib-CRITICAL **: g_dir_read_name: 
assertion 'dir != NULL' failed

  .
  NetworkManager[770]: info (eth1): link connected
  NetworkManager[770]: info (eth1): device state change: unavailable - 
disconnected (reason 'carrier-changed') [20 30 40]
  NetworkManager[770]: info Auto-activating connection 'Wired connection 1'.
  Feb 23 15:06:39 u32 NetworkManager[770]: info Activation (eth1) starting 
connection 'Wired connection 1'
  NetworkManager[770]: info Activation (eth1) Stage 1 of 5 (Device Prepare) 
scheduled...
  NetworkManager[770]: info Activation (eth1) Stage 1 of 5 (Device Prepare) 
started...
  NetworkManager[770]: info (eth1): device state change: disconnected - 
prepare (reason 'none') [30 40 0]
  NetworkManager[770]: info NetworkManager state is now CONNECTING

  note: only eth1 is used to get stream; so it looks like a race as
  networkmanager seems working as expected; but what a confusing
  process: do really need a better design, because that one is a real
  mess.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-6.6-generic 3.19.0
  Uname: Linux 3.19.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Feb 23 15:45:26 2015
  IpRoute:
   default via 192.168.1.1 dev eth1  proto static  metric 1024
   169.254.0.0/16 dev eth1  scope link  metric 1000
   192.168.1.0/24 dev eth1  proto kernel  scope link  src 192.168.1.3
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.

[Desktop-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store

2015-03-10 Thread Jim Hodapp
I would go one step further with the proposed indicator method of
letting the user know when an app is recording audio. I would have the
indicator-sound icon change to an image of a microphone (or even pop up
a new icon) and set the color as red. This would be much more self-
evident that recording is taking place than just a red speaker (the
first thing that I would think if I saw that without knowing what it
meant was that something was broken with my audio).

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

Title:
  Pulseaudio should integrate with trust-store

Status in the base for Ubuntu mobile products:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user (Foo wants to use
  the microphone. Is this ok? Yes|No), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it can ship that 
information off to a server somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1224756/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should return Mincho(serif) font in ja locale

2015-03-10 Thread Nobuto Murata
@Rolf,

 As you may know, I usually remain with the LTS releases and only run
the development release from time to time. As such, I hope the fix for
this ticket will be backported to trusty as well.

If this fix lands into vivid successfully and no regression reported in
vivid, we can consider to backport it to trusty as well. However I'm
under the impression that this Ryumin thing is not so critical.

 Furthermore, my system is mainly English-based. I hope you won't mind me 
 adding my own experiences here.
 
 I can basically confirm your findings, except that my US-locale returns a 
 different font.
 
 $ env LC_ALL=en_US.UTF-8 fc-match Ryumin
 ipamp.ttf: IPAPMincho Regular
 $ env LC_ALL=ja_JP.UTF-8 fc-match Ryumin
 fonts-japanese-gothic.ttf: Takao Pゴシック Regular

My patch fixes this behavior, the result for Ryumin will be always the
same in all locales.

 I tried the test PDF in different viewers and noticed there were some
alignment issues in the viewer built into Firefox (please refer to my
screenshot). I suspect that is another, separate issue?

Yes, that's separate issue in Mozilla's pdf.js I think. The PDF I
attached is rather complicated, I think it's natural rendering is broken
in some viewers.

 One of the things I sometimes notice is that Chinese at times seems to
have precedence over Japanese. For someone like me, that is unfortunate.
Are you aware of a list of known issues or some website to check if
one's configuration has any errors? This area of Ubuntu seems to change
from release to release so it is hard to keep up (with a lot of
improvement being made, at least that has been my experience). I do not
know as much as you do, so at best, I will notice the effects but I
would be utterly unable to dig into the causes. That's why your work is
so much appreciated.

 You titled the ticket  fc-match Ryumin should return Mincho(serif)
font in ja locale. That name is so obviously Japanese that I wonder why
the returned value should be locale-specific. From the superficial
information I have it seems that optimizations for Japanese are
sometimes only made only for Japanese locale, leaving people like me who
only display and write Japanese in a non-Japanese locale out in the
rain. I understand that sometimes this might have to do with political
sensitivities and the power of numbers.

Nowadays Ubuntu switches font substitutions by locales. For example, `fc-match 
serif` returns DejaVu Serif for most locales, TakaoPMincho for ja locale. 
You can specify per-user font locale settings(actually it's LC_CTYPE) in 
~/.pam_environment or ~/.profile.
https://help.ubuntu.com/community/EnvironmentVariables#Session-wide_environment_variables

Can you please put LC_CTYPE=ja_JP.UTF-8 in your ~/.pam_environment,
re-login and see how it works?

** Also affects: ubuntu-translations
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-takao in Ubuntu.
https://bugs.launchpad.net/bugs/1430339

Title:
  fc-match Ryumin should return Mincho(serif) font in ja locale

Status in Ubuntu Translations:
  New
Status in fonts-takao package in Ubuntu:
  Confirmed

Bug description:
  Ryumin and Gothic-BBB are generic font names for serif/sans-serif like
  Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer
  substitute for Ryumin, however `fc-match Ryumin` does not return
  fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif)
  instead.

  Expected result:
  $ fc-match Ryumin
  fonts-japanese-mincho.ttf: TakaoPMincho Regular

  Actual result:
  $ fc-match Ryumin
  fonts-japanese-gothic.ttf: Takao Pゴシック Regular

  
  [1]
  /etc/fonts/conf.d/65-fonts-takao-mincho.conf
   21 match target=pattern
   22 test qual=any name=family
   23 stringRyumin/string
   24 /test
   25 edit name=family mode=prepend
   26 stringTakao P明朝/string
   27 /edit
   28 /match

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fonts-takao-mincho 003.02.01-9ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 22:41:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-28 (9 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228)
  PackageArchitecture: all
  SourcePackage: fonts-takao
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1430339/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 987462] Re: Can't use virtual secondary display in VMWare Player

2015-03-10 Thread Fabián Rodríguez
I've removed myself from this bug's notifications as I don't have access
to this environment anymore and can't test further/provide further
feedback.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/987462

Title:
  Can't use virtual secondary display in VMWare Player

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Despite VMWare Player being configured to provide 2 displays, gnome-
  control-center only detects one.

  VMWare Player Version: 4.0.2 build-591240

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  Date: Mon Apr 23 11:52:05 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup22.0-0ubuntu2
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/987462/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering

2015-03-10 Thread Stephen M. Webb
** Changed in: unity/7.2
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1316265

Title:
  Maximized Window's Title Bar Does Not Merge into Menu Bar after
  Performing Super+W (window spread) filtering

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  A maximized application's title bar does not merge into the menu bar
  once a user has performed Super + W (window slide). Note that if one
  does not do Super+E, then the bars to merge together. However, once
  Super+E has been performed, this bug persists for the lifetime of the
  windowed application. If the application is restarted after doing
  Super+E, then the bug is gone. Thus, it seems like Super+E introduces
  this bug for the lifetime of the windowed application.

  Expected behavior: Maximized window's title bar is merged into menu bar.
  Observed: Does not occur after Super+W is performed.

  [ Test Case ]

  (1) Open one or more Terminals, place one in maximized mode (eg. by using 
control-super-up or clicking the embiggen button).
  (2) use super-W to enter the spread mode
  (3) select the maximized terminal window
  (4) lookee lookee, separate title bars without the fix!

  [ Regression Potential ]

  Any change to the Unity desktop shell could potentially introduce a
  new crash or hangup.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity where it has been a part of the Ubuntu Vivid Vervet dev
  release for some time now and has demonstrated no regressions.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works

2015-03-10 Thread Jeroen T. Vermeulen
I'm trying the BIOS upgrade as per those instructions.  The only
applicable option was the flashrom one, which seems to have hosed my
BIOS.  It's still on now, but I won't be able to boot it again.  Kindly
mark this bug New again to give me time to recover and retry!

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

Title:
  Screen resolution no longer works

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that resolution as the highest
  possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.

  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to
  work with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  1 09:52:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16510
   vendor DEL
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should return Mincho(serif) font in ja locale

2015-03-10 Thread Nobuto Murata
lp:ubuntu/fonts-takao seems out-of-date unfortunately. I'm attaching
debdiff instead.

** Patch added: fonts-takao_vivid.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+attachment/4340222/+files/fonts-takao_vivid.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-takao in Ubuntu.
https://bugs.launchpad.net/bugs/1430339

Title:
  fc-match Ryumin should return Mincho(serif) font in ja locale

Status in fonts-takao package in Ubuntu:
  New

Bug description:
  Ryumin and Gothic-BBB are generic font names for serif/sans-serif like
  Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer
  substitute for Ryumin, however `fc-match Ryumin` does not return
  fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif)
  instead.

  Expected result:
  $ fc-match Ryumin
  fonts-japanese-mincho.ttf: TakaoPMincho Regular

  Actual result:
  $ fc-match Ryumin
  fonts-japanese-gothic.ttf: Takao Pゴシック Regular

  
  [1]
  /etc/fonts/conf.d/65-fonts-takao-mincho.conf
   21 match target=pattern
   22 test qual=any name=family
   23 stringRyumin/string
   24 /test
   25 edit name=family mode=prepend
   26 stringTakao P明朝/string
   27 /edit
   28 /match

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fonts-takao-mincho 003.02.01-9ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 22:41:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-28 (9 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228)
  PackageArchitecture: all
  SourcePackage: fonts-takao
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430440] Re: gvfsd-trash crashed with SIGSEGV in g_slice_alloc()

2015-03-10 Thread Apport retracing service
*** This bug is a duplicate of bug 1353758 ***
https://bugs.launchpad.net/bugs/1353758

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1353758, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1430440/+attachment/4340205/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1430440/+attachment/4340207/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1430440/+attachment/4340208/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1430440/+attachment/4340209/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1430440/+attachment/4340210/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1430440/+attachment/4340211/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1430440/+attachment/4340212/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1353758

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  gvfsd-trash crashed with SIGSEGV in g_slice_alloc()

Status in gvfs package in Ubuntu:
  New

Bug description:
  random error

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gvfs-daemons 1.23.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Mar 10 14:10:40 2015
  ExecutablePath: /usr/lib/gvfs/gvfsd-trash
  InstallationDate: Installed on 2014-12-10 (90 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141209)
  ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.9 
/org/gtk/gvfs/exec_spaw/1
  ProcEnviron:
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
   LANGUAGE=pl_PL
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
  SegvAnalysis:
   Segfault happened at: 0xb739fb02 g_slice_alloc+114:mov
(%esi),%edx
   PC (0xb739fb02) ok
   source (%esi) (0x01867530) not located in a known VMA region (needed 
readable region)!
   destination %edx ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_slice_alloc0 () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gvfsd-trash crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom debian-tor dip disk libvirtd lpadmin plugdev 
sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1430440/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should return Mincho(serif) font in ja locale

2015-03-10 Thread Nobuto Murata
I don't think it causes any side effects for other locale. Because all
binding=strong are guarded by ja locale or ja specific font. But to be
safe, adding CJK testers as subscriber to notify this change beforehand.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-takao in Ubuntu.
https://bugs.launchpad.net/bugs/1430339

Title:
  fc-match Ryumin should return Mincho(serif) font in ja locale

Status in fonts-takao package in Ubuntu:
  New

Bug description:
  Ryumin and Gothic-BBB are generic font names for serif/sans-serif like
  Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer
  substitute for Ryumin, however `fc-match Ryumin` does not return
  fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif)
  instead.

  Expected result:
  $ fc-match Ryumin
  fonts-japanese-mincho.ttf: TakaoPMincho Regular

  Actual result:
  $ fc-match Ryumin
  fonts-japanese-gothic.ttf: Takao Pゴシック Regular

  
  [1]
  /etc/fonts/conf.d/65-fonts-takao-mincho.conf
   21 match target=pattern
   22 test qual=any name=family
   23 stringRyumin/string
   24 /test
   25 edit name=family mode=prepend
   26 stringTakao P明朝/string
   27 /edit
   28 /match

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fonts-takao-mincho 003.02.01-9ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 22:41:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-28 (9 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228)
  PackageArchitecture: all
  SourcePackage: fonts-takao
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430459] [NEW] Mouse not working

2015-03-10 Thread Kyle Pierce
Public bug reported:

USB mouse worked fine upon installation.  Has since stopped working.
Unplug and plug in does not fix.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Mar 10 12:39:25 2015
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.16.0-31-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:022f]
   Subsystem: Dell Device [1028:022f]
InstallationDate: Installed on 2015-03-10 (0 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
MachineType: Dell Inc. Inspiron 1525
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=60e2d5d1-f3aa-4e89-b9bf-0cf49e479a33 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Tue Mar 10 12:00:35 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 769 
 vendor LPL
xserver.version: 2:1.16.0-1ubuntu1.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic

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

Title:
  Mouse not working

Status in xorg package in Ubuntu:
  New

Bug description:
  USB mouse worked fine upon installation.  Has since stopped working.
  Unplug and plug in does not fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Mar 10 12:39:25 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.16.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:022f]
 Subsystem: Dell Device [1028:022f]
  InstallationDate: Installed on 2015-03-10 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: Dell Inc. Inspiron 1525
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=60e2d5d1-f3aa-4e89-b9bf-0cf49e479a33 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0U990C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Desktop-packages] [Bug 953342] Re: [ffe] Add support for Qt Designer UI files

2015-03-10 Thread Sebastien Bacher
the new upstream release

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

Title:
  [ffe] Add support for Qt Designer UI files

Status in Internationalization Tool Collection:
  Fix Released
Status in intltool package in Ubuntu:
  New

Bug description:
  Qt Designer files are XML files that describe the UI of a Qt
  application, and are the Glade .ui file equivalent in the Qt world.

  Their format definition can be found here:

  - http://qt-project.org/doc/designer-ui-file-format.html

  While many Qt projects use Qt's own i18n/l10n framework, others rely
  on gettext. Some examples are core Ubuntu applications such as the
  Ubuntu One client and Checkbox, which have started to migrate to Qt-
  based user interfaces while overriding Qt's i18n system and using
  gettext instead.

  These cases need a way to extract translatable messages from Qt's .ui
  files, merge the translations in .pot files and thus integrate with
  the gettext workflow.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430280] Re: NetworkManager-wait-online.service not enabled after package installation

2015-03-10 Thread Marc Deslauriers
I confirm the instructions in comment #6 have solved my issue with nfs
mounts at boot.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1430280

Title:
  NetworkManager-wait-online.service not enabled after package
  installation

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After installing NetworkManager in a fresh vivid VM, NetworkManager-
  wait-online.service is disabled. We should consider enabling it on
  systems which don't have any static interfaces in
  /etc/network/interfaces, so that units that need network-online.target
  work properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1430280/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 953342] Re: [ffe] Add support for Qt Designer UI files

2015-03-10 Thread Sebastien Bacher
the corresponding changes/requested upload is
https://code.launchpad.net/~dobey/ubuntu/vivid/intltool/release-0-51-0/+merge/252235

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

Title:
  [ffe] Add support for Qt Designer UI files

Status in Internationalization Tool Collection:
  Fix Released
Status in intltool package in Ubuntu:
  New

Bug description:
  Qt Designer files are XML files that describe the UI of a Qt
  application, and are the Glade .ui file equivalent in the Qt world.

  Their format definition can be found here:

  - http://qt-project.org/doc/designer-ui-file-format.html

  While many Qt projects use Qt's own i18n/l10n framework, others rely
  on gettext. Some examples are core Ubuntu applications such as the
  Ubuntu One client and Checkbox, which have started to migrate to Qt-
  based user interfaces while overriding Qt's i18n system and using
  gettext instead.

  These cases need a way to extract translatable messages from Qt's .ui
  files, merge the translations in .pot files and thus integrate with
  the gettext workflow.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should return Mincho(serif) font in ja locale

2015-03-10 Thread Nobuto Murata
** Changed in: fonts-takao (Ubuntu)
 Assignee: (unassigned) = Nobuto Murata (nobuto)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-takao in Ubuntu.
https://bugs.launchpad.net/bugs/1430339

Title:
  fc-match Ryumin should return Mincho(serif) font in ja locale

Status in fonts-takao package in Ubuntu:
  New

Bug description:
  Ryumin and Gothic-BBB are generic font names for serif/sans-serif like
  Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer
  substitute for Ryumin, however `fc-match Ryumin` does not return
  fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif)
  instead.

  Expected result:
  $ fc-match Ryumin
  fonts-japanese-mincho.ttf: TakaoPMincho Regular

  Actual result:
  $ fc-match Ryumin
  fonts-japanese-gothic.ttf: Takao Pゴシック Regular

  
  [1]
  /etc/fonts/conf.d/65-fonts-takao-mincho.conf
   21 match target=pattern
   22 test qual=any name=family
   23 stringRyumin/string
   24 /test
   25 edit name=family mode=prepend
   26 stringTakao P明朝/string
   27 /edit
   28 /match

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fonts-takao-mincho 003.02.01-9ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 22:41:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-28 (9 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228)
  PackageArchitecture: all
  SourcePackage: fonts-takao
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 608537] Re: Rhythmbox not support cue sheet for lossless audio disk image (external and embedded) and cue sheet for tracks

2015-03-10 Thread Bug Watch Updater
** Changed in: rhythmbox
   Status: New = Confirmed

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

Title:
  Rhythmbox not support cue sheet for lossless audio disk image
  (external and embedded) and cue sheet for tracks

Status in The GStreamer Multimedia Framework:
  Confirmed
Status in The Rhythmbox Music Management Application:
  Confirmed
Status in rhythmbox package in Ubuntu:
  Triaged
Status in rhythmbox package in Debian:
  Confirmed

Bug description:
  Rhythmbox not support cue sheet for lossless audio disk image
  (external and embedded) and cue sheet for tracks.

  It's a bit strange. There is a lot  of peoples, who need support of
  cue sheet. There is a few open source players for Linux with proper
  cue sheet support (Audacious, DeaDBeeF, qmmp) - Rhythmbox and
  GStreamer developers can use code from this player for implement cue
  sheet support in Rhythmbox. Users ask Rhythmbox developers about that
  last five years (looks like the first time it happened here:
  http://www.mail-archive.com/rhythmbox-devel@gnome.org/msg02395.html ),
  but support of cue sheet still not implement in Rhythmbox. Even Amarok
  have basic cue sheet support since version 2.3. So, maybe it's a time
  for cooperate Rhythmbox and GStreamer developers and add cue sheet
  support to  Rhythmbox?

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works

2015-03-10 Thread Jeroen T. Vermeulen
Okay, I got out of that situation with the help of the flashrom people.
My BIOS is now updated.

It helped a bit in that I can now define and add my resolution again
using xrandr.  It won't stay added though: I need to define and add it
every time I boot.  Otherwise, the resolution is not in the Displays
settings dropdown.

The dmidecode output is:

F7
08/12/2014

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

Title:
  Screen resolution no longer works

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that resolution as the highest
  possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.

  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to
  work with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  1 09:52:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16510
   vendor DEL
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


  1   2   3   >