[Desktop-packages] [Bug 1901609] Re: signond causes qprocess crash

2020-12-04 Thread Sandro
Sorry read the message only partially on my phone at the time.   Here is
the requisite info:

Tested on Ubuntu 20.04 (KDE Neon, the only way this bug manifests
currently, as it only affects systems running Qt >= 5.19.0)

Updated the package and it successfully fixes the bug, using package in
proposed channel: 8.59+17.10.20170606-0ubuntu2.20.04.1

Opening SystemSettings/Online Accounts and adding a new Google account
now works:  A window appears with a web view asking user to submit
authentication credentials.  I added two accounts, and all worked fine.
Removing and re-adding an account also worked.  Closing the window
without completing workflow and trying again also works.  I couldn't
think of any other reasonable scenario.

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Fix Committed
Status in signon source package in Groovy:
  Fix Committed
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1901609] Re: signond causes qprocess crash

2020-12-04 Thread Sandro
I can confirm that the updated packages work for me.  After adding them
to my system using -proposed as suggested, I am now able to get the
window to open asking for my google credentials when selecting to add a
new Google account.

As far as I'm concerned this fixes it for me.  Thanks to all for taking
the time to fix this :)

Please note, in case people come back here and start conflating issues
again - the scope of this fix is *only* to get the web view window where
you can enter your Google credentials.  It is well known that there were
other issues that may come along *after* that, but they are not related
to this bug at all.  As long as you get the window where you can enter
your email address, this bug is fixed.

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Fix Committed
Status in signon source package in Groovy:
  Fix Committed
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1901609] [NEW] signond causes qprocess crash

2020-10-26 Thread Sandro
Public bug reported:

I'm reporting this bug upstream from where I found it, since I've
learned that the signond package in KDE Neon is sourced from Ubuntu
focal.

This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
from Focal Fossa

Steps to reproduce:

1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
2. Install the kaccounts integration and kio-gdrive packages.
3. Open System settings and navigate to "Online Accounts"
4. Press "+ Add New Account"
5. Select "Google"

Observed behaviour:

- Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
- system logs show a segfault in libqt5core.so which can be traced to a failure 
in qporcess, casued by signond (see links for further details)

Expected behaviour: 
- New window opens with a webview where Google authentication credentials can 
be posted.
- When qprocess runs it does not crash.


Further reference information at the following links:

1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
sso/signond/-/merge_requests/27

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

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  New

Bug description:
  I'm reporting this bug upstream from where I found it, since I've
  learned that the signond package in KDE Neon is sourced from Ubuntu
  focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour: 
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  
  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1888317] [NEW] on screen keyboad pops up nor requested

2020-07-20 Thread sandro dentella
Public bug reported:

Every now and then the on-screen keyboard pops up not intentionally
required and no evident way to clear it is available.

The only way I can clear it is via "universal access" adding (it is
normally not set) and then disabling it.

I noticed an issue that was closed and invited those who experiment this
problem to re-open an issue... here I am.

It only happens when working on my touch notepad (laptop keyboard).
Never happens if I use external keyboard.

sandro

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.3-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 20 23:04:49 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-02-15 (156 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan third-party-packages

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

Title:
  on screen keyboad pops up nor requested

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Every now and then the on-screen keyboard pops up not intentionally
  required and no evident way to clear it is available.

  The only way I can clear it is via "universal access" adding (it is
  normally not set) and then disabling it.

  I noticed an issue that was closed and invited those who experiment
  this problem to re-open an issue... here I am.

  It only happens when working on my touch notepad (laptop keyboard).
  Never happens if I use external keyboard.

  sandro

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.3-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 23:04:49 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-15 (156 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888317/+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 1832268] [NEW] Low performance when I play a game

2019-06-10 Thread Sandro
Public bug reported:

Low performance when I play a game, i have a 18 fps frame rate, but when
I press "Esc" the frame rate come back to usual performance!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 10 17:30:56 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.116, 4.15.0-51-generic, x86_64: installed
 nvidia, 390.116, 4.18.0-20-generic, x86_64: installed
 nvidia, 390.116, 4.18.0-21-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP107 [GeForce GTX 1050] 
[1462:8c97]
InstallationDate: Installed on 2019-05-14 (27 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=ffe2dbb1-cd8c-415e-91c3-d382f32bb40e ro locale=pt_BR quiet splash 
vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0502
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M PLUS/USB3
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.:bvr0502:bd11/18/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MPLUS/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
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 bionic performance 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/1832268

Title:
  Low performance when I play a game

Status in xorg package in Ubuntu:
  New

Bug description:
  Low performance when I play a game, i have a 18 fps frame rate, but
  when I press "Esc" the frame rate come back to usual performance!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 10 17:30:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.15.0-51-generic, x86_64: installed
   nvidia, 390.116, 4.18.0-20-generic, x86_64: installed
   nvidia, 390.116, 4.18.0-21-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP107 [GeForce GTX 
1050] [1462:8c97]
  InstallationDate: 

[Desktop-packages] [Bug 1735991] Re: QL-570 printer : the led flashes red and nothing happens

2018-08-10 Thread Sandro
I resolved the issue by setting proper Page Size (62 x 38 mm) in CUPS
and glabels. My QL-570 is now working with the latest driver version
1.4.2-3+b1 from Ubuntu. I attached the glabels template for reference.
It is also possible to print smaller labels (same width, different
height) without adjusting the printer settings. Perfect!

~napk

** Attachment added: "Brother_DK44205_62x38.template"
   
https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+attachment/5173684/+files/Brother_DK44205_62x38.template

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

Title:
  QL-570 printer : the led flashes red and nothing happens

Status in ptouch-driver package in Ubuntu:
  Confirmed

Bug description:

  The label printer Brother QL-570 refuses to print ...

  When I ask the printer to print, the led flashes red and nothing
  happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: printer-driver-ptouch 1.4.2-2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 13:46:56 2017
  InstallationDate: Installed on 2017-12-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ptouch-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+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 1735991] Re: QL-570 printer : the led flashes red and nothing happens

2018-02-06 Thread Sandro
Not sure what happened to the attachment. Gonna try again.

** Attachment added: "Error: Unable to send data to printer."
   
https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+attachment/5049943/+files/error.log

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

Title:
  QL-570 printer : the led flashes red and nothing happens

Status in ptouch-driver package in Ubuntu:
  Confirmed

Bug description:

  The label printer Brother QL-570 refuses to print ...

  When I ask the printer to print, the led flashes red and nothing
  happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: printer-driver-ptouch 1.4.2-2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 13:46:56 2017
  InstallationDate: Installed on 2017-12-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ptouch-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+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 1735991] Re: QL-570 printer : the led flashes red and nothing happens

2018-02-06 Thread Sandro
I attached the log file for a failed print job from
/var/log/cups/error.log. I am not entirely sure I was using driver
version 1.4.2-2 at the time. Maybe this helps though.

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

Title:
  QL-570 printer : the led flashes red and nothing happens

Status in ptouch-driver package in Ubuntu:
  Confirmed

Bug description:

  The label printer Brother QL-570 refuses to print ...

  When I ask the printer to print, the led flashes red and nothing
  happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: printer-driver-ptouch 1.4.2-2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 13:46:56 2017
  InstallationDate: Installed on 2017-12-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ptouch-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+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 1735991] Re: QL-570 printer : the led flashes red and nothing happens

2018-02-06 Thread Sandro
To clear things up, I was referring to Page Size in CUPS when saying
Media Size.

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

Title:
  QL-570 printer : the led flashes red and nothing happens

Status in ptouch-driver package in Ubuntu:
  Confirmed

Bug description:

  The label printer Brother QL-570 refuses to print ...

  When I ask the printer to print, the led flashes red and nothing
  happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: printer-driver-ptouch 1.4.2-2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 13:46:56 2017
  InstallationDate: Installed on 2017-12-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ptouch-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+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 1735991] Re: QL-570 printer : the led flashes red and nothing happens

2018-02-06 Thread Sandro
I have the exact same problem with my Brother QL-570 label printer.

I am running Raspbian Jessie and manually installed the binary driver
package from the Stretch (v1.4.2-2) repository. This was an attempt to
fix a problem with the cutter that was introduced after upgrading from
Wheezy (v1.3-4) to Jessie (v1.3-8). However with version 1.4.2-2 my
printer stopped working altogether and the red light comes up when
attempting to print labels, in my case 62 mm wide continuous roll tape.

I have set up Custom Media Size as 59 x 32 mm (yielding 62 x 38 mm paper
size effectively) in CUPS to account for the hardware margins (1.5 x 3
mm). This was working fine in Wheezy when printing custom labels
generated with glabels having the same dimensions as the printer media
size (59 x 32 mm). I have seen that provided label templates follow the
same approach (at least in earlier versions of glabels).

As already pointed out in the discussion the reported problem is
potentially related to the media size. I have noticed the latest PPD has
updated the HWMargins option which may conflict with the Custom Media
Size I am using.

Can you tell me what setting to use for Custom Media Size in CUPS and
the correct dimensions for labels created with glabels. I am aiming at
62 x 38 mm. I can report back if this fixes the problem with the
blinking red light. Meanwhile I downgraded to v1.3-4, but I want to see
the problem resolved properly. I also managed to compile the drivers
from source, so I can try out driver patches if necessary.

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

Title:
  QL-570 printer : the led flashes red and nothing happens

Status in ptouch-driver package in Ubuntu:
  Confirmed

Bug description:

  The label printer Brother QL-570 refuses to print ...

  When I ask the printer to print, the led flashes red and nothing
  happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: printer-driver-ptouch 1.4.2-2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 13:46:56 2017
  InstallationDate: Installed on 2017-12-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ptouch-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+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 1643089] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-11-18 Thread Sandro Marrone
Public bug reported:

cashed after update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CupsErrorLog:
 
Date: Sat Nov 19 00:36:37 2016
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2015-11-14 (370 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Lpstat:
 device for Deskjet_F4500: hp:/usb/Deskjet_F4500_series?serial=CN036C24P905H5
 device for HP-Deskjet-F4500-series: 
hp:/usb/Deskjet_F4500_series?serial=CN036C24P905H5
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Papersize: a4
PpdFiles:
 Deskjet_F4500: HP Deskjet f4500 Series, hpcups 3.16.9
 HP-Deskjet-F4500-series: HP Deskjet f4500 Series, hpcups 3.16.3
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=567c4e11-56e8-44e9-9201-d37bab3d6e7e ro vesafb.invalid=1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=567c4e11-56e8-44e9-9201-d37bab3d6e7e ro vesafb.invalid=1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-07-31 (110 days ago)
dmi.bios.date: 11/17/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080014
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: PI-AM3RS760G
dmi.board.vendor: Sapphire Tech
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.:bvr080014:bd11/17/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnSapphireTech:rnPI-AM3RS760G:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
modified.conffile..etc.default.cups:
 # Cups configure options
 
 # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
 # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
 # LOAD_LP_MODULE=yes
mtime.conffile..etc.default.cups: 2015-08-05T07:20:06

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


** Tags: amd64 apport-package need-duplicate-check xenial

-- 
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/1643089

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  cashed after update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Nov 19 00:36:37 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-11-14 (370 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lpstat:
   device for Deskjet_F4500: hp:/usb/Deskjet_F4500_series?serial=CN036C24P905H5
   device for HP-Deskjet-F4500-series: 
hp:/usb/Deskjet_F4500_series?serial=CN036C24P905H5
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles:
   Deskjet_F4500: HP Deskjet f4500 Series, hpcups 3.16.9
   HP-Deskjet-F4500-series: HP Deskjet f4500 Series, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=567c4e11-56e8-44e9-9201-d37bab3d6e7e ro vesafb.invalid=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=567c4e11-56e8-44e9-9201-d37bab3d6e7e ro vesafb.invalid=1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (110 days ago)
  dmi.bios.date: 11/17/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080014
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: PI-AM3RS760G
  dmi.board.vendor: Sapphire Tech
  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.:bvr080014:bd11/17/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnSapphireTech:rnPI-AM3RS760G:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  

[Desktop-packages] [Bug 1513251] Re: Sync preferences not visible in device properties window

2015-11-15 Thread Sandro
** Tags added: verification-done

-- 
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/1513251

Title:
  Sync preferences not visible in device properties window

Status in Rhythmbox:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released
Status in rhythmbox source package in Wily:
  Fix Committed

Bug description:
  * Impact
  the Sync Preferences list tree box appears empty

  * Test Case
  - open rhythmbox
  - connect a device (phone, player, etc)
  - select it in the sidebar
  - click on the "properties" tab at the top of the screen
  - open the sync tab

  * Regression potential
  - check the layout of the sync dialog

  -

  After upgrading to wily the Sync Preferences list tree box appears
  empty. Resizing the window does not help. The same problem occurs when
  booting Ubuntu GNOME 15.10 from a live CD. The device I want to sync
  music to is an Ipod shuffle model xC323. I also tried resetting it to
  factory to no avail.

  I was expecting to see a list tree with my Music library on top and
  all my playlists as child nodes.

  The problem could in fact be a GTK problem, but I've only seen it in
  Rhythmbox so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: rhythmbox 3.2.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov  4 23:03:31 2015
  EcryptfsInUse: Yes
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to wily on 2015-10-27 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/1513251/+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 1513251] Re: Sync preferences not visible in device properties window

2015-11-15 Thread Sandro
Thanks,  I can confirm that the issue is fixed with rhythmbox
3.2.1-1ubuntu3.1.

-- 
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/1513251

Title:
  Sync preferences not visible in device properties window

Status in Rhythmbox:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released
Status in rhythmbox source package in Wily:
  Fix Committed

Bug description:
  * Impact
  the Sync Preferences list tree box appears empty

  * Test Case
  - open rhythmbox
  - connect a device (phone, player, etc)
  - select it in the sidebar
  - click on the "properties" tab at the top of the screen
  - open the sync tab

  * Regression potential
  - check the layout of the sync dialog

  -

  After upgrading to wily the Sync Preferences list tree box appears
  empty. Resizing the window does not help. The same problem occurs when
  booting Ubuntu GNOME 15.10 from a live CD. The device I want to sync
  music to is an Ipod shuffle model xC323. I also tried resetting it to
  factory to no avail.

  I was expecting to see a list tree with my Music library on top and
  all my playlists as child nodes.

  The problem could in fact be a GTK problem, but I've only seen it in
  Rhythmbox so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: rhythmbox 3.2.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov  4 23:03:31 2015
  EcryptfsInUse: Yes
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to wily on 2015-10-27 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/1513251/+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 1513251] [NEW] Sync preferences not visible in device properties window

2015-11-04 Thread Sandro
Public bug reported:

After upgrading to wily the Sync Preferences list tree box appears
empty. Resizing the window does not help. The same problem occurs when
booting Ubuntu GNOME 15.10 from a live CD. The device I want to sync
music to is an Ipod shuffle model xC323. I also tried resetting it to
factory to no avail.

I was expecting to see a list tree with my Music library on top and all
my playlists as child nodes.

The problem could in fact be a GTK problem, but I've only seen it in
Rhythmbox so far.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: rhythmbox 3.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Nov  4 23:03:31 2015
EcryptfsInUse: Yes
SourcePackage: rhythmbox
UpgradeStatus: Upgraded to wily on 2015-10-27 (8 days ago)

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


** Tags: amd64 apport-bug wily

** Attachment added: "Screenshot from 2015-11-04 23-12-37.png"
   
https://bugs.launchpad.net/bugs/1513251/+attachment/4513096/+files/Screenshot%20from%202015-11-04%2023-12-37.png

-- 
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/1513251

Title:
  Sync preferences not visible in device properties window

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  After upgrading to wily the Sync Preferences list tree box appears
  empty. Resizing the window does not help. The same problem occurs when
  booting Ubuntu GNOME 15.10 from a live CD. The device I want to sync
  music to is an Ipod shuffle model xC323. I also tried resetting it to
  factory to no avail.

  I was expecting to see a list tree with my Music library on top and
  all my playlists as child nodes.

  The problem could in fact be a GTK problem, but I've only seen it in
  Rhythmbox so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: rhythmbox 3.2.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov  4 23:03:31 2015
  EcryptfsInUse: Yes
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to wily on 2015-10-27 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1513251/+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 926917] Re: Mouse wheel tilt not works

2015-03-04 Thread Sandro
I can confirm that on Kubuntu 15.04 beta, this is still an issue, where
the system does not recognize left/right scroll action using mouse
wheel.

It's exactly the same problem as previously.

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

Title:
  Mouse wheel tilt not works

Status in xserver-xorg-input-evdev package in Ubuntu:
  Expired

Bug description:
  Ubuntu 12.04After updating the xserver-xorg-input-evdev package from 
2.6.0-1ubuntu13 to 2.6.99.901-1ubuntu3
  the Microsoft Wireless Laser Mouse 8000 wheel tilt works like scrolling and 
the xev utility  reports that buttons 4 and 5 clicked when I try to tilt the 
wheel left and right (should report 6 and 7 buttons for the tilt, 4 and 5 for 
wheel scroll). 
  It worked right before the update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/926917/+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 1410855] [NEW] nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build (objdump: '/var/lib/dkms/nvidia-331/331.113/build/.tmp_nv.o': No such file)

2015-01-14 Thread Sandro
*** This bug is a duplicate of bug 1268257 ***
https://bugs.launchpad.net/bugs/1268257

Public bug reported:

Very similar to #1268257 but different kernel version.  Sorry, I don't
know if I should report it as part of that bug or not.

DKMSKernelVersion: 3.13.0-44-generic
Date: Wed Jan 14 09:02:02 2015
Package: nvidia-331-uvm
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 (objdump: '/var/lib/dkms/nvidia-331/331.113/build/.tmp_nv.o': No such 
file)

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
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
DKMSKernelVersion: 3.13.0-44-generic
Date: Wed Jan 14 09:02:02 2015
InstallationDate: Installed on 2014-12-12 (33 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
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)

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

-- 
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/1410855

Title:
  nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module
  failed to build (objdump:
  '/var/lib/dkms/nvidia-331/331.113/build/.tmp_nv.o': No such file)

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

Bug description:
  Very similar to #1268257 but different kernel version.  Sorry, I don't
  know if I should report it as part of that bug or not.

  DKMSKernelVersion: 3.13.0-44-generic
  Date: Wed Jan 14 09:02:02 2015
  Package: nvidia-331-uvm
  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 (objdump: '/var/lib/dkms/nvidia-331/331.113/build/.tmp_nv.o': 
No such file)

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-44-generic
  Date: Wed Jan 14 09:02:02 2015
  InstallationDate: Installed on 2014-12-12 (33 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  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/1410855/+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

2014-12-04 Thread Sandro Mani
Shouldn't the result of getXMLstring be passed to entity_decode first?
Something along the attached patch. Perhaps I'm not doing this as was
planned (basically I'm running a regex-replace on the generate ui_XXX.h
files to replace QApplication::translate calls with gettext ones, see
[1]), but without entity_decode, the msgids of strings containing html
markup does not match what is actually in the ui_XXX.h files, plus
having all html-escaped characters in the po files is somewhat unplesant
for translators.

[1]
https://github.com/manisandro/gImageReader/blob/master/cmake/gettextizeui.cmake

** Patch added: intltool_designer_decode.patch
   
https://bugs.launchpad.net/intltool/+bug/953342/+attachment/4274236/+files/intltool_designer_decode.patch

-- 
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:
  Add support for Qt Designer UI files

Status in Internationalization Tool Collection:
  Fix Committed
Status in intltool package in Ubuntu:
  Triaged

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 1362026] [NEW] toggle-shaded not working as it should

2014-08-27 Thread sandro
Public bug reported:

Dear admins, please feel free to move this report to the appropriate
place in case. I was waiting for someone who knows how to file a bug
report to do it, but after half a year I give up waiting.

Problem is that when you toggle-shaded, defaulting to 'Ctrl-Alt-s' in
dconf (org.gnome.desktop.wm.keybindings) or to double-click top-bar on a
window the window just disappears instead of showing you only the top
bar. Additionally it is impossible for me to get the disappeared window
back, for example via alt-tab.

Remark: toggle-shaded behaves like this only since I upgraded to trusty
(14.04).

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

-- 
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/1362026

Title:
  toggle-shaded not working as it should

Status in “unity” package in Ubuntu:
  New

Bug description:
  Dear admins, please feel free to move this report to the appropriate
  place in case. I was waiting for someone who knows how to file a bug
  report to do it, but after half a year I give up waiting.

  Problem is that when you toggle-shaded, defaulting to 'Ctrl-Alt-s' in
  dconf (org.gnome.desktop.wm.keybindings) or to double-click top-bar on
  a window the window just disappears instead of showing you only the
  top bar. Additionally it is impossible for me to get the disappeared
  window back, for example via alt-tab.

  Remark: toggle-shaded behaves like this only since I upgraded to
  trusty (14.04).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1362026/+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 1171342] Re: mouse scroll wheel not working in gedit System Monitor

2014-03-21 Thread Sandro Rettinger
I see the same issue after upgrading (yes, just recently, I'm a slacker)
to 13.10 from 13.04, on evince and nautilus.  I too am running XFCE.
(Specifically 4.10)

Hovering over those applications and using the scroll wheel still raises
them, just as if I'd clicked on them, but does not scroll them.

click scrolling (as described above by Willy) does cause the
applications in question to scroll.  The click functionality of my
scrollwheel is normal unix middle button behaviour.

I will try the PPA listed above and report back.

-- 
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/1171342

Title:
  mouse scroll wheel not working in gedit  System Monitor

Status in GTK+ GUI Toolkit:
  Fix Released
Status in X.Org X server:
  Confirmed
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “xorg-server” package in Ubuntu:
  Triaged

Bug description:
  Open System Monitor

  Using mouse wheel button - scroll up or down - list does not move. If
  Press the wheel button and then scroll up or down the list will move.

  This also occurs in Gedit. Firefox and Terminal work as expected. IE
  do not need to press the wheel and then scroll

  Linux kylea-hpxt 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux
  Description:  Ubuntu 13.04
  Release:  13.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1171342/+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 1157649] Re: GPU hang

2013-03-22 Thread Sandro
I'm not an expert, I only like Ubuntu Philosofy, but is really hard
for me to manage the problem that Bruno Girin explains (better then
me). Everithing started after the update of 20th March.

2013/3/22, Bruno Girin brunogi...@gmail.com:
 Chris, is there a possibility to backport the fix to Quantal? It really
 makes the computer difficult to use as it hangs every few minutes, in
 particular when scrolling. This has been happening to me since the
 kernel update on Wednesday 20th March (when this bug was first
 reported).

 What info is required to diagnose the problem? I'm happy to do as much
 investigation and digging as necessary to find the root cause.

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

 Title:
   GPU hang

 Status in “xserver-xorg-video-intel” package in Ubuntu:
   Incomplete

 Bug description:
   GPU hang

   ProblemType: Bug
   DistroRelease: Ubuntu 12.10
   Package: xorg 1:7.7+1ubuntu4
   ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
   Uname: Linux 3.5.0-26-generic x86_64
   .tmp.unity.support.test.0:

   ApportVersion: 2.6.1-0ubuntu10
   Architecture: amd64
   CompizPlugins: No value set for
 `/apps/compiz-1/general/screen0/options/active_plugins'
   CompositorRunning: compiz
   Date: Wed Mar 20 11:42:11 2013
   DistUpgraded: Fresh install
   DistroCodename: quantal
   DistroVariant: ubuntu
   ExtraDebuggingInterest: Yes, if not too technical
   GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated
 Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
  Subsystem: Toshiba America Info Systems Device [1179:fb30]
   InstallationDate: Installed on 2013-02-01 (46 days ago)
   InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64
 (20121017.5)
   MachineType: TOSHIBA SATELLITE PRO C850-1CU
   MarkForUpload: True
   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic
 root=UUID=c4b7d602-2fba-44b2-bb49-e583fb9b991d ro plymouth:debug=1=1=1=1=1
 plymouth:debug drm.debug=0xe =1=1=1=1=1=1=1
   SourcePackage: xorg
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 06/27/2012
   dmi.bios.vendor: Insyde Corp.
   dmi.bios.version: 1.60
   dmi.board.asset.tag: Type2 - Board Asset Tag
   dmi.board.name: Type2 - Board Product Name1
   dmi.board.vendor: Type2 - Board Vendor Name1
   dmi.board.version: Type2 - Board Version
   dmi.chassis.asset.tag: No Asset Tag
   dmi.chassis.type: 10
   dmi.chassis.vendor: OEM Chassis Manufacturer
   dmi.chassis.version: OEM Chassis Version
   dmi.modalias:
 dmi:bvnInsydeCorp.:bvr1.60:bd06/27/2012:svnTOSHIBA:pnSATELLITEPROC850-1CU:pvrPSKCBE-003003IT:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
   dmi.product.name: SATELLITE PRO C850-1CU
   dmi.product.version: PSKCBE-003003IT
   dmi.sys.vendor: TOSHIBA
   version.compiz: compiz 1:0.9.8.6-0ubuntu1
   version.ia32-libs: ia32-libs N/A
   version.libdrm2: libdrm2 2.4.39-0ubuntu1
   version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu0.1
   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
   version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu0.1
   version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1
   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
 1:2.7.3-0ubuntu2
   version.xserver-xorg-video-ati: xserver-xorg-video-ati
 1:6.99.99~git20120913.8637f772-0ubuntu1
   version.xserver-xorg-video-intel: xserver-xorg-video-intel
 2:2.20.9-0ubuntu2
   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
 1:1.0.2-0ubuntu3

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1157649/+subscriptions


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

Title:
  GPU hang

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Incomplete

Bug description:
  GPU hang

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Wed Mar 20 11:42:11 2013
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fb30]
  InstallationDate: Installed on 2013-02-01 (46 days ago)
  InstallationMedia: 

[Desktop-packages] [Bug 1157649] [NEW] GPU hang

2013-03-20 Thread Sandro
Public bug reported:

GPU hang

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
Uname: Linux 3.5.0-26-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Wed Mar 20 11:42:11 2013
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Device [1179:fb30]
InstallationDate: Installed on 2013-02-01 (46 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
MachineType: TOSHIBA SATELLITE PRO C850-1CU
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic 
root=UUID=c4b7d602-2fba-44b2-bb49-e583fb9b991d ro plymouth:debug=1=1=1=1=1 
plymouth:debug drm.debug=0xe =1=1=1=1=1=1=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.60
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.60:bd06/27/2012:svnTOSHIBA:pnSATELLITEPROC850-1CU:pvrPSKCBE-003003IT:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE PRO C850-1CU
dmi.product.version: PSKCBE-003003IT
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.8.6-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3

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


** Tags: amd64 apport-bug compiz-0.9 quantal 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/1157649

Title:
  GPU hang

Status in “xorg” package in Ubuntu:
  New

Bug description:
  GPU hang

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Wed Mar 20 11:42:11 2013
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fb30]
  InstallationDate: Installed on 2013-02-01 (46 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MachineType: TOSHIBA SATELLITE PRO C850-1CU
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic 
root=UUID=c4b7d602-2fba-44b2-bb49-e583fb9b991d ro plymouth:debug=1=1=1=1=1 
plymouth:debug drm.debug=0xe =1=1=1=1=1=1=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.60:bd06/27/2012:svnTOSHIBA:pnSATELLITEPROC850-1CU:pvrPSKCBE-003003IT:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE PRO C850-1CU
  

[Desktop-packages] [Bug 926917] Re: Mouse wheel tilt not works

2012-10-29 Thread Sandro
Finally had time to throw at this.  Worked fine on Kubuntu 12.10 except
for the pkg-config package which was required for ./configure to
complete.  MInor issue, was very obvious to discern, fix and move on.

Scott - this essentially works fine on 12.10 but rather than use
xserver-xorg-input-evdev 2.7.0, which is likely valid for 12.04, I
searched for the latest in quantal and found it to be 2.7.3.  So just
replace the 2.7.0 with 2.7.3 and you'll be fine.

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

Title:
  Mouse wheel tilt not works

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.04After updating the xserver-xorg-input-evdev package from 
2.6.0-1ubuntu13 to 2.6.99.901-1ubuntu3
  the Microsoft Wireless Laser Mouse 8000 wheel tilt works like scrolling and 
the xev utility  reports that buttons 4 and 5 clicked when I try to tilt the 
wheel left and right (should report 6 and 7 buttons for the tilt, 4 and 5 for 
wheel scroll). 
  It worked right before the update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/926917/+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 926917] Re: Mouse wheel tilt not works

2012-10-05 Thread Sandro
Hi Phil,

I appreciate the detailed instructions, Thanks.  I'll give it a run this
weekend.

/SM

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

Title:
  Mouse wheel tilt not works

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.04After updating the xserver-xorg-input-evdev package from 
2.6.0-1ubuntu13 to 2.6.99.901-1ubuntu3
  the Microsoft Wireless Laser Mouse 8000 wheel tilt works like scrolling and 
the xev utility  reports that buttons 4 and 5 clicked when I try to tilt the 
wheel left and right (should report 6 and 7 buttons for the tilt, 4 and 5 for 
wheel scroll). 
  It worked right before the update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/926917/+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 926917] Re: Mouse wheel tilt not works

2012-10-04 Thread Sandro
Phil,

Did you simply patch source / compile / drop in?  Haven't (bothered to)
compile any source since moving to Ubuntu dapper.  Not sure if there's a
ton of other dependencies that need a recompile in order for this to
work.

Thanks for any input on this!

/SM

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

Title:
  Mouse wheel tilt not works

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.04After updating the xserver-xorg-input-evdev package from 
2.6.0-1ubuntu13 to 2.6.99.901-1ubuntu3
  the Microsoft Wireless Laser Mouse 8000 wheel tilt works like scrolling and 
the xev utility  reports that buttons 4 and 5 clicked when I try to tilt the 
wheel left and right (should report 6 and 7 buttons for the tilt, 4 and 5 for 
wheel scroll). 
  It worked right before the update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/926917/+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 835202] Re: gwibber not refreshing twitter timeline

2012-05-03 Thread Sandro Tolksdorf
I'm running Arch Linux and my twitter timeline also doesn't refresh.

Output of gwibber:

(gwibber:15606): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion
`!g_slist_find (group, radio_button)' failed

(gwibber:15606): Gtk-CRITICAL **: gtk_widget_show: assertion
`GTK_IS_WIDGET (widget)' failed

(gwibber:15606): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion
`!g_slist_find (group, radio_button)' failed

(gwibber:15606): Json-CRITICAL **: json_object_has_member: assertion
`object != NULL' failed

The last line appears repeatedly.

Output of gwibber-service -do:

root MainThread  : INFO Logger initialized
Service  MainThread  : INFO Service starting
Service  MainThread  : INFO Running from the source tree
root MainThread  : ERRORCould not find any typelib for Unity
root MainThread  : ERRORCould not find any typelib for Dbusmenu
root MainThread  : ERRORCould not find any typelib for Indicate
Digg MainThread  : DEBUGInitializing.
Ping.FM  MainThread  : DEBUGInitializing.
FourSquare   MainThread  : DEBUGInitializing.
QaikuMainThread  : DEBUGInitializing.
Identica MainThread  : DEBUGInitializing.
Twitter  MainThread  : DEBUGInitializing.
Facebook MainThread  : DEBUGInitializing.
Buzz MainThread  : DEBUGInitializing.
FriendFeed   MainThread  : DEBUGInitializing.
StatusNetMainThread  : DEBUGInitializing.
Flickr   MainThread  : DEBUGInitializing.
Service  MainThread  : DEBUGSetting up monitors
Dispatcher   MainThread  : DEBUGNM Version is 0.9.4.0
Dispatcher   MainThread  : DEBUGNM Version is greater than 0.8.997
Storage  MainThread  : DEBUGCreating indexes
Dispatcher   MainThread  : DEBUGRefresh interval is set to 5
Dispatcher   MainThread  : DEBUG** Starting Refresh - 2012-05-03 
17:12:28.01 **
Dispatcher   MainThread  : INFO Running Jobs: 0
Dispatcher   MainThread  : INFO Running Jobs: 0
Dispatcher   Thread-1: DEBUGtwitter:receive Performing operation
Dispatcher   Thread-2: DEBUGtwitter:responses Performing operation
Dispatcher   Thread-3: DEBUGtwitter:private Performing operation
Dispatcher   Thread-4: DEBUGtwitter:lists Performing operation
Dispatcher   Thread-5: DEBUGtwitter:user_messages Performing operation
Dispatcher   Thread-6: DEBUGtwitter:user_messages Performing operation
Dispatcher   Thread-7: DEBUGtwitter:user_messages Performing operation
Dispatcher   Thread-8: DEBUGtwitter:user_messages Performing operation
Dispatcher   Thread-10   : DEBUGtwitter:user_messages Performing operation
Dispatcher   Thread-9: DEBUGtwitter:user_messages Performing operation
Dispatcher   Thread-11   : DEBUGtwitter:user_messages Performing operation
Dispatcher   Thread-12   : DEBUGtwitter:user_messages Performing operation
Dispatcher   Thread-13   : DEBUGtwitter:user_messages Performing operation
Dispatcher   Thread-14   : DEBUGtwitter:user_messages Performing operation
Dispatcher   Thread-15   : DEBUGtwitter:user_messages Performing operation
Dispatcher   Thread-16   : DEBUGtwitter:search Performing operation
Dispatcher   Thread-17   : DEBUGtwitter:search Performing operation
Dispatcher   Thread-18   : DEBUGtwitter:search Performing operation
Dispatcher   Thread-19   : DEBUGtwitter:search Performing operation
Dispatcher   Thread-20   : DEBUGtwitter:search Performing operation
Dispatcher   Thread-21   : DEBUGtwitter:search Performing operation
Dispatcher   Thread-22   : DEBUGtwitter:search Performing operation
Dispatcher   MainThread  : INFO Running Jobs: 23
Dispatcher   Thread-23   : DEBUGtwitter:search Performing operation
Dispatcher   Thread-18   : INFO Loading complete: 1 - 0
Dispatcher   Thread-18   : DEBUGtwitter:search Finished operation 
(0:00:00.625512)
Dispatcher   Thread-22   : INFO Loading complete: 2 - 0
Dispatcher   Thread-22   : DEBUGtwitter:search Finished operation 
(0:00:00.637023)
Dispatcher   Thread-23   : INFO Loading complete: 3 - 0
Dispatcher   Thread-23   : DEBUGtwitter:search Finished operation 
(0:00:00.668869)
Dispatcher   Thread-21   : INFO Loading complete: 4 - 0
Dispatcher   Thread-21   : DEBUGtwitter:search Finished operation 
(0:00:00.706391)
Dispatcher   Thread-17   : INFO Loading complete: 5 - 0
Dispatcher   Thread-17   : DEBUGtwitter:search Finished operation 
(0:00:00.737039)
Dispatcher   Thread-16   : INFO Loading complete: 6 - 0
Dispatcher   Thread-16   : DEBUGtwitter:search Finished operation 
(0:00:00.776430)
Dispatcher   Thread-20   : INFO Loading complete: 7 - 0
Dispatcher   Thread-20   : DEBUGtwitter:search Finished operation 
(0:00:00.771643)
Dispatcher   Thread-19   : DEBUGtwitter:search Adding record
Network  Thread-2: ERRORHTTP Error for 

[Desktop-packages] [Bug 284687] Re: fglrx works, but window moving/resizing and scrolling are very, very slow; desktop effects don't work

2012-03-10 Thread Sandro Salvatierra Arias
** Changed in: jockey (Ubuntu)
   Status: Triaged = Confirmed

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

Title:
  fglrx works, but window moving/resizing and scrolling are very, very
  slow; desktop effects don't work

Status in “jockey” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: xorg-driver-fglrx

  I upgraded to intrepid as soon as I saw that the issue with fglrx and
  the new xorg was resolved. The driver works, but with some pretty big
  problems. The biggest problem is that scrolling and moving/resizing
  windows is very, very slow and choppy. Also trying to enable desktop
  effects fails with this output in the terminal:

  jeremy@jeremy-laptop:~$ gnome-appearance-properties
  [here I try to enable desktop effects through the appearance menu]
  There is no available graphics driver for your system which supports the 
composite extension, or the current one already supports it.
  Checking for Xgl: not present. 
  Detected PCI ID for VGA: 
  Checking for texture_from_pixmap: not present. 
  Trying again with indirect rendering:
  Checking for texture_from_pixmap: not present. 
  aborting and using fallback: /usr/bin/metacity

  Running fglrxinfo in the terminal gives me this:

  jeremy@jeremy-laptop:~$ fglrxinfo 
  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
Major opcode of failed request:  160 (GLX)
Minor opcode of failed request:  19 (X_GLXQueryServerString)
Serial number of failed request:  10
Current serial number in output stream:  10

  In the jockey/Hardware Drivers menu, there is a green light beside the
  fglrx driver, and it says This driver is activated but not currently
  in use.

  I have tried with a stock dpkg-reconfigure -phigh xserver-xorg
  xorg.conf, then again after running aticonfig --initial, and also with
  the xorg.conf created by jockey, and experimented with different xorg
  options myself, all to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/284687/+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