[Desktop-packages] [Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen

[pqwoerituytrueiwoq]

Reason for "Won't Fix"?

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

Title:
  XFCE window buttons are not clickable at the top of the screen

Status in X.Org X server:
  New
Status in greybird-gtk-theme package in Ubuntu:
  Fix Released
Status in xfce4-panel package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in greybird-gtk-theme source package in Cosmic:
  Triaged
Status in xfce4-panel source package in Cosmic:
  Triaged
Status in xorg-server source package in Cosmic:
  Confirmed
Status in greybird-gtk-theme source package in Disco:
  Fix Released
Status in xfce4-panel source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Won't Fix

Bug description:
  This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic.

  With Cosmic, it is not possible to click on the window buttons after
  moving the mouse cursor to the top of the screen. Unlike similar bugs,
  no amount of moving left or right triggers the hover event or the
  ability to click on the window button.

  With Adwaita and Numix, we see the same issues we see elsewhere, where
  the buttons can sometimes be clicked, but also have issue with the
  topmost part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: greybird-gtk-theme 3.22.9-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 29 09:05:24 2018
  InstallationDate: Installed on 2018-09-29 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929)
  PackageArchitecture: all
  SourcePackage: greybird-gtk-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1795135/+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 1795135] Re: XFCE window buttons are not clickable at the top of the screen

[pqwoerituytrueiwoq]

Awesome!
Any idea when it will land in the ubuntu groovy repos?
Just pulled it into my 20.04 install and it seems to not be there yet
$ xfce4-panel --version
xfce4-panel 4.14.4 (Xfce 4.14)

Copyright (c) 2004-2011
The Xfce development team. All rights reserved.

Please report bugs to .

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

Title:
  XFCE window buttons are not clickable at the top of the screen

Status in X.Org X server:
  New
Status in greybird-gtk-theme package in Ubuntu:
  Fix Released
Status in xfce4-panel package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in greybird-gtk-theme source package in Cosmic:
  Triaged
Status in xfce4-panel source package in Cosmic:
  Triaged
Status in xorg-server source package in Cosmic:
  Confirmed
Status in greybird-gtk-theme source package in Disco:
  Fix Released
Status in xfce4-panel source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Won't Fix

Bug description:
  This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic.

  With Cosmic, it is not possible to click on the window buttons after
  moving the mouse cursor to the top of the screen. Unlike similar bugs,
  no amount of moving left or right triggers the hover event or the
  ability to click on the window button.

  With Adwaita and Numix, we see the same issues we see elsewhere, where
  the buttons can sometimes be clicked, but also have issue with the
  topmost part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: greybird-gtk-theme 3.22.9-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 29 09:05:24 2018
  InstallationDate: Installed on 2018-09-29 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929)
  PackageArchitecture: all
  SourcePackage: greybird-gtk-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1795135/+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 1795135] Re: XFCE window buttons are not clickable at the top of the screen

[pqwoerituytrueiwoq]

Confirmed in 20.04 with screenshot, weather applets, and notification area 
applets
whiskers menu, clock, and show desktop are unaffected

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

Title:
  XFCE window buttons are not clickable at the top of the screen

Status in X.Org X server:
  New
Status in greybird-gtk-theme package in Ubuntu:
  Fix Released
Status in xfce4-panel package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in greybird-gtk-theme source package in Cosmic:
  Triaged
Status in xfce4-panel source package in Cosmic:
  Triaged
Status in xorg-server source package in Cosmic:
  Confirmed
Status in greybird-gtk-theme source package in Disco:
  Fix Released
Status in xfce4-panel source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Confirmed

Bug description:
  This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic.

  With Cosmic, it is not possible to click on the window buttons after
  moving the mouse cursor to the top of the screen. Unlike similar bugs,
  no amount of moving left or right triggers the hover event or the
  ability to click on the window button.

  With Adwaita and Numix, we see the same issues we see elsewhere, where
  the buttons can sometimes be clicked, but also have issue with the
  topmost part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: greybird-gtk-theme 3.22.9-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 29 09:05:24 2018
  InstallationDate: Installed on 2018-09-29 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929)
  PackageArchitecture: all
  SourcePackage: greybird-gtk-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1795135/+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 1878330] [NEW] Primary hicolor icons are missing

[pqwoerituytrueiwoq]

Public bug reported:

Broken image icon appears in the title bar, notifications, and in the
about dialog

These files are missing:
/usr/share/icons/hicolor/
├── 16x16
│   └── apps
│   └── rhythmbox.png
├── 22x22
│   └── apps
│   └── rhythmbox.png
├── 24x24
│   └── apps
│   └── rhythmbox.png
├── 256x256
│   └── apps
│   └── rhythmbox.png
├── 32x32
│   └── apps
│   └── rhythmbox.png
├── 48x48
│   └── apps
│   └── rhythmbox.png
└── scalable
└── apps
└── rhythmbox-symbolic.svg

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: rhythmbox 3.4.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed May 13 00:03:50 2020
InstallationDate: Installed on 2018-04-29 (744 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "The problem"
   
https://bugs.launchpad.net/bugs/1878330/+attachment/5370730/+files/Screenshot_2020-05-11_11-44-10.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/1878330

Title:
  Primary hicolor icons are missing

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Broken image icon appears in the title bar, notifications, and in the
  about dialog

  These files are missing:
  /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
  └── apps
  └── rhythmbox-symbolic.svg

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1878330/+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 1878330] Re: Primary hicolor icons are missing

[pqwoerituytrueiwoq]

Here are the icons i pulled from my backup

This can be fixed on a existing install by doing this

sudo cp -a ./hicolor /usr/share/icons/
sudo touch /usr/share/icons/hicolor
sudo gtk-update-icon-cache

** Attachment added: "The missing files"
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1878330/+attachment/5370737/+files/Rhythmbox-hicolor_Ubuntu-18.04.zip

** Description changed:

  These files are missing:
- hicolor/
+ /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
- └── apps
- └── rhythmbox-symbolic.svg
+ └── apps
+ └── rhythmbox-symbolic.svg
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

+ Broken image icon appears in the title bar, notifications, and in the
+ about dialog
+ 
  These files are missing:
  /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
  └── apps
  └── rhythmbox-symbolic.svg
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  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 rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1878330

Title:
  Primary hicolor icons are missing

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Broken image icon appears in the title bar, notifications, and in the
  about dialog

  These files are missing:
  /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
  └── apps
  └── rhythmbox-symbolic.svg

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1878330/+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 1878330] Re: Primary hicolor icons are missing

[pqwoerituytrueiwoq]

Xubuntu XFWM4 Greybird-dark
i edited /usr/share/themes/Greybird-dark/xfwm4/themerc
added this line:
show_app_icon=true

You can see the issue in the screenshot in the top left, this affected
every theme that shows the icon for the menu

This also affects notifications (song change/hit play)

** Attachment added: "Notifications-Settings"
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1878330/+attachment/5370947/+files/Screenshot_2020-05-13_10-00-54.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/1878330

Title:
  Primary hicolor icons are missing

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Broken image icon appears in the title bar, notifications, and in the
  about dialog

  These files are missing:
  /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
  └── apps
  └── rhythmbox-symbolic.svg

  Rhythmbox Plugins: Tray Icon, ReplyGain, Notification,  MPRIS D-Bus
  interface, MediaServer2 D-Bus interface, and Hine rhythmbox on start

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1878330/+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 1878330] Re: Primary hicolor icons are missing

[pqwoerituytrueiwoq]

** Description changed:

  Broken image icon appears in the title bar, notifications, and in the
  about dialog
  
  These files are missing:
  /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
  └── apps
  └── rhythmbox-symbolic.svg
  
+ Rhythmbox addons: Tray Icon, ReplyGain, Notification,  MPRIS D-Bus
+ interface, MediaServer2 D-Bus interface, and Hine rhythmbox on start
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Broken image icon appears in the title bar, notifications, and in the
  about dialog
  
  These files are missing:
  /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
  └── apps
  └── rhythmbox-symbolic.svg
  
- Rhythmbox addons: Tray Icon, ReplyGain, Notification,  MPRIS D-Bus
+ Rhythmbox Plugins: Tray Icon, ReplyGain, Notification,  MPRIS D-Bus
  interface, MediaServer2 D-Bus interface, and Hine rhythmbox on start
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  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 rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1878330

Title:
  Primary hicolor icons are missing

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Broken image icon appears in the title bar, notifications, and in the
  about dialog

  These files are missing:
  /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
  └── apps
  └── rhythmbox-symbolic.svg

  Rhythmbox Plugins: Tray Icon, ReplyGain, Notification,  MPRIS D-Bus
  interface, MediaServer2 D-Bus interface, and Hine rhythmbox on start

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1878330/+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 1878330] Re: wrong icon used in the about dialog

[pqwoerituytrueiwoq]

I find that hard to believe when every system theme is affected and adding the 
missing icons fixes it
sorry for low frame rate in recording i wanted to keep it a small file size

** Attachment added: "Screen Capture - Live USB"
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1878330/+attachment/5373488/+files/Screencast.mp4

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

Title:
  wrong icon used in the about dialog

Status in rhythmbox package in Ubuntu:
  Fix Committed

Bug description:
  Broken image icon appears in the title bar, notifications, and in the
  about dialog

  These files are missing:
  /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
  └── apps
  └── rhythmbox-symbolic.svg

  Rhythmbox Plugins: Tray Icon, ReplyGain, Notification,  MPRIS D-Bus
  interface, MediaServer2 D-Bus interface, and Hine rhythmbox on start

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1878330/+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 1978429] [NEW] Crashes when smart info is open while the drive is pulled

[pqwoerituytrueiwoq]

Public bug reported:

1. Open smart data for a given drive (not the boot drive, *points at step 2*)
2. detach drive from system (sata drives support hot swap)
3. wait a few seconds
4. disk utility has crashed

if smart info is not open it will not crash and the drive drops out of
the drive list

the smart data window should either close or remain open and stop
updating if the drive is removed

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-disk-utility 42.0-1ubuntu1
Uname: Linux 5.17.13-051713-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Sun Jun 12 22:42:11 2022
InstallationDate: Installed on 2021-11-26 (198 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211126)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-disk-utility
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Crashes when smart info is open while the drive is pulled

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  1. Open smart data for a given drive (not the boot drive, *points at step 2*)
  2. detach drive from system (sata drives support hot swap)
  3. wait a few seconds
  4. disk utility has crashed

  if smart info is not open it will not crash and the drive drops out of
  the drive list

  the smart data window should either close or remain open and stop
  updating if the drive is removed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-disk-utility 42.0-1ubuntu1
  Uname: Linux 5.17.13-051713-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Sun Jun 12 22:42:11 2022
  InstallationDate: Installed on 2021-11-26 (198 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211126)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1978429/+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 1978429] Re: Crashes when smart info is open while the drive is pulled

[pqwoerituytrueiwoq]

https://errors.ubuntu.com/oops/e159c992-eb0c-11ec-abf9-fa163ef35206

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

Title:
  Crashes when smart info is open while the drive is pulled

Status in gnome-disk-utility package in Ubuntu:
  Incomplete

Bug description:
  1. Open smart data for a given drive (not the boot drive, *points at step 2*)
  2. detach drive from system (sata drives support hot swap)
  3. wait a few seconds
  4. disk utility has crashed

  if smart info is not open it will not crash and the drive drops out of
  the drive list

  the smart data window should either close or remain open and stop
  updating if the drive is removed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-disk-utility 42.0-1ubuntu1
  Uname: Linux 5.17.13-051713-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Sun Jun 12 22:42:11 2022
  InstallationDate: Installed on 2021-11-26 (198 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211126)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1978429/+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 473650] Re: file-roller assert failure: *** glibc detected *** file-roller: free(): invalid pointer: 0x08b2da68 ***

[pqwoerituytrueiwoq]

I was able to get this issue in xubuntu 18.04 64bit Live (April 15 daily ISO)
Apport gave me this summary: file-roller assert failure: free(): invalid pointer

I made a .zip file of a system theme Adwaita
attempted to drag/drop the containing file to the desktop
It seems to be reproducible with a rate of about 1 in 3 or 1 in 2

** Attachment added: "valgrind.log.zip"
   
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/473650/+attachment/5118638/+files/valgrind.log.zip

** Changed in: file-roller (Ubuntu)
   Status: Invalid => New

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

Title:
  file-roller assert failure: *** glibc detected *** file-roller:
  free(): invalid pointer: 0x08b2da68 ***

Status in file-roller package in Ubuntu:
  New

Bug description:
  Binary package hint: file-roller

  trying to drag and drop file from File Roller 2.28.1 to Desktop after
  tried to drag & drop to smb: folder.

  ProblemType: Crash
  Architecture: i386
  AssertionMessage: *** glibc detected *** file-roller: free(): invalid 
pointer: 0x08b2da68 ***
  Date: Wed Nov  4 02:02:11 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/file-roller
  Package: file-roller 2.28.1-0ubuntu1
  ProcCmdline: file-roller /home/username/Desktop/Scooters.zip
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  Signal: 6
  SourcePackage: file-roller
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/tls/i686/cmov/libc.so.6
   abort () from /lib/tls/i686/cmov/libc.so.6
   ?? () from /lib/tls/i686/cmov/libc.so.6
   ?? () from /lib/tls/i686/cmov/libc.so.6
  Title: file-roller assert failure: *** glibc detected *** file-roller: 
free(): invalid pointer: 0x08b2da68 ***
  Uname: Linux 2.6.31-14-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/473650/+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 473650] Re: file-roller assert failure: *** glibc detected *** file-roller: free(): invalid pointer: 0x08b2da68 ***

[pqwoerituytrueiwoq]

Zip file I was using trying to check for other bugs
Here is my apport.log file:
ERROR: apport (pid 2343) Mon Apr 16 23:07:43 2018: called for pid 2335, signal 
6, core limit 0, dump mode 1
ERROR: apport (pid 2343) Mon Apr 16 23:07:43 2018: executable: 
/usr/bin/file-roller (command line "file-roller 
/home/xubuntu/Desktop/Adwaita.zip")
ERROR: apport (pid 2343) Mon Apr 16 23:07:43 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 2343) Mon Apr 16 23:07:43 2018: debug: session gdbus call: 
ERROR: apport (pid 2343) Mon Apr 16 23:07:47 2018: wrote report 
/var/crash/_usr_bin_file-roller.999.crash
ERROR: apport (pid 3812) Mon Apr 16 23:14:53 2018: called for pid 3805, signal 
11, core limit 0, dump mode 1
ERROR: apport (pid 3812) Mon Apr 16 23:14:53 2018: executable: 
/usr/bin/file-roller (command line "file-roller 
/home/xubuntu/Desktop/Adwaita.zip")
ERROR: apport (pid 3812) Mon Apr 16 23:14:53 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 3812) Mon Apr 16 23:14:53 2018: debug: session gdbus call: 
ERROR: apport (pid 3812) Mon Apr 16 23:14:57 2018: wrote report 
/var/crash/_usr_bin_file-roller.999.crash
ERROR: apport (pid 4815) Mon Apr 16 23:18:39 2018: called for pid 3857, signal 
11, core limit 0, dump mode 1
ERROR: apport (pid 4815) Mon Apr 16 23:18:39 2018: executable: 
/usr/lib/valgrind/memcheck-amd64-linux (command line "/usr/bin/valgrind.bin -v 
--tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log 
/usr/bin/file-roller /home/xubuntu/Desktop/Adwaita.zip")
ERROR: apport (pid 4815) Mon Apr 16 23:18:39 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 4815) Mon Apr 16 23:18:39 2018: debug: session gdbus call: 
ERROR: apport (pid 4815) Mon Apr 16 23:19:26 2018: wrote report 
/var/crash/_usr_lib_valgrind_memcheck-amd64-linux.999.crash


** Attachment added: "Adwaita.zip"
   
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/473650/+attachment/5118673/+files/Adwaita.zip

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

Title:
  file-roller assert failure: *** glibc detected *** file-roller:
  free(): invalid pointer: 0x08b2da68 ***

Status in file-roller package in Ubuntu:
  New

Bug description:
  Binary package hint: file-roller

  trying to drag and drop file from File Roller 2.28.1 to Desktop after
  tried to drag & drop to smb: folder.

  ProblemType: Crash
  Architecture: i386
  AssertionMessage: *** glibc detected *** file-roller: free(): invalid 
pointer: 0x08b2da68 ***
  Date: Wed Nov  4 02:02:11 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/file-roller
  Package: file-roller 2.28.1-0ubuntu1
  ProcCmdline: file-roller /home/username/Desktop/Scooters.zip
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  Signal: 6
  SourcePackage: file-roller
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/tls/i686/cmov/libc.so.6
   abort () from /lib/tls/i686/cmov/libc.so.6
   ?? () from /lib/tls/i686/cmov/libc.so.6
   ?? () from /lib/tls/i686/cmov/libc.so.6
  Title: file-roller assert failure: *** glibc detected *** file-roller: 
free(): invalid pointer: 0x08b2da68 ***
  Uname: Linux 2.6.31-14-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/473650/+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 1173952] Re: Suspend and hibernate not working in 13.04/13.10 with alx module

[pqwoerituytrueiwoq]

@azm1 sounds like the system is using the S1 or maybe S2 state to me,
not the usual S3 state, check your bios setting for the type of suspend

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

Title:
  Suspend and hibernate not working in 13.04/13.10 with alx module

Status in “linux” package in Ubuntu:
  Confirmed
Status in “pm-utils” package in Ubuntu:
  Fix Released
Status in “linux” source package in Precise:
  Won't Fix
Status in “pm-utils” source package in Precise:
  Invalid
Status in “linux” source package in Raring:
  Won't Fix
Status in “pm-utils” source package in Raring:
  Fix Released
Status in “linux” source package in Saucy:
  Fix Released
Status in “pm-utils” source package in Saucy:
  Fix Released

Bug description:
  Description:  Ubuntu 13.04
  Release:  13.04

  After upgrading to 13.04 suspend and hibernate do not work.
  In terminal window following error is displayed: "PM: Some devices failed to 
suspend". Then the suspend fails and the screensaver gets activated, requiring 
a password to unlock.

  dmesg

  [  893.962025] PM: Syncing filesystems ... done.
  [  894.030726] Freezing user space processes ... (elapsed 0.01 seconds) done.
  [  894.047580] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) 
done.
  [  894.064140] Suspending console(s) (use no_console_suspend to debug)
  [  894.071511] sd 0:0:0:0: [sda] Synchronizing SCSI cache
  [  894.085881] alx :03:00.0: PHY SPD/DPLX unresolved :
  [  894.085884] alx :03:00.0 eth1: shutown err(ffea)
  [  894.085886] alx :03:00.0: shutdown fail in suspend -5
  [  894.085901] pci_pm_suspend(): alx_suspend+0x0/0x90 [alx] returns -5
  [  894.085906] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -5
  [  894.085908] PM: Device :03:00.0 failed to suspend async: error -5
  [  894.47] sd 0:0:0:0: [sda] Stopping disk
  [  894.684692] PM: Some devices failed to suspend
  [  894.684903] ath: phy0: ASPM enabled: 0x43
  [  894.685198] sd 0:0:0:0: [sda] Starting disk
  [  895.442853] PM: resume of devices complete after 758.396 msecs
  [  895.443224] Restarting tasks ... done.
  [  895.445509] video LNXVIDEO:00: Restoring backlight state
  ---
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  DistroRelease: Ubuntu 13.04
  InstallationDate: Installed on 2012-12-20 (166 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  Package: pm-utils 1.4.1-9git1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Tags:  raring
  Uname: Linux 3.8.0-19-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-04-28 (37 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

  SRU INFORMATION
  ---
  * Impact: suspend regression in 13.04 with Qualcomm Atheros Gigabit ethernet 
devices
  * Test case: Suspend is broken in current raring when the alx module is 
loaded, should work again with the fix; needs to be tested on actual hardware, 
see comment 56 for positive testing result that this pm-utils workaround works.
  * Regression potential: If the script is malformed, it could potentially 
break suspend on other devices; this should generate an error in 
/var/log/pm-suspend.log. Please test suspend on devices without the alx module 
as well (for the record, Martin Pitt did that on his ThinkPad X201)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173952/+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 978789] Re: file-roller crashed with SIGABRT in __libc_message()

[pqwoerituytrueiwoq]

I can also confirm what sampo555 just said

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

Title:
  file-roller crashed with SIGABRT in __libc_message()

Status in File Roller:
  Fix Released
Status in “file-roller” package in Ubuntu:
  Fix Released
Status in “file-roller” source package in Quantal:
  Fix Committed

Bug description:
  Impact:
  It's not possible to extract archives in a specific location, the code 
segfaults

  Test Case:
  - wget http://ftp.acc.umu.se/pub/GNOME/sources/gedit/3.6/gedit-3.6.2.tar.xz
  - run "file-roller --extract-to /tmp/debug gedit-3.6.2.tar.xz"
  - ls /tmp/debug

  the archive should be properly unpacked in the destination dir

  Regression potential:
  Check that archives get correct unpacked still, from nautilus and from the 
command line

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/978789/+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 1098955] [NEW] SNA on Intel B970 and hedgewars

[pqwoerituytrueiwoq]

Public bug reported:

found issue when using hedgewars with SNA enabled, i have reproduced this with 
the 3.7 and 3.6 kernels
using xubuntu, no compiz just xfwm4, i have the xubuntu 4.12 ppa enabled

nice to see pixel shaders work now :)

xorg.conf contents:
Section "Device"
   Identifier  "Intel Graphics"
   Driver  "intel"
   Option  "AccelMethod"  "sna"
EndSection

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
Uname: Linux 3.8.0-030800rc3-generic x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
Date: Sat Jan 12 14:28:18 2013
InstallationDate: Installed on 2012-09-29 (105 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
MarkForUpload: True
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug quantal

** Attachment added: "black blob appears above game when launched"
   
https://bugs.launchpad.net/bugs/1098955/+attachment/3481289/+files/Screenshot%20-%2001122013%20-%2002%3A30%3A56%20PM.png

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

Title:
  SNA on Intel B970 and hedgewars

Status in “xorg” package in Ubuntu:
  New

Bug description:
  found issue when using hedgewars with SNA enabled, i have reproduced this 
with the 3.7 and 3.6 kernels
  using xubuntu, no compiz just xfwm4, i have the xubuntu 4.12 ppa enabled

  nice to see pixel shaders work now :)

  xorg.conf contents:
  Section "Device"
 Identifier  "Intel Graphics"
 Driver  "intel"
 Option  "AccelMethod"  "sna"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  Uname: Linux 3.8.0-030800rc3-generic x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Sat Jan 12 14:28:18 2013
  InstallationDate: Installed on 2012-09-29 (105 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
  MarkForUpload: True
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1098955/+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 1064117] [NEW] Extremly poor compression for .tar.bz2

[pqwoerituytrueiwoq]

Public bug reported:

I am running Xubuntu 12.10 beta 64bit
i created a archive for a folder 
the contents are ~1.5kb the archive is over 10kb
i compressed the same files on my Ubuntu 10.04 install and the archive is 851 
bytes

archive was created from the create archive option in the right click
menu in the file browser (thunar)

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1064117/+attachment/3388129/+files/Screenshot%20-%2010082012%20-%2007%3A13%3A10%20PM.png

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

Title:
  Extremly poor compression for .tar.bz2

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  I am running Xubuntu 12.10 beta 64bit
  i created a archive for a folder 
  the contents are ~1.5kb the archive is over 10kb
  i compressed the same files on my Ubuntu 10.04 install and the archive is 851 
bytes

  archive was created from the create archive option in the right click
  menu in the file browser (thunar)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1064117/+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 1064117] Re: Extremly poor compression for .tar.bz2

[pqwoerituytrueiwoq]

launchpad only allows 1 attachemt here is the other

** Attachment added: "Archive made on ubuntu 10.04"
   
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1064117/+attachment/3388158/+files/backlightx.tar.bz2

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

Title:
  Extremly poor compression for .tar.bz2

Status in “file-roller” package in Ubuntu:
  New

Bug description:
  I am running Xubuntu 12.10 beta 64bit
  i created a archive for a folder 
  the contents are ~1.5kb the archive is over 10kb
  i compressed the same files on my Ubuntu 10.04 install and the archive is 851 
bytes

  archive was created from the create archive option in the right click
  menu in the file browser (thunar)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1064117/+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 1064117] Re: Extremly poor compression for .tar.bz2

[pqwoerituytrueiwoq]

chad@Compaq-Presario-CQ60:~$ tar cjf ./back.tar.bz2 Desktop/backlightx
chad@Compaq-Presario-CQ60:~$ ls -l back*
-rw-rw-r-- 1 chad chad 864 Oct  8 20:34 back.tar.bz2

the file is 864byetes

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

Title:
  Extremly poor compression for .tar.bz2

Status in “file-roller” package in Ubuntu:
  Incomplete

Bug description:
  I am running Xubuntu 12.10 beta 64bit
  i created a archive for a folder 
  the contents are ~1.5kb the archive is over 10kb
  i compressed the same files on my Ubuntu 10.04 install and the archive is 851 
bytes

  archive was created from the create archive option in the right click
  menu in the file browser (thunar)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1064117/+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 1064117] Re: Extremly poor compression for .tar.bz2

[pqwoerituytrueiwoq]

seems it does compress it just sets a min size (sounds really dumb for a
compression app to do)

from http://ubuntuforums.org/showthread.php?t=2065402#4 :
  here file-roller is 'compressing' but will never go below 10.2kB
  So - a folder with a number of small files
  43.6kB goes to 10.6kB
  34kB goes to 10.2kB
  15kB goes to 10.2kB
  1.5kB goes UP to 10.2kB

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

Title:
  Extremly poor compression for .tar.bz2

Status in “file-roller” package in Ubuntu:
  Confirmed

Bug description:
  I am running Xubuntu 12.10 beta 64bit
  i created a archive for a folder 
  the contents are ~1.5kb the archive is over 10kb
  i compressed the same files on my Ubuntu 10.04 install and the archive is 851 
bytes

  archive was created from the create archive option in the right click
  menu in the file browser (thunar)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1064117/+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 604635]

[pqwoerituytrueiwoq]

Release Notes on firefox 14.0.1 say there is a api for prevent the display from 
sleeping could someone please tell me what the api (i was not able to find a 
documented api)
It would be nice to be able to stop a screensaver from coming on when playing 
video

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

Title:
  Have default settings be energy star 5.0 compliant

Status in Chromium Browser:
  Unknown
Status in The Mozilla Firefox Browser:
  Fix Released
Status in Gnome Powermanager:
  Won't Fix
Status in OEM Priority Project:
  Fix Released
Status in “chromium-browser” package in Ubuntu:
  Triaged
Status in “firefox” package in Ubuntu:
  Triaged
Status in “gnome-power-manager” package in Ubuntu:
  Fix Released
Status in “rhythmbox” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-power-manager

  Energy star is a standard backed by the US government to set standards for 
energy use of devices.
  The specification for Operating System settings can be found here:
  http://www.energystar.gov/index.cfm?c=revisions.computer_spec

  Spec direct link (page 13):
  
http://www.energystar.gov/ia/partners/prod_development/revisions/downloads/computer/Version5.0_Computer_Spec.pdf

  Also to better help understand Energy Star. The Open Suse team actually 
heavily looked into this, and have a great presentation here:
  http://files.opensuse.org/opensuse/en/3/34/EnergyStar.pdf

  The reason you want to be Energy star compliant:

  - Many retailers will not sell machines that are not Energy Star compliant
  - Most Government agencies will not buy hardware solutions that are not 
Energy Star compliant
  - OEMs are now pushing heavily to have all hardware be Energy Star compliant
   - The OS software default settings are apart of the Energy Star 
compliance of machines

  There are only two default settings preventing Ubuntu from being energy star 
compliant:
  * Put display to Sleep within 15 minutes of user inactivity when on A/C
  - Currently this is set to 30 min. So setting it to 15 or below would 
fix this.
  * Activate computer's Sleep mode within 30 minutes of user inactivity when on 
A/C.
  - Currently this is set to never
  - It is also under stood that this could potentially have user 
experience impact

  If both settings cannot be done by deafult.  It has been requested to
  have an Energy Star button in Gnome Power Management interface that
  would set settings to be energy star compliant.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/604635/+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 604635]

[pqwoerituytrueiwoq]

Ok, thanks
Guess I won't be making that Greasemonkey script...

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

Title:
  Have default settings be energy star 5.0 compliant

Status in Chromium Browser:
  Unknown
Status in The Mozilla Firefox Browser:
  Fix Released
Status in Gnome Powermanager:
  Won't Fix
Status in OEM Priority Project:
  Fix Released
Status in “chromium-browser” package in Ubuntu:
  Triaged
Status in “firefox” package in Ubuntu:
  Triaged
Status in “gnome-power-manager” package in Ubuntu:
  Fix Released
Status in “rhythmbox” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-power-manager

  Energy star is a standard backed by the US government to set standards for 
energy use of devices.
  The specification for Operating System settings can be found here:
  http://www.energystar.gov/index.cfm?c=revisions.computer_spec

  Spec direct link (page 13):
  
http://www.energystar.gov/ia/partners/prod_development/revisions/downloads/computer/Version5.0_Computer_Spec.pdf

  Also to better help understand Energy Star. The Open Suse team actually 
heavily looked into this, and have a great presentation here:
  http://files.opensuse.org/opensuse/en/3/34/EnergyStar.pdf

  The reason you want to be Energy star compliant:

  - Many retailers will not sell machines that are not Energy Star compliant
  - Most Government agencies will not buy hardware solutions that are not 
Energy Star compliant
  - OEMs are now pushing heavily to have all hardware be Energy Star compliant
   - The OS software default settings are apart of the Energy Star 
compliance of machines

  There are only two default settings preventing Ubuntu from being energy star 
compliant:
  * Put display to Sleep within 15 minutes of user inactivity when on A/C
  - Currently this is set to 30 min. So setting it to 15 or below would 
fix this.
  * Activate computer's Sleep mode within 30 minutes of user inactivity when on 
A/C.
  - Currently this is set to never
  - It is also under stood that this could potentially have user 
experience impact

  If both settings cannot be done by deafult.  It has been requested to
  have an Energy Star button in Gnome Power Management interface that
  would set settings to be energy star compliant.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/604635/+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 1064117] Re: Extremly poor compression for .tar.bz2

[pqwoerituytrueiwoq]

workaround:
downgrade file-roller 
http://packages.ubuntu.com/precise/file-roller#pdownload
then lock the package with this command
echo "file-roller hold" | sudo dpkg --set-selections
also lock it in synaptic

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

Title:
  Extremly poor compression for .tar.bz2

Status in “file-roller” package in Ubuntu:
  Confirmed

Bug description:
  I am running Xubuntu 12.10 beta 64bit
  i created a archive for a folder 
  the contents are ~1.5kb the archive is over 10kb
  i compressed the same files on my Ubuntu 10.04 install and the archive is 851 
bytes

  archive was created from the create archive option in the right click
  menu in the file browser (thunar)

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

[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 

  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 378783] Re: xdg-open *.desktop opens text editor

[pqwoerituytrueiwoq]

xdg-open works as expected in Xubuntu 14.04

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

Title:
  xdg-open *.desktop opens text editor

Status in GVFS:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: xdg-utils

  In order to reproduce it execute "xdg-open *.desktop" (choose any
  .desktop file, e.g. one from /usr/share/applications). Actually your
  favorite text editor will open the file. Expected result: It'll be
  executed.

  Because of this bug, desktop entries with the new "#!/usr/bin/env xdg-
  open" shebang feature were opened in the text editor when executed
  from command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/378783/+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 1222162] [NEW] scanimage crashed with SIGSEGV in _int_malloc()

[pqwoerituytrueiwoq]

Public bug reported:

Not a issue in 13.04
Also 10.0.0.50 is running 13.04
This does not have a 100% reproduction rate, sometimes it hangs indefinitely 
and some times it works
Terminal output, last 6 lines matter, the rest proves it should work
www-data@127.0.0.1:/home/www-data/PHP-Scanner-Server$ scanimage -f 
"{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
{"ID":0,"INUSE":0,"DEVICE":"net:10.0.0.50:plustek:libusb:004:002","NAME":"UMAX 
3400 flatbed 
scanner"},{"ID":1,"INUSE":0,"DEVICE":"net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5","NAME":"Hewlett-Packard
 Deskjet_F4400_series all-in-one"},
www-data@127.0.0.1:/home/www-data/PHP-Scanner-Server$ scanimage --help -d 
'net:10.0.0.50:plustek:libusb:004:002'
Usage: scanimage [OPTION]...

Start image acquisition on a scanner device and write image data to
standard output.

Parameters are separated by a blank from single-character options (e.g.
-d epson) and by a "=" from multi-character options (e.g. --device-name=epson).
-d, --device-name=DEVICE   use a given scanner device (e.g. hp:/dev/scanner)
--format=pnm|tiff  file format of output file
-i, --icc-profile=PROFILE  include this ICC profile into TIFF file
-L, --list-devices show available scanner devices
-f, --formatted-device-list=FORMAT similar to -L, but the FORMAT of the output
   can be specified: %d (device name), %v (vendor),
   %m (model), %t (type), %i (index number), and
   %n (newline)
-b, --batch[=FORMAT]   working in batch mode, FORMAT is `out%d.pnm' or
   `out%d.tif' by default depending on --format
--batch-start=#page number to start naming files with
--batch-count=#how many pages to scan in batch mode
--batch-increment=#increase page number in filename by #
--batch-double increment page number by two, same as
   --batch-increment=2
--batch-prompt ask for pressing a key before scanning a page
--accept-md5-only  only accept authorization requests using md5
-p, --progress print progress messages
-n, --dont-scanonly set options, don't actually scan
-T, --test test backend thoroughly
-A, --all-options  list all available backend options
-h, --help display this help message and exit
-v, --verbose  give even more status messages
-B, --buffer-size=#change input buffer size (in kB, default 32)
-V, --version  print version information

Options specific to device `net:10.0.0.50:plustek:libusb:004:002':
  Scan Mode:
--mode Lineart|Gray|Color [Color]
Selects the scan mode (e.g., lineart, monochrome, or color).
--depth 8|14bit [8]
Number of bits per sample, typical values are 1 for "line-art" and 8
for multibit scans.
--source Normal|Transparency|Negative [inactive]
Selects the scan source (such as a document-feeder).
--resolution 50..1200dpi [50]
Sets the resolution of the scanned image.
--preview[=(yes|no)] [no]
Request a preview-quality scan.
  Geometry:
-l 0..215mm [0]
Top-left x position of scan area.
-t 0..297mm [0]
Top-left y position of scan area.
-x 0..215mm [103]
Width of scan-area.
-y 0..297mm [76.21]
Height of scan-area.
  Enhancement:
--brightness -100..100% (in steps of 1) [0]
Controls the brightness of the acquired image.
--contrast -100..100% (in steps of 1) [0]
Controls the contrast of the acquired image.
--custom-gamma[=(yes|no)] [no]
Determines whether a builtin or a custom gamma-table should be used.
--gamma-table 0..255,... [inactive]
Gamma-correction table.  In color mode this option equally affects the
red, green, and blue channels simultaneously (i.e., it is an intensity
gamma table).
--red-gamma-table 0..255,... [inactive]
Gamma-correction table for the red band.
--green-gamma-table 0..255,... [inactive]
Gamma-correction table for the green band.
--blue-gamma-table 0..255,... [inactive]
Gamma-correction table for the blue band.
  Device-Settings:
--lamp-switch[=(yes|no)] [no]
Manually switching the lamp(s).
--lampoff-time 0..999 (in steps of 1) [300]
Lampoff-time in seconds.
--lamp-off-at-exit[=(yes|no)] [yes]
Turn off lamp when program exits
--warmup-time -1..999 (in steps of 1) [-1]
Warmup-time in seconds.
--lamp-off-during-dcal[=(yes|no)] [inactive]
Always switches lamp off when doing dark calibration.
--calibration-cache[=(yes|no)] [no]
Enables or disables calibration data cache.
--speedup-switch[=(yes|no)] [yes]
Enables or disables speeding up sensor movement.
--calibrate [inactive]
Performs calibration
  Analog frontend:
--red-gai

[Desktop-packages] [Bug 1224764] [NEW] scanimage crashed with SIGSEGV in memchr()

[pqwoerituytrueiwoq]

Public bug reported:

clearly still  unstable

chad@chad-VirtualBox:~$ scanimage -L
device `net:10.0.0.50:plustek:libusb:004:002' is a UMAX 3400 flatbed scanner
device `net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5' is 
a Hewlett-Packard Deskjet_F4400_series all-in-one
chad@chad-VirtualBox:~$ scanimage -L
device `net:10.0.0.50:plustek:libusb:004:002' is a UMAX 3400 flatbed scanner
device `net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5' is 
a Hewlett-Packard Deskjet_F4400_series all-in-one
chad@chad-VirtualBox:~$ scanimage -f 
"{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
Segmentation fault (core dumped)
chad@chad-VirtualBox:~$ scanimage -f 
"{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
{"ID":0,"INUSE":0,"DEVICE":"net:10.0.0.50:plustek:libusb:004:002","NAME":"UMAX 
3400 flatbed 
scanner"},{"ID":1,"INUSE":0,"DEVICE":"net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5","NAME":"Hewlett-Packard
 Deskjet_F4400_series all-in-one"},chad@chad-VirtualBox:~$ ^C
chad@chad-VirtualBox:~$ scanimage -f 
"{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
Segmentation fault (core dumped)
chad@chad-VirtualBox:~$

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: sane-utils 1.0.23-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
Date: Thu Sep 12 22:56:32 2013
ExecutablePath: /usr/bin/scanimage
InstallationDate: Installed on 2013-07-27 (47 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130727)
MarkForUpload: True
ProcCmdline: scanimage -f {"ID":%i,"INUSE":0,"DEVICE":"%d","NAME":"%v\ %m\ %t"},
SegvAnalysis:
 Segfault happened at: 0x7f462dca8e20 : movdqa (%rdi),%xmm0
 PC (0x7f462dca8e20) ok
 source "(%rdi)" (0x7f462e40a000) not located in a known VMA region (needed 
readable region)!
 destination "%xmm0" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: sane-backends
StacktraceTop:
 memchr () at ../sysdeps/x86_64/memchr.S:88
 __GI__IO_getline_info (fp=fp@entry=0x688950, buf=buf@entry=0x7f462179d100 
"z3950", n=n@entry=1023, delim=delim@entry=10, 
extract_delim=extract_delim@entry=1, eof=eof@entry=0x0) at iogetline.c:94
 __GI__IO_getline (fp=fp@entry=0x688950, buf=buf@entry=0x7f462179d100 "z3950", 
n=n@entry=1023, delim=delim@entry=10, extract_delim=extract_delim@entry=1) at 
iogetline.c:38
 __GI_fgets_unlocked (buf=buf@entry=0x7f462179d100 "z3950", n=n@entry=1024, 
fp=0x688950) at iofgets_u.c:55
 internal_getent (result=result@entry=0x7f462179d530, 
buffer=buffer@entry=0x7f462179d100 "z3950", buflen=buflen@entry=1024, 
errnop=errnop@entry=0x7f462179e680) at nss_files/files-XXX.c:207
Title: scanimage crashed with SIGSEGV in memchr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace saucy

** Information type changed from Private to Public

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

Title:
  scanimage crashed with SIGSEGV in memchr()

Status in “sane-backends” package in Ubuntu:
  New

Bug description:
  clearly still  unstable

  chad@chad-VirtualBox:~$ scanimage -L
  device `net:10.0.0.50:plustek:libusb:004:002' is a UMAX 3400 flatbed scanner
  device `net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5' 
is a Hewlett-Packard Deskjet_F4400_series all-in-one
  chad@chad-VirtualBox:~$ scanimage -L
  device `net:10.0.0.50:plustek:libusb:004:002' is a UMAX 3400 flatbed scanner
  device `net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5' 
is a Hewlett-Packard Deskjet_F4400_series all-in-one
  chad@chad-VirtualBox:~$ scanimage -f 
"{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
  Segmentation fault (core dumped)
  chad@chad-VirtualBox:~$ scanimage -f 
"{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
  
{"ID":0,"INUSE":0,"DEVICE":"net:10.0.0.50:plustek:libusb:004:002","NAME":"UMAX 
3400 flatbed 
scanner"},{"ID":1,"INUSE":0,"DEVICE":"net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5","NAME":"Hewlett-Packard
 Deskjet_F4400_series all-in-one"},chad@chad-VirtualBox:~$ ^C
  chad@chad-VirtualBox:~$ scanimage -f 
"{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
  Segmentation fault (core dumped)
  chad@chad-VirtualBox:~$

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: sane-utils 1.0.23-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  Date: Thu Sep 12 22:56:32 2013

[Desktop-packages] [Bug 1225027] [NEW] scanimage crashed with SIGSEGV in __libc_message()

[pqwoerituytrueiwoq]

Public bug reported:

Yet another crash in a different section
This crash occurred yesterday, all i did was print out a list of devices and 
try to get help data output from the device

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: sane-utils 1.0.23-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
AssertionMessage: *** Error in `scanimage': double free or corruption (top): 
0x02058f50 ***
CrashCounter: 1
Date: Thu Sep 12 22:48:40 2013
ExecutablePath: /usr/bin/scanimage
InstallationDate: Installed on 2013-07-27 (47 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130727)
MarkForUpload: True
ProcCmdline: scanimage --help -d net:10.0.0.50:plustek:libusb:004:002
ProcEnviron:
 PATH=(custom, no user)
 LANG=C
Signal: 11
SourcePackage: sane-backends
StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f502e96a6a0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
 malloc_printerr (ptr=0x2058f50, str=0x7f502e96a7b0 "double free or corruption 
(top)", action=3) at malloc.c:4902
 _int_free (av=, p=0x2058f40, have_lock=0) at malloc.c:3758
 _IO_new_fclose (fp=0x2058f50) at iofclose.c:85
 internal_endent () at nss_files/files-XXX.c:161
Title: scanimage crashed with SIGSEGV in __libc_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: lp

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace saucy

** Information type changed from Private to Public

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

Title:
  scanimage crashed with SIGSEGV in __libc_message()

Status in “sane-backends” package in Ubuntu:
  New

Bug description:
  Yet another crash in a different section
  This crash occurred yesterday, all i did was print out a list of devices and 
try to get help data output from the device

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: sane-utils 1.0.23-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  AssertionMessage: *** Error in `scanimage': double free or corruption (top): 
0x02058f50 ***
  CrashCounter: 1
  Date: Thu Sep 12 22:48:40 2013
  ExecutablePath: /usr/bin/scanimage
  InstallationDate: Installed on 2013-07-27 (47 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130727)
  MarkForUpload: True
  ProcCmdline: scanimage --help -d net:10.0.0.50:plustek:libusb:004:002
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C
  Signal: 11
  SourcePackage: sane-backends
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f502e96a6a0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
   malloc_printerr (ptr=0x2058f50, str=0x7f502e96a7b0 "double free or 
corruption (top)", action=3) at malloc.c:4902
   _int_free (av=, p=0x2058f40, have_lock=0) at malloc.c:3758
   _IO_new_fclose (fp=0x2058f50) at iofclose.c:85
   internal_endent () at nss_files/files-XXX.c:161
  Title: scanimage crashed with SIGSEGV in __libc_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: lp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1225027/+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 1168963] [NEW] Default benchmarking options

[pqwoerituytrueiwoq]

Public bug reported:

This bug is a opinion

When running a benchmark the write option should be opt-in for the sake of SSD, 
by accident i just wrote several hundred MB to my drive, it wasted the amount 
of space for a fresh install
writing to a ssd just wears them out, that should be noted next to the option

at the very least it should remember that it unchecked it last time and
not have it checked the next time

it is nice to see you can write benchmark a drive without deleting
everything, the data looks fine in the file manager, i hope i can still
boot

i whet through a week of getting my setup script just right to write a
little as possible when i installed this drive, just to waste a huge
amount of my write limit

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: gnome-disk-utility 3.6.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
Uname: Linux 3.8.0-17-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CasperVersion: 1.330
Date: Sun Apr 14 20:40:52 2013
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130414)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-disk-utility
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug raring

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

Title:
  Default benchmarking options

Status in “gnome-disk-utility” package in Ubuntu:
  New

Bug description:
  This bug is a opinion

  When running a benchmark the write option should be opt-in for the sake of 
SSD, by accident i just wrote several hundred MB to my drive, it wasted the 
amount of space for a fresh install
  writing to a ssd just wears them out, that should be noted next to the option

  at the very least it should remember that it unchecked it last time
  and not have it checked the next time

  it is nice to see you can write benchmark a drive without deleting
  everything, the data looks fine in the file manager, i hope i can
  still boot

  i whet through a week of getting my setup script just right to write a
  little as possible when i installed this drive, just to waste a huge
  amount of my write limit

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-disk-utility 3.6.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CasperVersion: 1.330
  Date: Sun Apr 14 20:40:52 2013
  LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130414)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1168963/+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 1264734] [NEW] cant uninstall, missing dependancy

[pqwoerituytrueiwoq]

Public bug reported:

the uninstall script requires that dpkg-dev be installed for the dpkg-
architecture command

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-prime 0.5.2
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.7-0ubuntu3
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Dec 28 14:43:23 2013
InstallationDate: Installed on 2013-12-27 (0 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131223)
SourcePackage: nvidia-prime
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-prime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  cant uninstall, missing dependancy

Status in “nvidia-prime” package in Ubuntu:
  New

Bug description:
  the uninstall script requires that dpkg-dev be installed for the dpkg-
  architecture command

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.5.2
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Dec 28 14:43:23 2013
  InstallationDate: Installed on 2013-12-27 (0 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131223)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1264734/+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 1087520] Re: Zenity windows get TOO HIGH when text contains many words

[pqwoerituytrueiwoq]

Confirmed on Xubuntu 14.04
can this get fixed already?

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

Title:
  Zenity windows get TOO HIGH when text contains many words

Status in Zenity:
  In Progress
Status in “zenity” package in Ubuntu:
  Confirmed

Bug description:
  On 11.10, 12.04, and 12.10:

  --info , --warning , --error windows get higher for each word which is added 
to
  the text.
  Seems like useless blank lines are added below the text.

  This is a big usability issue for applications using Zenity.

  Remark: with --error, the bug is 2x more important than with --info ,
  --warning

  HOW TO REPRODUCE:
  zenity --info --text='A b c d e f g h i j k l m n o p q r s t u v w x y z'
  zenity --warning --text='A b c d e f g h i j k l m n o p q r s t u v w x y z'
  zenity --error --text='A b c d e f g h i j k l m n o p q r s t u v w x y z'
  zenity --error --text='A-b-c-d-e-f-g-h-i-j-k-l-m-n-o-p-q-r-s-t-u-v-w-x-y-z'

  Examples which DON'T have the bug:
  zenity --question --text='A b c d e f g h i j k l m n o p q r s t u v w x y z'
  zenity --error --text='A,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z'

To manage notifications about this bug go to:
https://bugs.launchpad.net/zenity/+bug/1087520/+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 1098955] Re: SNA on Intel B970 and hedgewars

[pqwoerituytrueiwoq]

yes, i did yesterday using the daily iso (xubuntu 64bit  2013-03-03)
i used the copy of hedgewars in the quantal detdeb mirror since it was a newer 
version
it also shows up if you try to run the heaven 3.0 benchmark
i even saw a small distortion on some input boxes in firefox, the page was on 
my router that is running tomato firmware

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

Title:
  SNA on Intel B970 and hedgewars

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

Bug description:
  found issue when using hedgewars with SNA enabled, i have reproduced this 
with the 3.7 and 3.6 kernels
  using xubuntu, no compiz just xfwm4, i have the xubuntu 4.12 ppa enabled

  nice to see pixel shaders work now :)

  xorg.conf contents:
  Section "Device"
 Identifier  "Intel Graphics"
 Driver  "intel"
 Option  "AccelMethod"  "sna"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  Uname: Linux 3.8.0-030800rc3-generic x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Sat Jan 12 14:28:18 2013
  InstallationDate: Installed on 2012-09-29 (105 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
  MarkForUpload: True
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1098955/+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 1098955] Re: SNA on Intel B970 and hedgewars

[pqwoerituytrueiwoq]

here are some screenshots
http://ubuntuforums.org/showthread.php?p=12490395#post12490395

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

Title:
  SNA on Intel B970 and hedgewars

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

Bug description:
  found issue when using hedgewars with SNA enabled, i have reproduced this 
with the 3.7 and 3.6 kernels
  using xubuntu, no compiz just xfwm4, i have the xubuntu 4.12 ppa enabled

  nice to see pixel shaders work now :)

  xorg.conf contents:
  Section "Device"
 Identifier  "Intel Graphics"
 Driver  "intel"
 Option  "AccelMethod"  "sna"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  Uname: Linux 3.8.0-030800rc3-generic x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Sat Jan 12 14:28:18 2013
  InstallationDate: Installed on 2012-09-29 (105 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
  MarkForUpload: True
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1098955/+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 1064117] Re: Extremly poor compression for .tar.bz2

[pqwoerituytrueiwoq]

Also affects  file-roller 3.6.3-1ubuntu3 in raring

** Tags added: file-roller quantal raring regression

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

Title:
  Extremly poor compression for .tar.bz2

Status in “file-roller” package in Ubuntu:
  Confirmed

Bug description:
  I am running Xubuntu 12.10 beta 64bit
  i created a archive for a folder 
  the contents are ~1.5kb the archive is over 10kb
  i compressed the same files on my Ubuntu 10.04 install and the archive is 851 
bytes

  archive was created from the create archive option in the right click
  menu in the file browser (thunar)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1064117/+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 1064117] Re: Extremly poor compression for .tar.bz2

[pqwoerituytrueiwoq]

Fixed up stream:
https://bugzilla.gnome.org/show_bug.cgi?id=695672

** Bug watch added: GNOME Bug Tracker #695672
   https://bugzilla.gnome.org/show_bug.cgi?id=695672

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

Title:
  Extremly poor compression for .tar.bz2

Status in “file-roller” package in Ubuntu:
  Confirmed

Bug description:
  I am running Xubuntu 12.10 beta 64bit
  i created a archive for a folder 
  the contents are ~1.5kb the archive is over 10kb
  i compressed the same files on my Ubuntu 10.04 install and the archive is 851 
bytes

  archive was created from the create archive option in the right click
  menu in the file browser (thunar)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1064117/+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 850840] Re: file-roller crashed with SIGSEGV in g_simple_async_result_complete()

[pqwoerituytrueiwoq]

Occured while extracting the linux kernel from a .tar.xz file using the
'extract to' option in thunar

~$ apt-cache policy file-roller thunar tar
file-roller:
  Installed: 3.6.3-1ubuntu4
  Candidate: 3.6.3-1ubuntu4
  Version table:
 *** 3.6.3-1ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
100 /var/lib/dpkg/status
thunar:
  Installed: 1.6.2-0ubuntu1
  Candidate: 1.6.2-0ubuntu1
  Version table:
 *** 1.6.2-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages
100 /var/lib/dpkg/status
tar:
  Installed: 1.26+dfsg-0.1ubuntu1
  Candidate: 1.26+dfsg-0.1ubuntu1
  Version table:
 *** 1.26+dfsg-0.1ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  file-roller crashed with SIGSEGV in g_simple_async_result_complete()

Status in File Roller:
  New
Status in “file-roller” package in Ubuntu:
  Confirmed

Bug description:
  I have this crash just after the startup!

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: file-roller 3.1.91-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: i386
  Date: Thu Sep 15 09:09:35 2011
  ExecutablePath: /usr/bin/file-roller
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcCmdline: file-roller /home/username/development/Qt\ 
development/QOgre1.0.0.0-build-desktop/meshes/SdkTrays.zip
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x8d13e2:  mov%eax,0x24(%edi)
   PC (0x008d13e2) ok
   source "%eax" ok
   destination "0x24(%edi)" (0xaace) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   ?? () from /usr/lib/libgtk-3.so.0
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/libgtk-3.so.0
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: file-roller crashed with SIGSEGV in g_simple_async_result_complete()
  UpgradeStatus: Upgraded to oneiric on 2011-09-14 (1 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/850840/+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 1042506] Re: Info box gets too tall too fast

[pqwoerituytrueiwoq]

** Attachment added: "Screenshot of issue (zoom out compiz expo)"
   
https://bugs.launchpad.net/bugs/1042506/+attachment/3279849/+files/Screenshot%20-%2008272012%20-%2009%3A55%3A26%20PM.png

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

Title:
  Info box gets too tall too fast

Status in “zenity” package in Ubuntu:
  New

Bug description:
  ~$ zenity --version
  3.4.0
  ~$ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=12.04
  DISTRIB_CODENAME=precise
  DISTRIB_DESCRIPTION="Ubuntu 12.04.1 LTS"

  From what I can tell it appears to be this bug:
  https://bugzilla.redhat.com/show_bug.cgi?id=754431

  Reproduce:
  zenity --title "Fortune" --info --text "`fortune`"

  You can gradually wach it get bigger with this
  a="_";i=1;while [ true ];do zenity --info --title "$i" --text 
"$a";i=$(($i+2));a="$a _";done

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1042506/+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 1042506] [NEW] Info box gets too tall too fast

[pqwoerituytrueiwoq]

Public bug reported:

~$ zenity --version
3.4.0
~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.1 LTS"

>From what I can tell it appears to be this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=754431

Reproduce:
zenity --title "Fortune" --info --text "`fortune`"

You can gradually wach it get bigger with this
a="_";i=1;while [ true ];do zenity --info --title "$i" --text 
"$a";i=$(($i+2));a="$a _";done

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

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

Title:
  Info box gets too tall too fast

Status in “zenity” package in Ubuntu:
  New

Bug description:
  ~$ zenity --version
  3.4.0
  ~$ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=12.04
  DISTRIB_CODENAME=precise
  DISTRIB_DESCRIPTION="Ubuntu 12.04.1 LTS"

  From what I can tell it appears to be this bug:
  https://bugzilla.redhat.com/show_bug.cgi?id=754431

  Reproduce:
  zenity --title "Fortune" --info --text "`fortune`"

  You can gradually wach it get bigger with this
  a="_";i=1;while [ true ];do zenity --info --title "$i" --text 
"$a";i=$(($i+2));a="$a _";done

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1042506/+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 270206] Re: Rhythmbox should never start minimised to tray

[pqwoerituytrueiwoq]

That was a feature not a bug and a very useful one especially now that 
rhythmbox-client --play will open and start the player
which i had been using a script for on lucid that opens the player waits for it 
to open then tells it to play till it does
now i have to close the window every time i login 
the --hide option on rhythmbox-client does nothing nor does any option in the 
status plugin to re-enable it work
i have tried using devils pie on it but it minimizes it to the window list
Rhythmbox 0.13.3
Ubuntu - natty

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

Title:
  Rhythmbox should never start minimised to tray

Status in One Hundred Paper Cuts:
  Fix Released
Status in The Rhythmbox Music Management Application:
  Fix Released
Status in “rhythmbox” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rhythmbox

  I have noticed that RB remembers whether it was minimised to tray when
  it closed, and starts in the same state. Some users might find that
  confusing, however. My mother does actually, sometimes she opens RB to
  listen to her music and she doesn't realise that small white square on
  the notification area, so she thinks the program didn't start
  properly.

  I think RB should NEVER start minimised to tray, unless it's specified
  through a command option.

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